When to use a sales pipeline template
Many agencies and consultancies win most of their work from referrals and a small number of conversations at a time. They do not need a large sales system, but they do need to know which deals are active, what was promised and when to follow up. Without that, leads go cold, proposals go unanswered and the delivery team learns about a new client on the day work starts.
Use this template as a lightweight pipeline on a kanban board: one task per deal, moving through the stages. It suits small service firms, founders who sell and teams who want sales and delivery visible in one place.
How the template is structured
- Lead. Capture the lead, research the company and make first contact quickly.
- Qualify. Hold a discovery call and decide whether the deal is worth pursuing.
- Proposal. Scope the work, price it by role and send a clear proposal.
- Negotiation. Handle questions and agree final terms in writing.
- Won or lost. Sign the contract, record the outcome and review lost deals monthly.
- Handover. Brief the delivery team, start onboarding and follow up after delivery.
The handover phase is what makes this template different from a standard pipeline: it connects the sale to the work.
How to use it in Worklenz
- Start from the built-in Sales & CRM template during setup, or create a project with these phases.
- Create one task per deal and move it across the kanban board as it progresses.
- Use labels such as Hot, Warm and Proposal sent to see where to focus.
- Set follow-up dates as due dates so no deal goes quiet.
- When a deal is won, start the client project from the client onboarding template.
Pricing proposals from real data
The most useful input for pricing a proposal is how long similar work took last time. If your team logs time with time tracking on the Pro plan and above, you can look at past projects by role and phase and price the next one on evidence rather than memory. On the Business plan, organisation and project rate cards help you price consistently across the team.
Example: a small agency’s pipeline
A five-person design agency gets most of its work from referrals. Each enquiry becomes a task in the Lead column. The founder calls within a day, qualifies on budget and timeline, and moves good fits to Proposal. Proposals are priced from time logged on similar past projects.
Won deals move to Handover, where the founder briefs the designer who will run the work and creates the client project. Each month, the founder reviews lost deals and notices that most were lost on timeline, not price, which leads to clearer availability in proposals.
Writing proposals that win
For service businesses, the proposal is often the first piece of work a client sees from you. Lead with the client’s problem and goals in their own words from the discovery call. Describe the outcome before the method. Break the work into clear phases with deliverables, so the client can see what they get and when. Show the price with what it includes and what it does not, and give a clear next step with a date.
Who should be involved
In small firms, the founder or a partner usually owns sales. Senior delivery people should help scope and price, so proposals are realistic. Whoever will run the work should join the handover. In larger teams, an account manager owns the pipeline and the delivery lead joins from the proposal stage.
Common pipeline mistakes
The first mistake is slow first contact, which loses warm leads. The second is pricing from memory instead of data. The third is a poor handover, where delivery does not know what sales promised. This template puts each of these on the board.
Tips for a healthier pipeline
- Reply within a day. Speed wins more service deals than polish.
- Qualify honestly. Saying no to poor fits saves time for good ones.
- Price from past projects. Logged time is the best estimate you have.
- Write down every promise. Delivery should never be surprised.
Related: the client onboarding template and the consulting engagement template.






