Integrations
Integrations: working with the software you already run
We work with whatever your company already runs. Every field service app, project system and accounting package exports data and accepts an import in some form; learning a platform's export and import is a matter of reading its documentation, and the bridge is built from that. 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.
Systems we commonly see
- 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.
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.