Why the handoff breaks
Most teams do not lose the client between the pitch and the kickoff. They lose the context. The agreement lives in a proposal document, the promises live in the account lead’s inbox, the amount lives on the pipeline, and the plan lives in a project tool that has never heard of the customer. If you are still deciding whether the sales record and the delivery record belong in one place, start with Do you need both a CRM and project management software? and come back here for the handoff itself.
Say an agency wins a brand refresh on a Tuesday. The account lead who sold it posts the good news in chat and turns to the next pitch. The producer who will run it opens the project tool on Thursday and finds an empty board. The client’s three must-haves, the two review rounds that were promised, and the launch date the client mentioned on the second call are in the deck and in someone’s notes. The producer rebuilds the brief from memory and a forwarded email, and the client is asked the same questions twice.
Or say a consultancy signs a three-month engagement with two workstreams. The partner who wrote the proposal knows which deliverable the client cares about and which one was added to win the work. The manager running the engagement inherits a start date and a fee. By the second Friday status, the client is asking about the deliverable nobody on the delivery side knew was the point, and the follow-on conversation at month three starts from an apology rather than from the record of what was delivered.
The same information gets recreated at every stage: once when selling, once when onboarding, once during delivery, and once more at renewal, when someone asks what was promised the first time. Each recreation loses a detail, and the lost detail is usually the one the client remembers. The account lead who sold the work and the producer who runs it are reading different pages, so neither of them can tell when the other one is wrong.
The person who holds the whole story becomes the human status API. The owner or the operations lead spends the day answering what is happening, who owns it, and what is stuck, because the record cannot. That arrangement works for three clients. It strains at twelve, and it stops entirely the week that person is away.
The fix is not a longer kickoff template or another meeting. It is a record the account lead and the producer read from the same page: the customer, the deal that was won, the project that came from it, and the first piece of work with an owner. This is the handoff that agencies and consultancies run most often, one with a pitch and an SOW, the other with a proposal and an engagement. The checklist below is what the record has to contain. The sections after it show how Scoped carries it across and how operations picks it up without a meeting.
Eight things delivery needs to know
Review these with the person who sold the work and the person responsible for delivery. Mark each item when it has an answer, then copy the agreed details into the project record. The checkboxes on this page do not save a handoff to your workspace.
An unanswered item is useful information. Give it an owner and a date for resolution rather than treating a checked list as permission to guess. Working through the list once with both people in the room is usually enough to learn which items your business tends to skip; after that, the record does the asking.
The items that get skipped are predictable. Agencies tend to lose the promises made during the pitch, because they were said in a room rather than written in the SOW, and the review rounds that were agreed verbally are the first thing a client holds them to. Consultancies tend to lose the acceptance criteria, because the proposal describes an approach and the client is expecting a result. Owner-operators tend to lose the dates, because the start date was promised on the phone before anyone checked what else was already scheduled. Each of these is one line on the record, written by the person who was in the room, at the moment it is still fresh.
Won → Project → Today: the deal-to-project workflow in three beats
The handoff has three beats, and a fair demonstration of any software for it should show all three without leaving the record. Those three beats are a useful test for any tool you evaluate, Scoped included: can you see the customer at the moment the deal is won, can you turn the sold work into a project without re-entering the client, and can you then read what has to happen today?
Won: the deal and the customer history
The deal reaches the Won stage on a pipeline board, with the quoted amount on the card. Behind it sits the customer’s history: the company page, the contacts, every note from the pitch, and the earlier engagements if there were any. Nothing about the client has to be re-entered, because the deal was never separate from the client.
Project: convert the sold work without re-entering the client
Moving the deal to Won offers a project with the company, the deal, the name, and the team already filled in. A person reviews that offer, adds the summary and the lead, and confirms. The project keeps its links back to the customer and the deal, so the producer who opens it on Thursday can read the pitch notes without asking who has them. The steps are in Turn a won deal into a project, and the lesson of the same name walks through it at a slower pace.
Today: owner, status, dependency, next action
Once the project exists, the question changes from what did we sell to what has to happen today. Each piece of work has an owner, a current status, and a date; a dependency is written down as work that waits on other work; and the next action is visible on the project rather than held in someone’s head. Each person reads their part in Focus, which lists the issues assigned to them. This is the beat most handoffs never reach, because the project was created without the context it needed and the team went back to asking.
What goes into the project is the sold work, in the shape the agreement gave it. A proposal with three phases becomes three milestones with their issues; an SOW with two review rounds becomes two dated review issues, each with an owner; a retainer becomes a project on the same client record, with each month’s work added as it is agreed. The planning is still done by a person, with the proposal open beside the project, and that is the point: the plan should be read against what was sold, not reconstructed from what someone remembers selling.
If you are weighing tools for this, run the three beats in each one. When you need both a CRM and project management covers the category question, and the buyer’s guide lists what else to compare.
From a won deal to a linked project in Scoped
Scoped connects the customer, sales opportunity, and delivery work. Changing a deal to Won from the pipeline or the All deals table offers project creation; you review the proposed details and confirm. The handoff does not automatically turn every sales note into a delivery task.
Demo scenario. These screenshots were captured on September 25, 2026 in a controlled local workspace with a fictional customer and an $8,400 USD kitchen refresh. We verified the offer, project creation, and customer/deal links. This is a product walkthrough, not a customer result.
- Capture the agreement on the customer record. Create a company named Demo client, add the relevant contact, and record the agreed scope and promises in notes. Keep the final estimate in your estimating tool and link to its agreed version where the team can find it.
- Create the opportunity. In Clients → Deals, create Kitchen refresh, associate Demo client, and record the quoted amount as $8,400 USD. The deal value is a record of the opportunity; it does not send an estimate or establish that payment was received.
- Move the deal to Won in the table. In Clients → Deals, choose the All deals table and use the deal’s Stage cell to change Lead to Won. Use Start a project in the follow-up banner. Saving Won inside the full deal form does not show this banner; use that form’s project action instead.
Open full-size screenshot Changing the stage in the table presents the project offer. It has not created a project yet. Controlled local demo, September 25, 2026; fictional data, not a customer result. - Review the offered project and confirm. Check the proposed name, team, company, and deal. The form carries the deal name, deal link, company, and company team where available. In this demo, we entered the summary and description and selected Demo owner as the lead ourselves, then selected Create project. These fields were not generated from the sales notes.
Open full-size screenshot The company, deal, name, and team were prefilled. The summary, description, and lead shown here were added manually before confirmation. Controlled local demo, September 25, 2026; fictional data, not a customer result. - Check the result. Open the project and confirm the company and deal links. Return to the company page to find the project with its related work. We verified both directions in this demo. The new project had zero issues and zero notes; creating it did not generate a delivery plan.
Open full-size screenshot The saved project keeps the customer and deal linked. The description was entered manually; the delivery work still needs to be planned. Controlled local demo, September 25, 2026; fictional data, not a customer result. - Plan the first pieces of work. Create an issue to confirm the customer’s selections, name its owner, and set its date. Record ordering materials as dependent on that confirmation. Capture the agreed finish and who approves it in the project description or relevant issues.
- Have the delivery owner read it back. Ask them to find the agreed scope, quoted amount, customer promises, and the first unresolved question through the project and linked customer record. Fill the gaps before scheduling the job.
For the current interface steps, use Turn a won deal into a project and Plan and track project work.
Check the relationship before starting another project
If you dismissed the project offer, or changed the stage inside the full deal form, open the deal’s form and use its project action. Review existing linked projects first so you do not start another project for work that already has one.
Keep open decisions explicit. A delivery date still awaiting materials should remain an open question until someone confirms it. If the scope changes after the sale, record the change and its source, then update the affected work with the people responsible.
Use separate tools for estimates, signatures, customer invoices, payments, and field dispatch when you need them. Record the relevant references and decisions in Scoped so the team knows where to find the agreement and the payment status.
The handoff is ready when the delivery owner can explain the outcome, next action, dependencies, and approval criteria without relying on someone’s memory. Review workspace access and plan limits before inviting the delivery team.
Three signs it worked, a week later: the person who sold the work has not been asked to repeat anything from the pitch; the client has not been asked a question they already answered; and the owner can open the project and read the current status without messaging anyone. Three signs it did not: the kickoff note is in a chat thread, the first piece of work has no date, and the quoted amount on the project does not match the one on the deal.
Hand off to operations without a meeting
The handoff meeting exists because the record is incomplete. When the project carries the agreement, operations can pick the work up from the record and spend the meeting, if there still is one, on sequencing rather than on reconstructing the sale. Three habits make that possible.
The kickoff note on the project
The person who sold the work writes one note on the project: what the client is buying, what was promised beyond the SOW, which dates are confirmed and which are hopes, and who approves the result. Keep it short enough to read in two minutes, and keep it on the project rather than in a message, so it is still there in month three when a new producer joins. The lesson Hand work to a teammate with context shows how an assignment, a line of context, and a mention make a handoff readable by someone who was not in the room.
The Focus view instead of the nudge
Assign the first piece of work with a date. The delivery owner sees it in Focus, beside the other issues assigned to them. Nobody sends the did-you-see-the-new-project message, and the operations lead can read who owns what on the project instead of asking. The daily routine that grows out of this is in How to track client project status without status meetings, and the client onboarding page shows the same habit applied to a new account’s first weeks.
The standup note, posted by your assistant
If the team has connected an assistant, it can read the project and post the standup note: owner, status, blocker, next action. Every update is recorded under the person who authorized the connection and the connection it came through; a read-only connection cannot write, and access can be revoked at any time. Scoped does not run the assistant; it supplies the record and accepts the updates you allow. How assistant access works covers the boundaries.
Two things stay with people. The summary, the description, and the lead are typed by a person, because the delivery owner should start from an agreement someone stood behind rather than from a guess at the sales notes. And the client hears about progress through the email, decks, or review links you already use: Scoped has no client portal, and everyone in the workspace sees the same records, so the decisions get written on the project and the client conversation stays where it is.
The payoff arrives at renewal. When the retainer comes up or the follow-on proposal is due, the person writing it opens the client record and finds the original deal, the project that came from it, what was delivered, and what changed along the way. The handoff that was done once, on the record, is the reason the second sale does not start from a blank page either.
Questions about the sales-to-project handoff
How do agencies hand off a new client from sales to delivery?+
The account lead who won the pitch records the agreed scope, the promises made outside the SOW, the quoted amount, and the confirmed dates on the client record, then moves the pitch to Won. The producer opens the project that came from it, reads the client history and the kickoff note on the same record, and assigns the first piece of work. The handoff is complete when the producer can explain the outcome, the next action, and the open questions without asking the account lead.
How do I turn a won deal into a project automatically?+
In Scoped, moving a deal to Won on the pipeline board or in the All deals table offers a project with the company, the deal, the name, and the team already filled in. A person reviews that offer and confirms it; nothing is created silently, and changing the stage on its own does not create a project. The summary, the description, and the project lead are typed by a person rather than generated from sales notes, so the delivery owner starts from an agreement someone stood behind.
What should a sales-to-project handoff checklist include?+
Eight things: the customer and the contacts who can approve changes, the agreed scope and where the signed version lives, the quoted amount and currency, the promises made during the sale, the delivery owner and their first action, the confirmed and proposed dates, the dependencies and open questions, and the acceptance criteria. An item without an answer gets an owner and a date instead of a guess.
Who should own the handoff from sales to operations?+
The person who sold the work owns it until the delivery owner has read the record back. Selling gives them the context; delivery gives the producer or operations lead the responsibility, and the moment of transfer is when the first piece of work is assigned with a date. If both sides share one record, the owner of the business does not have to sit between them repeating what was promised.
Can sales hand off to operations without a kickoff meeting?+
Yes, when the project carries the agreement. A short kickoff note on the project, the first piece of work assigned to a named owner, and the Focus view, where that owner sees the issues assigned to them, replace most of what a handoff meeting is for. Keep the meeting for sequencing decisions and for anything the client said that nobody wrote down, and drop it when the record already answers the questions.
If the question underneath all of this is whether the sales record and the delivery record belong in one tool at all, Do you need both a CRM and project management software? is where to settle it. Once the answer is yes, this playbook is the handoff that follows.
Sources and next steps
Prepared by the Scoped editorial team. Product details were reviewed against the following guides and published terms on October 16, 2026. Use the Help Center for current operating instructions.
- Manage your sales pipeline
- Turn a won deal into a project
- Plan and track project work
- Lesson: Turn a won deal into a project
- Lesson: Hand work to a teammate with context
Read next: Choosing CRM and project management software for a service business.
Read next: Do you need both a CRM and project management software?.
Read next: How to track client project status without status meetings.