Lead routing
HubSpot → BigQuery: lead score crosses the threshold, the workflow flips the lifecycle stage. n8n hands it to Claude via MCP for the brief, Slack pings the AE.
Marketing Engineering
Pipelines that take over the manual work between your tools.
HubSpot, n8n, Claude, BigQuery, Measurement. I build the stack between your data and your sales team.
Five layers.
Each layer runs on its own. Together they're one pipeline.
- 01
HubSpot
Where your contacts, deals and lifecycle stages live.
- 02
n8n
Self-hosted. Connects the tools HubSpot doesn't reach on its own.
- 03
Claude
Writes the brief, scores ICP fit, wired into the record via MCP.
- 04
BigQuery
The warehouse where every event lands.
- 05
Measurement
Server-side tracking and attribution, without leaking data to third parties.
Examples
Reporting
HubSpot and Google Analytics flow into BigQuery via Coupler.io, Looker Studio reads straight from it. One dashboard instead of CSV exports.
Intake
A form submission comes in: n8n creates the Asana task, the briefing doc lands in Google Drive, Slack pings the team. Nobody retypes anything.
CRM sync
Salesforce and HubSpot stay in sync via n8n. Conflicts surface as a Slack alert instead of silently disappearing.
How it works.
Four weeks. One Slack channel.
Diagnosis → Foundation → Build → Handover. Each week, a piece that runs.
- IWeek 1
Diagnosis
I look at what you have and where it breaks. The week ends with a plan: what gets built, in what order.
- IIWeek 2
Foundation
The scaffolding goes up. Structure, integrations, the path the data takes.
- IIIWeek 3
Build
It runs end to end for the first time. You watch it work, I tune where it pinches.
- IVWeek 4
Handover
You get the docs, and I walk you through all of it once. After that it runs on your side, not mine.
FAQ
What does a site or pipeline at brimbreak cost?
Pricing on request. Sites are quoted per build, whether one-pager or multi-page. Pipelines per scope. Send me your context and you'll get a ballpark.
Who does the work?
Steven Dörr, marketing engineer based in Passau. Concept, code and handover all come from one place, with a fixed ship date.
How long does it take?
Typically four weeks, for a site as for a pipeline. Diagnosis in week 1, foundation in week 2, build in week 3, handover in week 4. Larger scopes scale linearly.
What happens after launch?
Optional €19/month maintenance mode: Vercel Pro hosting, a Lighthouse audit each quarter, security patches, a bugfix pool. Cancel anytime. Details at /hosting.
Which tools do you use?
Next.js and Vercel for sites. HubSpot, n8n, Claude, BigQuery and Measurement for pipelines. The full stack audit happens in the first call.
Who is this for?
SMBs in the DACH region who want a site that holds up. And B2B SaaS RevOps teams who need a pipeline. Functional buyers, not aesthetic buyers.