Straight answers
If something's a bad idea, you'll hear it, nicely.
How we work
No 40-page proposal. No jargon. Just a clear path from "this is a mess" to "oh, that's actually useful."
Explain the messy version. Screenshots, voice notes, a spreadsheet nobody understands - all fine. No perfect brief required.
I ask the annoying questions until the real problem shows up, then turn it into a plan in plain language: what gets built, what it costs, and when.
Something you can click, use and show people early, so we fix the wrong turns before they get expensive.
Test, improve, simplify, automate and polish until it does the job without you babysitting it.
Hosting, updates and fixes where it makes sense, so it doesn't quietly fall over six months later.
About whether it actually works for the people who use it, not just whether it technically runs.
If something's a bad idea, you'll hear it, nicely.
You'll know what's included before work starts.
Your domain, your content, your call.