A product-and-engineering studio that holds one continuous chain — from why we build, through how we ship, to whether we served. This site is the corpus that makes the chain learnable. Written for the new hire on day one, the senior practitioner returning for depth, and the AI agent fetching at scale.
This is not a methodology. It is a working corpus. The chain it describes — why we build · before we build · what we shape · as we build · after we build · did we serve — runs in the work, every cycle. The pages here are the artefacts that make the chain learnable.
200apps is a product-and-engineering studio. We are hired by founders, operators, and clinical teams to build software they need to depend on — lending platforms, field-service systems, e-commerce, support tooling, education, utilities. We work as embedded squads: a Product Owner, a Tech Lead, designers, developers, QA, CS, on-call — together holding the chain end to end.
We don't sell methodology. We sell software that meets the people it was built for. The chain on this site is the shape of how we get there.
Six phases of one continuous chain. The first four run per cycle, in sequence. The last two are persistent — Why We Build sets the bet above any single cycle; Did We Serve? is the relationship that holds across cycles.
A defect that surfaces in production traces back through these phases to the level that produced it. A bug found at L5 (operation) often has its root at L3 (a story written six weeks ago) or L2 (a brief that was never witnessed). The discipline of this corpus is to trace and to fix at the level, not at the symptom. See The Map for the level diagram.
The corpus is built around the people walking up to it. Pick the door that matches why you're here.
The cycle (canon), thirteen Master Areas, operational practice, anti-pattern clinics, and skill paths. Read end-to-end to internalise; read by topic to find what you need today.
Open The Cycle →If you hold a role on a teamSeven role hubs — Product Owner, Tech Lead, Designer, Developer, QA, CS Lead, On-call, Leadership. Each one names what good looks like, the first 30 days, the deepening menu, and the anti-symptom catalogue.
Open the role hubs →If you want to know why this stanceSix short essays on why the corpus is shaped the way it is — person-first, witnessed-not-described, predictions over plans, chain-level thinking, the only worthless outcome, compounding small changes.
Read what we believe →Same knowledge, different depths. Pick the layer that matches the moment you arrived.
| Depth | When | Form |
|---|---|---|
| Glance | "I'm about to act" | Checklist |
| Skim | "What's this in 2 minutes?" | Field card or template |
| Do | "Walk me through it now" | Practice page |
| Diagnose | "What does going wrong look like?" | Clinic |
| Internalise | "Read it like a book" | Cycle phase |
| Grow | "How do I become this?" | Skill path |
| Believe | "Why this stance, not another?" | Principle |
The corpus's lifeblood is reusable pieces. Three places to grab what you need without reading the whole chain.
Copy-pasteable artefacts. Briefs, predictions, ADRs, retros, postmortems.
Glance-level guides for the moment you're about to act.
Every term the corpus uses, defined once.
How the phases, levels, and crafts cross.
The corpus exposes structured artefacts at the site root, designed for retrieval and grounding:
/llms.txt — index with one-line descriptions and a when to use which slice guide/llms-canon.txt — the cycle (canon), one file/llms-practice.txt — practice and clinics/llms-reference.txt — areas, glossary, templates, checklists/llms-roles.txt · /llms-skills.txt — role hubs and learning paths/llms-full.txt — everything, one file/corpus-graph.json — every page as a node, with derives_from, owners, roles, areas — for structured retrieval