How a project runs
The same route for every kind of work. At each step it should be clear what's done, what's next and who does what.
- 1
Conversation on WhatsApp or email
You start from the brief on this site. I ask how the process works today, who does it and how often.
- A straight answer: worth automating or not, and why.
- A description of the process, with one real example.
- 2
Written proposal
I write down what I'll build, what's out of scope and how we'll check that it works.
- A one-page document with scope, stages and cost.
- Your agreement on scope, before any code.
- 3
Building in small steps
I work in stages you can see and test. If something isn't what you expected, we change course early.
- Working versions along the way, not only at the end.
- Feedback at each stage and access to the apps involved.
- 4
Handover
I show you how everything works and where to change it. My access to your systems is closed.
- The handover documentation and a session explaining the system.
- Someone on the team to take the system over.
Example: a new quote request
1Form
A client fills in the form on the website. The details land in one place.
2The system reads
The agent pulls out what the client wants, the budget and the deadline, and flags what's missing.
3CRM
The request goes into the CRM with the details filled in. Nobody copies by hand.
4Reply
A draft reply is prepared. A person reads it and sends it.
5Calendar
If the client wants a call, they get the booking link.
Access to company data
I only ask for the access the project needs, ideally through separate accounts rather than your passwords.
At handover my access is closed. Company data is not used in other projects.