Approve the scope
Nothing is built until you approve.
ApproveRequest changes
PROCESS
Process
A clear path from the first conversation to software your team can use.
THE PROJECT
From conversation to launch.
The scope sets the details. These are the steps you will see in the client portal.
- 01 / CONVERSATION
Conversation
You explain what you need, who it is for and what already exists. We talk through the job and decide whether to work together.
- 02 / SCOPE
Scope
You receive a written scope for the project. It names the work, the cost and the target date before the build begins.
- 03 / BUILD
Build
The real work appears in your client portal as it takes shape. You can follow progress, open files and send feedback in one place.
- Automated tests
- End-to-end testing
- Issue tracking
- 04 / REVIEW
Review
Builds and project stages come to you for review. Approvals and change requests stay attached to the work they concern.
- Code review
- Security review
- Human approval
- 05 / LAUNCH
Launch
The finished work is put into service and checked where people will use it. Optional support is available after launch.
AFTER LAUNCH
Support and iteration.
Software needs changes as the workflow it serves changes. Monthly support is available after launch.
Support is optional and can be cancelled at any time; the software stays yours after the plan ends.
DEVELOPMENT PRACTICE
Tools assist. People decide.
AI-assisted development helps with the build. Human review, testing, issue tracking and validation support the result.
START A CONVERSATION
Let’s talk through the workflow.
Tell us what is slowing your team down and what you use today.
WHAT HAPPENS NEXT
- 01We reply to your email.
- 02We talk through the workflow.
- 03You get a written scope with the work, cost and target date before anything is built.