Systems that talk to each other
WordPress, Telegram and the accounting all hang together. A post is created and published without anyone opening an interface.
Programs that keep each other informed.
I connect your programs to each other so the same information is current everywhere — without anyone copying data across by hand.
In many companies the programs run side by side without talking — CRM, project management, accounting, marketing platforms, and more. I build custom API integrations that let these programs pass data and changes to one another, so nobody has to reconcile them.
Where data gets stuck today
Every program in its own silo
CRM, accounting, project management, and marketing don't know each other — only the people in between do.
Copy and paste as part of the job
The same address, the same order, typed in three times — and three chances to swap two digits.
Numbers that contradict each other
Nobody knows which version is right until someone puts both systems side by side.
From the CRM to stock levels
Keeping CRM and marketing in sync
Keep your CRM and your marketing software up to date with each other
Online shop
Handle orders from your online shop without any intermediate steps
Financial data
Pull together and analyse financial data from several sources
One record per customer
Merge customer data from every channel into a single record
Stock levels
Keep stock levels consistent across several sales channels
Where there's no ready-made integration
Set up your own webhooks for services that don't come with a suitable integration
Enter it once, and every program involved has it
Unified data flow
Each record is entered once, and from then on every program involved knows about it.
No more retyping
Whatever is created in one program, the sync carries over into the others. Nobody copies anything by hand.
Custom middleware
When off-the-shelf integrations fall short, I build the connecting piece myself — around the interfaces your programs actually offer.
Sync as soon as something changes
Where your programs support it, they notify each other of changes straight away (via webhooks).
Five steps from first call to handover
- 1
Intro call
30 minutes, free, booked through my calendar. You tell me which process is costing you time.
- 2
Process review
Together we work out which process is worth tackling first and what it will take.
- 3
Prototype
Within days rather than months, there's a first version for you to try out.
- 4
Pilot
The solution runs in day-to-day operations with your team. Any rough edges get smoothed out.
- 5
Handover and support
Documented, monitored, and developed further if you want. You're not left to deal with it on your own.
Technologies used
REST · GraphQL · Webhooks · Node.js · TypeScript · n8n · Make · Supabase · PostgreSQL
Further reading
Frequently asked questions
What you'll want to know first
What if there's no ready-made integration for my program?
Then I build the connecting piece myself — around the interfaces your programs actually offer. For services that don't come with a suitable integration, I build custom webhooks.
How quickly is the data up to date everywhere?
Straight away, where your programs support it: they notify each other of changes through webhooks. Each record is entered once, and from then on every program involved knows about it.
Roughly how much does it cost?
That depends on what needs to be built. We work it out in the free intro call.
How long does it take?
You get a first working prototype in days, not months.
What happens in the intro call?
Half an hour, free, booked through my calendar. You tell me which process is costing you time today; together we look at which one is worth tackling first — and whether I'm the right person for it.
Attila Arndt · Triple A Digital, Cologne
Which data does someone at your company still copy across by hand?
Pick a time that suits you. In the intro call, we'll work out which process is worth tackling first — and whether I'm the right person for it.
Or email me directly: hello@tripleadigital.de · I reply within 48 hours.