The process
How we work
No discovery-phase invoice, sprint theatre or account-manager relay. Here is the whole operating model.
Five steps
Tell us the problem
A rough explanation is enough.
See one prototype
One clickable direction and feedback round are included before billing.
Approve the scope
Billing begins only after the written scope and price are accepted.
Watch daily progress
Review working increments instead of waiting for a reveal.
Take the handover
Receive the agreed repository, documentation and access.
What a day means
One engineer working one standard business day. Product, design and engineering build time is billable; initial calls, scope ideation and the included prototype are not.
If we underestimate an accepted fixed scope, that does not increase your invoice.
What you get at handover
Repository access
Delivered when applicable to the accepted scope and subject to our Terms.
Practical documentation
Delivered when applicable to the accepted scope and subject to our Terms.
Knowledge base or operating notes
Delivered when applicable to the accepted scope and subject to our Terms.
Hosting access
Delivered when applicable to the accepted scope and subject to our Terms.
14-day in-scope fix window
Delivered when applicable to the accepted scope and subject to our Terms.
What we ask of you
Timely feedback
Aim for decisions within three business days.
One decision owner
Conflicting approvals create avoidable delay.
Content and access
Provide the materials and permissions the build actually needs.
Honest deadlines
Tell us what is fixed and what is flexible.
What we will not do
Design deception
We will not build interfaces intended to mislead.
Expose protected data
Privileged or confidential data stays outside third-party AI tools when required.
Hold hosting hostage
The agreed access and deliverables transfer under the Terms.
Quote what we do not believe
Uncertainty is named before scope approval.