How it works
From first email to handover
Six steps. Nothing starts until you have seen a scope and a price in writing.
- 01
A first conversation
You email me a rough description of the problem. We talk it through — a call or more email, whichever suits you. No charge for this part, and no obligation at the end of it.
- 02
A look at how you work now
Before proposing anything I want to see the actual process: the spreadsheet, the inbox, the thing your staff do at close. Problems usually turn out to be a step or two away from where they appear.
- 03
A written scope and quote
You get it in writing: what I will do, what you will have at the end, what it costs, and how long it should take. If I think the job is smaller than you feared, the quote says that.
- 04
The work itself
I build it and keep you updated as I go. If something turns out to be harder or larger than the scope said, you hear about it when I find out, not when the invoice arrives.
- 05
Handover and training
Nothing is finished until the people who have to use it can use it. That means sitting down with your team, plain-language documentation, and time for the questions that only come up once it is real.
- 06
Support, if you want it
Some jobs end here and that is fine. If you would rather have someone on hand for changes and the occasional thing that breaks, that becomes an ongoing arrangement instead.
Questions
The things people ask first
I do not really know what I need. Is that a problem?
No — that is the normal starting point. Most people arrive with a symptom rather than a diagnosis: something takes too long, or keeps going wrong. Describing the annoyance is enough. Working out what is actually causing it is part of the job.
Is this going to replace someone on my team?
That is not what I am for. The work I do takes the repetitive parts off people so they can spend their time on the parts that need a person. If you are looking to cut headcount, I am the wrong hire.
Do I have to change all the software I already use?
Usually not, and I will push back if someone suggests it. Ripping out working systems is expensive and disruptive. The first look is always at making what you already own work properly together.
What happens to my data?
It stays yours. I only ask for access to what a job genuinely needs, I tell you before anything goes into a third-party tool, and access gets handed back or removed when the work is done. If you have rules about where your data can live, say so early and we will design around them.
Who owns what you build?
You do. Anything built for you is yours, source code included, along with documentation on how it works. You are not renting it from me, and you are not stuck with me to keep it running.
How quickly can you start?
Depends on what is already booked. Email me and you will get an honest answer about timing, including if the honest answer is that someone else could get to it sooner.
Do you work in person or remotely?
Both. Plenty of this can be done remotely, but some of it genuinely cannot — seeing how a process runs during an actual shift is worth more than any amount of describing it over email.
Still have a question?
Ask it directly — you will get a plain answer, and there is nothing to sign to get one.