Why you have to ask

You cannot read the code, and you cannot judge a workflow by looking at it. What you can judge is the answers you get when you ask how it will be built, who will own it and what happens when it breaks.

That is the whole job of this list. The person you hire will know everything about the system, and you will know almost nothing, so the questions are your inspection. Ask the same seven of every candidate, in writing, and compare the answers side by side.

The person you hire might be a freelancer, an agency or a consultant. Either way, they build the connections, rules and tools that move work between your people, your software and your customers. Think quote follow-up, missed-call text-back, intake forms, invoice reminders or a voice assistant on your phone line.

A good answer is specific, written down and still true when you ask a follow-up. A bad answer is vague, delayed or irritated that you asked. Under each question below you will find both, plus a short note on how we answer it, so you can hold us to the same standard.

Question one: what exactly will you build?

Scope is where projects go wrong first, and it is the cheapest place to catch the problem. You are asking the builder to name the workflow, the systems it touches, what a person approves, what is excluded and the date it will be done.

A good answer

  • A written scope that names one workflow, the tools it connects and who approves each consequential step.
  • A plain list of what is out of scope, so you know what a later change would cost.
  • A first project small enough to finish in days or weeks, with a date.
  • Willingness to say the answer is a tool you already own, or one you can buy, when that is true.

A bad answer

  • We will figure it out as we go.
  • An AI that runs your business, with no list of what it does.
  • A single line item with no description of the work.
  • A scope that grows every time you ask a question.

How we answer it: every project starts with a free consultation and a workflow walkthrough, a fixed-scope look at one thing slowing you down. It ends in a ranked plan and an impact estimate, whether you hire us or not. A written quote and statement of work come before any work begins, and sometimes the answer is an existing tool you never have to build.

A good first project is narrow and measurable. Missed call recovery for an HVAC company is one example. Pick the one workflow that costs you the most and prove it before you ask for a second.

Questions two and three: who owns it and who holds the passwords?

Question two: who owns it when it is done?

Ownership covers three things: the accounts, the data and the work itself. The right answer is that you own all three, and the quote says so. The wrong answer is a domain registered in the builder's name, a system that lives in the builder's account or files you receive only while you keep paying.

Ask three follow-ups. Whose name is the domain registered in? Who can export the data, and in what format? What does the statement of work say you own when the project ends?

How we answer it: customers own their domain, their data and, for custom work, what the statement of work says they own. Your domain is registered in your name, you get your files on request or automatically if you cancel, and custom software ships with documentation and a proper handover.

Question three: who holds the passwords?

Every automation runs on logins: your phone system, your CRM, your email, your payment tool. You want those accounts opened in your company's name, with the builder given only the access the work needs. You also want a written list of every account, key and service the system uses.

  • Good: your admin login stays yours, the builder works with scoped access you can remove, and actions are logged.
  • Good: a handover list names every account, key and subscription, and who pays for each.
  • Bad: the builder asks for your owner password, or sets up your accounts under their own email.
  • Bad: passwords arrive by text message or sit in a shared document.

How we answer it: access during a build is scoped to what the work needs, and every action is logged. The handover includes documentation and credentials, so the system is yours to run.

Question four: what happens when it breaks?

Everything breaks eventually. A phone provider changes a setting, a software update shifts a field, a card on file expires. The question is whether you find out in an hour or in a month, and whether anyone is on the hook to fix it.

A good answer names a person, a response time and a way to see what happened. It names a backup too, for the week the builder is out. It describes a fallback, so the business keeps running by hand while the fix is made. It includes a log of every action the system took and a switch that turns the automation off.

A bad answer is that it will not break, that support is the software vendor's job, or that you are on your own after launch. Treat each of those as a no. A builder who has not planned for failure has not planned for your business.

Ask to see a failure on purpose. A confident builder will cut a connection and show you the alert, the log and the fallback. A short demonstration tells you more than a promise.

How we answer it: systems get a human sign-off at consequential steps, and every action is logged, so you can read what happened. Hosted builds carry a 99.9 percent uptime target. It is a target, and we do not call it a guarantee. Monthly plans cover updates and maintenance, and anything outside a plan is $50 an hour.

Question five: what does it cost after launch?

The build price is only the first line. Ask what you pay in month two, month ten and year two, and ask who pays for the tools the system runs on. A flat quote that leaves out the monthly costs is an invitation to a surprise.

Cost lines to ask about
Cost lineWhat to askA clear answer sounds like
The buildIs the price flat or hourly, and what is excluded?A flat price, or an hourly rate with an estimate, written in the quote
Monthly planWhat does the monthly fee cover?A short list: hosting, updates, fixes and uptime, with one plain number
Software subscriptionsWhich tools bill me directly, and for how much?A list of every subscription, in your name, with current prices
Changes laterWhat does one more change cost?An hourly rate and an estimate before any work starts
LeavingWhat does it cost to walk away?Nothing beyond what has been invoiced, plus your files and a handover

Work one example on paper. Say a builder quotes $3,000 flat and a $60 monthly plan, and the tools in your own name cost $40 a month. Suppose you also need two hours of changes in the first year at $50 an hour. Year one adds up like this.

  • The build is $3,000, quoted flat.
  • The plan is 12 times $60, or $720.
  • The subscriptions are 12 times $40, or $480.
  • The changes are 2 times $50, or $100.

Year one costs $4,300. The quote said $3,000, and now you know the real figure before you sign. In year two the build drops out, and the plan and subscriptions come to $720 plus $480, or $1,200, before any changes. A fair quote lets you see both numbers on day one.

How we answer it: a starter website is $499 plus $29 a month, and a voice assistant is $700 to set up and from $200 a month. Custom software and automation typically runs $1,000 to $5,000, flat rate or $50 an hour. Anything else is $50 an hour, invoiced weekly. The numbers are on the pricing page before you ever call.

Question six: how do I say no?

You should be able to decline the project, decline a change and leave halfway through without a fight. Ask what happens at each of those moments, because a builder's answer shows how the relationship works when you disagree.

Good answers

  • You can walk away after the first look and keep a usable plan.
  • Changes are quoted before work starts, and you can decline them.
  • Revision rounds are counted in the contract, so you know how many are included.
  • If you stop mid-project, you receive what has been built, with documentation.

Warning signs

  • A price that expires on Friday.
  • A large payment up front for work you cannot see yet.
  • A long contract with a penalty for leaving.
  • Files you can only have if you keep paying.

Practice the no before you need it. When a builder proposes an addition mid-project, ask for the price, the date and what it replaces, then take a day. A good builder is comfortable with the day, and the answer comes back in writing.

How we answer it: the walkthrough is free and its plan is yours either way. You get a written quote and a statement of work before anything starts. Three rounds of revisions are included on every project, and invoices arrive every week, so you see what you have spent while you spend it.

Question seven: how will we know it worked?

Work that cannot be measured cannot be judged. Ask the builder to name the number that should move, to record where it stands today and to agree on a date to look at it again. If they cannot, all you will have is a feeling.

Good answers are concrete. For a quote follow-up flow, the number is quotes that get any reply and jobs won from older quotes, as on the roofing quote follow-up page. For a phone line, it is missed calls and booked jobs. For intake, it is days from first contact to a signed form.

Bad answers talk about activity. Messages sent, hours saved and tasks completed all sound good and prove nothing about revenue, time or capacity. Ask for the outcome, in your own numbers, from your own records.

Set the review date before the work starts. Thirty days after launch is a reasonable first look, with a written note on what changed. If the number did not move, the next step is a smaller change.

How we answer it: we baseline the current numbers before launch, agree the yardstick in writing and report against it after launch. You see where the work stands every week, and the results are measured in your own records.

What to do this week

Use the seven questions as a script. Send them by email before you take a call, so the answers arrive in writing and you can compare candidates side by side.

  1. Scope: what exactly will you build, and what will it not do?
  2. Ownership: who owns the accounts, the data and the work when it is done?
  3. Access: who holds the passwords, and what can each person reach?
  4. Failure: what happens when it breaks, and how do I turn it off?
  5. Cost: what do I pay after launch, line by line?
  6. Exit: how do I say no, change my mind or leave?
  7. Results: which number should move, and when do we look?

Score each answer as clear, vague or missing. Two missing answers should end the conversation, and a vague one deserves a follow-up in writing. If you want to see how we answer the same seven, start with three pages. The process page lays out the six steps, the pricing page shows what work costs, and the services page lists what we build.

A good first call sounds like a conversation about your week. The builder asks which task eats the most hours, what it costs you when it slips and who touches it today. If the call is mostly about the builder's tools, ask the seven questions anyway and listen for what is missing.

A free workflow walkthrough is the lowest-risk place to start with any builder, because it ends in a ranked plan you can use with or without them. Bring your seven answers and the one process that costs you the most time.