Integrations
Integrations: working with the software you already run
We connect anything. If a system exports a file or has an API, we connect it, whatever the brand and whatever the format, proprietary or not. Every export is a file we can read, and every API is a door we can use, so the work moves once between the systems you already run. A Production Build includes up to two standard integrations.
How we connect to a system
Every system a company runs has a way in and a way out: an export, an import, a report it can send, or an API. In the Workflow Spec we read the documentation for each system involved and look at what your people actually export today. The bridge is built from that, so information moves the way the system already supports and nobody retypes it.
You can see the idea with sample data in the Bridge: a field export on one side, the import your accounting or job-costing side needs on the other.
Any system, any file, any API
The brand on the box does not matter. Exports come out as the same kinds of files, spreadsheets, CSV, XML, JSON, PDF reports and proprietary formats, and we read all of them. Anything with an API we connect to directly. A few of the systems our clients run:
- Field service and dispatch: ServiceTitan, Jobber, FieldEdge, ServiceM8 and similar
- Construction and project management: Procore and similar
- Accounting and ERP: QuickBooks Online and Desktop, Sage 300 CRE, Viewpoint Vista, Acumatica, Foundation and similar
- Spreadsheets kept by the office, which are often where the real system lives
At WERCS, the company in our proof case, the systems were QuickBooks and ServiceM8.
In production, not a pilot
A connection is only finished when it runs every day without someone watching it. Every bridge we build handles the parts a demo skips:
- Access: each person sees and changes only what their role allows, and the tool uses its own account with the narrowest permission each system offers.
- Failures: a sync that fails is retried, and one that keeps failing is flagged to a named person with the record and the reason, never dropped quietly.
- Duplicates and mismatches: records are matched on what the systems share, and anything uncertain waits for a person instead of being guessed.
- Approvals: where a mistake would cost money or a customer, a person approves before anything is written.
- Monitoring: after go-live the bridge is watched, and the 30 days of stabilization fix whatever the real work turns up.
PAM is one in daily use: finished jobs move from ServiceM8 in the field to invoices in QuickBooks, the parts come off inventory, and the paid status flows back to the job.
What we will and won't do
- We will connect the systems you already run so information moves once.
- We will build the tools your people use around those systems, with them, on site.
- We won't replace your ERP, accounting or field software, or become a second system of record.
- We won't ship a demo and leave. A tool is done when the crew uses it every day.
What stays the same
Your systems stay the systems of record. A tool we build does not hold a second copy of the truth; it carries information from where it is created to where it is needed, in the form that system expects.
What you own
Your data, your production accounts and, after payment, the tool itself, with the copyright assignment in writing.
Questions people ask
Do you work with our software?
Almost certainly. If a system can export what it holds and accept an import, or offers an API, we can build around it. Which route a Build uses is decided in the Workflow Spec, from the system's own documentation.
Will the tool replace our system?
No. The tool reads and writes through the systems you already run and never becomes a second system of record.
Who owns the data that moves between systems?
You do. Your data stays in your systems and your production accounts, and after payment you own the tool that moves it.
How many integrations does a Build include?
Up to two standard integrations with what you already have. More can be scoped in the Spec when the work needs them.
