Datacat

Insights

2026-11-10 · 6 min

New customers who start work without the stall

A signed deal can sit idle while sales, finance and operations each wait on the other. Set up a start-up step that gets every new customer to a first job.

Here is an illustrative example, not a customer account. A cleaning and maintenance business wins a contract for a customer’s offices. The sales lead celebrates, marks the deal as won and moves on to the next prospect. Finance waits for a purchase order number. Operations waits for site access details. The customer waits for someone to tell them when the first crew is coming.

Nobody in the example has done anything wrong. Each person is waiting on information they assume someone else is collecting. The first job slips, the customer’s first impression is silence, and the sales lead takes an irritated call about a contract they thought was finished.

Where a signed deal stalls

The gap can sit between the moment a deal is marked won and the moment someone owns delivery. Check whether any of these apply in your business:

  • “Won” is the last step in the sales pipeline. The record stops moving, and no new task is created for anyone else.
  • The details live in the sales lead’s inbox. Contacts, scope notes and promises made during the pitch never reach the people delivering the work.
  • Billing set-up is a separate conversation. Finance asks for a purchase order or payment details on its own thread, often after operations has already asked the same customer different questions.
  • No date is promised. The customer signed, but nobody told them what happens next or when.

These are examples of process gaps to look for, not measured rates across businesses. Your own records will show which, if any, apply to you.

Make “won” the start of a job, not the end of a deal

Treat a won deal as the trigger for a start-up job with its own owner and target start date. Marking the deal won should create that job, assigned to the person responsible for getting the customer to their first visit, so the record keeps moving after sales steps back.

The start-up job can carry a short, fixed list of what delivery needs before work begins: site contacts, access arrangements, agreed scope, pricing, billing details and any compliance documents the customer requires. Each item shows who is collecting it and whether it has arrived.

Ask the customer once, in one place

Customers lose patience when three people from the same business ask overlapping questions. Collect start-up information through a single request, such as one form or one email from the delivery owner, and store the answers on the customer record where sales, finance and operations can all see them.

If you already hold the details from the sales process, prefill them and ask the customer to confirm rather than retype. One customer, one record covers why that shared record matters well beyond onboarding.

Carry the promises from the pitch into delivery

Sales conversations often include commitments that never make it into a contract clause: a preferred service window, a named contact on the customer side, a sensitive area of the site. Ask the sales lead to record these on the start-up job before handing over, in plain sentences rather than shorthand only they understand.

A short handover conversation between the sales lead and the delivery owner can help, but the written record is what the crew and the office will check later. Handoffs that don’t restart the job goes deeper on what a handover record should hold.

Tell the customer what happens next

Send the new customer a short welcome that names their delivery contact, lists anything still needed from them and gives a target date for the first visit. When the date is confirmed, tell them. When something changes, tell them before they have to ask.

Artificial intelligence (AI) could help draft that welcome from the start-up job, or summarise outstanding items for the delivery owner, where your system supports it. A person should still check the details and the dates before anything goes to the customer.

Measure the gap between signature and first job

To see whether this is a problem in your business, pull a sample of recently won customers and note two dates for each: when the deal was marked won and when the first job was completed. This is a suggested review, not a benchmark, and it may show your onboarding already works well.

For the slowest cases, look at what the start-up was waiting on. If the same item keeps appearing, such as billing details or site access, that is where to change the process first.

Build the start-up step into the system you already use

Datacat can review how won deals reach delivery in your current customer relationship management (CRM) system and design a start-up job, a shared customer record and a welcome step around the way your teams already work. Where your current tools can’t carry the process, a custom CRM and ops platform can be scoped around it, and ops workflow automation can create the start-up job and its checklist when a deal is marked won, depending on system access and integration support.

See work we have delivered, book paid strategy and discovery to map your onboarding from signature to first job, or tell us where your last new customer waited longest. Remove customer names and other sensitive details before sharing.