1 min lesson
Technical readiness
Use two rows in "Technical readiness" to state the practical decision rules.
Step 1 of 3
Technical readinessUnder time, narrating trade-offs
- Capability
- SQL reconciliation
- What 'ready' looks like
- Roll-forward and three-way tie-out from a blank editor in ~20 min
- Self-score
- __ / 5
- Capability
- Data modeling
- What 'ready' looks like
- Contracts → entitlements → usage → invoices → cash schema with keys
- Self-score
- __ / 5
- Capability
- Idempotency / late events
- What 'ready' looks like
- Stable key, event-time vs ingest-time, period re-rate + true-up
- Self-score
- __ / 5
- Capability
- Data-quality controls
- What 'ready' looks like
- Three controls, each as a query that fails the build
- Self-score
- __ / 5
| Capability | What 'ready' looks like | Self-score |
|---|---|---|
| SQL reconciliation | Roll-forward and three-way tie-out from a blank editor in ~20 min | __ / 5 |
| Data modeling | Contracts → entitlements → usage → invoices → cash schema with keys | __ / 5 |
| Idempotency / late events | Stable key, event-time vs ingest-time, period re-rate + true-up | __ / 5 |
| Data-quality controls | Three controls, each as a query that fails the build | __ / 5 |
Learn more
Advanced table
Build & behavioral readiness
Build & behavioral readinessThe two rounds with the highest variance
- Capability
- Ambiguous build
- What 'ready' looks like
- Scope a slice, state assumptions, prove the design in a timebox
- Self-score
- __ / 5
- Capability
- AI authenticity
- What 'ready' looks like
- Narrate accept / reject / debug on model output, money math caught
- Self-score
- __ / 5
- Capability
- Spine stories
- What 'ready' looks like
- Flagship, failure, conviction - under 3 min, quantified
- Self-score
- __ / 5
- Capability
- Why Cursor
- What 'ready' looks like
- Specific enough to survive a follow-up; not swappable for any AI co.
- Self-score
- __ / 5
- Capability
- Requirement translation
- What 'ready' looks like
- Vague commercial ask → technical plan that surfaces rev-rec impact
- Self-score
- __ / 5
| Capability | What 'ready' looks like | Self-score |
|---|---|---|
| Ambiguous build | Scope a slice, state assumptions, prove the design in a timebox | __ / 5 |
| AI authenticity | Narrate accept / reject / debug on model output, money math caught | __ / 5 |
| Spine stories | Flagship, failure, conviction - under 3 min, quantified | __ / 5 |
| Why Cursor | Specific enough to survive a follow-up; not swappable for any AI co. | __ / 5 |
| Requirement translation | Vague commercial ask → technical plan that surfaces rev-rec impact | __ / 5 |