TT core tool stack preferences confirmed Friday 22 May 2026 — Google Workspace + Stripe + Cloudflare as core infra; ScoreApp + Facebook ads for quiz-led marketing; Linear in trial mode for workflow tracking (trial-then-commit); Steven Abols scoping Linear adoption playbook Saturday 23 May 2026
4 min read
TT core tool stack — Rich-confirmed Friday 22 May 2026 during the Tim Deeson LawtechUK brief iteration.
Core infrastructure (locked intent)
Tool
Role
Disposition
Google Workspace
Email + Calendar + Docs + Drive + Shared Drives
Core; assume in place
Stripe
Payments + subscriptions + (later) Stripe Identity for ID&V
Core; supports legacylists.com + future TT brands; cost-efficient match for operator-first frame
Marketing stack (intent)
Tool
Role
Disposition
ScoreApp (scoreapp.com)
Quiz-led lead generation (inbound)
Intent — for LegacyLists launch + MyFamilyInherits lead-routing funnel. Steven Abols is keen on ScoreApp — candidate follow-on engagement to design + run the LL quiz funnel (see [[project-steven-abols-kinetic-integrations]] — surfaced 2026-05-22 ~16:35 BST)
Facebook ads
Quiz distribution + audience targeting (inbound)
Intent — distributes ScoreApp quizzes; lead-gen funnel start. Steven Abols experienced/interested in Meta ads — likely paired with ScoreApp engagement
Instantly.ai (instantly.ai)
Cold-email outbound prospecting
Intent — for MFI will-writer recruitment ahead of Phase 2 launch (pre-launch supply-side network building); pairs with Tim brief Q5 partnership development + Q6 lead-routing platform integration. Steven Abols proposed as candidate operator — surfaced 2026-05-22 ~16:50 BST
Shared workflow for Rich + Josh + Steven + Charis; cross-repo task tracking; GitHub-synced ticketing
Lead candidate. Operator-first buy-not-build call after Rich-deliberation 2026-05-22 ~17:10 BST. Free plan covers 4 users + 2 teams + 250 issues + Linear Agent (beta). First-party Claude MCP. Bidirectional GitHub Issues sync. Steven scopes setup as first engagement; 2-3 week trial; revert to markdown if trial fails.
Sentry User Feedback Widget
Charis bug reporting on legacylists.com (in-product feedback collection layer)
Lead candidate (paired with Linear). Sentry already in stack + SDK already wired into code-ll (sentry.edge.config.ts + sentry.server.config.ts + instrumentation.ts present). Feedback widget on LL site → Sentry → routes to Linear triage queue. Session replay (60s pre-feedback) is the killer feature for non-tech tester workflow.
Custom Josh→Rich visibility tool
(Was: likely answer if Linear over-engineered)
REJECTED for Phase 1. Custom code has hidden maintenance/security/knowledge-concentration costs. Try Linear first. Revisit only if Linear trial fails. Operator-first principle: buy not build.
GitHub Projects
(Was: alternative for Josh-Rich visibility)
Rejected due to Rich’s prior negative experience with manual milestone-to-project-board sync overhead.
Markdown ledger
v2 build fleet coordination across 7 repos
Status quo for Phase 1. Works fine for Phase 1 solo + Claude. May migrate to Linear at end of trial if commit decision fires.
Why this stack
Operator-first frame (per [[project-strategic-position-operator-first-2026-05-22]]) favours capital-efficient, integration-rich tools — Cloudflare over AWS, Google Workspace over enterprise alternatives, free-tier Linear before commercial commitment.
Linear-vs-alternatives concern was addressed via research 2026-05-22: Linear has first-party Claude MCP integration (mcp.linear.app/mcp, OAuth 2.1, hosted by Linear); free plan covers 3 users + 2 teams + 250 issues + Linear Agent (beta); bidirectional GitHub Issues sync via first-party integration. The 2025 concerns about weak Claude integration no longer apply post the February 2026 Linear MCP launch.
ScoreApp + Facebook ads is a lead-gen funnel pattern: quiz attracts qualified prospect → results page captures email → MyFamilyInherits lead-routing sends qualified prospect to partner will-drafting software (Q6 of the Tim brief is the integration question — Arken vs WillSuite).
Steven Abols (engineer + spec-writer at UK nuclear power company) scoping Linear adoption Saturday 23 May 2026 — first fixed-price engagement test. Engagement substrate in ~/testatetech/docs-admin/external-partners/steven-abols/scoping-conversation-discussion-points.md v1.0.
How to apply
Do NOT recommend alternatives to the locked-intent core apps (Google Workspace / Stripe / Cloudflare) without explicit Rich-direction. These are settled choices.
For Linear: the decision to commit (migrate the phase-1-5-richard-tasks.md ledger + 5 BUILD-PLAN.md files into Linear) OR revert (stay markdown-led) depends on Steven’s adoption playbook + the 2–3 week trial outcome. Don’t assume committed until trial concludes.
For ScoreApp + Facebook ads: marketing-tactic-level decision; Tim brief Q3 (LL launch + marketing) might surface deeper questions about this stack during the Tuesday 26 May session.
For future tool additions: prefer the same operator-first frame (capital-efficient, mature, integration-rich, ideally with a Claude MCP server). Steven’s “tool-stack discipline spec” (project γ in his discussion-points doc) is the eventual framework for this.
Companions
[[project-strategic-position-operator-first-2026-05-22]] (operator-first frame justifies the cost-efficient tool choices)
[[project-steven-abols-kinetic-integrations]] (Steven engagement; Linear adoption playbook is his first project)
[[project-stainless-acquired-by-anthropic-2026-05-18]] (Stainless invalidated as TT vendor; free-stack SDK generation preferred per operator-first frame — same logic applies to all vendor decisions)