Two practical routes for Phase One — one if Cube gives us the access we need, one if it doesn't. Both deliver the same operational outcome: more cases booked, on time, without adding team headcount.
Cube stays the system of record. We build the booking layer alongside it.
A focused booking system with every customer's calls, emails, SMS and messages in one timeline.
More work is arriving than the current booking process can absorb. Cube sits at the centre of operations, and how it exposes data shapes the right path forward.
Surveyor rules, mileage, current bookings and cluster opportunities all need to be checked before the system ever picks up the phone.
Most cases are routine. Automating these frees the team for the complex ones that genuinely need human judgement.
If Cube exposes the data we need cleanly, we integrate. If it doesn't, we build natively. The work itself is the same.
The operational outcome is identical. The difference is where the booking workflow lives — inside Cube's orbit, or in a focused CRM purpose-built around Paterson's way of working.
A purpose-built booking CRM for Phase One, replacing Cube for the booking workflow if Cube cannot give us the access required. Every customer has a single, searchable booking record. Inbound and outbound calls (recorded and transcribed), emails, SMS and messages all sit on the customer timeline. The £38,000 includes the CRM build and agreed active workflow data needed for go-live. Full historical Cube export, cleansing and migration is available as an optional £12,000 + VAT add-on.
Every call recorded, transcribed and tagged to the customer — voice AI calls and surveyor calls alike.
Inbound and outbound email captured against the customer — no more lost replies in personal inboxes.
Two-way SMS plus messaging-app threads on the same record. Replies route back to the right case automatically.
Filter by customer, surveyor, case stage or keyword. The full back-story is one click away.
When the AI calls back or follows up, it does so already knowing what was said before — no awkward repeats.
Timestamped, attributed and exportable. If a case gets challenged, the conversation history is right there.
Standard inspections booked end-to-end, with joint expert coordination available where the workflow lives inside the Native Booking CRM.
Dependent on everyone working on the same system. This is the only way the AI can manage the complexity; otherwise it still needs to be done manually. Only available on the custom CRM build.
Later phases extend the booking foundation into broader case lifecycle workflows, reporting, portals and more advanced exception automation.
The build price is fixed once the route is confirmed. The managed service is a flat monthly. Provider usage stays separate so you keep direct visibility and control.
The 4–6 and 6–8 week timelines assume timely provision of all client dependencies. Delays in providing required materials may extend the delivery timeline proportionally.
Export, clean, map and import historic structured Cube case data into the Native Booking CRM. Subject to receiving usable Cube exports. Document/file migration, scanned PDFs, email archives and manual correction of poor-quality records would be scoped separately.
Paterson owns the provider accounts; we set them up and manage them. These figures assume ~100 cases per week and are not part of the managed service fee.
As an FCA-regulated firm and the Data Controller, it is important that you hold all third-party service accounts directly in your name. This means full regulatory compliance with no data processing through intermediary accounts, complete transparency on costs with no markup, and no vendor dependency. If your relationship with Engage AI ever ends, your accounts, your data, and your service relationships remain yours.
Pricing reflects the scope as we currently understand it. If something material was missed and only surfaces during the build, we'll flag it openly and agree any adjustment with you before continuing.
We review what Cube can do at no charge. You see workflow mockups before committing. Then we issue the fixed Phase One proposal for the confirmed route.
Most of what we need already exists. We're not asking for new documentation.