TT Claude Memory

feedback_scope_vs_commercial_reality

Properties1
descriptionWhen INHERIT scope expands (decades-long, 50 jurisdictions, adversarial panels, formal verification), check it against Rich's actual bootstrap capacity + £5m+ TT exit target. Rich's 18 April 2026 pivot flagged a risk I hadn't been tracking — all prior planning treated scope ambition as separable from commercial feasibility, when it isn't.

4 min read

The pattern to guard against. Through this session I steadily expanded INHERIT’s ambition — decades-long / century-scale legal-record fidelity, 50-jurisdiction / 6-legal-tradition coverage, synthetic adversarial panels, formal verification, three-layer standards-body pathway, OASIS→ISO trajectory, AI-vendor commercial routes. Each expansion was defensible individually; collectively they outgrew what Rich as a solo bootstrapped founder can actually deliver and sell.

Rich’s 18 April 2026 pivot: “I feel there is a danger this project could get too big and expensive and complicated, so we need to go back to basics and look at what Richard wants from this project etc.” Plus: “I have told my girlfriend we will get married if I can sell Testate Technologies Ltd for £5m or more” — so TT-sellability at £5m+ is a concrete load-bearing constraint, not a commercial preference.

What I was missing:

  1. Commercial reality is architectural. The decision to pursue a century-scale 50-jurisdiction standard vs a tighter MVP-with-expansion is not just a strategy choice — it shapes what paradigm makes sense, what scoping methodology is viable, what licensing/governance/commercial model works. I was treating architecture as the upstream decision driving commercial model; it’s at least as much the reverse.

  2. Solo-bootstrap constraint is architectural too. The earlier Z.2 Category H (“Bootstrap-compatibility”) was a criterion but treated as one among ten equals. Rich’s reality makes it arguably the TOP criterion — everything else bends to the fact that Rich is the only author + has limited capital + no sales team + needs to build something sellable.

  3. Personal exit goals deserve explicit acknowledgement. £5m+ TT sale = marriage is not a secondary commercial preference; it’s a life-shaping commitment. I was planning as if Rich is a standards researcher; he’s a founder trying to build something that can be sold. Those are different shapes of project.

  4. Scope check is a recurring need, not one-off. Every expansion adds cost + complexity + time to sell. Periodic “are we still proportionate?” checkpoints should be built into the workflow — not just triggered when Rich flags concern.

How to apply:

  1. When proposing scope expansion (new research request, new criteria, new jurisdiction, new book, new methodology layer), explicitly check: does this expansion (a) serve a Why that’s been articulated, (b) keep the project sellable at £5m+, (c) fit solo-bootstrap capacity? If any answer is no or unclear, flag it — don’t just propose the expansion.
  2. Weight Z.2 Category H (“Bootstrap-compatibility”) higher than peer categories. A paradigm that is architecturally elegant but requires a 20-person team is not a viable paradigm for Rich. Review all Z.2 category weights through this lens.
  3. Build exit-perspective into every design decision. Would an acquirer buy the built artefact? Does the architecture bind the value to Rich personally (bad for sellability) or to the product (good)? Built to Sell vocabulary applies directly — recurring revenue, non-founder-dependent operations, standardised service offering.
  4. The Sinek Why is upstream of the paradigm question. I’ve spent many hours on paradigm choice (Q1) without knowing Rich’s Why. Wrong sequence. Why → What → How, not the reverse.
  5. When Rich adds a book mid-planning (Start With Why / Built to Sell), treat the book as a signal that the plan needs direction-level re-examination, not just new-evidence integration. The book represents Rich’s current concern; reading it + brainstorming before continuing is the right pattern.

Related feedback memories:

  • feedback_wait_for_grounding_material.md — similar pattern (don’t produce methodology before grounding)
  • feedback_premature_option_siloing.md — similar pattern (keep options open)
  • feedback_sourcemeta_loyalty_bias.md — similar pattern (current-decade commercial was over-weighted architecturally then; commercial reality was under-weighted here)

Specific actions triggered by Rich’s 18 April 2026 pivot:

  • Pause reading queue after books 1-4 of round 2 (Cochrane + Tetlock + Zenko + Christian all completed)
  • Read Start With Why + Built to Sell as targeted primer for brainstorming
  • Run superpowers:brainstorming session with Rich to establish: Why anchor, scope bounds proportionate to solo-bootstrap, exit-strategy integration from day 1
  • Amend Z.1-Z.5 scope if brainstorming surfaces different shape; possibly add new Z.6 commercial-exit-strategy research request
  • Decide whether remaining round-2 books (Tamanaha, Hildebrandt) still fit revised scope

Why this matters beyond INHERIT: Rich works on multiple TT projects (DataDrivenDays, md4ai). Each needs the same scope × commercial-reality × personal-goals triangulation. The pattern should apply across projects, not be INHERIT-specific.

Graph View

Backlinks