Process
Five phases, the same every time
Proposal, Discovery, Development, Deployment, Support. Each phase ends with something you can hold: a written proposal, a prototype you have clicked through, working software, a live release, a quarterly report.
- 01 Proposal
- 02 Discovery
- 03 Development
- 04 Deployment
- 05 Support
-
Phase 1
Proposal
You tell us what you are building and roughly how many screens it has. We confirm the count, flag anything that changes it, and send a proposal with the monthly fee, the one-time deposit, and the minimum term (12 months for an app with dynamic screens, or 6 months for a static-only site). No hourly estimates to argue over.
Deliverable. A written proposal with screen count, monthly fee, one-time deposit, and term. -
Phase 2
Discovery
We work through your users, screens, data, and integrations in focused sessions. With AI assistance we turn that into an interactive prototype: a working click-through mock of the real app. You review it, change it, and approve it before engineering starts.
Deliverable. An interactive prototype you have clicked through and approved, plus a confirmed screen list. -
Phase 3
Development
Engineering runs in iterations of 1 to 3 weeks. Each one ends with testable software on a staging environment. Every change is linted and fully type-checked before it can merge, then verified by QA before it ships. You see real progress and steer as you go.
Deliverable. Working software on staging at the end of every iteration. -
Phase 4
Deployment
Once staging passes, one click puts the release into production in an AWS account you own. Static pages, the containerized API, managed Postgres, and login are all provisioned in your account. The code is yours too.
Deliverable. Your application live in production, in your own cloud account. -
Phase 5
Support
Launch is the start of the maintenance plan. Dependencies are scanned continuously and triaged weekly. Cloud advisories and deprecations are tracked. Backups are encrypted with retained snapshots. Every quarter you get a written audit across ten engineering dimensions.
Deliverable. A maintained, backed-up application and a quarterly audit report with ranked findings.See the maintenance plan
Short iterations
Work ships in 1 to 3 week increments. Small releases are easier to review, easier to verify, and easier to roll back.
Nothing hidden
Staging is yours to use at any time. The source code sits in a repository you can read. Estimates and findings are written down.
You decide
Urgent work outside the app comes with a recommended action and a cost estimate before anything starts. Approval is always yours.
Start with a screen count
A short description and a rough count are enough for the Proposal phase. We take it from there.