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

11 matching projects

  • Featured · Technical Systems & AI

    Build · Software project

    Detector Coverage Atlas

    Help security practitioners and technical sellers inspect secret-detection coverage and identify what needs review. Explore a small source-backed comparison sample.

    How it works

    Intended value: What I can claim in discovery, and what I have to leave gray.

    Contribution: I built the sample comparing three sources across five credential types and the rule that an unreviewed cell stays gray.

    Next.js, React, and TypeScript. The rows live in this repository.

    Recorded stage: Software project. Lifecycle: Build.

    The comparison is the table on the case study. A later parser is described there and is not part of this page.

    Try the example: Detector Coverage Atlas
  • Featured · Account & Market Intelligence

    Discover · Used professionally

    Competitive Intelligence Engine

    Help sellers turn competitive research into useful buyer conversations. Explore a source-backed field brief and a proposed review workflow.

    How it works

    Intended value: How to position in this cycle, and what not to claim.

    Contribution: I wrote the briefs and taught them.

    Field documents and a Next.js walkthrough on this page.

    Recorded stage: Used professionally. Lifecycle: Discover.

    The case study walkthrough stays in the browser. It does not monitor sites.

    Try the example: Competitive Intelligence Engine
  • Featured · Account & Market Intelligence

    Distribute · Workflow design

    Account Intelligence

    Help enterprise sellers connect account changes to relevant conversations. Explore a fictional workflow from a signal to a draft, with evidence and assumptions kept separate.

    How it works

    Intended value: Who to contact, what to ask, and what not to treat as fact.

    Contribution: I designed the personal feed and the path from an account change to a draft.

    Next.js walkthrough on this page.

    Recorded stage: Workflow design. Lifecycle: Distribute.

    Copy stays in the browser. Planned research sources are named on the case study and are not called from this page.

    Try the example: Account Intelligence
  • Featured · Customer & Product Intelligence

    Discover · Workflow design

    Customer Feedback Intelligence

    Group customer requests into themes with the account still attached.

    How it works

    Intended value: What to prioritize, and what to tell the customer who asked.

    Contribution: I run the sales-to-product loop in the field and designed this review.

    Next.js walkthrough on this page.

    Fictional accounts.

    Recorded stage: Workflow design. Lifecycle: Discover.

    Confirming a theme stays in the browser and does not send a message.

    No product screenshot

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

    Case study · Preview unavailable
    Try the example: Customer Feedback Intelligence
  • Customer & Product Intelligence

    Launch · Workflow design

    Product Release Intelligence

    Turn a release into reviewed lines for Sales, Customer Success, and customers.

    How it works

    Intended value: Inform, push adoption, re-engage, expand, renew, run a proof of concept, or say nothing.

    Contribution: I designed the question set I use with the field.

    The questions on this page.

    Recorded stage: Workflow design. Lifecycle: Launch.

    This page is that question set.

    No product screenshot

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

    Case study · Preview unavailable
    Explore the project: Product Release Intelligence
  • Sales Enablement & Productivity

    Enable · Workflow design

    Truffle Camp

    A secrets-security learning path with a written module and one synthetic practice question.

    How it works

    Intended value: Whether this person can talk to a Head of AppSec without overclaiming coverage.

    Contribution: I designed the curriculum on top of enablement I have already done with teams.

    A written module and one practice question on this page.

    Recorded stage: Workflow design. Lifecycle: Enable.

    The knowledge check stays in this page session.

    No product screenshot

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

    Case study · Preview unavailable
    Try the example: Truffle Camp
  • Sales Enablement & Productivity

    Enable · Software project

    A Key's Day

    A five-part interactive lesson that follows one made-up key through a workday, from a laptop to the key being shut off.

    How it works

    Intended value: Whether the reader can separate finding a copy, checking that it still works, telling the owner, and replacing it.

    Contribution: I designed the story, the cast, and the lesson, and built it with an AI coding assistant.

    A static site: HTML, CSS, and JavaScript.

    Recorded stage: Software project. Lifecycle: Enable.

    The key is made up. Nothing is scanned and progress is not saved.

    No product screenshot

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

    Case study · Preview unavailable
    Explore the project: A Key's Day
  • 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.