Questions

Everything owners ask twice, answered once. There are four jobs listed on this site; the answers below apply to all of them.

The work

Is my business too small?: Maybe. If one or two jobs are the problem, a single automation is the right size, and the triage call will tell you in thirty minutes. If nothing here is worth building, you will have spent half an hour.
How long does it take?: The Blueprint gives you a date for your build before you commit, and that date is part of the scope. A larger build goes live in pieces, so the first automation is working while the next is being built.
What if the job I want automated is not one of the ones you list?: They are the common ones, not the limit. If it is repetitive, happens in software, and the rules can be written down, bring it to the call.
Will my team have to change how they work?: Some, and the amount is worth knowing before you commit. The Blueprint says which steps change and who is affected. An automation that depends on people changing habits they will not change is a bad automation, and I would rather not build it.
Do I have to let anyone go?: No, and most owners do not want to. They use the hours to grow without the next hire, or to put people back on work that needs a person.

It is just you. What if you are ill, or you quit?: You hold the code, the prompts, the credentials and a plain-English runbook from the day each automation goes live, so another developer can pick it up without me. For monthly clients the alerting and escalation paths are written down rather than kept in my head.
How many clients do you take at once?: A small number, deliberately. If I am full I will tell you rather than start late.
Do you work with developers we already use?: Yes. The Blueprint is written so somebody else can build from it, which is the point.
What do you need from us?: System access and one person who can make a decision, in the first week. That is genuinely the whole requirement.

Why do you not publish prices?: Because I have never seen two businesses with the same problem, and a published figure would be either wrong or meaningless. What I will commit to is the structure: the Blueprint is quoted before you commit, the build is one fixed number against a written scope, and the monthly plan is flat and cancellable on thirty days.
Why do you charge for the Blueprint when others audit for free?: A free audit is a sales call with a document attached. Mine takes days of real work and produces a specification you own and can hand to any developer. It costs nothing if you build with me.
What are the ongoing costs?: Model and platform costs, billed to your own accounts at cost. I do not mark them up, and the Blueprint tells you the figure before you commit.

What happens to my data?: Your systems stay yours. Each automation sends only the data that job needs to a model provider, under terms that bar training on it. I show you which provider, and which data, in writing before anything is built. I spent four and a half years as technical architect on the platform Azure ran its compliance program on, so this is the part of the conversation I take most seriously.
Who is liable if an automation sends something wrong?: Anything financial or customer-facing has a human approval step, and removing one is a decision you make explicitly and in writing.
What happens when it breaks?: Alerts come to me, not to you, and every release can be rolled back to the last good state. Fixing it is what the monthly plan pays for. I answer within one business day.
Can I not just do this myself with Claude or ChatGPT?: For some of it, yes, and I publish how, free. The gap is everything after the demo works: retries, access control, spend caps, rollback, monitoring, and one named person responsible when it stops.