WHEN THE PLATFORMS DON'T TALK TO EACH OTHER, I make them.
Stripe, Twilio, Retell AI, Mapbox, OpenAI — the API and integration work behind the platforms I build. Solo, in West Wales, on Webflow and Bubble.
Most no-code builds break at the seams. The integration is the build.
The money side, done properly.
Stripe · Stripe Connect · Stripe Identity · GoCardless · Chargebee
Phone agents, content generation, transcription.
Retell AI · OpenAI · Anthropic · ElevenLabs · AssemblyAI
Email, SMS, voice — wherever the customer is.
Twilio · Postmark · SendGrid · Slack · Resend · ClickSend
Pickups, deliveries, catchment areas, what3words.
Mapbox · Google Maps Platform · what3words
Logins that don't get in the way.
Auth0 · Magic · Stripe Identity · Persona
Search that's actually fast. Data that lives somewhere sensible.
Algolia · Typesense · Airtable · Xano · Supabase
The internal tools your team already opens every morning.
HubSpot · Notion · ClickUp · Calendly
The glue. Sometimes Make, sometimes raw webhook orchestration.
Make · n8n · Zapier · custom webhook handlers
Integrations aren't features. They're commitments.
Map the flow
Before any code, we draw it. What triggers what, what data moves where, what happens when it fails. Most integrations break because nobody asked the second question.
Pick the right layer
Sometimes it's native, sometimes Make, sometimes a custom webhook. I'll tell you which, and why. No-code where it earns its keep, real code where it has to.
Talk it through
Idempotency keys, retry logic, dead-letter handling, signed webhook verification. The stuff that makes the difference at 2am on a bank holiday.
Hand it over with the wiring labelled
A screen recording, an integration map, every key and webhook documented. Your future developer will thank me.
Built and live, paying customers, real failure modes.
Stripe Connect with platform fees, split payouts, and webhook-driven order state. Contactless QR payments for rural businesses with laser-etched Welsh slate plaques. Built on Bubble, live in fields across the UK.
Stripe Connect · Webhooks · Bubble · Stripe Identity
An AI voice agent that answers restaurant phones, takes orders, and pushes them into the Yonder dispatch system. SIP trunking via Twilio, conversation logic in Retell, sequential driver dispatch in Bubble. Replaces the phone shouts at peak Saturday.
Stripe Connect · Webhooks · Bubble · Stripe Identity · Webflow
A housing compliance platform structured to HACT data standards, built ahead of Awaab's Law. Tenant evidence upload, compliance scoring, and integration paths into housing association stacks.
HACT · Compliance · Bubble · Document handling
What people ask me before they hire me.
Yes — HonestyBox runs on it. Platform fees, split payouts, refunds, Stripe Identity, webhook-driven order state. I've built it three times now, including with branded onboarding for the platform's customers.
For reads and simple writes, yes — Webflow's Logic and native API actions go further than people think. For anything stateful or transactional, I usually pair Webflow with Bubble or a serverless function. I'll tell you which on the first call.
Yes. Yonder uses Twilio SIP to route restaurant calls through a Retell AI voice agent, with fallback to human staff. SMS, voice, and number provisioning all in.
Retell AI for the conversation layer, Twilio for the telephony, webhooks back into Bubble for the order data. The hard part isn't the integration — it's designing the conversation so it actually works at 7pm on a Friday.
Always. Signed verification, idempotency keys, retry queues, and dead-letter logging. If a webhook fails silently, it's worse than not having one.
Often, yes — usually via a middleware layer (Make, n8n, or a custom Node function). I'll look at the legacy API first and tell you honestly whether it's a two-day job or a two-week one.
Yes. I take on integration-only projects — typically rescuing a Bubble or Webflow build where the third-party piece has gone wrong. Fixed quote, usually 1–3 weeks.
West Wales — Cardigan Bay. Roughly half my work is UK, half international. Async-friendly, two working days for replies.
Got an integration that's bleeding money or time?
One email. The two systems you're trying to connect, what's gone wrong, and what success looks like. I reply within two working days.