CRM and pipeline
Win the work. Keep the context.
Contacts, companies and deals sit beside delivery, so a won deal becomes a project with its budget attached.

One company. Its people. Every deal it brings.
A contact is a person. A company is the organization you work with. A deal is one opportunity, with its own value, stage and next decision.
Keep them separate and a returning client never means rebuilding the relationship. The second engagement lands on the same company, with the same people.
Six stages. Agree what each one means.
Lead, qualified, proposal, negotiation, won and lost. Use the board to see where deals pile up, then switch to the list to inspect them one by one.
The handoff
A won deal becomes a project.
Delivery starts with the client, the budget and the sales notes in one place, instead of a hallway conversation.
The company becomes the client
The new project takes the deal’s company as its client.
The value becomes the budget
The deal value carries over as the project budget.
You confirm the words
Check the project name and description before you convert.
Then set up delivery
Choose the billing model and client visibility, then add the delivery plan.
The deal keeps its history
Notes stay on the deal. The company and its people stay useful for the next piece of work.
People and dates come next
Conversion gives delivery a start. Owners, tasks and dates still need a plan.
A CRM habit your team will keep.
The useful CRM is the one the team updates after real conversations. Ask for less detail and the record survives between weekly meetings.
Record
Add the company and the people involved, with names and roles a teammate can follow.
Companies and contactsDefine
Create a deal for the specific engagement, with its value, owner and context.
DealMove
Agree the evidence each stage needs, and update the next action after every conversation.
PipelineConvert
Create the project, confirm its commercial setup and turn the notes into a brief.
Project
Clear about where the CRM stops.
What the CRM does
- Keeps contacts, companies, deals and sales activity in the workspace you deliver from.
- Runs six fixed stages, on a board or as a list.
- Converts a won deal into a project with its client and budget.
What it leaves to you
- Email sequences and deliverability. Those stay with your sending tool.
- Qualification. Budget, need, timing and fit are your team’s call.
- The delivery plan. Owners, dates and tasks come after conversion.
The details.
Everything above, in depth. Open what you need.
Separate the relationship from the opportunity
A contact is a person. A company is the organization you work with. A deal is a specific opportunity with its own value, stage, and next decision. Keeping those concepts distinct helps when the same company returns for a second engagement or when several people influence one purchase. You should not need to duplicate the entire relationship every time a new piece of work appears.
Use the deal record for the commercial conversation: what the client needs, the proposed scope, the current stage, and the activity that explains why the opportunity is there. A stage label only becomes useful when the team agrees what must be true before a deal moves forward. Proposal sent, negotiation, and won should represent observable events rather than optimism.
Make the pipeline review about the next action
A pipeline board helps the team see where opportunities are accumulating. A list supports closer inspection of individual records. The pipeline uses six fixed stages: lead, qualified, proposal, negotiation, won and lost. Agree what each one means in your agency and the action that moves a deal onward, so the board reflects real decisions rather than hopeful labels.
During the review, ask who owns the next step and whether the expected engagement still fits the agency. A large opportunity may be unattractive if the timing conflicts with delivery capacity or the scope is too uncertain to price responsibly. Connect the sales discussion to resource planning before making a delivery promise, while keeping the commercial record useful even if the deal does not close.
An illustrative handoff from discovery to delivery
Imagine a design studio discussing a $15,000 brand project with an existing company. Two contacts participate: a marketing lead who coordinates the work and a founder who approves the scope. The deal holds the opportunity and its notes, while the company and people remain useful relationship records for future work.
When the engagement is won, create a project from the deal. The new project takes the deal's company as its client and the deal value as its budget; you confirm the name and description. Then set the billing model and client visibility and add the delivery plan. The project owner has the agreed outputs, review responsibilities, and budget context in one place before assigning work.
| Sales evidence | Delivery interpretation | Check before kickoff |
|---|---|---|
| Approved scope | Sections and concrete tasks | Are exclusions documented? |
| Commercial amount | Project fee or budget basis | Does it match the agreement? |
| Client stakeholders | Review and communication plan | Who gives final approval? |
Build a CRM habit that stays maintainable
The most useful CRM is the one the team updates after real conversations. Avoid demanding so much administrative detail that the record is abandoned between weekly meetings.
Create the relationship records
Add the company and relevant contacts. Keep names and roles clear so another teammate can understand who is involved.
Define the opportunity
Create a deal for the specific engagement. Record the proposed value, the owner, and enough context to distinguish it from other work at the same company.
Use stages consistently
Agree the evidence required for each stage. Review stalled opportunities and update the next action after the conversation changes.
Review the won-deal conversion
Create the project, confirm its commercial setup, and turn the sales notes into a brief and an executable delivery plan.
Keep sales promises within delivery reality
Flowboard brings contacts, companies, opportunities, and sales activity into the same workspace as delivery. Once an opportunity is ready, use the CRM to give it a clear owner, next step, and path into project work.
Proposals, forms, and automations can extend the workflow. Keep each connection explicit: a form submission captures information, a proposal records a commercial offer, and an automation performs the actions you configure. Check the resulting record rather than assuming that every captured lead should become an active client project.
Find the next client
Catch companies asking for an agency, opening a location or rebuilding their site, with the proof attached.
Prepare the commercial offer
Use a proposal to present scope, pricing, and acceptance in a coherent client document.
Explore this workflow ↗Check delivery capacity
Compare a proposed start date with the team's planned weekly workload.
Explore this workflow ↗Questions
Before you import the first contact.
Can one company have more than one deal?
Treat each distinct engagement as its own opportunity while keeping the relationship connected to the company and contacts. This makes a new project, renewal discussion, or additional service understandable without treating it as an entirely new client relationship.
What happens when we win a deal?
The won-deal workflow can create a project from the opportunity. Review the resulting project name, description, client context, and commercial setup. Then add the actual delivery structure, owners, dates, and documents needed to begin work responsibly.
Should the pipeline include every inquiry?
Use a clear qualification policy. An inquiry may need more information before it represents a real commercial opportunity. The CRM can hold the record, but your team must decide whether the budget, need, timing, and service fit justify moving it through the pipeline.
How much information should sales hand to the project owner?
At minimum, make the agreed outcomes, scope boundaries, commercial amount, key contacts, and approval process understandable. The project owner should be able to identify unresolved questions before assigning delivery work. A long history is less valuable than a clear account of what was actually agreed.