Integrations
For a business whose tools do not talk to each other. We connect them. The plan names each system, and what is allowed to move between them.
Book a callWhat you get
- A written list of the systems involved, and what moves between them.
- The connection, running where the plan says it should run.
- A short note on what to do when one of those systems changes.
How it works
- 1
Call
You tell us which tools are involved and where the double entry hurts.
- 2
Plan
We write what is allowed to move, and what stays where it is.
- 3
Build
You can see a real record move while it is being built.
- 4
Launch
We turn it on and hand over the note.
Stack
APIs. Most tools already offer an API. We use that, and we say so in the plan if one of them does not.
Questions
How much does it cost to build a integration?
It depends on the number of screens and what has to happen behind them. We don't publish a price list. Tell us what you're building and we'll price that scope in writing.
How long does it take?
We don't publish a standard number of weeks. Smaller first versions ship sooner, and we'll usually suggest one. You get a date once the scope is written down.
Who owns the code when the project ends?
Who holds the repo is written into the agreement before work starts. Ask in your message if the code needs to sit in your name.
What happens after launch? Do you fix bugs and keep it updated?
Fixes and updates after launch are written into the scope before we start. Tell us what you need looked after and we'll include it. We don't advertise a fixed support window on this page.
Will you sign an NDA?
If you need an NDA, say so in your message before you share anything private.
Can you fix or finish a project someone else started?
Send what exists, or describe where it stopped. We'll read it and tell you whether finishing it or rebuilding a piece is the sensible path.