Booking and field operationsBuy
Keep ConvertLabs
It already handles self-booking, schedules, availability, assignments and the job information cleaners need. Rebuilding those functions would add cost before solving the coordination problem.
← Resource library
Opportunity review in practice
What NeatNow bought, what it built and what it chose not to replace.
A real review of booking, customer communication and lead coordination inside a cleaning business—using Build, Buy or Skip to protect the systems that already work and build only the missing operational layer.
The decision
Keep the systems of record. Build the coordination layer.
NeatNow already had software for booking, scheduling, calls and messages. The missing capability sat between those systems: recognizing what had changed, what had not happened and which action should come next.
The review therefore supported two Buy decisions, one Build decision and a clear Skip boundary: keep ConvertLabs and Quo, build Ops Copilot above them, and avoid recreating functions that proven products already handle.
Build, Buy or Skip
Three needs. Three grounded decisions.
Each decision considers the value of the work, operational readiness, implementation risk and the fit of systems already in place.
Calls and customer messagesBuy
Keep Quo
It already provides the live phone and messaging experience. The useful opportunity is to give those conversations stronger operational context, not to replace the communications client.
Cross-system coordinationBuild
Build Ops Copilot
Lead state, messages, bookings, policies and missing events span several systems. The coordination layer has to understand NeatNow’s operating rules and decide what needs attention next.
Skip boundary
Do not build another booking platform or another live phone client. Custom work should address the coordination gap those products do not own.
Current-state workflow
One customer journey, several operational systems.
The difficulty is not any single step. It is preserving context and noticing important gaps as work moves from lead capture to conversation, booking and service.
- 01
Lead arrives
A Meta form, direct enquiry or another channel creates a prospect record.
- 02
Quote and follow-up
The lead enters the dashboard and the appropriate response or follow-up lane begins.
- 03
Conversation
Quo remains the live channel for calls and text messages with the prospect or customer.
- 04
Booking
ConvertLabs records the customer, service, schedule, assignment and field-service details.
- 05
Coordination
Ops Copilot watches the state across those systems, surfaces gaps and prepares the next action.
The coordination gap
The owner was the integration layer.
Someone had to remember the last conversation, reconcile lead and booking state, detect silence, check policy and decide whether to follow up. Ops Copilot externalizes that working memory while leaving each operational system responsible for the job it already performs well.
Operating status
Live capability with deliberate control.
The operational lanes below are live for NeatNow. Customer-facing messages still use manual approval while rule-following is evaluated in production. Template-based follow-up lanes have matured enough to be candidates for autonomous sending, but readiness and activation are separate decisions.
Live in the NeatNow installation
- Lead dashboard
- Follow-up sequence
- Re-engagement workflows
- Booking sensors
- Morning brief
- Controlled autonomous-send capability
Current control
Manual approval remains the default for customer-facing sends while the model is evaluated against operating rules.
Implementation brief
What the Build must preserve and prove.
The implementation is successful when it improves coordination without weakening the systems of record, customer consent or human control over consequential actions.
Surface the next justified action.
Join lead, conversation and booking signals so the operator can see what requires attention, why it matters and what response is permitted.
ConvertLabs and Quo remain authoritative.
Ops Copilot coordinates their signals. It does not become a second booking editor or a replacement phone and messaging client.
The operator owns exceptions and approvals.
Automation handles bounded, inspectable work. Uncertain identity, unusual scope and reputation-bearing decisions return to a person.
Earn new integrations and autonomy.
End-to-end Gmail handling and broader autonomous sending remain controlled expansion decisions rather than assumptions inside the first implementation.
Acceptance conditions
The tests that make the recommendation operational.
A Build recommendation is incomplete until the client and implementer agree how to recognize correct behaviour, exceptions and a safe failure.
- 01
A reply, booking, opt-out or manual intervention stops the wrong follow-up path.
- 02
A lead and booking match only when the identity evidence is reliable; uncertain matches are surfaced for review.
- 03
Drafts use current NeatNow scope, pricing and operating policy rather than generic model knowledge.
- 04
The operator can see why an item needs attention and which system supplied the underlying fact.
- 05
No message is sent autonomously unless its lane, template and safety checks have been explicitly approved.
- 06
Customer and cleaner messages cannot be routed to the wrong recipient when a booking involves several people.
Known constraints
The review does not hide the difficult parts.
Identity matching
Lead and booking records may use different phone numbers. Uncertain matches need an operator.
Polling and API gaps
Some booking and message changes arrive through polling, and vendor APIs do not expose every useful field in the same place.
Recipient safety
A booking can involve a customer and several cleaners. Message routing must make the intended recipient explicit.
Email boundary
Gmail participates in local and planned workflows, but this review does not claim complete end-to-end email coordination in the current installation.
The resulting direction
Buy the mature capability. Build the missing judgment. Skip duplicate infrastructure.
That direction keeps NeatNow’s operating stack legible: ConvertLabs owns bookings, Quo owns live communications and Ops Copilot owns the cross-system work of noticing, grounding and coordinating what happens next.
Ask about an Opportunity Review