Pipeline and field sales
Sales CRM built around your pipeline
Every CRM claims to be a sales CRM, and most of them model one pipeline that closes once. Businesses with field teams, several products or a quoting step need something specific, and that specificity is the whole build.
Stages that mean something
Most pipelines are named after feelings. Interested, warm, hot, nurturing. None of those can be verified, so different people move records at different moments and the conversion rate measures vocabulary rather than performance.
We define each stage by its exit criterion: the observable thing that must have happened for a record to leave it.
| Stage | Weak version | Exit criterion that works |
|---|---|---|
| Qualified | They seem serious | Budget, timeline and decision maker recorded |
| Quoted | We sent something | A quote document exists, with a value and a date |
| Negotiation | They are keen | The customer responded to the quote in writing |
| Won | Verbal yes | Signed acceptance or a paid deposit attached |
| Lost | Went quiet | A reason code set, and a re-contact date |
Two things follow. Conversion becomes comparable between people, and the stage becomes automatable, because a system can chase for a written response when it knows that is what moves the record.
Several pipelines, one system
The most common reason a mainstream tool stops fitting is that a business sells in two different ways at once and is forced to pick one shape.
A landscaping firm runs maintenance rounds and design projects. A manufacturer runs direct sales and a dealer channel. An agency runs new business and retainer renewals. These have different stages, different fields and different reports, and forcing them into one pipeline makes both sets of numbers useless.
A built system carries as many pipelines as you need, each with its own stages, required fields, automations and reports, over the same customers. Nobody sees the pipelines that are not theirs, and the board level view rolls them up without pretending they are the same thing.
If your team has ever said the pipeline is fine for the other side of the business, you are paying the two shapes tax. It usually shows up as a spreadsheet that the team trusts more than the CRM.
Field and outside sales
Field sales is where most CRMs quietly fail, because the interface was designed for a desk. Four things decide whether a field team uses a system at all.
- A phone view built for standing up. Large targets, few fields, works on one bar of signal, and does not lose a note when the connection drops on the way out of a basement.
- A map and a route, so the next call is chosen by geography rather than by scrolling a list.
- Quoting on site, from a price book, producing a document the customer can accept with one tap before the van leaves.
- Photos and signatures attached to the record from the phone camera, which is what turns a visit into evidence.
Get those four right and adoption stops being a management problem. Get them wrong and the field team keeps a private system, which is what they are doing today in most businesses that ask us to look.
Forecasting without the fiction
Weighted forecasts are usually theatre. A ten percent chance multiplied by a made up value is not information, and everybody in the room knows it.
What produces a usable forecast is duller. Stages with verifiable exit criteria, so the position of a deal is a fact. Days in stage, so stalled work is visible. Historical conversion by stage, computed from your own closed deals rather than from a default. And a close date that has to be changed deliberately, with the change recorded, so slipping is measurable.
With those four, a forecast is arithmetic on evidence instead of a survey of optimism. The reports we ship first are open value by stage, days in stage, win rate by person and source, and anything with no next action, which is the report that recovers the most money.
Sales enablement and collaboration inside the CRM
Sales enablement CRM features answer one question for a salesperson: what should I send or say next to this customer. The useful version is small: approved case studies, price sheets and proposal templates attached to the stage where they help, with usage tracked so marketing knows which materials actually appear in won deals.
Sales collaboration software covers the other half: deals that need more than one person. We build deal rooms on the record, where a salesperson, a solution engineer and a manager share notes, mentions and approvals for discounts, so nobody forwards an email chain to catch up.
For very small teams, free sales tracking software or a spreadsheet does the job until there is a second salesperson. After that, shared stages, ownership and one forecast matter more than any feature list.
What we build
What a sales build includes
The parts that decide whether a sales team uses the system, rather than the parts that demo well.
Pipelines per way you sell
Each with its own stages, fields, automations and reports, over one set of customers, rolled up for management without being flattened.
A phone view for outside
Few fields, large targets, offline tolerant, with photos, notes and signatures captured where the work happens.
Quoting from a price book
Documents that look right to the customer, accepted with one tap, and pushed to your accounting system on acceptance.
Reports that change behaviour
Open value by stage, days in stage, win rate by source and person, and everything with no next action.
Questions we get asked
What makes a good sales CRM?
Stages defined by verifiable exit criteria rather than by feelings, as few required fields as you can bear, a phone view that works outside, quoting that produces a document the customer respects, and one report showing everything with no owner or no next action. Features beyond those rarely change results.
Can one CRM handle several sales pipelines?
Yes, and it is one of the most common reasons businesses outgrow a mainstream tool. Each pipeline gets its own stages, required fields, automations and reports over the same customers, with management able to roll them up without pretending that maintenance work and project work are the same thing.
What do field sales teams need that office teams do not?
Four things: a phone interface designed for standing up, a map and route so the next call is chosen by geography, quoting on site from a price book with one tap acceptance, and photos and signatures attached from the camera. Without those, field teams keep a private system instead.
How should a sales forecast be calculated?
From evidence rather than optimism. Use stages with verifiable exit criteria so a deal's position is a fact, days in stage so stalled work is visible, conversion rates computed from your own closed deals, and close dates that must be changed deliberately so slippage is measurable rather than invisible.
Do we need a separate tool for quoting?
Usually not, and a separate tool is where quoting goes wrong, because the quote stops being attached to the record. Quoting from a price book inside the CRM keeps the value, the version history and the acceptance on the deal, and pushes only the accepted version to your accounting system.
Tell us how your business works. We will quote the CRM that fits it.
A 30 minute written brief from you, a fixed price and a two page scope from us within two business days. No call required, no obligation.