Before you hire anyone to build AI for your business, get clear answers to five questions: what exactly is included, what isn't, who owns the accounts and the work, what support covers after launch, and how you switch it off. A good AI developer will answer all five in plain English before you sign. If they can't, keep looking.
These questions work whether you're hiring a freelancer, an agency or a local consultant.
The best time to protect your business is before the work starts, not after something goes wrong.
1. What exactly will you build, and how will we know it's done?
A vague promise like "we'll automate your office" is how projects drag on. Ask for a written scope that names:
- The specific jobs the AI will do, such as answering calls, sorting service requests or pulling numbers into a weekly report.
- The tools it connects to, like your email, calendar, phone system or spreadsheet.
- What "done" looks like, in a sentence you can check yourself, such as "New web requests are sorted and assigned within an hour, and the office manager approves anything unusual."
- A test period where the AI runs alongside your team before it handles anything on its own.
If you can't tell from the scope when the project is finished, neither can the developer.
2. What is not included?
This question gets skipped more than any other, and it causes most of the surprises later. Ask the developer to list what's out of scope, in writing. Common gray areas include:
- Connecting extra tools that come up halfway through.
- Cleaning up messy data before the AI can use it.
- Training additional staff or locations.
- Changes after launch, like new questions for a phone agent or a new report.
- Ongoing costs from the AI services themselves, which are often billed separately from the developer's work.
You're not trying to catch anyone out. You're making sure you both picture the same project.
3. Will my business own the accounts, logins and work?
This is the one to insist on. You own your accounts. Every AI service, automation tool, phone number and data store used for your business should be set up in your company's name, with your company's email as the owner, and billed to you.
Ask specifically:
- Whose name are the accounts in? Yours, not the developer's.
- Who has the admin login? You should, even if the developer also has access while they work.
- Where do the instructions, workflows and code live? In accounts you control, with a copy you can get at any time.
- What happens to access when the project ends? The developer's access should be easy to remove without breaking anything.
If a developer builds everything inside their own accounts, you're renting your own system. Leaving later can mean starting over. Our AI tool cleanup checklist shows what it looks like when nobody's sure who owns what.
4. What does support cover after launch?
AI tools change. Models get updated, connected apps change their settings, and your business changes too. Ask:
- How long is support included, and what does it cover?
- How do I report a problem, and how fast will someone respond?
- Who watches for updates to the AI services the system depends on?
- Will someone review how it's working, such as a monthly check of results and mistakes?
A clear answer here is a good sign the developer plans to stick around, or at least plans for you to manage without them.
5. How do I switch it off?
Every AI system should have a simple, documented way to pause it. Ask the developer to show you:
- How to stop it in one or two steps, without calling anyone.
- What happens when it's off, such as calls going back to your regular line or requests landing in a shared inbox.
- Which actions need a person's approval, like sending money, deleting records or saying no to a customer.
You may never need the off switch. Knowing exactly where it is lets you say yes to AI with more confidence. Security can stay simple at this stage: limit who has access, and know where your data goes.
StorenTech AI builds AI systems in accounts our Orange County clients own, with a written scope, a clear stopping point and a simple way to switch things off.
Put the answers in writing
Once you have answers to all five, ask for them in the proposal or agreement. Then compare developers on the answers, not just the demo. The developer who explains scope, ownership, support and the off switch clearly is usually the one who'll be easiest to work with.
If you'd like to talk it through, book a 15-minute intro call at no cost. Bring your questions, and we'll answer all five for your business. If there's a fit, the next step is an AI Opportunity Map with a written plan for what to build first.
FAQ
What should I ask before hiring an AI developer?
Ask what exactly will be built, what's not included, who owns the accounts and work, what support covers after launch, and how to switch the system off.
Should my business own the accounts an AI developer sets up?
Yes. AI services, automation tools and data used for your business should be in your company's name, with your company holding the admin login.
What should an AI project scope include?
The specific jobs the AI will do, the tools it connects to, a checkable definition of done and a test period before it works on its own.
Why does an AI system need an off switch?
So you can pause it quickly without calling anyone, with calls or requests falling back to your team and risky actions always needing a person's approval.
Who builds AI for small businesses in Orange County with client-owned accounts?
StorenTech AI builds AI systems for Orange County businesses in accounts the client owns, with a written scope and a simple way to switch things off.