Everything else we build runs on top of this.
Quoting and enquiries both come down to reading and writing your systems correctly, every time, with no invention anywhere in the path. That is what sits underneath them. We don’t sell you another place to put your data, we build around the software your business already relies on, and your systems stay the source of truth.
Connect by API, webhook, database or the backend you already paid for.
Can we work with your software?
Curated and checked by hand, not generated. If your software isn’t listed, ask us.
One accepted quote, from read to write-back.
Every automation company says it integrates. The question underneath it is narrower: what will the workflow be allowed to read, what is it allowed to decide on its own, and what is it allowed to write back into your systems. Here is one request with all three answered.
01Reads
- InboxThe reply, and the quote number it refers to.
- Customer recordsThe matching customer, and whether there is more than one.
- Job systemThe quote, its total, and whether it is still current.
02Decides
- The quote is still current.
- The total has not changed since it was sent.
- The reply matches one customer record, not two.
- No new price, term or date was asked for.
Four true and it continues. One false and it stops, with everything it gathered attached.
03Writes back
- Job systemQuote marked accepted, job created against the customer record that already existed.
- CalendarA scheduling request, not a booking. A person still places it.
- EmailConfirmation to the customer, from your address.
Illustration of one sequence, not a screenshot. Those three lists are exactly what we check your software will allow before we quote a workflow, and the middle one is where a workflow stops.
Nothing above this layer works if this layer guesses.
When the software offers a documented route
- Public APIs
- The front door most modern software offers. Documented, versioned, and open to anyone with an account.
- Partner and private APIs
- Where the access comes with your plan or has to be approved by the vendor before anyone can build against it.
- Webhooks
- Events in one system start work in another, so the workflow reacts when something happens instead of polling for it.
- Approved integrations
- Used as they are, where an off-the-shelf connector already does the job properly and nothing is gained by rebuilding it.
When it does not
- Databases
- Read and written directly, where the database is the real source of truth rather than the application on top of it.
- Existing backends
- Including the custom systems a business already paid to have built. They usually work. They rarely have documentation.
- Controlled middleware
- When two systems need a translator between them, we own the translator rather than hoping they agree.
If your software exposes the data and actions a workflow needs, it is usually a strong candidate for integration. We still check the exact permissions, endpoints, limitations and business rules before promising a workflow.
The systems we already work in.
ServiceM8
Our deepest integration seam. We write real jobs, quotes and customer records, not just notifications.
ServiceM8 automation in depth →Tell us what you run.
Show us the software you run, and what has to happen between the systems.
- Maybe your software has an API and nobody has ever used it.
- Maybe two systems hold the same customer and disagree about the details.
- Maybe the vendor says integration is possible and won’t say what that means.
Tell us what you run and what has to move between it. We’ll check what can be read, what can be written back, and what your software simply won’t allow, before anyone promises a workflow. If it can’t be done safely, that is the answer you get.
Would rather talk it through than type it out? Book a 30-minute call.
About the process
Four questions. Owen picks up the rest on the call.
Got it, thanks.
We read every one of these ourselves. Here’s what happens next.
- We look at the process you described and how it touches your systems.
- We come back within one working day. Reply to that email and it reaches Owen directly.
- If it’s worth building, we’ll tell you what we’d build and what should stay human. If it isn’t, we’ll tell you that.