Frequently asked questions
The questions people actually ask, answered directly.
No vague reassurances. If you're weighing whether to reach out, this is what you'd want to know first.
-
01
How much does this cost?
It depends on scope, so I won't pretend there's a fixed price list. What I will say: you get a specific number before any work starts, not an hourly rate that quietly grows. Small builds (a single integration, a focused dashboard) often run in the low thousands; a full site or a more involved AI workflow costs more. You'll know the number upfront, and it won't move once we've agreed it.
-
02
How long does a project take?
Most projects land somewhere between two and six weeks from kickoff to handover, depending on scope. A simple website build moves faster than a custom ML pipeline. I'll give you a realistic estimate in the proposal, not an optimistic one designed to win the job.
-
03
What happens if I'm not happy with the result?
We talk about it, specifically, not vaguely. Because you see working versions throughout the build, not just at the end, there shouldn't be a big surprise at handover. If something genuinely isn't right, I fix it. If the issue is scope that changed along the way, we'll agree what that's worth separately, honestly, before I do the extra work.
-
04
Do I need to understand any of the technical side?
No, that's the point of hiring someone who does. I'll explain what I'm building in plain terms when it's useful, but you're not expected to review code or make technical decisions you're not equipped to make. You should understand what you're getting and why it solves your problem. That's it.
-
05
What happens after launch? Is there ongoing support?
I don't disappear after handover. You get a period of included support for fixes and questions; the length depends on the project and is agreed in the proposal upfront. After that, you can bring me back for anything new, or hand the plain-English handover docs to someone else. Nothing is deliberately built to lock you into needing me.