FAQ
Questions before you start.
The straight version — what I build, how fast, who owns the output, and what the first step actually looks like.
Is this real, or vaporware?
Real. Every tool on this site runs in your browser right now — synthetic data, no login, nothing to install. What I ship for you is the same: deployed software, not a prototype that dies after the demo.
I’m small — no ERP, just spreadsheets. Is this for me?
Especially. You don’t need big systems to start — your spreadsheets are enough. First I build the tool that turns them into something live and actionable — a working AI product you can use right away; then, when you’re ready, the custom system your business runs on — one you fully own. No enterprise budget required.
We’re stuck with big-name software that won’t do what we need. Can you help?
That’s a classic fit. The platform stays — I build the tool, process, or integration around it that makes it do the specific thing you need, tailored to your operation instead of the average company it was designed for. AI is what finally makes that practical.
Do I actually own what you build?
Yes — outright. You get the codebase and the data model, deployed on infrastructure you control. No per-seat license, no subscription holding it hostage, and you’re free to change it or hand it to anyone. You own it, not rent it.
Where does it run — and what does hosting cost?
In accounts that belong to you. Standard onboarding: I set up the hosting, code, and database accounts in your name — your email, your billing — and build as an invited collaborator you can revoke anytime. A single tool typically runs free on modern hosting; a full system with logins and a database usually costs a few dollars a month, paid by you directly to the providers — at cost, no markup, no middleman. If I disappeared tomorrow, everything keeps running.
It’s just you?
Yes — and that’s the point. The domain insight isn’t diluted through a delivery team, and AI is the leverage that lets one operator who knows the problem cold ship production software fast. You work directly with the person building it — and because you own the codebase outright, you’re never locked to me: hand it to any developer and they can run with it.
What about our data and security?
Your data stays yours. I build on your real data models, with access controls and audit trails where they matter, and I’m happy to work inside your IT and security review. Nothing here requires handing sensitive data to a third party.
What do you build on?
Owned, version-controlled codebases — modern web stacks, real data models, deployed to infrastructure you control. No black-box platform, no per-seat license trapping you. You own what I ship.
How fast?
Fast enough to surprise you. The hard part — knowing exactly what to build — is solved before any code is written, so the build itself is quick. A focused first tool is usually weeks, not quarters — and at the fastest, some of the tools on this site went from pain-point to a working, deployed solution in under an hour. That’s what domain depth plus AI velocity buys you.
Is it always a custom tool?
No. A tool is the most common output, but the work spans the whole range — a full implementation or solution suite, system integration, or pure problem-solving: troubleshooting and root-cause analysis when the question is “why is this broken,” not “build me something new.” I take on whatever the operational problem actually needs.
What does a first engagement look like?
It starts with a conversation, and that one is free — you tell me the hard, specific problem your software never solved, and I tell you straight how I’d build the fix. From there I scope it, quote it, build a working tool against your real workflow, and you put it to use — then we iterate or expand from there.
Ask · live
Didn’t find it? Ask the assistant.
A live assistant in Ian’s voice — put your question to the tooling directly and get a straight, on-the-spot read. For a real quote or a commitment, it points you to Ian.
Rather ask Ian directly?
Ask it straight — I read every message myself, and you’ll get an honest read on the problem and how I’d build it.