Build Request
You submit a build request through the contact form. Include the workflow problem, the outcome you need, your budget range, and your timeline.
- No discovery call required to submit
- The more detail you provide, the faster we can scope
Discovery Call
We review the request and schedule a short discovery call to ask clarifying questions, understand the workflow in detail, and confirm whether the project is a good fit.
- Usually 30–45 minutes
- We come prepared with questions based on your submission
Scope & Quote
We define exactly what gets built — the features, the interfaces, the integrations, and the delivery format. A written scope document and fixed quote are provided.
- Scope is fixed before work begins
- No guaranteed results — we scope outcomes, not guarantees
- Delivery timeline depends on scope
Invoice
Once the scope is accepted, an invoice is issued. Work begins after payment or agreed deposit is received.
- Payment structure varies by project size
- Scope is locked at this stage
Build
Development begins. We build to the agreed scope. You may be asked to provide access to existing tools, credentials, or data during this phase.
- Build timeline is provided at scope stage
- We communicate progress at defined checkpoints
Review & Testing
The finished build is reviewed against the scope. We run internal QA and then provide you access to test the build before final delivery.
- Revisions within scope are included
- Out-of-scope changes are scoped separately
Delivery
The completed build is handed off with documentation, access instructions, and any relevant deployment steps. You own the delivered build.
- Includes written handoff documentation
- Deployment support included where applicable
Optional Maintenance
After delivery, you can choose to add a monthly maintenance plan. This covers updates, bug fixes, small improvements, and direct support. It is not required.
- Maintenance is optional — no pressure
- Applies only after a completed build
Important to know
What to expect before you submit.
Every project is scoped before build.
No work begins until the scope document is reviewed and the invoice is accepted. We do not start open-ended.
No guaranteed results.
We build to the agreed scope. We cannot guarantee specific revenue outcomes, user counts, or conversion rates.
Delivery depends on scope.
Timelines are defined at the scope stage. Complexity, integrations, and revision cycles all affect delivery timing.
Maintenance is optional.
Monthly maintenance is available after delivery but is never required. It is a separate agreement.