Initial conversation
In 20 minutes, explain what happens today, who is involved and where time or information is lost. No technical brief is required.
Outcome: an honest first assessment and a sensible next step.
A delivery system designed to make risk visible.
Trust should not depend on promises. It should rest on clear scope, visible decisions and working software you can review.
Discovery and scope
We map the workflow, rules, exceptions and the result the first release must produce. Any paid discovery work is agreed before it begins.
Outcome: goal, risks and a prioritized first release.A proposal you understand
You receive scope, deliverables, schedule, price, exclusions and responsibilities. Out-of-scope work is explained before it is carried out.
Outcome: you know what will be built, what it costs and what is excluded.Development with demonstrations
I work through milestones and show functional versions. Reviews test the agreed scope and expose wrong assumptions early.
Outcome: you validate decisions before final delivery.Delivery and continuity
You receive the agreed result, access and essential documentation. Domains, hosting and service accounts remain in the client’s name wherever possible.
Outcome: a usable, transferable solution without hidden dependency.REFERENCE TERMS
Important conditions are agreed before delivery, not after.
These principles guide the conversation. The written proposal defines the final commitments for each project.
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.
Defined reviews
The proposal states the rounds included. New features or a change of direction are assessed separately.
Ownership and access
Once paid, the client receives the agreed result. Code and material handover are defined in writing.
Security and privacy
Permissions, data exposure, providers and responsibilities are reviewed against the project's actual risk.
Separate running costs
Domains, hosting, licences and external services are identified before you commit.
Initial warranty
A typical reference is 30 days to correct errors within the delivered scope. Improvements are separate.
Confidentiality
I can work under a non-disclosure agreement when the project requires it.
Capacity and schedule
A start date is confirmed when delivery capacity is reserved. Timing depends on scope, validation and external dependencies.
Complex discovery, integrations, maintenance and extended support are priced for the specific project.
Ownership should not depend on the provider.
I want you to stay because the work creates value, not because access is withheld. Accounts, code, data and documentation are defined from the start.
See how a real workflow becomes a working product →Tell me about the process, not the technology.
The first conversation determines whether you need custom software, an existing product or simply a better-organised workflow.
First 20-minute conversation, free of charge · reply within 1–2 business days.