Layers 4–5 · Sales and retention

Stop losing the leads you already paid for

A CRM that reflects how you actually sell, a pipeline someone other than you can run, and follow-up that keeps chasing without anyone remembering to.

Get a growth system audit What gets built

Routing with a response standard, not a hope
Follow-up that runs whether or not someone remembers
A pipeline a new hire can operate

010203040506070809Routing · Follow-up · Sales

A lead you already paid to acquire and then never contacted a second time is direct waste. It carried the same acquisition cost as a lead that closed and produced no return.

This is often a system problem rather than a discipline problem. When follow-up depends on someone noticing an email, remembering a name, and finding a spare ten minutes, it becomes least reliable when the team is busiest.

Diagnostic checkpoints 4 through 6 cover what happens after an inquiry exists: getting it to the right person, keeping contact until there is a decision, and making the close repeatable by someone other than the founder.

Fit

Who this is for

A good fit

You have more inbound than you can personally chase.
One new customer is worth several thousand dollars, so a dropped lead is expensive.
Two or more people touch a deal before it closes.
A CRM exists but nobody trusts what is in it.

Not a fit

You have no inbound yet. Fix demand and conversion first.
You sell a low-value transactional product where speed of checkout matters more than follow-up.
You want an outbound cold-calling operation run for you.

Symptoms

You're in the right place if

Good inquiries sit unread for hours because nobody is formally responsible for the inbox.
You have a CRM, but it holds a partial and out-of-date picture, so nobody trusts it.
Follow-up happens for the leads someone happens to remember.
Some of your "lost" deals were contacted once and never again.
You are the only person who can run a deal from first call to signature.
Nobody can tell you how many open opportunities exist right now without checking three places.

Scope

What gets built

Response routing and standards

Assignment rules that send an inquiry to the right person with the context they need, an agreed first-response target, escalation when it is missed, and a fallback for when the assigned person is away. Measuring and improving first response is often a lower-cost intervention than buying more demand.

CRM architecture

A CRM configured around how you actually sell rather than how the vendor demo sells. Over-configuration is one avoidable failure mode: fields nobody fills in, pipeline stages that carry no decision, and automation that fires at the wrong moment. I build the minimum that stays accurate under pressure.

Pipeline design

Stages that describe real decisions rather than internal wishful thinking, entry and exit criteria for each, and a definition of qualified that you and I both agree on before anything gets built.

Consent-aware follow-up

Sequences that keep contact until there is a decision, with timing and personalisation that do not read as automated. Canadian commercial email and SMS carry CASL obligations around consent, sender identification, unsubscribe handling, and record-keeping. Those are built in, not bolted on.

Failure alerts and manual paths

When an integration breaks, a sequence stops firing, or a lead lands unassigned, someone finds out the same day. Every automated path keeps a manual override, because automation you cannot see is a liability rather than an asset.

A documented sales process

The qualification criteria, discovery questions, quoting steps, and handoffs written down. This gives a new salesperson an inspectable process instead of asking them to reconstruct the founder’s judgement by observation.

Process

How the work runs.

Measure what happens now

I time the response across a useful sample of recent inquiries, trace where each one went, and find the point they stop moving. The diagnosis uses timestamps rather than anyone’s recollection.

Design the pipeline

Stages that describe real decisions, entry and exit criteria for each, and a written definition of qualified that we agree on before anything is configured.

Build routing and follow-up

Assignment rules, a response standard, escalation, and consent-aware sequences. Every automated path gets a failure alert and a manual override.

Document and hand over

The qualification criteria, discovery questions, and handoffs written down, so a new hire inherits a process rather than an apprenticeship.

Outcomes

What changes, and what does not.

Every inquiry is assigned to a named person within a defined window, with escalation when that window is missed
Follow-up continues to a decision without anyone remembering to send it
The pipeline reflects reality closely enough that the team uses it instead of a spreadsheet
Someone other than the founder can run a deal end to end from written material
Lost deals are lost for a reason you can name, rather than to silence

Tooling

Tools this typically connects

CRM

HubSpot
Pipedrive
Close
GoHighLevel
Airtable
Notion

Scheduling

Calendly
Cal.com
Google Calendar
Microsoft 365

Messaging

Gmail / Google Workspace
Outlook
Transactional email providers
SMS gateways

Workflow

Zapier
Make
n8n
Direct API integrations

What this is not

It is not a CRM licence resale. You buy your own tools directly and own the accounts.
It is not a rip-and-replace by default. If your current CRM is adequate once it is fed correctly, I will tell you that and the project gets smaller.
It is not an outbound cold-email operation. This system works on demand that already exists.

The connected view

This sits inside the diagnostic path.

Checkpoint 9 feeds evidence back into checkpoint 1. That loop is the point.

Where this sits in the system

The checkpoints connected to this work.

Before this: an inquiry has to be captured in one place before it can be routed anywhere.

Lead generation systems

After this: follow-up you cannot measure cannot be improved, and repeated steps should stop being manual.

Business automation

Straight answers

Common questions.

If yours is more specific, put it in the audit form.

support@ariadne.fyi

Which CRM do you recommend?

The one your team will actually use, which usually means the simplest tool that supports the real pipeline. I have no reseller relationships and no incentive to push a platform. If the existing CRM can meet the requirements reliably, keeping it avoids migration cost and risk.

Will automated follow-up annoy our customers?

It can when it is written as generic marketing and sent on a machine schedule. The design should instead match the timing of the real sale, preserve a human handoff, and use messages a person actually approved. There is also a hard requirement here: under CASL, Canadian commercial messages need consent, sender identification, and working unsubscribe handling. That is built in.

How fast should we respond to a new inquiry?

The right standard depends on buyer urgency, channel, service, and staffing. Rather than quote a context-free benchmark, the audit measures your actual median first-response time, relates it to outcomes where the records allow, and sets a standard the team can reliably meet.

We tried a CRM before and it died. Why would this be different?

A CRM is likely to be abandoned when data entry is a separate chore from doing the work. The design should capture what it can automatically, ask for the smallest number of fields that keep it accurate, and make the pipeline view more useful than the spreadsheet it replaces.

Primary references

These first-party sources support the platform, policy, and regulatory statements on this page. Ariadne’s recommendations and planning heuristics are identified separately.

Your practical starting point

Find out whether follow-up is actually your constraint.

The audit measures current response time, traces where inquiries go, and tests whether checkpoints 4 to 6 contain the active constraint or whether the problem sits earlier in the path.

Request a growth system audit