Pipeline, Proposals, and Follow-ups
You have lost deals because someone did not follow up. Leads have disappeared into inboxes. Proposals have gone unchased. The pipeline exists in someone's head, and when they are busy, deals go quiet.
This is a systems problem. When there is no single place to see what is in your pipeline, no rule for who follows up and when, and no alert when a deal goes quiet, things fall through. Memory and good intentions do not scale past about fifteen active opportunities per person.
The fix is a system that matches how you actually sell. Leads land in one place regardless of how they arrived. Each one gets routed to a person, tracked through stages with clear exit criteria, and flagged the moment it goes stale. Whether that means configuring HubSpot properly or building something from scratch in Laravel, we have been doing this since 2005 across professional services, B2B, and recurring revenue businesses.
When Sales Runs on Memory
Most small businesses start selling informally. Leads come in through email, phone calls, referrals, and the odd conference conversation. Someone makes a note. Someone else promises to follow up. The proposal goes out, and then nobody quite remembers whether it was chased.
Over time, these problems compound as the business grows. One person can keep 15 opportunities in their head. Three salespeople managing 50 opportunities each cannot. The point where manual tracking breaks is usually well before anyone admits it.
When the Founder Is the Sales System
The most common version of this problem is the founder who built the business on personal relationships and follow-through. They know every deal, every contact, every promise made. It works until it does not. Then they hire a salesperson, hand over a CRM login, and wonder why the close rate drops. The problem is rarely the person. It is that the process was never written down because it lived in the founder's head.
If three or four of these are true in your business, founder-led sales has already stopped scaling.
The fix starts with documenting the process that currently lives in the founder's instincts. Write down how leads get qualified, what stages they move through, what triggers follow-up, and what information transfers when a deal closes. Then test it in HubSpot or Pipedrive. If the team has to keep working around the tool, stop forcing it and build around the process instead.
What a Sales System Should Do
A sales system does not need to be complicated. It needs to do six things well, and it needs to match the way your team actually sells, not the way a generic CRM template assumes you sell.
-
Route every lead to one place Regardless of how it arrived: website form, phone call, referral, or event.
-
Qualify leads consistently So you know what deserves attention and what does not.
-
Track opportunities through defined stages With clear criteria for progression from one stage to the next.
-
Alert when things go stale Expected close dates pass, no activity for two weeks, deals stuck in the same stage too long.
-
Automate follow-up reminders Reminders fire automatically on day 3, 7, and 14 so nobody has to remember to chase a quiet proposal.
-
Show the pipeline at a glance Total value, stage distribution, what is on track, what needs attention.
If your stages, reminders, and handoffs fit inside HubSpot or Pipedrive, buy one and configure it properly. If your team needs custom approval steps, unusual deal rules, or handoffs those tools fight against, stop bending the process to the software. The build vs buy decision comes down to how far your sales process diverges from the standard CRM template.
Pipeline Stages for Different Business Models
In practice, there is no universal sales pipeline. A consultancy selling six-figure projects has a fundamentally different sales motion from an e-commerce company processing hundreds of small orders. The pipeline stages need to reflect this reality.
Professional Services
Professional services firms sell expertise. The buying cycle is longer, trust matters more, and the discovery process is a substantial part of the sale itself. The discovery-to-scoping transition is where most deals stall. If discovery calls are happening but scoping documents are not following within a week, the pipeline has a blockage.
Enquiry
Initial contact, source captured. Exit: first meeting booked.
Discovery
Understanding the problem, assessing fit. Exit: problem and budget confirmed.
Scoping
Defining the work, estimating effort. Exit: scope document accepted.
Proposal
Formal quote with scope and terms. Exit: proposal reviewed by decision-maker.
Negotiation
Terms being finalised. Exit: signed agreement or lost with reason.
In other words, each exit criterion is a verifiable fact, not a feeling. "Discovery complete" is vague. "Problem confirmed in writing and budget range discussed" is testable. Stages without exit criteria become opinion, and deals sit in them indefinitely.
Transactional Sales
Transactional sales move faster. The product or service is well-defined, pricing is relatively standard, and the decision cycle is shorter. According to the MIT Lead Response Management Study, leads contacted within five minutes are 21 times more likely to be qualified than those contacted after 30 minutes. For transactional sales, response time is often the most important metric.
Lead
Contact captured. Exit: responded within SLA.
Qualified
Fit confirmed, need established. Exit: quote requested.
Quote Sent
Awaiting response. Exit: accepted or declined.
Closed
Won or lost, reason captured.
Enterprise Sales
Enterprise sales involve multiple decision-makers, longer evaluation cycles, and procurement processes that exist independently of the buying decision. The critical difference is tracking who has influence over the decision. A deal can have an enthusiastic champion and still die in procurement. Qualification frameworks like BANT (Budget, Authority, Need, Timeline) give you four testable questions: does the budget exist, is your contact the decision-maker, is there a genuine business need, and is there a timeline driving urgency? MEDDIC adds layers for larger deals: metrics the buyer will use to measure success, the economic buyer (often different from the champion), the decision process, and identified pain. Both frameworks exist to test whether the conditions for a decision actually exist, not just whether the contact is enthusiastic.
Identified
Opportunity surfaced. Exit: champion confirmed.
Qualified
BANT/MEDDIC criteria met. Exit: access to decision-maker.
Evaluation
Technical and commercial review. Exit: shortlisted.
Proposal
Formal submission. Exit: verbal commitment or rejection.
Procurement
Legal, security, contracts. Exit: signed or dead.
Subscription and Recurring Revenue
For subscription businesses, the pipeline extends beyond the initial sale into activation and retention. The activation rate during trial is the leading indicator. If 100 people start a trial and only 12 activate core features, the conversion problem is likely upstream of the sales follow-up. Common causes include onboarding friction, product-market fit, or a mismatch between the sales promise and the actual experience.
Signup
Account created. Exit: trial started.
Activation
Core features used. Exit: activation threshold met.
Conversion
Trial to paid. Exit: payment processed.
Expansion
Upsell and seat growth. Exit: expansion deal closed.
Renewal
Retention. Exit: renewed or churned with reason.
What's Breaking Your Sales Pipeline?
Answer eight questions about how your business sells. The advisor will diagnose where your pipeline is likely leaking and recommend the system structure, follow-up rules, and metrics that fit your sales motion.
Lead Capture, Routing, and Qualification
Leads arrive through web forms, phone calls, email, referrals, and the occasional LinkedIn message. The system needs to put all of them in one place. Every lead gets three things recorded immediately: where it came from, when it arrived, and who owns it. If any of those three is missing, the lead is already at risk.
Response time matters: The MIT Lead Response Management Study found that leads contacted within five minutes are 21 times more likely to be qualified than those contacted after thirty minutes. Put first-response time on the weekly sales meeting sheet. Pick a hard target (15 minutes in working hours) and treat misses as process failures, not individual lapses.
Qualification Criteria
A price-check from a company you would never serve should not get the same attention as a buyer who matches your best clients and wants to move this quarter. Check two things first: are they the right kind of client (fit), and are they actually trying to buy (intent)?
Fit Signals
Company size matches your sweet spot. Industry you have experience in. Budget compatible with your typical project value. Geographic location relevant for delivery. Technical environment compatible with your approach.
Fit tells you whether this prospect is the right type of client.
Intent Signals
Specific problem described, not vague enquiry. Active buying process with a timeline. Decision-maker involved in the conversation. Compelling event driving urgency.
Intent tells you whether this prospect is genuinely buying, not just browsing.
Scoring these signals gives you a prioritisation framework, but the score alone is not enough. What matters is what happens next. Each quadrant needs a routing action, not just a label.
| Quadrant | Profile | Action |
|---|---|---|
| High fit, high intent | Right client, active buyer | Immediate personal follow-up. Assign to senior seller. Respond within hours. |
| High fit, low intent | Right client, not buying yet | Enter nurture sequence. Periodic value touches until intent signals appear. |
| Low fit, high intent | Wrong client, ready to buy | Investigate. Confirm fit is genuinely low before disqualifying. Sometimes the initial data is incomplete. |
| Low fit, low intent | Wrong client, not buying | Polite deflection or referral. Do not invest sales time. |
The discipline is in the routing, not the scoring. A qualification framework that scores leads but leaves the next step to individual judgement will produce the same inconsistency as having no framework at all.
Follow-Up and Stalled Deal Management
Follow-up is where most sales processes fail. The proposal goes out, the prospect goes quiet, and the salesperson moves on to the next opportunity. Systematic follow-up means the system sends the reminders, not you. Three days after a proposal, a check-in goes out. Seven days, another. You handle the relationship; the system handles the persistence.
Proposal tracking itself matters. Beyond whether the proposal was sent, the system should record when it was opened (if using a tool like PandaDoc or Proposify that provides read receipts), which sections the prospect spent time on, and whether it was forwarded internally. A proposal opened five times and forwarded to a new email address is a stronger signal than one opened once. When the proposal is built from structured discovery data rather than from scratch each time, it is faster to produce and more likely to reflect what the prospect actually said they need.
Automated Follow-Up Sequences
The system runs this sequence automatically. If the prospect responds at any point, the reminders pause. If they go quiet, the cadence continues until day 30.
Day 3
Brief check-in if no response
Day 7
Follow-up with additional insight
Day 14
Another touch, adding value
Day 21
Final check-in, offer to help
Day 30
Mark as stalled, request feedback
Stalled Deal Detection
Deals go stale for many reasons: the champion left, the budget was redirected, a competitor undercut on price. A healthy pipeline requires active detection of stalled deals.
Deal States: Beyond Open and Closed
Most pipelines treat deals as either open or closed. In practice, a deal that has been sitting at "proposal sent" for six weeks is not really open. It needs its own state so it does not pollute the active pipeline or distort your forecast. We use five states:
The critical transition is from Waiting to Stalled. A deal in Waiting has a follow-up date. A deal in Stalled has missed that date and received no response. The system should move deals to Stalled automatically when the follow-up deadline passes, making them visible for triage rather than leaving them to quietly age in the pipeline.
Once a quarter, put every open deal on one screen and ask three questions: who owns it, what is the next step, and when is it happening? If nobody can answer, move it to nurture or close it. Dead deals should not sit in the forecast pretending to be revenue.
Measuring What Matters
If the team can tell you how many calls they made last week but not their win rate or average sales cycle, the reporting is giving you motion instead of signal. You need both activity metrics and outcome metrics.
| Type | Examples | What It Tells You |
|---|---|---|
| Activity (leading) | Calls made, meetings booked, proposals submitted | What your sales team is doing |
| Outcome (lagging) | Win rate, average deal value, sales cycle length, revenue per salesperson | What is actually working |
As a rough guide, if your win rate drops below 25%, the problem is usually upstream: poor qualification, weak proposals, or misaligned pricing. If activity is high but outcomes are low, the team is busy but not effective.
Beyond overall win rate, the most valuable metric for pipeline management is conversion rate by stage. Tracking what percentage of deals move from one stage to the next reveals exactly where the pipeline leaks.
| Stage Transition | Typical Range | Signal if Low |
|---|---|---|
| Lead to qualified | 40-60% | Lead quality issue, targeting wrong audience |
| Qualified to proposal | 60-80% | Discovery not compelling, competition winning earlier |
| Proposal to close | 25-40% | Pricing, positioning, or proposal quality issue |
Win/Loss Tracking
Every closed opportunity, whether won or lost, should capture the reason. Won deals: what was the deciding factor? Lost deals: who did they choose and why? No-decision outcomes: why did they stop the process? Quarterly win/loss reviews are where the real patterns emerge, but only if the system captures reasons consistently. Without that data, you are guessing why you win and lose.
Forecasting and Pipeline Health
Sales forecasting for a growing business comes down to one question: what is your actual close rate, and how much pipeline do you need to hit the number? The foundation is pipeline value by stage, weighted by the probability of closing.
A simple weighted pipeline gives a more honest number. Five proposals worth a combined GBP 200,000 at a 30% historical close rate gives a weighted forecast of GBP 60,000. In practice, check whether one deal dominates the total. If a single GBP 120,000 opportunity accounts for 60% of the pipeline, your forecast depends almost entirely on that one decision. That is not a forecast; it is a bet.
Pipeline Coverage
According to Salesforce research, top-performing sales teams maintain 3x to 4x pipeline coverage against quota. This means total (unweighted) pipeline value, not the weighted forecast. If your quarterly target is GBP 150,000 and your overall win rate is 30%, you need roughly GBP 500,000 in raw pipeline to close GBP 150,000.
Below 3x: increase top-of-funnel activity. Above 5x: the pipeline may contain stale deals that need culling.
Velocity Metrics
Pipeline velocity combines four numbers: how many deals you have, what they are worth, what percentage you close, and how long they take. It is the single most useful diagnostic because it shows you which lever to pull. A team with a decent win rate but a 90-day cycle should not be chasing more leads; they should be shortening the cycle.
A slowdown in velocity is an early warning sign. Diagnose it before revenue drops.
Sales Velocity: The Formula That Connects Everything
Sales Velocity = (Number of Opportunities × Average Deal Value × Win Rate) ÷ Average Sales Cycle Length
Example: 25 opportunities × GBP 12,000 average deal × 30% win rate ÷ 60 days = GBP 1,500 per day. Shortening the cycle from 60 to 45 days lifts daily velocity to GBP 2,000 without a single extra lead.
Use the velocity number to decide where to intervene. If deals are stalling in legal review for six weeks, fix the approval process before paying for more lead generation. If deals close quickly but stay small, tighten qualification or raise the minimum project size. The number tells you which problem to solve first.
Which Metrics to Start With
Enterprise sales teams might track twenty or more metrics. A small team of one to five sellers can start with six. These give you enough data to diagnose problems without creating administrative overhead that kills adoption.
The Six Metrics for a Small Sales Team
1. Pipeline coverage ratio (3x to 4x target). 2. Conversion rate by stage (where deals drop out). 3. Average sales cycle length (how long deals take). 4. Win rate (what percentage you close). 5. Response time to new leads (how fast you engage). 6. Percentage of deals with a scheduled next step (pipeline discipline). Track these weekly. Everything else is a refinement you add later.
From Sale to Delivery
Most sales systems end when the deal closes. That is a mistake. The handoff to delivery is where promises get tested. If the delivery team walks into the first meeting without knowing what the salesperson committed to, the relationship starts with a credibility gap.
Most handoffs transfer the scope, the contacts, and the timeline. They lose the why. The delivery team does not know what the client actually cares about, what alternatives they rejected, or what promises the salesperson made that are not in the contract. That gap shows up in the first project meeting, when the client references a conversation the delivery lead has never heard of.
Decision Rationale
Why the client chose you. What they valued. What alternatives they considered and rejected. This is the single most useful piece of context for the delivery team, and the one most often missing.
Scope and Promises
What was agreed, what is in scope, what is explicitly out of scope. Include any commitments made during the sales process that are not in the formal contract.
Key Contacts and Sensitivities
Who the decision-makers are, their roles, communication preferences, and any interpersonal dynamics the delivery team should know about.
Risks and Constraints
Budget constraints not in the contract, timeline pressures, political dynamics, technical dependencies. Anything the delivery team needs to know before the first client meeting.
When a deal is marked won, three things should happen without anyone chasing them: delivery gets the handoff notes via client onboarding, finance gets the billing details from the deal terms, and the client gets the first onboarding email. Keep the original lead source on the customer record as well, so later you can see whether that referral partner or Google Ads campaign produced actual revenue. Upstream, marketing systems feed the pipeline with the leads that start this whole process.
Making the System Stick
The most common failure mode for sales systems is adoption. The technology works fine. The team just stops using it. A CRM that nobody uses is worse than a spreadsheet, because it creates the illusion of a system without the reality. We have seen more implementations fail from friction than from resistance.
The 60-second rule of thumb: If logging a new lead takes more than 60 seconds, adoption tends to collapse regardless of training quality. The fix is usually fewer required fields, not more training sessions. Start with the minimum data needed to route and qualify. Add fields later, when people are already using the system daily.
Adoption also requires ownership. Someone needs to be accountable for each part of the system. That includes stage definitions (sales lead), data hygiene (operations or admin), forecast accuracy (sales lead and finance together), and handoff completeness (sales and delivery jointly). When nobody owns the process, the tool decays within months.
Ultimately, the businesses that sustain CRM adoption are the ones where the system gives back more than it takes. If logging activity produces a pipeline view that helps the team sell better, adoption is self-reinforcing. If logging activity produces reports that only management reads, the team will find ways around it.
Build Your Sales System
If your process already fits an off-the-shelf CRM, we will tell you and help you configure it properly. If it does not, we build the stages, reminders, handoffs, and reporting around the way your team already sells. Our integration service also handles connecting your CRM to the rest of your operational stack so data flows without manual re-entry. The first call is simply to map the gaps.
Book a discovery call →