Technical decisions
Make architecture decisions with stronger evidence
PostgreSQL or DynamoDB. Build or buy. Migrate or stay. Get independent evaluations against your constraints, with the assumptions written down.
For: Engineering leads, architects and fractional CTOs.
How it works
- 1Start from a template
The Technical Architecture Review template pre-fills scalability, operational complexity, resilience, cost and team fit.
- 2Add your constraints
Data residency, budget, team skills. Must-haves exclude options that violate them.
- 3Attach design docs
Architecture notes and requirements are read by page and cited.
- 4Challenge the leader
Deep and Comprehensive runs add an adversarial review of the leading option.
What you get
- +Comparison of every option against every criterion
- +Assumptions and the conditions that would change the recommendation
- +Missing information that would most improve confidence
- +A written record you can attach to an architecture decision record
Example
| Criterion | Option 1 | Option 2 |
|---|---|---|
| Scalability (25%) | 8 (Model) | 9 (Model) |
| Operational complexity (20%) | 7 (Model) | 5 (Model) |
| Team expertise fit (15%) | 9 (Source) | 4 (Source) |
| Weighted score | 7.9 | 6.4 |
Illustrative layout with sample values, not a real analysis.
Models do not know your production environment. Treat the output as structured input to your judgment, not a substitute for a load test.