HOW WE WILL WORKLess uncertainty before we begin.
Trust in an independent provider should not depend on promises. It should rest on a clear scope, visible decisions and work you can review.
REFERENCE TERMS
Important conditions are agreed before delivery, not after.
These principles guide the conversation. The written proposal for each project defines the final commitments.
Milestone payments
A common reference is 40% to begin, 30% at a functional version and 30% on delivery. It can be adapted to the project.
Two revision rounds
Included as a reference against the approved scope. New functions or a change of direction are assessed separately.
Ownership and access
Once paid, the client owns the agreed result. Code and material handover are defined in the proposal according to project type.
No hidden lock-in
There is no mandatory ongoing term unless a recurring service or third-party subscription is explicitly agreed.
Separate running costs
Domains, hosting, licences and external services are identified so you know what depends on each provider.
Initial warranty
A typical reference is 30 days to correct errors within the delivered scope. Improvements and maintenance are separate.
Confidentiality
I can work under a non-disclosure agreement when the project requires it.
Realistic schedules
An essential website may take 2–4 weeks and a first tool 4–8 weeks. Final timing depends on scope, content and review availability.
YOUR CONTROLYou will be able to change provider.
I want you to stay because the work creates value, not because access is withheld. We define from the beginning which accounts, code, data and documentation form part of the handover.
See this approach in a real case →NEXT STEP / A CONVERSATIONTell me about the process, not the technology.
In the first conversation, we will decide whether you need custom software, an existing product or simply a better organised process.
First 20-minute conversation, free of charge · reply within 1–2 business days.