Small jobs
For maintenance or a small fix, some steps merge; scope, approval and release are still recorded separately.
01 / Process
How we work
Eight steps. Each one has a matching screen in the portal, so you can see what you approved, what is waiting and whose turn it is from the same record.
- 01
First conversation
We talk about what you want to build, who you serve and how you will measure success. By the end the rough boundaries of the work are clear.
Contact form - 02
Scope and quote
The scope, acceptance criteria and schedule are written down and the quote is versioned. The version you accept becomes the single reference for the work.
Quotes screen - 03
Contract
The contract is sent at the start; the signed copy is uploaded to the portal and every version is kept. Uploading is not signature verification on its own: review is a separate step.
Documents - 04
Design
The main user flow is prototyped first, then the visual language settles. Design feedback is collected per version and moves through records instead of scattered messages.
Design service - 05
Development
The work is broken into tasks whose weight and status are visible in the portal. Progress is computed from completed weight, not from the calendar.
Projects - 06
Private preview
Every version is reviewed at a protected address opened only to authorised people. Knowing the address grants nothing; the grant can be revoked and each version stays separate.
Preview - 07
Approval and launch
Approval applies to exactly the version you reviewed. Publishing is a separate team step, and which version went live when — plus the rollback history — stays on record.
Approvals - 08
Care and growth
After launch, updates, backup checks, monitoring and — if you want — advertising and SEO work continue. A new request opens as a scope change and follows the same path.
Maintenance
The schedule is an estimate, not a promise: if something slips we write the reason and the new estimate in the portal. Work pauses on steps waiting for approval, and that is visible too.
When the process changes
Security testing
Security testing has one extra step before the contract: the list of systems to be tested and the owner's written permission. Testing does not start without that permission.