Build an agency CRM pipeline around discovery, not activity

An agency CRM pipeline is not a sales process. It is a row of labels until the team agrees what must be true before a deal moves forward.

That gap shows up in familiar ways: a proposal goes out before the agency understands the buyer’s problem, a founder’s promising call never reaches the CRM, or a salesperson marks a deal “hot” because the prospect was friendly. The fix is not more stages. It is a discovery routine tied to clear stage gates.

Tim Kilroy’s SalesOS is built around repeatable sales processes. Its Discovery Lab is one diagnostic tool agencies can bring into their discovery work. A CRM such as HubSpot or GoHighLevel can hold the opportunity record and the team’s process. Treat these as separate parts of the stack unless you have verified a specific integration. The working connection can be a disciplined handoff: use the diagnostic in the conversation, then record the useful findings in the CRM.

Start with the decision you need to make

Before changing fields or stages, decide what the pipeline should help the team answer. For most agencies, the useful question is not “How many calls did we have?” It is “Do we understand enough to decide whether to pursue this work, and what must happen next?”

Keep the first version small. A practical pipeline might use these stages: New inquiry, Qualified, Discovery scheduled, Discovery complete, Solution and decision, Closed won, and Closed lost. Adapt the labels to your sales motion. Avoid creating separate stages for every email, meeting or internal task. Those are activities, not meaningful changes in the buyer’s decision.

Make discovery the gate, not a calendar event

For each stage, write down the evidence required to move forward. “Qualified” should mean the agency has a plausible fit and a real business issue to explore. “Discovery scheduled” means a conversation is booked, not that the opportunity is understood. “Discovery complete” should mean the team can summarize the buyer’s situation and agree on a next step.

Build a short set of CRM fields around that summary. Include the buyer’s stated goal, the business problem behind it, the cost or consequence of leaving it unresolved, relevant constraints, the people involved in the decision, and the buyer’s timing. Add a field for the agreed next action and its owner. Use concise prompts rather than long forms that invite generic answers.

Use Discovery Lab as a companion to the discovery conversation, then put the relevant findings into the CRM record. Do not assume the tool fills CRM fields automatically. If the team has to transfer notes by hand, keep the summary brief and make one person responsible for doing it. A CRM field that nobody maintains is worse than no field at all.

Configure the stage gates

1. New inquiry: Record the source, contact and requested outcome. The next action is to decide whether to qualify, refer or close out the inquiry.
2. Qualified: Record why the agency may be a fit and what remains uncertain. Do not advance an opportunity just because a prospect has accepted a meeting.
3. Discovery scheduled: Add the meeting date and the questions the team needs answered. Use the diagnostic conversation to learn about the buyer’s business, priorities and limits.
4. Discovery complete: Capture the buyer’s goal, problem, constraints, decision participants and agreed next step. If those basics are missing, the deal is not ready for a proposal.
5. Solution and decision: Record what the proposed work is intended to change, who will decide, and when the buyer expects to decide. Keep the next action and owner visible.
6. Closed won or lost: Record the outcome and a short reason. Lost reasons should describe what happened, not blame the prospect.

HubSpot and GoHighLevel differ in their available configuration and workflow options. The process above does not depend on a particular feature: create the stages and fields your chosen CRM supports, then agree on who updates them and when. Do not build elaborate automation before the team follows the basic rules consistently.

Use the record to coach, not police

Review a few active opportunities each week. Ask whether the recorded evidence supports the current stage, whether the next step is specific, and what the team still needs to learn. If the notes say only “good call” or “send proposal,” the record is not doing its job.

This discipline matters before a founder hires a salesperson. A rep cannot inherit a process that exists only in the founder’s memory. The same principle sits behind the case for giving an agency’s first sales hire a process before a quota.

There is a trade-off. More required fields can improve handoffs, but they also add data-entry work and can slow small teams. Start with the few facts needed to decide fit and next steps. Add fields only when a recurring missed detail causes a real problem. A monthly review of closed deals can show whether the questions and gates are helping the team qualify better or simply generating paperwork.

For agencies that want help building a repeatable sales process, SalesOS is Tim Kilroy’s sales systems offering. It is one option for shaping the method; the CRM remains the team’s record of what happened and what comes next. The stack works when discovery changes the decision, and the CRM makes that decision legible to everyone involved.