Case Study

Building a Revenue Engine From Zero Inside a Seed-Stage B2B Data Company — Through the Teeth of GDPR

Published 2026-03-17

There is a particular kind of engagement that defines my career more than any other: walking into an environment where nothing exists and building everything. Not inheriting a half-built marketing function with legacy systems and institutional knowledge. Not optimising an existing engine. Building. From zero.

This is the story of the most consequential of those builds — the one where the company I joined as employee number three went on to raise $130M+, reach a £319M valuation, employ 550+ people, and generate$ 83M in annual recurring revenue. The infrastructure I built in the first fourteen months laid the commercial foundation for all of it.

I'm going to tell this story in detail because I think it illustrates something important about what "first marketing hire" actually means in practice — not the LinkedIn version where someone lists a title and a growth number, but the lived reality of building every system, writing every piece of copy, configuring every workflow, designing every asset, and standing on a conference stage representing a company that three months earlier was three people in a small office in Bermondsey.

The Starting Point

When I joined, the company was a seed-stage B2B data intelligence platform. Three people. A working product with genuine technical differentiation — including an AI patent application. A seed round that gave the company runway but not certainty. And absolutely nothing on the commercial side.

No website beyond a placeholder. No CRM. No marketing automation. No content. No brand identity. No sales collateral. No event programme. No pipeline. No attribution infrastructure. No team beyond me.

I was the first marketing hire. The title was Head of Marketing, and I was the only marketer.

What made this engagement unique — and what elevated it from a standard startup marketing build to something genuinely high-stakes — was timing. This was 2017-2018, and GDPR enforcement was months away.

For a B2B data intelligence company, GDPR wasn't background regulatory noise. It was an existential question. The company's core product involved collecting, structuring, and selling business contact data. GDPR was about to fundamentally reshape what data companies could collect, how they could store it, who they could sell it to, and what consent meant in the context of B2B contact data.

The dual nature of this situation is important to understand: GDPR simultaneously threatened to make the product illegal and created the market opportunity that would define the company's trajectory. Before GDPR, data quality was a nice-to-have. After GDPR, data compliance became a must-have — and every company in Europe needed a data vendor they could trust to be compliant. The companies that positioned themselves credibly as GDPR-compliant data providers would win the entire market.

That's the strategic backdrop against which everything I built was designed.

What I Actually Built

CRM Architecture: Salesforce + HubSpot

The first system decision was CRM architecture. This might sound like a boring infrastructure choice, but in a company with no existing data, no pipeline, and no commercial process, the CRM is the foundation everything else depends on.

I implemented a dual-CRM architecture: Salesforce for the sales pipeline and deal management, HubSpot for marketing automation, content, and lead management. This wasn't a default choice — it was deliberate. The company needed enterprise-grade pipeline management (Salesforce) because the sales process was complex, multi-stakeholder, and high-value. But it also needed a marketing system that could handle content, nurture sequences, forms, landing pages, and lifecycle management without requiring a developer for every change (HubSpot).

The integration between the two systems was designed from day one with clean data flow in mind:

Leads entered through HubSpot via content, forms, events, and paid campaigns
Qualification criteria were defined as explicit predicates — not subjective judgements
When a lead met the qualification threshold, it synced to Salesforce with full attribution data
Pipeline stages in Salesforce had their own predicate logic — each transition required specific, verifiable conditions
Attribution data flowed back from Salesforce closed-won deals to HubSpot campaigns, enabling true ROI calculation

This architecture meant that from the very first lead, I could trace the full journey: which campaign sourced them, which content they engaged with, how long they took to qualify, which sales rep closed them, and what the deal was worth. That level of attribution in a seed-stage company is unusual — most startups don't build attribution until they're post-Series A and already struggling with data quality. I built it before the first campaign ran.

The Company Website

I designed and built the company website on WordPress using ThemeX, writing all the copy myself. This wasn't a design-agency engagement where someone else handled copy and I approved it. I wrote every word on every page — the homepage, the product pages, the about page, the blog templates. I also wrote all the sales emails, marketing emails, nurture sequences, and business materials.

The website needed to do something specific: establish credibility for a company that had none. We were three people asking enterprises to trust us with their data strategy. The website had to project the authority and polish of a company ten times our size.

I designed the site architecture around a content-led approach: the homepage established the value proposition, product pages explained the data model and compliance positioning, and the blog became the content engine that would drive organic traffic and establish thought leadership.

The Content Engine: Case Study Framework and Hero Content Strategy

One of the most important things I built wasn't a system — it was a methodology. I created two proprietary content frameworks that became the company's repeatable growth playbooks for years after I left.

The Case Study Framework was a structured approach to turning customer wins into high-converting content. Most B2B companies produce case studies that read like press releases — vague claims about "improved efficiency" with no specifics. My framework required specific, named metrics at every stage: the situation before, the specific intervention, the measurable outcome, and the business impact in pounds or percentage terms.

This framework was important because case studies were our most effective conversion content. In a market where every data vendor claimed to have "the best data" and "GDPR compliance," concrete case studies with real numbers were the differentiator that moved prospects from consideration to conversion.

The Hero Content Strategy was a framework for creating anchor content that could be repurposed across multiple channels and formats. Rather than producing high volumes of thin content that competed for the same keywords, I focused on creating fewer, more substantial pieces that established authority on specific topics. Each piece of hero content was designed to:

Rank for a specific high-value keyword cluster
Serve as the anchor for a related email nurture sequence
Generate social distribution through shareability
Be repurposed into speaking topics for event programmes
Function as a sales enablement tool that reps could share with prospects

This approach meant that content production wasn't a volume game — it was an architecture game. Every piece served multiple purposes across multiple channels, and each piece reinforced the others.

International Trade Show Programme

I built and ran an international trade show programme with six-figure budgets — over $100,000 in event spend managed during my tenure.

This wasn't attending events and handing out brochures. I designed the entire programme end-to-end:

Booth Strategy: I designed the booth concepts, worked with fabricators on the physical build, created all the visual collateral (banners, displays, handout materials), and planned the flow of the booth experience to maximise lead capture and meaningful conversations.

Collateral Production: Every piece of material used at events — brochures, one-pagers, product sheets, pricing guides, competitive comparison documents — I wrote and designed. These materials had to establish instant credibility with C-level prospects who were evaluating multiple vendors on the same exhibition floor.

Staffing and Training: I coordinated the event team, briefed them on messaging, and ensured everyone could articulate the value proposition consistently. At this stage, "the team" was often just me and one or two colleagues.

Follow-Up Infrastructure: Post-event pipeline management was built into the CRM from the start. Every lead captured at an event was entered with event attribution, enabling me to measure ROI per event and make data-driven decisions about which events to attend in future.

The trade show programme was strategically important for a reason beyond lead generation: in B2B data and SaaS at this stage, physical presence at the right events was a credibility signal. Prospects needed to see us at the events their other vendors attended. It normalised the company in the market and positioned us alongside established players.

I developed a public speaking programme focused specifically on GDPR compliance and data regulation. This wasn't generic thought leadership — it was strategic positioning.

The speaking programme served a specific commercial purpose: reframing GDPR from a threat into a competitive advantage. While other data vendors were anxious about compliance, we positioned ourselves as the vendor that embraced GDPR because our data model was designed for a compliant world.

I represented the company at industry events, speaking on panels about data compliance, the impact of GDPR on B2B data strategies, and how companies should evaluate data vendors in a post-GDPR landscape. Every speaking engagement was designed to reinforce the positioning and drive qualified leads back to the pipeline.

Team Building

During my tenure, I recruited and managed a four-person marketing team: a graphic designer, a copywriter, and a junior marketer. I hired each of them, designed their roles, managed their output, and integrated their work into the broader marketing infrastructure I'd built.

This is worth noting because it illustrates the breadth of the first-hire role. I wasn't just executing marketing — I was building an organisation. Defining job descriptions, running interviews, onboarding new team members, establishing workflows, and creating the documentation and processes that would allow the function to scale beyond me.

The Results

The numbers tell a clear story:

20× MRR growth — from $10,000 to$ 200,000 monthly recurring revenue in 12 months
32% month-on-month average growth rate — sustained, not a spike
6.8× ROI on $104,000 in direct marketing spend
SQLs increased 239% while the budget scaled 293% — meaning we scaled spend faster than SQL growth, but the SQL growth was still dramatically positive
Company grew from ~3 to 40+ employees during my tenure
Infrastructure supported Series A, B, and C funding rounds totalling $130M+

That last point is the one I want to emphasise. The revenue architecture I built during those fourteen months wasn't a temporary scaffolding that got replaced. It was the commercial foundation the company used to grow through three subsequent funding rounds. The CRM schema, the attribution model, the content frameworks, the event programme, the lifecycle automation — all of it continued to operate and evolve long after I left.

As of 2026, the company has 550+ employees, $83M in annual recurring revenue, and a £319M valuation. I'm not claiming credit for everything that happened after I left — hundreds of talented people built on what was started. But the architecture was designed to scale, and it scaled.

What This Engagement Teaches About First-Hire Marketing Roles

The Breadth Problem

Most companies hiring their first marketer don't understand what they're asking for. They write a job description that says "Head of Marketing" and lists 15 responsibilities spanning brand strategy, content production, paid acquisition, event management, CRM administration, analytics, design, copywriting, PR, partnerships, social media, and team building.

The assumption is that the first hire will either do all of these things or immediately hire a team. The reality is neither — you need someone who can prioritise ruthlessly, build foundational systems, and create the infrastructure that allows future hires to be productive from day one.

That's what I did. I didn't try to do everything simultaneously. I built the CRM and attribution infrastructure first (because everything else depends on data), then the website and content engine (because you need a digital presence before you can run paid campaigns), then the event programme (because B2B credibility required physical presence), then the team (because the systems were now in place for additional people to operate within).

Building marketing infrastructure is hard enough. Building it while the regulatory ground is shifting under your feet is a categorically different challenge.

GDPR didn't just affect our product positioning — it affected every marketing system I was building. Email marketing had new consent requirements. Data capture on forms had new disclosure obligations. The CRM needed to handle data deletion requests. Lead sourcing strategies had to account for consent models that didn't exist six months earlier.

I didn't treat compliance as a constraint — I wired it into the infrastructure from day one. The CRM was designed with consent tracking built into the data model. Email nurture sequences included compliant opt-in and opt-out mechanisms. Lead scoring accounted for consent status. Attribution tracked not just the source of a lead but the consent basis under which they entered the pipeline.

This meant that when GDPR enforced in May 2018, we didn't have a scramble-to-comply moment. The infrastructure was already compliant because compliance had been a design requirement, not a retrofit.

The Build-to-Last Problem

The most important decision I made wasn't any specific tactical choice — it was the decision to build infrastructure that would outlast my tenure. Every system, every workflow, every piece of documentation was designed with the assumption that someone else would eventually operate it.

This is harder than it sounds. When you're the only person doing everything, the temptation is to build systems optimised for how you work — shortcuts, undocumented workflows, tribal knowledge. I deliberately avoided this. Every automation was documented. Every CRM workflow had a description. Every campaign taxonomy followed a naming convention that was written down.

When I left, the next marketing leader inherited a working system with documentation. They didn't need to reverse-engineer my thinking or rebuild from scratch. They could iterate on a foundation that was designed to be inherited.

The Pattern

This engagement established a pattern that has defined my career since: I step into zero-infrastructure environments — typically in industries facing regulatory pressure or market disruption — and build the complete commercial operating system. Not advise on it. Build it. Hands on keyboard.

The B2B data platform was GDPR. The EdTech engagement was AI disruption. The Insurtech engagement was insurance regulation. The gaming platform was DFS regulatory upheaval. The pattern is consistent: regulated or disrupted markets, zero existing infrastructure, and the need for one person who can design the architecture and then implement it end-to-end.

If this sounds like your situation — seed-stage with no marketing infrastructure, or growth-stage with broken infrastructure that was never properly designed — I've built this before. Not once. Six times across four industries and fifteen years.

Use Case: B2B SaaS Data Platform — Summary overview of this engagement
Fractional CMO — Embedded marketing leadership with hands-on execution
CRM Architecture — Schema, lifecycle, and automation design
Event Programs — Trade show strategy and execution
Public Speaking — Thought leadership and stage presence

→ Book a Diagnostic Call — I'll tell you what your infrastructure needs to look like.