CRM to accounting
Won deals create customers and draft invoices in the accounting system, and payment status flows back to the CRM.
Integrations and Custom Internal Tools
APIs, data synchronisation, and internal tools that help the business systems you already pay for work together reliably.
How it works · From online order to every system in sync
STEP BY STEP
In
- Online store
- Payments
- CRM
- 1
Event01
An order is paid in the store
Order #5521
- 2
Map02
Fields translated between systems
SKU → item code
- 3
Sync03
Stock, customer, and invoice updated
3 systems updated
- 4
Reconcile04
Totals compared across systems
Totals match
- 5
Alert05
Failures retried, then flagged
Retry queue: 0
Human checkpoint
Out
- Accounting
- Inventory
- Courier booking
See how this would run on your own process, with your tools.
Book a free callThe problem
01
What this solves.
Systems that do not exchange information properly leave people copying data between them, reconciling spreadsheets, and fixing mismatches by hand.
What changes
- Data entered once and synchronised everywhere
- Fewer mismatches between systems
- Simple internal tools in place of fragile spreadsheets
- Connections that are monitored, not forgotten
Use cases
02
What this looks like in practice.
Typical examples. Every build is scoped to your own process and systems.
Internal portal
A simple web app replaces a shared spreadsheet used to track jobs, with role-based access, validation, and an audit log.
E-commerce operations
Orders, stock, and fulfilment data are synchronised between the online store, inventory system, and courier.
Scope
03
What we can build.
Capabilities
- API integrations
- Data transformation and synchronisation
- Webhooks and event-driven workflows
- Database-connected workflows
- Custom internal tools and portals
- Improvements to existing web applications
How it works
We review the systems involved, their APIs and access, and the data that needs to move. Calculations and validation use deterministic rules; AI is used only where it adds something.
Tools we commonly work with
REST and GraphQL APIs- Webhooks
Next.js
Node.js
Python
PostgreSQL
Shopify
Stripe
Xero
Limits and human review
What can be connected depends on each system's APIs, licensing, and access permissions. We assess this before proposing a solution rather than assuming an integration exists.
Delivery
04
From first call to working system.
- 01
Discover
Days
- 02
Map
1–2 weeks
- 03
Design
Days
- 04
Build and test
2–6 weeks
- 05
Improve
Ongoing
You receive
- Integration or internal tool, deployed
- Error handling, retries, and alerts
- Technical documentation
- Access and credentials handover
Questions
05
Common questions.
Who owns the code?
Ownership and licensing are set out in the project agreement. Our standard position is that you own what we build specifically for you.
What if a system has no API?
We look at exports, email parsing, database access, or file drops first. Screen automation is a last resort, and we tell you the trade-offs.
Do you always use n8n?
Usually, because it is open, flexible, and you can own it. Where custom code or another tool is the better fit, we say so.
Next step
What would you like to improve?
Tell us what is taking too much time, what is difficult to manage, or what you would like your systems to do differently. You do not need a technical specification to start.