Forward-Deployed CRM Architect

Rev Ops is changing fast, and so is the way GTM processes get built and maintained inside the CRM. This role puts you on the front edge of it: forward-deployed in our clients' Rev Ops teams, building and running their GTM systems in a genuinely AI-first environment.

GTMBase is an AI-first GTM engineering and Rev Ops agency. We help post-PMF B2B companies (€8M to €50M ARR, 5+ reps) whose go-to-market is over-performing their systems. Reps do manually what should be automated, sales and marketing data doesn't connect, and leadership can't trust the reporting.

We combine strategic GTM thinking with hands-on technical build, and we fix the foundation before running campaigns.

We deliver across Four Pillars:

We've done this for clients including Groupon, Blinkist, Booksy, and Sendify. We work in small pods, with a Strategist, a CRM Architect, and a GTM Engineer.

We run the company on Claude Code. It's our operating system: client context, playbooks, automations, and delivery all live in it, and AI is the default way we work rather than a bolt-on. You'll work this way too, and get very good at it.

You're the person who turns our GTM strategy into a CRM that actually works. Most clients run their entire revenue motion on Hub Spot or Salesforce, and the quality of that system runs through this role: how clean the data is, how well leads route, whether leadership can trust the reporting.

Here, "Architect" means architecting inside the CRM: the object model, pipelines, workflows, and automations. The GTM and revenue strategy is set with you in your pod, not by you alone, and you build it with real craft.

You're forward-deployed: you embed with clients' Rev Ops and sales teams and build inside their live CRM.

You'll build and maintain GTM process and automation inside our clients' CRMs, mostly Hub Spot. Working from the direction set in your pod, you turn requirements into a clean, well-built system the sales team can rely on.

One week you're building a client's lead lifecycle and routing. The next you're debugging a broken automation, untangling duplicate deals, or shipping a dashboard a CRO asked for. You move across several client instances at once without dropping threads.

You're a builder with an admin's discipline. You know the object model, not just the UI. You sweat the details others miss, you test before you ship, and you document what you build so the rest of the pod can run it. When something breaks, you find the root cause and fix it properly.

Your pod is you (CRM Architect), a Strategist who sets direction and hands you requirements, and a GTM Engineer. You and the GTM Engineer are both builders, but you own different layers:

• You (CRM Architect, Pillar
  2): the GTM process inside the CRM. Hub Spot/Salesforce architecture, lifecycle, routing, deal logic, automation, reporting, data integrity. You live in Hub Spot, Salesforce, Operations Hub, and n8n.
• GTM Engineer (Pillar
  1): the data layer. Enrichment, scraping, signal detection, list building, custom research agents. They live in Clay, Apify, custom scrapers, and data APIs.

Think of it as the data into the CRM (GTM Engineer) versus the system it lands in and the process the sales team runs on (you). You don't need to be a Clay or Apify expert. You just need a solid working understanding of what a GTM Engineer does, enough to spec what you need, integrate their output cleanly, and know what's possible.

• Architect and build in client Hub Spot instances: information architecture (objects, associations, lifecycle stages, pipeline structure), workflows, deal logic, lead scoring, routing, properties, and permissions
• Build and debug automations across the GTM stack:
  Hub Spot workflows, n8n, APIs, and webhooks. When an automation breaks, you find the root cause rather than just toggling features
• Guard data integrity: deduplication, field validation, association hygiene, and import discipline so reporting and forecasting can be trusted
• Build the reporting leadership relies on: pipeline coverage and velocity, stage-by-stage conversion, and full-funnel dashboards. You know where Hub Spot's platform and paywall limits force a different approach
• Design integrations and data flows between Hub Spot and the rest of the stack (Clay, Aircall, telephony, billing, enrichment pipelines)
• Turn requirements into working builds: take a brief like a 15-minute lead-response SLA and ship the routing system that delivers it
• Keep…