Ship AI features without mortgaging your margin.
Software companies embedding AI face a different problem: not whether it works, but whether unit economics survive scale.
A feature that costs more per call than it earns cannot ship.
A model or prompt change degrades output with no error raised.
Isolation retrofitted after launch is expensive and risky.
Embed a grounded assistant with per-tenant cost metering.
Tenant-isolated retrieval with strict namespace separation.
Catch quality regressions before customers do.
Route by task difficulty; reserve expensive models for work that needs them.
Technology assessments lead on unit economics and isolation — the two things hardest to retrofit.
Compliance we ask about first
Data sources we expect
Questions this template pushes on
These are suggestions surfaced alongside the questions — never pre-filled answers. The assessment still asks you everything, because a score built on assumptions you never confirmed is not a score you could act on.
The Internet & Technology template sharpens the questions. Ten minutes gets you a feasibility score, an architecture and a costed plan.