The questions everyone asks first.
How much does this cost?
It depends on the problem, so I quote each project. The Pricing page lists exactly what pushes cost up or down, and a free 15-minute call is usually enough to tell you where you'd land.
I'm not technical. Can I still work with you?
That's most of who I work with. I won't assume you know the jargon. Translating this into plain English is part of the job.
How long does a project take?
One to two weeks for a website shell, three to six weeks for a custom automation or client-facing app. The timeline mostly tracks how quickly we trade feedback, not build time.
Do you host and maintain it after launch?
Usually, yes. I host it and charge a flat monthly rate for hosting and maintenance. If you'd rather keep it with your own provider, I'll work with them.
I only have a vague idea of what I need.
That's normal. Most projects start as “this takes too long and I hate doing it,” not a spec document. Figuring out the rest is what the discovery call is for.
How do you handle my data?
A tool only stores what it needs to run. Your data never goes anywhere it doesn't need to, and I don't keep it longer than necessary.
What if my project is too small?
If it's a real, recurring pain, it probably isn't too small. Worst case, I'll tell you honestly that it's not a good fit.
Tell me what you’re doing by hand. I’ll tell you if I can build it.
I reply within two business days. Free call, and if I’m not the right fit, I’ll say so.