Builds · Side Quests

Systems for how a revenue team plans, sells, and learns.

I design and build GTM systems that turn fragmented information into structured intelligence and workflows a person can use. The work joins enterprise sales, product thinking, and technical implementation, from competitive intelligence and customer feedback to security research, enablement, and account-based GTM.

Builder / Side Quests

Explore all projects

Filter by focus or lifecycle stage, then open a project for the problem, the contribution, and one next step.

One system

GTM Revenue OS

Planning, coverage, and pipeline review for one fictional company. The figures are planning fixtures. These workflows belong to the same system, and each write-up stays on its own page.

The working planner is a separate app. These pages explain the decisions. They do not save a scenario, export a file, or open that app.

Request a walkthrough

4 matching projects

  • Revenue Strategy & Operations

    Distribute · Workflow design

    Partner GTM Engine

    Match partner account lists on domain, leave uncertain rows for a person, and show whitespace.

    How it works

    Intended value: Whether to co-sell, resolve a conflict, or leave the account alone until the domain is confirmed.

    Contribution: I designed the match rule from channel work: a similar name is not a confirmed account.

    A written example on this page.

    One fictional match.

    Recorded stage: Workflow design. Lifecycle: Distribute.

    The example does not upload a spreadsheet or sync a CRM.

    No product screenshot

    This card links to the case study. It is not a running interface.

    Case study · Preview unavailable
    Explore the project: Partner GTM Engine
  • Revenue Strategy & Operations

    Decide · Software project

    Revenue Planning Simulator

    An editable planning year for a fictional company. Retention, expansion, and the new-ARR residual are formulas. The dollars are fixtures.

    How it works

    Intended value: Whether the residual is already covered, or the plan still needs capacity and pipeline.

    Contribution: I built the planner so retention, expansion, and new ARR stay separate formulas.

    Next.js, TypeScript, and Postgres in the separate planner. The formulas are deterministic.

    Recorded stage: Software project. Lifecycle: Decide.

    The planner is a separate app. This page does not save a scenario or export a file.

    No product screenshot

    This card links to the case study. It is not a running interface.

    Case study · Preview unavailable
    Explore the project: Revenue Planning Simulator
  • Revenue Strategy & Operations

    Measure · Software project

    Revenue Intelligence

    Pipeline health from stage history, then planned new ARR against bookings and what is still required. The book is synthetic.

    How it works

    Intended value: What is still required after bookings, without treating a stale stage as open pipeline.

    Contribution: I wrote the queries so win rate comes from the close, not the current stage.

    Next.js and PostgreSQL in the separate dashboard.

    Recorded stage: Software project. Lifecycle: Measure.

    The dashboard is a separate app. This page does not query a database.

    No product screenshot

    This card links to the case study. It is not a running interface.

    Case study · Preview unavailable
    Explore the project: Revenue Intelligence
  • Revenue Strategy & Operations

    Enable · Software project

    GTM Operating Plan

    Territory coverage and AE capacity for the same fictional company: where to add sellers, and the proven pipeline each hire should be built on. Potential figures are estimates.

    How it works

    Intended value: Whether the plan is a coverage plan or a capacity plan.

    Contribution: I built the operating plan so a hiring change moves capacity and leaves bookings still.

    Next.js and PostgreSQL in the separate operating plan. Same capacity formulas as the planner.

    Recorded stage: Software project. Lifecycle: Enable.

    The plan is a separate app. This page does not assign live accounts.

    No product screenshot

    This card links to the case study. It is not a running interface.

    Case study · Preview unavailable
    Explore the project: GTM Operating Plan

Connected GTM systems

From market intelligence to customer execution.

These projects cover different parts of the same motion. Selecting one shows its inputs and output. The lines are a map, not a data integration.

Explore how the systems connect

Market and customer intelligence

GTM and product execution

Field enablement

Dashed links are a conceptual map. These projects do not exchange data.