ERP, CRM and third-party integrations · Build
Your ERP or CRM stays, and new software works alongside it
We connect new software to the system you keep, and shared data such as invoices matches in both. A construction ERP we built syncs six kinds of data with SAP.
EngagementHourly · remote
Hours9–18 CET · 4 h overlap
StackTypeScript · Node.js · NestJS
Proof3 case studies
The service in 4 parts
01 · Who it’s for
A company that needs new software to work alongside a system it won’t replace: an ERP, a CRM or a national registry.
02 · What we’ve built
- A construction ERP connected to SAP, which the company kept. Instead of a monthly export, the integration carried customers, items, orders, invoices, stock and finance.Case study 16 →
- Custom purchase and contact forms for a Swedish SaaS company, built against the HubSpot API. Each submission passes on the tracking cookie, so marketing can attribute it to the visit that produced it.Case study 17 →
- A passport system for a West African national identity authority checks applications against the national registry. The connection requires keys, digest authentication, single-use tokens and a request from an allowed IP address, so someone holding a stolen key still cannot get in.Case study 09 →
03 · How we work
01 · YOUR SYSTEM STAYSThe system you keep remains the one everything else starts from. For the construction company, that system was SAP.
02 · FAILURES WITHOUT AN ERRORSome failures raise no error, so we test for them on purpose. A form that loses its tracking cookie still submits, but marketing can no longer tell which visit produced it.
04 · Stack
TypeScriptNode.jsNestJSNext.jsPostgreSQLSAPHubSpot CMSHubL
Proof
Where we’ve done this before
Case study 16 · Business systems150,000A construction ERP connected to SAP, which the company kept. Instead of a monthly export, the integration carried customers, items, orders, invoices, stock and finance.Read the case study →Case study 17 · Business systemsZero deploysCustom purchase and contact forms for a Swedish SaaS company, built against the HubSpot API. Each submission passes on the tracking cookie, so marketing can attribute it to the visit that produced it.Read the case study →Case study 09 · Identity1 working dayA passport system for a West African national identity authority checks applications against the national registry. The connection requires keys, digest authentication, single-use tokens and a request from an allowed IP address, so someone holding a stolen key still cannot get in.Read the case study →
FAQ
Questions about this service
In most cases, no. Replacing a system the business runs on is a separate decision with its own reasons. On the construction ERP, SAP stayed.
Keeping the two systems in agreement. When stock or an invoice differs between them, someone makes a decision on the wrong number.
Embedded, when the design allows it. A custom form gives you the design, but hidden fields, validation, error states, bot protection and the tracking cookie become your job, along with every later change in how the CRM expects submissions.
Next step
Describe the problem and we’ll come back with three options.
The first call takes 30 minutes, and you’re under no obligation.