ankit.kapoor /

ENGINEERING × STRATEGY

I build decision
systems for
ambiguous
strategic questions.

Former machine learning engineer.
MBA candidate at USC Marshall.

I turn messy questions about technology and business into working models. Assumptions you can challenge. Evidence you can inspect. Decisions you can explain.

THE DECISION ATLAS01 — 05
What has tobe true?GROWTHCOMPETITIONDEFENSIBILITYEXECUTIONECONOMICS

Where should we play?

Market Entry War Room
FIVE QUESTIONS. FIVE WORKING SYSTEMS.SCROLL TO EXPLORE

01 / SELECTED WORK

Strategy you can interact with.

Two deeper investigations.
From an open question to an inspectable decision.

02 / THE STRATEGY LAB

Follow the question.

Competitive moves. Product moats. Business value.
Three experiments to think with.

System 02 / schematic

02Competitive strategy

Disrupt This Business

How should we win?

A competitive strategy game about defending an established business or building the challenger. Explore decisions, inspect their consequences, and switch sides. The scenario is a fictional project-management market: an incumbent selling seats against a challenger selling completed work. Four quarterly commitments resolve through a deterministic economic model, so every outcome can be traced back to the rule that produced it.

System 03 / schematic

03Product strategy

The Moat Test

What remains defensible?

An investigation into what makes an AI product worth paying for. Build a small alternative, test its limits, and examine the business advantages the prototype leaves unresolved. The first case takes meeting assistants: if a model can summarise a transcript, what is the subscription actually buying? Every output is traced to the transcript lines behind it, and each claim carries its data mode.

System 05 / schematic

05Finance / valuation

Priced In

What has to be true economically?

A financial workbench for exploring the business performance required to justify a valuation. Connect assumptions to operating requirements and test the contribution an AI investment would need to make. It runs the valuation backwards: pick a target, see which growth and margin combinations satisfy it, translate one of those into required customers and price, and then try to break the case you just built.

TECHNICAL SYSTEMS & DOMAIN ENGINESExplore More Projects

03 / HOW I THINK

Make the reasoning visible.

Inside the method
  1. 01

    Frame the decision

    Start with the decision, not the technology: what choice is being made, what alternatives exist, and what would cause one option to beat another?

  2. 02

    Structure the ambiguity

    Use AI where interpretation is genuinely required, then expose the structured assumptions it produced so they can be corrected rather than trusted implicitly.

  3. 03

    Ground it in evidence

    Connect the structured question to data, documented assumptions, or explicit economic rules rather than allowing generated language to become evidence.

  4. 04

    Make the trade-offs inspectable

    Put weights, formulas, thresholds, missing information, and alternatives where the reader can see what is driving the answer.

  5. 05

    Stress-test the answer

    Try to break the conclusion by moving the assumptions, reversing the perspective, or searching for the conditions under which the recommendation fails.

04 / A LITTLE CONTEXT

From building models
to questioning
what they mean.

More about me

My background is in machine learning engineering, and I am now pursuing an MBA at USC Marshall. I am interested in the decisions around technology: where it creates value, what makes that value defensible, how organizations should act on it, and what would have to be true for the economics to work.

  • USC MarshallMBA candidate
  • BITS Pilani DubaiComputer science

HAVE A QUESTION WORTH WORKING ON?

Let’s think it through.