Hi — I’m Runze, I run RunzeWorks, a small automation studio. This is squarely in my wheelhouse — Brevo + Make + WordPress migrations are bread-and-butter work for me, and posts with this many moving parts are exactly the kind I like.
Transparency: we’re a new studio, so instead of client work under NDA, here are builds I’ve engineered that map to your stack — happy to walk you through any on a call or send a Loom:
1. Error-logged lead pipeline (Make): intake webhook → dedupe/enrichment → routing → CRM sync, with a separate error branch on every module and auto-retries. Duplicate prevention enforced at both scenario and database level.
2. Airtable-backed reporting engine (Make + Sheets → branded PDF): multi-source pull into a relational base — linked records and formulas doing the heavy lifting.
3. AI voice agent front desk (n8n + Twilio + ElevenLabs + GPT-4): missed-call capture, transcription, qualification, booking, Slack summary.
On your scope specifically — how I’d approach it:
- Mailchimp removal: audit first (find every place Mailchimp is wired in — forms, footers, hidden scripts, API keys in other tools), then remove cleanly so nothing breaks silently.
- Mailchimp → Brevo migration: contacts and lists first (dedupe on import — Mailchimp exports always carry duplicates), then campaigns/templates re-created in Brevo rather than copy-pasted, since the merge-tag syntax differs and paste-imports break subtly.
- Brevo ↔ Make connection: Brevo’s API via HTTP modules in Make (I prefer raw HTTP over pre-built connectors when auth gets non-standard), webhooks for inbound events, and a dedupe check on email before every contact create.
- Lead capture (pop-ups, forms, sign-up pages): form → Make → Brevo, mapped by field key not position, with a hidden honeypot and error branch that alerts us, never the visitor.
- Testing: I submit test leads through every path, verify in Brevo, then deliberately break one to confirm the alert fires — you get the evidence, not just my word.
I also leave you with short documentation of each configuration (what connects to what, and what to do if it breaks), as you mentioned.
Happy to start with a paid audit of the current setup if useful — you’d get a written map of what exists, what’s broken, and the fix order before committing to the full project.
Runze — RunzeWorks