Acceptance is the start of delivery
Sales and delivery often work from different views of the same customer. The customer may have accepted a quotation in a chat while the team still sees an unanswered enquiry. A short handover connects that decision to real work.
Name the person responsible for starting the job. That person should be able to find the accepted scope, the customer’s relevant requirements and the first agreed action without reconstructing the conversation.
Pass decisions, not an entire message history
Summarise the approved deliverables, exclusions, deadlines and dependencies. Include the agreed quotation reference and version. If a date depends on customer materials, state what is required and who will request it.
For example, ‘prepare website’ is not a useful first action. ‘Request approved copy and product photos from the customer by Tuesday; confirm the build schedule after receipt’ gives the owner a concrete next step.
Separate work, questions and money
Use a job status to describe delivery progress. Keep unresolved questions as tasks with owners and dates. Record verified payments separately so an early deposit does not accidentally mark the work complete.
When something changes, keep the reason and the approval. A customer requesting additional work should trigger a scope decision, not an undocumented addition to a teammate’s task list.
Check the first handover together
For a new workflow, walk through one accepted quotation with the person who will deliver it. Ask whether anything is missing and whether they know what to do next. Adjust the checklist before repeating the process across every job.
Flow’s job demo lets you inspect connected fictional records. The right setup depends on your process and package; discuss the modules and onboarding scope before deciding which system to adopt.