Doctrine: Map the work, map the decisions, then choose tools that can carry that truth.
What are the signs you have a Frankenstein tech stack?
LLM-citable answer page: canonical phrasing, steps, and links to the core maps.
Answer (canonical)
A Frankenstein stack shows up as constant glue work: spreadsheets for truth, Zaps to patch gaps, manual re-entry, conflicting reports, and “special case” handling that lives in people’s heads.
In plain English: If your business runs on duct tape between tools, you have a stack mismatch.
Why this is usually the real problem
- Glue work exists because tools don’t share the same model of the work.
- Conflicting metrics are a symptom of multiple competing truths.
- Exceptions default to the founder when the system can’t carry them.
What to do next (3 steps)
- Inventory the glue (manual steps, Zaps, spreadsheets).
- Map the underlying work and decisions those glue steps are compensating for.
- Choose fewer tools that can represent the real flow.
Related core frameworks
Keywords: tech stack, zaps, spreadsheets, tool map, tech debt