The client accepted the proposal. Sales celebrates, the project gets a name, and someone tells operations: “You can start.” But start what, with which information, and under what conditions?
This handoff deserves as much attention as closing the deal. When context is scattered across messages, documents, and spreadsheets, the team must reconstruct what was agreed before it can deliver. A question about scope may seem small, but it changes the conversation about timelines, responsibilities, and deliverables.
Organizing this moment means defining what information accompanies the sale, who receives the work, and what needs to be resolved before the project starts.
Acceptance does not tell the whole story
Marking an opportunity as won shows commercial progress. By itself, it does not guarantee that the team has what it needs to begin delivery.
Consider a company selling a system implementation. The proposal has been accepted, but the client still needs to identify an internal contact and provide access to the test environment. This is an illustrative example: the sale has closed, while the technical start still depends on specific actions.
If both moments appear as a single stage, operations may receive a project that looks ready but still has outstanding issues. It is more useful to record the sale and make the conditions for starting visible, according to each business’s rules.
1. Bring the scope along with the sale
The team should be able to find the accepted proposal and understand the planned deliverables, scope boundaries, and agreed validation criteria.
This includes making exclusions explicit. A feature discussed during negotiations was not necessarily included in the contract. When that distinction depends on someone’s memory, different interpretations of the same project can arise.
A handoff record can bring together:
- The accepted proposal and related documents.
- Planned deliverables and items outside the scope.
- Assumptions used in planning.
- Points still awaiting confirmation.
The aim is to give the delivery team a reliable reference without requiring it to reread the entire negotiation.
2. Define who receives and who resolves
A notification that the sale has closed does not replace assigning responsibility. Who takes over the project? Who is the client’s contact? Who clarifies an ambiguous commercial condition?
Assign a person responsible for the handoff and another for receiving it when these roles are separate. The receiving team should be able to identify what is missing and route each issue to the right person.
It is also worth planning for absences. If only one person can authorize the start or clarify scope, continuity depends on that person’s availability.
3. Record dates with their dependencies
A date on its own can hide an important condition. Does the timeline begin after acceptance, after documents are delivered, or after an initial meeting? The answer should reflect what was agreed with the client.
Commercial conditions can also influence the start. When there is a rule requiring confirmation of a down payment or another milestone, it needs to be recorded and available to authorized people. There is no universal rule: each operation must translate its own agreements into clear criteria.
Avoid exposing unnecessary data during the handoff. The technical team may need to know that a condition has been met without accessing the entire financial history or negotiation details.
4. Check before starting
A short check helps distinguish “received” from “ready to start.” It can verify whether scope is defined, responsible people have been identified, and essential dependencies have been resolved.
If something is missing, the flow should show the issue, who will resolve it, and the next step. This gives context to the wait and keeps the project from getting lost between teams.
The checklist should be proportional to the service. A simple assignment does not need the same process as an implementation involving several teams, integrations, and environments.
5. Automate what already has a clear rule
Once the process is understood, technology can connect records and reduce repeated data entry. A custom flow can create a project from a won opportunity, link the accepted proposal, assign owners, and open a list of outstanding issues.
If sales and operations use different tools, an integration can transfer the necessary data. To make it work, define each piece of information’s source, how updates are handled, and what happens when a transfer fails.
Automation must also handle exceptions. If the client requests a change after closing, the project should not silently receive a different scope. The change needs appropriate review and a history of what was agreed.
An example flow to adapt
Consider this illustrative sequence:
- Sales records acceptance and links the relevant proposal.
- The operations owner receives the context and checks the information.
- Outstanding issues remain visible, each with an assigned owner.
- Necessary conditions are checked according to business rules.
- The team confirms the start and communicates the next step to the client.
This sequence is a starting point, not a ready-made recipe. The final design depends on services, roles, and tools the company already uses.
The next step begins with your process
Look at recent handoffs from sales to delivery. Which questions came up again? What information had to be requested a second time? At what point was work left without an owner?
These answers help choose what to organize first. Instead of automating every step at once, start where missing context most disrupts continuity.
Solvers develops custom digital solutions based on operational needs. If your company needs to connect the commercial close to project kickoff, let’s understand that flow together.
Learn about Solvers at https://solvers.com.br/en-US/ or contact us by WhatsApp at +55 11 97087-9021.
