Two ways, and you choose. Most people take a fixed price with the scope written down. Some prefer to have me by the hour. Neither is a trick; here is what each one looks like in practice.
Most jobs
We talk for twenty minutes, or you send me the file. I write back with a scope: what I'm going to build, what I'm deliberately not building, what I need from you, and roughly when it will be done. Then a number. That number doesn't move unless the scope does.
The honest part is that scope usually does move a little, so I also tell you where I think it's likely to, before you say yes. There's a list further down.
If you'd rather
Some work doesn't want a fixed scope: a backlog of small fixes, a system that needs looking after, a job where we won't know what's in there until we open it up. For that you can have me by the hour.
Time is tracked as I go in my own software and invoiced regularly, so you can see where the hours went and stop whenever you like.
Every fixed quote I write comes with a note on where I think it might grow. These are the usual suspects. If one of them happens, you hear about it straight away with a price for the extra piece, and you decide. Nothing gets built or billed without that conversation.
The file you send me is one month. Month seven has a merged cell, a renamed column and a date typed as text. Cleaning that is real work, and it is the most common thing I did not see coming.
The best ideas arrive once the first version is in front of you. That is a good sign, not a problem, but each one is a small job with its own price rather than something that quietly gets absorbed.
A tool for one person and a tool for a team are different builds: permissions, who can see what, what happens when two people are in it at once.
Somewhere there is a monthly summary that someone compiles from the thing we are replacing. It surfaces about a week after handover.
Moving off a spreadsheet usually means running both for a while and keeping them in step. That is worth doing, and it takes time.
I don't have a price list, because two jobs that sound the same are rarely the same size. What I can do is tell you what has actually happened.
Most of this work is small. Of the 58 reviewed jobs where the price is on record, about two thirds came to £200 or less and about three quarters to £400 or less. The biggest was in the £800-£1,000 band.
About half were finished within two days; the longest took about 21 days.
Those were marketplace jobs. Projects that come directly are usually bigger, and get a written scope and a fixed price.
As a rough guide, a single-list app on SharePoint usually lands in the low thousands, and a full multi-screen system on Dataverse is a five-figure project. You'll know the number before I start.
After handover, keeping it running is around £200 a month: platform updates, small changes, questions. Month to month, no lock-in.
Usually one flow at a time, each on its own fixed quote. Most engagements start with the single process that costs someone an hour a day, and grow from there if it earns it.
Scoped in stages, each with its own fixed price, so you're never committing to the whole move at once. A single tracker can be a week or two; a multi-tab system of record is longer.
Each service page has its own figures and real examples: Excel & VBA, Power Apps, Power Automate, Spreadsheet to app.
Tell me what's slow and I'll say which way I'd price it, and why. No obligation.
Get a quote