Architect - Scoping & Estimation (Internal)¶
Never client-facing. The unit each step is sized in, its S/M/L/XL bands, and the role mix - one section per step, in step order. Hours per step per tier are in the effort model; the tier model and prices in productisation.md. Bands and tiers are defined in depth.md.
2.1 Experience & Content Structure¶
Unit: IA size (nodes / page types)
| Band | Approx size |
|---|---|
| S | ≤20 nodes |
| M | 20–50 nodes |
| L | 50–100 nodes |
| XL | 100+ nodes |
Role mix:
- Principal sets structure and leads the content-model pass
- Mid develops detailed IA and journeys
2.2 Technical & Delivery Definition¶
Unit: Integration kind & volatility (kind matters more than count - most projects carry analytics and perhaps form submissions; business systems are the step change)
| Band | Description |
|---|---|
| S | Analytics only |
| M | Analytics + form submissions / email |
| L | + business systems (CRM etc.) - Core tier and up |
| XL | Multiple / volatile / custom APIs |
Role mix:
- Principal-heavy (risk + architecture)
2.3 Visual Direction¶
Unit: concepts × rounds, multiplied by design complexity (ambition band). Hours per tier and band multipliers (System-led 1× · Expressive 1.5× · Premium 2×) in the effort model.
Role mix: design-led; principal reviews direction before client playback.
2.4 Scope & Priorities¶
Unit: number of workstreams triaged.
Role mix: principal-led (trade-offs are commercial decisions); mid documents.
2.5 The Cornerstone¶
Effort model: fixed effort per project plus a size component from the 2.1/2.2 bands (assembly scales with IA nodes and integration count; the boilerplate sections do not). 2.5 varies ~2.4× across tiers while the research-heavy steps vary ~4× - near-fixed by design; if assembly hours exceed the model, the Cornerstone prompt isn't doing its job.