How a 4 to 6 month engagement runs.
Six milestones. From first call to support.
Discovery
I learn how your business works today, who uses the software, and what a good result looks like.
Scope and estimate
We agree on what is in the first release and what waits. You get a written scope and a firm estimate. I work on a fixed price for a written scope, charged in full when we sign the contract. There are no milestone invoices. The contract sets a delivery schedule and refunds any work not yet delivered if either of us ends the engagement early.
Build in milestones
I build in small steps. After each one you review working software and tell me what to change.
Launch
I move your data, train your team, and we go live together.
Handover
You receive everything needed to own and run the software. The list is below.
Support
I stay on to fix, improve, and extend the software on a monthly retainer, or you take it from here.
How we stay in touch. Every week, in writing and on a call.
You always know where the project stands.
Weekly review
A short call to walk through working software and agree on the next week.
Written update
A short note after each week: what shipped, what is next, and anything that needs a decision from you.
Direct access
You message the person building your software. No account managers in between.
What you get at handover. Everything, in your hands.
You should never depend on me to keep your software alive.
The code
On delivery you receive the code, the accounts and a written guide to how everything works, so any engineer can take over. Ownership passes to you at that point.
Documentation
How the system is built, how to run it, and how to change it, written for the next developer and for your team.
Hosting in your own account
The software runs in accounts you own, so you hold the keys from the first day after launch.
Want to see how this would work for your project?
A 30-minute call is enough to talk through scope and timeline.