04 · Custom apps & integration
One operation, with data that stays true.
System Intelligence (SI) carries a record across your website, CRM, stock, and payments, so it moves once and stays reliable.
- 01Software shaped to the operation
- 02Website, CRM, stock, and payments
- 03Monitored links with clear ownership
The gap
Tools that each work, and still disagree.
The same order is typed into commerce and into accounts. The price on the website and the price in the warehouse diverge. CRM knows a customer the site has never seen. Each product can be fine alone and still cost the business every day.
Custom apps and integration close that gap on purpose. We map the source of truth, build the software the operation needs, and put failure handling on the links so they keep working after go-live.
How the system connects
Assess · Build · Run
- 01AssessMap the current website, software and tools. Written gaps, priorities and a plan to approve.
- 02BuildImplement against scope, milestones and acceptance criteria.
- 03RunOperate, fix and extend the system after go-live.
Outcomes
What changes when this is in place.
- 01
A single path for the record
Orders, customers, stock, and payments have an agreed source of truth and a documented way to move.
- 02
Software shaped to the work
Portals, internal tools, and operational apps cover the jobs the existing products do not, without a pile of side spreadsheets.
- 03
Fewer silent errors
Sync and API links report when they fail. Price, stock, and customer mismatches surface instead of hiding in a handoff.
- 04
Links someone owns
Field maps, credentials handling, and runbooks sit with you, and with the team that stays for Run.
Capabilities
What the work covers.
Connect-first. We extend the stack you already run, and add custom software where the operation has a real gap.
- 01
Flow and field mapping
Which system owns each field, what triggers a write, and what happens when a value conflicts.
- 02
Custom operational software
Apps and portals for ordering, approvals, catalogues, or internal work the off-the-shelf tools do not cover.
- 03
Commerce, CRM, and accounts links
Website, ERP, CRM, stock, and payments connected with an owner for each direction of data.
- 04
Failure handling
Retries, alerts, and a visible queue for records that did not sync, so a break is an operational event.
- 05
Change control
When a catalogue, price list, or vendor API changes, the link has a place to be updated under Run.
Tools in live work
- Accounts software
- Commerce platforms
- Stripe
- CRM APIs
- PostgreSQL
In the programme
Assess, build, then stay.
01
Assess
Inventory systems, fields, volumes, and the failures that already happen. The plan names the source of truth before anyone writes a sync.
02
Build
Implement the app or the integration against milestones and acceptance tests, including a failure case, not only the happy path.
03
Run
Monitor, fix, and extend as catalogues, tools, and volumes change. The same team holds the map.
What’s included
The delivery, in writing.
- Written map of systems, fields, and sources of truth
- Custom app or portal scoped to the operational gap
- Sync or API links with ownership per flow
- Failure handling and a way to see what did not sync
- Acceptance tests for the live paths, including a break
- Documentation and access notes you own
- A run plan for changes after go-live
Outside this service. Replacing a working stack before Assess shows that a replacement pays for itself.
What keeps working
Links that survive the next catalogue change.
An integration is durable when someone can see it fail, fix the record, and update the map when the business changes.
The map stays current
Field ownership and flow notes are part of delivery, and monthly care keeps them aligned with the live systems.
Failures are visible
A broken sync raises an alert and leaves a record you can repair. It does not fail quietly overnight.
The stack can grow
New tools join the same map. You do not restart the programme every time a vendor is added.
FAQ
Practical questions.
Do you only work with the tools we already have?
We choose tools for the requirement — accounts, commerce, CRM, and custom software — and document the links so they can be operated.
Will you replace our current stack?
We connect first. A replacement is recommended only when Assess shows the current tool cannot support the outcome.
Who maintains the links?
The same team, under monthly care. Monitoring, fixes, and vendor changes stay with the people who built the map.
What do we receive at handover?
The software or integration, the field map, access notes, and the acceptance record. You own the delivered work.
Discuss apps and integration
Tell us which service the operation needs. We map it into Assess, Build, and Run, and stay responsible after launch.