Verticals · Agencies & professional services
Pitches, campaigns, clients — the studio’s whole book in one place.
Pitches run as deal pipelines, campaigns carry the delivery work, and every client contact is one person across every brief, call, and invoice conversation.
Why one system
New business lives in a CRM, delivery lives in a project tool, and the retainer’s health lives in a month-end spreadsheet nobody trusts.
One system where the pitch, the campaign, and the client are the same story told once.
The objects you’d define
pitches
deal · contacts · attachments
Brief to win: the brand on one side, the agency on the other, a budget riding on it.
campaigns
workflow · tasks · attachments
The delivery engine — staged, assigned, and gated through review before anything ships.
clients
contacts · website · social
Brands and the people inside them, one directory across pitches and campaigns alike.
deliverables
tasks · attachments · activity
Owned, due, and versioned, attached to the campaign they belong to.
- Brief
- Concept
- Proposal
- Won
A pitches pipeline — agency ↔ brand — same deal primitive, your labels.
How it runs.
A pitch is a deal: the brief arrives, the concept develops, the proposal names a number, and the close is a win or a pass. The pipeline reports the book of new business at a glance.
Won pitches hand off to campaigns — same graph, no re-keying — where the delivery work is staged and gated through review.
The client’s people stay the same records throughout: the CMO who saw the pitch is the CMO who approves the campaign.
Nomi runs the Monday status report across every campaign, flags deliverables at risk, and logs the call notes where they belong.
Nothing here is an industry edition — it’s the same primitives, named by the people who run the business.