// Woodstock Ops // Proof of Work
Real operational puzzles solved. Deliberate, sequenced systems integrations that let scaling organizations work in harmony.
Featured Studies
Bringing acquired systems under unified operations without client or delivery friction.
Building automated lead enrichment, segmentation, and qualification pipelines.
Untangling years of tool growth into Notion and time tracking systems.
Case Study 01
Over four years, Brainlabs acquired six specialist agencies — each with its own way of working, its own tools, and its own idea of what "organised" looked like. The disciplines ranged from influencer marketing and SEO to paid social, PPC, CRO, and creative production. No two were the same.
My job was to bring each one into our global systems without disrupting the client work that was happening while we did it.
Each acquisition arrived with its own stack. Some were running three-person operations out of spreadsheets and shared inboxes. Others had invested heavily in tools that didn't talk to ours. All of them had live client relationships that couldn't afford downtime, confused invoicing, or a CRM that had just eaten their pipeline data.
The pressure was straightforward: get them operational on our systems as quickly as possible, without anyone — internally or client-side — noticing the join.
Each integration started the same way. Before touching anything, we spent time understanding how the incoming team actually worked — not how their tools were configured, but how people moved work through the business day to day. That distinction matters. You can migrate a CRM in a weekend. Changing how a team thinks about their pipeline takes longer, and forcing it too fast breaks things.
From there we built a sequenced plan for each agency. CRM first — getting contacts, deals, and pipeline into HubSpot cleanly, with the right structure for their specific sales motion. Then time-tracking and resourcing, so finance could see hours and utilisation without running two sets of books. Then contract management, project tooling, and finally the reporting layers that leadership needed to see the whole business in one place.
We ran each integration in parallel with normal operations. Nothing was switched off until the new system was verified and the team was comfortable. In most cases, the transition happened on a Friday and by Monday it was just how things worked.
A few acquisitions came with data that was genuinely difficult — years of inconsistent naming conventions, deals logged against the wrong companies, contacts duplicated across three systems. One agency had been running their entire client operation out of a single shared Gmail inbox. We untangled all of it, but it took longer than the clean ones and required some frank conversations about what data was worth migrating versus what was better left behind.
The influencer agency was a specific challenge — their workflow didn't map neatly onto how we'd built our project management setup, which was designed around paid media. We had to extend our tooling to accommodate a deliverable-based model rather than an hours-based one. That involved custom configuration in both our project management and time-tracking platforms, and building a new reporting view that finance hadn't needed before.
Six agencies, all operational on shared global systems. Finance could consolidate reporting across the group. Leadership had a single view of utilisation, pipeline, and delivery. Client teams didn't have to think about it.
The thing we were most careful about — and the thing that I think made the difference — was the order of operations. There's always pressure to move fast after an acquisition. We moved deliberately instead, and nothing fell over.
Case Study 02
[Case study details placeholder]
We built a custom automated outbound pipeline that acts as a multiplier for the sales team. The project involved connecting multiple modern tech APIs, enriching company signals, and automating deal logging back into the CRM.
The sales team spent hours manually finding, researching, and qualifying potential deals, leading to slow outreach times and high pipeline churn.
Replaced manual processes with automated routines. Prospect details are captured, enriched using database APIs, qualified by customized AI agents, and presented cleanly as validated pipeline deals inside their HubSpot environment.
Hours saved every single week, allowing the business to redirect creative commercial energy away from mechanical research tasks and directly into client conversations.
Case Study 03
[Case study details placeholder]
Designed and unified a scaling business's operational tech stacks. We brought three disconnected, confusing tools under a structured workspace, connecting team members directly to live resources.
Teams were tracking hours, tasks, and budgets across three distinct and uncoordinated platforms. Leadership had no clean way of checking utilization or real-time project progress.
Audited and dismantled redundant subscriptions. Migrated core business resource planning, contract management, and task systems into Notion, with synchronized back-end time logging.
One single source of truth for the entire company. Immediate visibility into profit margins, resourcing allocation, and project timelines across all operational delivery groups.