The customer hears Monday. The delivery lead hears about Monday after the contract is signed. That gap is where an attractive sale becomes an operating problem.
Before a service-business sales team offers a firm launch date, the person responsible for delivery capacity and the person responsible for cash commitments should accept it. Sales delivery handoff approval belongs before the customer promise, with a recorded release condition for anything still uncertain.
Arron Bennett's published work connects growth commitments to resources and cash, and scope boundaries to margin protection. This article applies those positions to one start-date decision. The workflow and fictional example are editorial proposals, not a claimed Bennett client case.
The delivery promise should describe work the team can start
A launch date means more than an open calendar slot. It may require customer access, specialist staff, setup work and money paid before the first invoice is collected.
The sales process should identify these dependencies while the deal can still change. The account lead brings the proposed scope and customer expectations. Delivery confirms the current state of available capacity. Finance checks the timing of any associated spending. The CEO resolves a conflict that those owners cannot settle.
A delivery date can be provisional. The important part is saying what must happen before it becomes firm. A dependable promise builds trust because the company knows what has been accepted.
Revenue goals need resource maps develops the wider planning argument. This handoff process puts that principle inside a specific sales conversation.
Confirm the promised delivery date with a simple checklist
Keep the approval in existing systems rather than building a separate platform. Project management tools or customer software can hold the record if sales, finance and operations can see the same critical information.
The supporting documents should answer five questions:
What scope and launch activities have been sold?
Who can actually deliver them on the proposed date?
What must the new client supply, and by when?
What cash or supplier commitment starts before payment?
Who may change the date if a dependency is missed?
A signature on a blank checklist is not a successful handoff. Missing information should produce a specific follow-up, owned by a named person. Data accuracy matters most where a date depends on another event: distinguish confirmed staff availability from a manager's estimate.
For a technology implementation, a supplier or supply chain dependency may matter. For a consulting engagement, the constraint may be one specialist's time. Use the actual dependency rather than importing delivery expectations from a different business model.
Hypothetical: two Monday launches, one onboarding team
Assume two new customers each buy a $25,000 project. Sales proposes the same Monday launch for both. Total contracted project value would be $50,000.
In this fictional example, one onboarding team can start only one project that week. Each launch also requires $8,000 of setup spending before its first receipt. Starting both together would require $16,000, while starting one requires $8,000. The example assumes identical setup costs and excludes other operating payments.
The delivery lead cannot approve two starts simply because both customers want them. The company can sequence the projects, revise scope or secure verified extra capacity. Finance must review whichever option creates new spending.
Changing the proposal before signature lets the customer evaluate an honest offer. After signature, a delay may require a different conversation about what the company has already promised. The commercial agreement, not an internal checklist alone, determines the next step.
If sales promises and delivery resources repeatedly diverge, bring that handoff to the Profit & Tax Leak Check so the financial consequence can be examined alongside the operating decision.
Customer expectations need one approved version
Do not allow sales to sell one date while project management carries another. The approved version should describe the start, prerequisites and any agreed sequence. The customer-facing owner should confirm that version before commitment.
Balancing speed with responsible approval does not mean waiting for perfect certainty. It means explaining the uncertainty that affects the purchase journey. New customers can choose a later reliable start, a smaller initial scope or a contingent proposal when those options are clearly communicated.
The delivery handoff also needs an exception route. A strategic customer may warrant a different sequence, but the decision maker must accept the cost and displaced work. The team should document who authorized the change and maintain visibility of its consequences.
Bennett's project staffing mix article owns the deeper staffing economics. Use that analysis where needed rather than treating a signed deal as evidence of fulfillment capacity.
Test a successful handoff before accepting more customers
The test is simple: can the delivery lead describe the accepted promise without asking sales to reconstruct it? Can finance identify the first cash commitment? Can the account owner explain what happens if a prerequisite is late?
Those answers support a positive customer experience more directly than adding another approval field. A process that nobody can follow under pressure will not protect delivery timelines.
Protecting service quality while scaling covers the broader growth issue. For the next live proposal, confirm one date, one delivery owner and one cash owner before it reaches the customer. If nobody can identify those owners today, use the Leak Check to start with the promise that creates the greatest exposure.
Frequently asked questions
When should delivery approve a launch date?
Before sales makes a firm customer commitment, while the date, sequence or scope can still be changed.
Who approves the cash associated with the launch?
The person authorized to release the spending should verify timing and available resources before approval.
Can sales quote a provisional start date?
Yes, if the customer understands the dependency and the condition that makes the date firm.
What does the onboarding team need from sales?
Approved scope, prerequisites, customer contacts, the proposed date and any spending or supplier dependencies.
Should every launch need CEO approval?
No. Ordinary launches should follow delegated authority. The CEO handles exceptions that exceed those boundaries.
What if both customers want the same date?
Compare sequencing, scope changes and verified extra capacity before promising both starts.
Can a shared tool replace the approval conversation?
It can preserve the evidence and decision, but a field marked approved does not establish that capacity or cash was checked.
What changes after the contract is signed?
The company must consider what it actually agreed with the customer. An internal revised date does not automatically revise the commercial commitment.
Sources and context
Arron on funded growth and Arron on scope control support the broad position. The approval workflow and worked example are original editorial applications.