What you get
Enough to decide with. Then enough to build from.
Two sets of documents. One arrives free and is enough to decide with. The other arrives on signature and is enough to build from. Every estimate in them rests on assumptions you can see.
- English only confirmed
- Under ten thousand users confirmed
- You provide the content confirmed
- Payment gateway has a standard API to confirm
If one turns out to be wrong, that is a pre-agreed trigger to re-quote — not an argument.
Item by item
What arrives free, and what arrives on signature
| Artifact | Free | On signature |
|---|---|---|
| Readable requirements Plain prose, not a bullet dump | Included | |
| Watermarked wireframes Server-rendered images | Included | |
| Scope summary What the build covers | Included | |
| Explicit exclusions The "not in this release" list, with backlog prices | Included | |
| Assumptions register Every load-bearing assumption, stated | Included | |
| Three-tier itemized price Traceable line items | Included | |
| Machine-readable spec exports | On signature | |
| Editable wireframe files | On signature | |
| openapi.yaml The API contract | On signature | |
| Mapping CSVs | On signature | |
| Given/when/then suites | On signature | |
| Architecture decisions | On signature |
What arrives free
- Readable requirements Included Plain prose, not a bullet dump
- Watermarked wireframes Included Server-rendered images
- Scope summary Included What the build covers
- Explicit exclusions Included The "not in this release" list, with backlog prices
- Assumptions register Included Every load-bearing assumption, stated
- Three-tier itemized price Included Traceable line items
What arrives on signature
- Machine-readable spec exports On signature
- Editable wireframe files On signature
- openapi.yaml On signature
- Mapping CSVs On signature
- Given/when/then suites On signature
- Architecture decisions On signature
Build-grade documents are not displayed before signature, and the reason is practical rather than defensive: for these artifacts the format is the value. A screenshot of YAML is not YAML, and a picture of a mapping CSV cannot be imported.
Enough to decide
Why the free set is enough to decide with
Three things make a quote comparable, and all three arrive before you pay anything.
Explicit exclusions
The adjacent features that usually ride along unspoken, listed under Not in this release — each with its backlog price.
- Password reset
- Notifications
- Multi-language
Firmness that follows confidence
We never print certainty the specification does not have.
- High A fixed price
- Medium Fixed, with a stated contingency band
- Low A discovery sprint first
A walkthrough, as a story
A "day in the life of your app" before signature. People catch missing scope in a story far more reliably than in a table of requirements.
Example excerpt "At 9:10 a patient opens the link, picks the 4:30 slot and pays by card. The front desk sees it appear…"
Honest limits
No specification is complete. Ours says where.
No requirements process — human or automated — extracts everything. Clients discover what they need by touching the real thing. So we design for incompleteness to be visible, priced, and contractually graceful.
Disputes come from surprise, not from gaps.
Ownership
Who owns what
Your inputs stay yours
Your idea and your business data remain yours, and remain confidential.
The documents are licensed to you
The generated documents are IOanyT's. Free artifacts are licensed for evaluating an engagement with us; the Portable Spec Pack is licensed to travel to any vendor.
Defined by both lists
Describe your project. See what comes back.
No signature, no call. A business email unlocks the full quote.