Services for Schools
Ordering and reporting for schools buying services from the borough of Hounslow, simple at the front and serious behind it.
Read the case study: Services for Schools →
Integrations and data
Your website is the front end of everything else you run. A CRM, a payment stack, a finance system and a membership database. We connect them with one system of record per field, queued syncs that never lose a transaction, and failures that reach a named person.
Where you're starting from
- Salesforce
- Dynamics 365
- Raiser's Edge
- Xero / Sage
Where you go next is decided in the Blueprint. Sometimes the answer is to upgrade.
Which situation are you in?
Duplicated
The same record in three places
The CRM, the email tool and the website each hold a version of the same person, and reporting becomes an argument about whose number is right.
We agree one system of record for each field.
Manual
Spreadsheets in the middle
Exports and imports that someone runs every Monday. They work until that person is on leave, and nobody can say when the data was last right.
We replace the manual step with a logged sync.
Fragile
Syncs that fail silently
An integration that drops a payment or a booking without telling anyone. You find out from a customer, weeks later.
We queue, retry and alert a named person.
What usually goes wrong, and how we stop it
Integrations fail at the edges: a field that means something different in each system, a timeout nobody planned for, a change on the other side that nobody announced.
1
System of record
For every shared field, one system that owns it, written down and agreed by the teams that use it.
2
Lost transactions
Queued, retried syncs, so a payment or booking is never lost because another system was briefly down.
3
Silent failure
Errors logged and routed to a named person, with enough detail to fix them without a developer.
4
Data protection
Only the fields each system needs, consent recorded at the point of capture, and access reviewed.
5
Vendor changes
Integrations built against documented APIs and monitored, so an upstream change is caught rather than discovered.
6
Support after launch
Monitoring and ongoing care through WebsiteSupport.io if you want it.
How an integration project runs
- InventoryEvery system, data flow, owner and manual step listed.
- DesignSystem of record per field, sync direction, error handling.
- BuildIntegrations built and tested against copies of real data.
- CutoverOld syncs retired, new ones switched on, parallel checks.
- MonitorAlerts, logs and a handover to the people who own each system.
Integration work we've delivered
Beat the Street
Tens of thousands of activity readings a day from a single borough, turned into leaderboards children actually want to check.
Read the case study: Beat the Street →Questions
If yours isn't here, it's usually quicker to ask on the phone.
Can you integrate without a full rebuild?
Yes. Integration work is often delivered on its own, on top of the platform you already have.
Which systems do you work with?
Commonly Salesforce, Dynamics 365, Raiser's Edge NXT, Stripe, GoCardless, Xero, Sage, Entra ID and GA4. If yours has a documented API, we can usually connect it.
What happens when a sync fails?
It is queued and retried. If it still fails, a named person is told what failed and why, and nothing is lost in the meantime.
Who owns the integrations after launch?
You do. We document each one and hand it over, and WebsiteSupport.io can monitor and maintain them if you want.
Start with a Blueprint!
Three weeks, from £5,500 + VAT. Credited against the build, and yours to take to any supplier.