How I work
A disciplined process,from first call to a systemyour team owns.
Every engagement follows the same five phases. You know what will be delivered, when you will see it, what it costs and what is needed from your side — before any build begins.
- Typical duration
- 1–6 weeks
- Pricing
- Fixed, per project
- Progress reporting
- Weekly demo + written update
- Post-launch support
- 30 days included
01 — Principles
Four commitments behind every engagement.
Outcome before technology
Each engagement starts from a measurable result — hours saved, response time, error rate. Tools are chosen afterwards.
Scope in writing
Deliverables, acceptance criteria and revision rounds are agreed before a line of code is written.
Progress you can see
Working software every week — a live demo you can test, not a status slide.
Built to be owned
Documentation, ownership notes and monitoring, so the system never depends on me to keep running.
02 — The engagement
Phase by phase: what happens, what you receive, what I need from you.
01 Discovery call
Day 1 · 30 minutesWhat happens
We walk through the workflow end to end — volumes, manual steps, failure points — and separate what should be automated from what needs human judgement.
You receive
A clear recommendation on whether, and how, to proceed — useful even if we don’t work together.
Your input
The person who runs the process today, and a few real examples of its inputs and outputs.
02 Proposal & scope
Day 2–3What happens
I design the architecture, choose the tooling, and list every risk and dependency before committing to a timeline.
You receive
A written proposal: scope, deliverables, fixed price, milestones, acceptance criteria and included revision rounds.
Your input
Review and sign-off. An NDA is signed first if anything sensitive is involved.
03 Design & build
1–3 weeksWhat happens
The system is built in working modules and connected to your tools through APIs and webhooks, with error handling, retries and alerting from the start.
You receive
A weekly demo and written update, with risks and open decisions raised early — never at the deadline.
Your input
Feedback on each demo, plus access to test data and the accounts the system connects to.
04 Launch & handover
Final weekWhat happens
QA against the agreed acceptance criteria, production deployment, and monitoring switched on.
You receive
The live system, full documentation and ownership notes your team can maintain from.
Your input
Final acceptance against the criteria agreed in phase 02.
05 Support & partnership
30 days includedWhat happens
Fixes, tuning and small adjustments as real usage arrives — the period where systems earn trust.
You receive
Written response expectations, and the option of a monthly retainer for monitoring and new features.
Your input
Report anything unexpected through the channel your team already uses.
03 — Typical timelines
Weeks, not quarters. Confirmed in your proposal.
Typical minimumRange, depending on scope
04 — Engineering standards
Included in every build, not sold as extras.
Error handling & retries
Failed steps retry safely and never leave half-processed records.
Alerting & monitoring
The right person hears about a problem before your customers do.
Secure access
Authentication, role-based permissions and least-privilege credentials.
Data validation
Field mapping, deduplication and checks before anything reaches your CRM.
Version control & CI/CD
Every change tracked in Git and deployed through a repeatable pipeline.
Documentation
How it works, how to change it, and what to do when something breaks.
05 — Working together
Predictable communication across time zones.
- Working hours
- Monday–Friday, 9:00–17:00 UTC+1
- Response time
- Within a few hours, business days
- Progress updates
- Weekly demo and written summary
- Time-zone overlap
- Full with Europe · Mornings with the US
- Confidentiality
- NDA before any sensitive information