FAQ
Frequently asked questions
If yours isn’t here, email me.
What people ask before they start.
What to expect, what’s included, and what we settle before starting.
Can we start with one problem?
Yes. One workflow is a good first project. Before starting, we agree what it should do, how we'll test it, and what's out of scope.
Will you recommend software we can already buy?
Yes. If an existing product does the job at a sensible long-term cost, I'll tell you. I compare setting up what you have, connecting tools, and building custom before recommending anything.
Do we need a new website to improve our workflow?
No. I can start with the tools you already use. A new website only makes sense when it helps solve the problem.
How do you price the work?
Reviews have a fixed scope. Builds are quoted once I understand the workflow, the access needed, and how we'll know it works. Subscriptions and ongoing support are listed separately.
What do you need from us?
Someone who owns the process, a few real examples, access to the systems involved, and timely feedback. Everything else is settled before work starts.
What happens if an integration fails?
Before building, we decide how a failure gets reported, which steps can retry on their own, and when a person needs to step in. Support coverage is written into the scope.
Do you use AI?
When it's the right tool for a specific task. I test its inputs, limits, and failure cases first, and decisions that need judgment stay with people.
Who owns the finished system?
The proposal spells out ownership, licenses, account access, and handoff. You'll know what you control, and what it takes to keep it running, before you commit.
Who actually does the work?
I do, from the first conversation through handoff. If a project needs a specialist, we discuss their role before they start.
Can you help after launch?
Yes. System Care covers scheduled checks, fixes, and small improvements on the systems we name. We set the checks, schedule, and hours before it starts.