IIIOrganization & Project ManagementGuide
Handoff From Sales to the Project Team: What Must Be Recorded
The salesperson has known the customer for months, the project team for one email. Whatever gets lost in this gap, the customer has to explain a second time later, and some of it the team only learns when it is too late.
Key takeaways
- The seven-point handoff from order processing applies to the handoff to the project team. In project business three points are added: success criteria, people involved at the customer, and costing assumptions.
- A sheet alone is not enough. A handoff meeting of 30 to 45 minutes transfers what is hard to write down.
- Customers see a project as a sequence of steps from defining requirements to support afterwards. Suppliers often think only of what is delivered.
- The salesperson remains responsible for the relationship until the review on day 30.
Why does so much get lost in the handoff to the project team?
In the sales conversation the customer explained why they are switching, who internally is skeptical, and that the date cannot be moved because of a trade fair. The salesperson promised that training would take place on site and assumed in the costing that the customer would prepare the data themselves. Only part of this made it into the quote.
The project team receives the quote, perhaps a short phone call, and starts planning. At the kickoff it asks questions the customer has already answered three times. Three weeks later it turns out that the on-site training is not planned anywhere. The customer is annoyed, the team feels let down by sales, and the salesperson has long moved on to the next deal.
The cause is not bad intent. Salespeople and project teams have different tasks, different schedules, and often different ideas of when a project begins. The handoff is the point where these worlds meet. Without a fixed form, it is left to chance. So the question is: how do you design the handoff from sales to the project team so that no promise and no assumption gets lost? To answer it, we first clarify what is different in project business and what has to be recorded, then describe the handoff meeting and the risky promises, and finally turn to measurement and the question of who is responsible afterwards.
Every promise that is not handed over will eventually be claimed by the customer, just not from the salesperson.
What is different about the handoff in project business?
For handing an order over to delivery, the article on how to optimize order processing describes the seven-point handoff: contact person, scope with exclusions, committed dates, price and payment terms, special agreements, open items, and background. It comes with the return rule: an incomplete handoff sheet goes back to sales the same day.
In project business that is not quite enough. Projects run for weeks or months, several people are involved at the customer, and the quote rests on assumptions that can prove wrong during the project. That is why this article adds three points. The result is called seven plus three here.
An interview study by Tuli, Kohli, and Bharadwaj (2007) shows why these particular points matter. They talked to 49 managers from customer firms and 55 from supplier firms and held two focus groups with 21 further managers. Suppliers mostly understood a solution as a customized bundle of goods and services. Customers, by contrast, saw a sequence of joint steps: defining requirements, customizing and integrating, deploying, and supporting afterwards. Suppliers often gave short shrift to precisely the definition of requirements and the support after deployment. Among the influencing factors on the supplier side, the authors name how much emphasis is placed on documentation and how stable the customer's contact persons are.
Zidane (2025) also describes how people within the same company understand the duration and scope of a project differently, depending on when they join. For sales, the project begins with the first inquiry; for the project team, with the kickoff. The handoff has to bring these two views together.
What must be recorded at the handoff?
| Item | Guiding question |
|---|---|
| 1. Customer and contact person | Who can be reached for the project, how, and when? |
| 2. Scope and exclusions | What exactly does the customer get, and what explicitly not? |
| 3. Committed dates | Which dates were mentioned, and how binding was each commitment? |
| 4. Price and payment terms | Which price, which discounts, which installments? |
| 5. Special agreements | What was promised beyond the standard, including verbally? |
| 6. Open items | What is unresolved, and who resolves it by when? |
| 7. Background | Why did the customer buy, and what do they care about most? |
| +1 Success criteria | How will the customer judge after the project whether it was worth it? |
| +2 People involved at the customer | Who decides, who uses the result, who approves, who is skeptical? |
| +3 Costing assumptions | What was assumed for price and schedule, such as customer input or conditions on site? |
The third additional item is forgotten most often and causes the most expensive surprises. In project business, delivery time, cost, and required capacity are estimated before an order is certain. Ohlson and Bäckstrand (2026) describe this in a case study of five Swedish companies that build to customer specifications. Each of these estimates rests on assumptions. If the project team does not know them, it only notices during the project that the price applied only under conditions that did not materialize.
What does a good handoff meeting look like?
A sheet transfers facts. What is hard to write down, such as how the customer ticks, who has influence in the background, or which promise was delicate, is transferred by a conversation. For projects above a certain size, both belong together.
Send the sheet in advance
The salesperson fills in the handoff sheet and sends it to the project lead at least one business day before the meeting.
Tell the story (10 minutes)
The salesperson tells how the order came about: trigger, the customer's alternatives, turning points in the sale.
Go through promises and assumptions (15 minutes)
Item by item through the sheet, focusing on special agreements, success criteria, and costing assumptions.
Mirror back (5 minutes)
The project lead summarizes in their own words what the customer expects. The salesperson corrects.
Schedule the kickoff (5 minutes)
Date for the joint kickoff meeting with the customer within five business days of the commitment, and who prepares what.
The kickoff meeting with the customer is the second touchpoint in the 30-day plan described in the article on customer onboarding. There the salesperson introduces the project lead, and the project lead restates to the customer what they have understood. A mistake caught here costs one conversation. The same mistake at acceptance costs money and trust.
Which sales promises are particularly risky?
Risky promises are those that are easy to make in a conversation and hard to keep in the project. They have one thing in common: they rarely appear in the quote.
Said during the sale
- “We can manage that by the end of the quarter.”
- “Of course we'll do the training at your site.”
- “Small changes are no problem.”
- “You'll always have me as your contact.”
Understood in the project
- A fixed deadline around which the customer plans internally
- Travel time and an appointment that is costed nowhere
- An open-ended scope of changes without a limit
- A salesperson who answers every question even after the start
Behind some of these promises lies a structural conflict. Steinhoff, Kim, Kanuri, and Palmatier (2025) observe among providers of business software that sales and customer management are often run separately and that sales receives bonuses for the largest possible packages, while customer management is supposed to ensure a smooth start. In their study, larger packages led to more cancellations in the early phase. If you measure sales only by the deal, you reward promises whose costs others bear.
A simple countermeasure: special agreements belong in the quote or in a confirmation to the customer, not only in the conversation. How quotes with clear exclusions are produced is described in the article on how to standardize your quoting process.
How do you measure whether the handoff works?
Order processing is measured by questions per order, days until the start, and the share of corrected invoices. For projects, one number is added: the share of projects in which scope or price had to be renegotiated because something from the sale was not known.
- Projects won
- With a complete handoff sheet75% of previous stage
- With a handoff meeting80% of previous stage
- Kickoff within 5 business days83% of previous stage
- No renegotiation of scope or price80% of previous stage
Worked example: only 8 of 20 projects run without renegotiation. The first gap is at the handoff sheet, which is where improvement starts.
Worked example
Discuss the numbers once a month with sales and the project lead together. The goal is not to find someone to blame but to identify the items on the sheet that are regularly missing. This often leads to a new building block for quotes or a new question for the first meeting.
Who is responsible when things go wrong after the handoff?
After the handoff, the project lead is responsible for the work. The salesperson remains responsible for the relationship until the review on day 30, and for everything related to their promises. If the customer asks about an agreement from the sale, the salesperson clarifies it with the project lead, not around the project team.
For the customer, continuity counts. Tuli and colleagues explicitly name the stability of contact persons as a factor in a solution's success. A project in which the customer experiences four contact persons in three months looks disorganized even when the work is good.
So that the handoff does not depend on individuals, it belongs in the mapped sales process as a stage of its own. The template is in the article on how to visualize your sales process. The handoff sheet itself can be captured as a page using the one-page method, and frequent questions from handoffs belong in the answer collection described in the article on sales knowledge management.
How to get started
- Take the seven-point handoff and add success criteria, people involved at the customer, and costing assumptions.
- Decide above which project size a handoff meeting also takes place.
- Go through the last three projects with sales and the project lead: what should have been on the sheet at the handoff?
- Agree on the return rule explicitly, for projects too.
- For the next half-year, count how many projects run without renegotiating scope or price.
After two or three projects with the new sheet, you will notice the difference above all at the kickoff: the customer has to explain less, and the project team asks about what is still missing instead of what the salesperson knew long ago.
Taken together: little gets lost in the handoff when it has a fixed form, meaning a sheet with the seven points, a handoff meeting above a certain project size, and an explicit rule on who is responsible when things go wrong afterwards. Whether this works is shown by the number of projects that run without renegotiating scope or price. Good will on both sides does not replace this form.
Frequently asked questions
What belongs in a handoff from sales to the project team?
The seven items of the order handoff: contact person, scope with exclusions, committed dates, price and payment terms, special agreements, open items, and background. In project business, the customer's success criteria, the people involved at the customer, and the costing assumptions are added.
How does a handoff meeting work?
The salesperson sends the handoff sheet in advance, tells the story of the order in the meeting, and goes through promises and assumptions. The project lead summarizes what the customer expects, and both schedule the kickoff with the customer. 30 to 45 minutes are enough.
Who is responsible for the customer after the handoff?
The project lead for the work, and the salesperson for the relationship and for their sales promises until about 30 days after the commitment. What matters is that the customer knows whom to contact for what.
Why does information get lost in the handoff?
Because much was only said in conversation with the customer and never appeared in the quote, such as verbal promises or costing assumptions. Without a fixed handoff sheet and meeting, what the project team learns is left to chance.
How do I recognize a poor handoff?
The customer has to explain at the kickoff what they already told the salesperson, the project team runs into promises it did not know about, and scope or price have to be renegotiated. Count how often that happens.
Sources
- Tuli, K. R.; Kohli, A. K.; Bharadwaj, S. G. (2007): Rethinking Customer Solutions: From Product Bundles to Relational Processes. Journal of Marketing, 71(3), 1-17.
- Zidane, Y. J.-T. (2025): Rethinking Project Boundaries. PM World Journal, 14(6), 1-23.
- Steinhoff, L.; Kim, J. J.; Kanuri, V. K.; Palmatier, R. W. (2025): Unintended consequences of selling B2B digital subscription add-ons for customer onboarding. Journal of the Academy of Marketing Science, 53(5), 1447-1481.
- Ohlson, N.-E.; Bäckstrand, J. (2026): The planning paradox: Why engineer-to-order companies must embrace contradictions in tactical planning. Production Planning & Control, advance online publication, 1-22.
