Where the selling time goes

Most sales teams do not lack leads. They lack the hours between leads, and those hours are being spent on admin.

  1. 01

    One event

    A new enquiry arrives through the website form or a shared sales inbox.

  2. 02

    Context

    Extract company, contact, need and timing from the message

  3. 03

    Interpretation

    Check the CRM for an existing account or previous conversations

  4. 04

    Rules

    Research the company's public footprint and likely operating context

  5. 05

    System action

    Score fit against agreed qualification criteria

  6. 06 · Human authority

    A person decides

    outside automated authority

  7. 07

    Outcome

    actioned, recorded, visible

Illustrative example · Inbound enquiry to qualified first call · not a client project, no result claimed

The problem

Where the selling time goes

A new enquiry arrives by email, web form or referral. Someone reads it, looks the company up, decides whether it is worth pursuing, creates the record in the CRM, and writes the first reply. Then the same person builds the quote from a spreadsheet, chases the approval, sends the proposal and sets a reminder to follow up. None of this is selling. All of it takes time.

As volume grows, the gaps show. Enquiries wait a day for a reply. Follow-ups are missed because the reminder was never set. The CRM shows what people remembered to type, not what actually happened. Pipeline reviews become a search for the truth rather than a conversation about it.

  • Enquiries answered late, or not at all, when the team is busy01
  • Company research repeated by hand before every first call02
  • Quotes assembled from spreadsheets and old proposals03
  • Follow-ups that depend on memory04
  • CRM records that are incomplete or out of date05
  • Pipeline reports that need explaining before they can be trusted06

The system response

What an intelligent sales workflow can do

  1. 1. Read and route every enquiry

    An intelligent workflow can read a new enquiry, extract the company, the need and the urgency, create a clean CRM record and route it to the right person within minutes.

  2. 2. Prepare the first call

    Before a conversation, a system can gather what is already known about the company, its systems and its likely problem, and put a short brief in front of the person taking the call.

  3. 3. Draft quotes from approved rules

    Pricing rules, product data and past proposals can be turned into a draft quote that a person reviews rather than a document a person builds.

  4. 4. Keep the CRM honest

    Meeting notes, emails and calendar activity can update the record automatically, so the pipeline reflects what happened rather than what was remembered.

  5. 5. Follow up on time

    A workflow can watch for silence, draft the appropriate follow-up and queue it for approval, so no opportunity goes quiet by accident.

Example workflows

Example workflows

These are illustrative examples of what can be built. They are not descriptions of client projects, and no outcomes are claimed.

Record · 01 · illustrative

Inbound enquiry to qualified first call

Trigger. A new enquiry arrives through the website form or a shared sales inbox.

  1. 01Extract company, contact, need and timing from the message
  2. 02Check the CRM for an existing account or previous conversations
  3. 03Research the company's public footprint and likely operating context
  4. 04Score fit against agreed qualification criteria
  5. 05Create or update the CRM record and draft a first reply
  6. 06Place the enquiry, brief and draft in the right person's queue

Human authority · A salesperson reviews the brief, edits the reply and decides whether to pursue the enquiry before anything is sent.

SYSTEMSCRM · shared inbox · website form · calendar
STEPS6 automated
DATAillustrative
HOLDa person decides

Record · 02 · illustrative

Quote assembly and approval

Trigger. A salesperson marks an opportunity as ready for a proposal.

  1. 01Pull the confirmed scope and quantities from the CRM record
  2. 02Apply current pricing rules, discounts and terms
  3. 03Assemble a draft proposal from approved content blocks
  4. 04Flag anything outside standard terms for review
  5. 05Route the draft for commercial approval where thresholds require it

Human authority · A sales manager approves any quote that falls outside standard pricing or terms, and the salesperson approves the final document before it goes to the customer.

SYSTEMSCRM · pricing spreadsheet or product catalogue · document generation · e-signature
STEPS5 automated
DATAillustrative
HOLDa person decides

Record · 03 · illustrative

Silent opportunity follow-up

Trigger. An open opportunity has had no activity for an agreed number of days.

  1. 01Identify the stage, the last contact and the reason for the pause
  2. 02Draft a follow-up appropriate to the stage and the history
  3. 03Queue the draft for the account owner
  4. 04Log the outcome and reschedule if there is still no response

Human authority · The account owner approves, edits or discards every draft before it is sent; nothing goes to a customer automatically.

SYSTEMSCRM · email · calendar
STEPS4 automated
DATAillustrative
HOLDa person decides

People decide what gets promised

Human authority · explicit thresholds, named owners

In sales, the decisions that matter are about commitment: what to offer, at what price, on what terms, and to whom. Those stay with people. The systems described here prepare, draft and remind. They do not send proposals, agree discounts or make promises on anyone's behalf.

Not every sales problem needs AI. A missed follow-up is often a rules problem, solved with a reminder that fires on time. An inaccurate pipeline is often an integration problem, solved by connecting the inbox and calendar to the CRM. We start from the workflow and choose the least complicated tool that fixes it.

Questions about this area

Will this work with the CRM we already use?

Usually, yes. Most CRMs expose an interface for reading and writing records, and the workflows above are designed to work with the system you have rather than replace it. Where a CRM has no usable interface, we say so early and look at practical alternatives.

Will customers be receiving messages written by a machine?

Not unless you decide they should. In the examples here, every outbound message is drafted for a person to review and send. Some businesses later choose to let routine acknowledgements go out automatically. That is a decision you make deliberately, not a default.

What if the real problem is just that follow-ups are being missed?

Then the answer is probably a well-designed reminder and a clean pipeline stage definition, not an AI agent. We would rather fix the process with a simple rule than build something clever that nobody needed.

How do we know the qualification is fair and consistent?

Qualification criteria are written down and agreed with you before anything is built. The system applies them consistently and shows its reasoning, so a salesperson can see why an enquiry was scored the way it was and override it when judgement says otherwise.

Where is capability hiding in your business?

Bring one workflow that costs your team more time than it should. We will tell you honestly whether AI, automation or a better system belongs there.