The Agency & Consulting Pipeline: From Inquiry to a Delivery-Ready Client

The proposal is signed. Delivery opens the record and asks: “What exactly did we promise?”

That is where a sales pipeline needs a deliberate handoff.

For agencies and consultants, I recommend two linked records with different jobs: the deal records the commercial decision; onboarding prepares the team to deliver. Use a task, project, ticket or suitable record type for onboarding. Keep it out of revenue forecasts. Small teams can start with separate statuses and responsibilities in one system.

This is an illustrative design, not a claim about a completed client implementation.

1. Separate the sale from delivery readiness

A simple commercial route:

Inquiry → Discovery → Scope reviewed → Closed won. Add a separate decision-pending stage only if it needs different actions or reporting.

Define what Closed won means for your business. It may require an executed agreement and a specified payment condition. Document the rule instead of assuming a signature always means ready to start.

The linked onboarding route:

Brief accepted → Inputs ready → Kickoff ready → Delivery active. Handoff review happens before the first readiness milestone.

These stages answer different questions. Do not reopen a won deal merely because access is missing. Flag the onboarding blocker and assign it.

HubSpot recommends separate pipelines when the underlying processes need different stages, not simply because different teams are involved. Official guidance.

2. Transfer a useful brief, not every sales note

The receiving owner should find five things:

• Outcome: why the client bought and how completion will be judged.
• Scope: the approved version, exclusions and change-request route.
• People: client decision-maker, delivery owner and escalation contact.
• Inputs: required content, access status and dependencies.
• Next step: kickoff conditions, agreed checkpoint and accountable owner.

Salesforce’s handoff guidance includes customer goals, success measures, contacts and obstacles. My agency-specific additions are the versioned scope and readiness checks. Sales-to-customer-success handoff.

Link to an approved access-management process. Never put passwords in a CRM note or onboarding email.

3. Let delivery accept the handoff

Fictional example: a course creator buys a CRM migration. The agreement is complete, but the source-system access is still awaiting approval.

The deal can be won under your commercial policy. The brief remains under review until the receiving owner accepts it; Inputs ready waits for the authorized access and agreed migration inputs. Do not start a migration merely because the sales automation fired.

Use three explicit responses:

Accept when the brief is complete. Return with reason when information is missing. Hold when a known dependency prevents progress.

Each exception needs an owner and a next-review date. “Waiting” without either is not a usable handoff.

Automate the setup, verify the result

When a deal meets your won rule, create or link one onboarding record. Use a unique source-deal key and a supported upsert or duplicate-prevention rule. Verify repeated or simultaneous events create only one onboarding record. Notify the owner, then record acceptance separately from the notification.

Test a duplicate event, an incomplete brief and a delayed dependency with synthetic records. Confirm that none silently starts delivery or creates a second onboarding job.

Try this today: ask your delivery lead to explain one new client’s promised outcome using only the handoff brief. Any missing answer belongs in the process.

Book a discovery call to map your sales-to-onboarding handoff.

Documentation checked October 1, 2026. Tool support and commercial rules vary.