Frequently asked questions
What's a roadmapping call?
It's a live, screen-share call where you walk me through the problem in greater depth. I ask questions, watch how the system actually works, and get everything I need to fully understand it. From there, I put together your roadmapping report: a written diagnosis and recommended solution, delivered within a couple of days.
Why isn't the roadmapping call free?
Because it's not a sales call, it's the actual work. You're not paying for a pitch — you're paying for my time diagnosing the problem, plus a written report you keep either way, whether or not we end up working together further. It's also what keeps the call focused: everyone who books it is serious about solving the problem, not just browsing.
Do I need to know what's wrong before I book?
No. "It's a mess, and I don't know why" is a completely normal starting point.
How long does a project take?
It depends on scope. A quick fix might take a few hours. A full system build might take a week or two. You'll get a specific timeline in your proposal before anything starts.
What if I need changes after delivery?
Minor fixes are included for two weeks after delivery. After that, just reach out, and I'll send a quick estimate for anything further.
Do you work with any type of business?
Mostly solopreneurs, small teams, and non-profits, but the common thread isn't industry. It's the problem: a spreadsheet, workflow, or system that's become more trouble than it's worth. If that sounds like you, it's worth a conversation.
Is my data safe?
Yes. Anything you share with me stays confidential and is only used to complete your project. If your project involves sensitive data, we'll talk through what access is actually needed before any work begins.
Do you write SOPs or procedures?
Yes. If the real issue is a process that only lives in your head, or one that's different every time someone tries to follow it, I can turn it into a clear, written procedure. This is often part of a build, but it can also stand on its own.