Systems · Point of view
The second time
should be cheaper.
A note on why I stopped thinking about websites as isolated projects—and started building the machinery behind them.
What is wrong with project-by-project web delivery?
Every studio rebuilds familiar components and prices the work as if every decision were new. The client pays for repetition. The studio’s margin depends on how quickly people can repeat themselves.
That is not a durable delivery model. It is a treadmill with invoicing.
What is a delivery system?
Not a template. A system is a set of decisions made once: a token layer, component library, content model, build pipeline and clear rules for when a human intervenes.
The output can vary. The expensive decisions do not have to.
Where does AI actually fit?
AI is good at filling a structure and unreliable at inventing one. I build the structure by hand—sections, tokens, motion rules and performance budgets—then use generation for content, configuration and assembly inside those constraints.
Constrained generation produces work that can ship. Unconstrained generation produces demos.
Craft, made repeatable.
Where should humans stay?
Approval gates, judgement calls and anything where being wrong is expensive. Automating the typing is different from automating the decision.
The system should remove repetition without removing accountability.
What am I building now?
PROMTURE is developing internal infrastructure for AI-assisted digital delivery: structured intake, creative direction, asset generation, component-led builds, automated quality checks and controlled deployment.
The goal is not to remove craft. It is to make craft repeatable.
A useful system starts with the right constraint.