Prototyping
Prototyping
Working software built to answer a question, within a fixed time, with an explicit boundary.

Kinds of prototype
- Feasibility
- Can the hard technical part be done at all, with your systems and data? Usually a few days to two weeks.
- Usability
- Will the intended people understand and use it? Clickable or lightly functional, tested with a handful of real users.
- Performance
- Does the approach hold at realistic volumes? Synthetic or sampled load against a minimal implementation.
- Integration
- Will two systems exchange what is needed? A thin working path end to end.
What you receive
- The prototype code in your repository, clearly labelled as a prototype.
- A short findings note: the question, the evidence, the conditions, what broke.
- A recommendation: stop, continue, or harden — with a rough estimate of what hardening would involve.
Trade-offs we make deliberately
Prototypes skip things a product cannot: full security hardening, accessibility audits, scale, edge cases, documentation for operations. That is how they stay fast. We list every skipped item so a prototype never ships by accident.
Inputs from you
A clear question, an owner who can make the next decision, access to representative data or systems under an agreed arrangement, and a few hours of a domain expert's time.