Best for a quick question, a photo of the spreadsheet you are trying to escape, or a voice note describing the mess. Send it however it comes out.
WhatsApp me →
Start a project
Start with the problem. I’ll work out what to build.
Three ways in, and all three land with me. Book the call, send it in writing, or just message me. The person who reads it is the person who would build it.
20 minutes. You leave with a clear view of what to build first, whether you hire me or not.
UK-based. I work with businesses across the country, entirely remotely. Discovery calls happen over video or phone. Scope, staging links, check-ins and handover are all shared digitally. None of it needs us in the same room.
I reply to every enquiry personally within one working day. If I can’t help, I’ll say so and point you at someone who can.
First way in · The call
Book the twenty minutes.
It is a working call, not a pitch. You describe how the job actually moves through your business, I ask the questions that decide what gets built, and you leave knowing what I would do first even if you never hire me.
Discovery call · 20 minutes · video or phone
Whichever route you use, it reaches me and nobody else.
What the call actually covers
- Where an enquiry lands today, and everywhere it gets retyped after that
- Which part is costing you hours, and which part is costing you work
- What I would build first, what I would leave alone, and why in that order
- Whether software you already pay for can do it, in which case I will say so
Every build is scoped and priced individually; it depends on what your workflow actually needs. The discovery call is where that gets nailed down, and you get a fixed written price before any work starts.
What happens next
Three steps, and a person at every one.
You get an instant acknowledgement with a copy of what you wrote, and every word after that comes from me. This is the actual sequence, and you can hold me to it.
-
01
Your enquiry gets read properly
Read in full, not skimmed. I go through what you have described, work out which part of it is actually costing you, and come to the call with questions ready rather than a script.
-
02
You get a reply from me
Within one working day, written by me. Either two or three times that work for a call, or a straight answer that this is not something I should take on, with a pointer to someone better placed.
-
03
The call itself
Twenty focused minutes, no commitment either way. You bring the situation. I bring what I would build first, what I would leave alone for now, and an honest view of how long the first useful piece takes.
Second way in · In writing
Put the actual problem in the box.
The fourth field is the one that matters. The more of the real situation you put in it, the more useful my first reply is, and the less of the call gets spent working out what we are talking about.
Third way in · Direct
Or skip the form entirely.
Same number, same inbox, same person. If you would rather ask one question before you commit to anything longer, ask it here.
Phone
If it is urgent, ring it. When I am mid-build I will not always answer, but I call back the same working day.
+44 7428 431562 →Best for detail. Screenshots, an existing spec, a list of the tools you are paying for. Send it over and I will reply on the same thread.
enquiries@oduex.com →
Before you write
Quick answers.
The four I would want answered before writing to someone like me.
Then you are the easiest kind of enquiry to answer. Come with the situation rather than a solution: what takes too long, what keeps getting forgotten, where work slips out of the door unnoticed.
Working out which one to fix first is the whole point of the call. You will not be sold something you do not need, and if the honest answer is that nothing needs building yet, you will get that answer too.
A single focused automation is usually days rather than weeks. A custom CRM or internal tool is measured in weeks, because how your data is modelled has to be right before anything is built on top of it. A website sits between the two.
You get a written scope with a timeline in it before any work starts, a staging link while it is being built, and regular check-ins so you are never waiting to find out how it is going. Two rounds of revisions are included in every project.
No. You own the code, the accounts and the workflows. Every account is opened in your name, not mine, and everything in the system is exportable.
Full handover documentation and a walkthrough come with launch, written so another developer could pick the work up without ringing me. If you ever stop working with me, nothing stops working.
It is the fair question to ask one person. Everything is documented as it is built, and the credentials, the repository and the workflow files live in your accounts from the first day, never only in mine.
That means the work is recoverable without me: another developer can carry on from the handover notes instead of starting again. For anything longer than a short absence you would hear it from me straight away, and we would agree what happens next in writing.