The systems layer I work across

The work often connects commercial systems, analytics, content operations, web delivery, and agentic development workflows into one clearer operating view.

Commercial operations

CRM, pipeline, lifecycle, and qualification systems.

HubSpotCRM workflowsPipeline designLead scoringLifecycle flows

Analytics & demand

Measurement, acquisition signals, channel performance, and decision-quality reporting.

GA4Google Tag ManagerGoogle AdsLinkedIn AdsSEOAttribution logic

Web & content operations

Static sites, content systems, localization workflows, landing pages, and delivery infrastructure.

ContentfulNetlifyLokaliseLanding pagesWeb performance

Agentic development environment

Development and analysis workflows used to inspect, automate, prototype, and iterate technical systems.

VS CodeGitHubCodexAstroDockerPython / PandasAutomation workflows

How I Work

The Growth Operating Method

The methodology is consistent across every engagement. What changes is the depth, the constraints already in play, and how far into execution the work needs to go.

  1. 01

    Discovery & Diagnosis

    Strong hypotheses come from understanding the current system: where signal is lost, which tools are trusted, and where the team is compensating manually.

    Creates the hypotheses Growth Strategy
    Get the PDF

  2. 02

    Strategic Framework

    A clear measurement model has to exist before experimentation begins. Goals, KPIs, ownership, and decision thresholds must be agreed before testing.

    Defines the measurement model Experimentation & Analytics

  3. 03

    Implementation & Optimization

    Automation and optimization are useful only when they improve execution quality, influence revenue, and reduce employee workload.

    Improves execution quality Marketing Automation / Process Optimization

  4. 04

    Knowledge Transfer

    Knowledge transfer works when the team can operate the system without the consultant. Reusable documentation and standards make the implementation easier to maintain.

    Packages reusable systems Technical Implementation

Operating inside constraints

Most companies are not starting from a clean slate. They inherit legacy tools, fragmented workflows, historical decisions, team dependencies, and technical debt.

Useful work respects those constraints. It does not pretend the business can be rebuilt from zero; it identifies the constraints that matter, the ones that can be changed, and the sequence that makes improvement realistic.

Operating principles

  • Systems need ownership. Processes, tools, and channels only work when the right people have enough clarity, authority, and continuity to operate them well.
  • Diagnosis before prescription. Recommendations should be grounded in business context, data quality, team workflows, and technical constraints.
  • Execution is organizational, not just tactical. Campaign quality depends on coordination between strategy, talent, resources, tooling, localization, and decision-making.
  • Clarity over reporting theatre. Metrics and dashboards should make decisions easier, not create more noise.
  • Practical progress over perfect models. The work should be clear enough to act on, structured enough to improve, and honest about uncertainty.