How to Buy AI Software for a Shop or Restaurant: Pre-Purchase Checks

Before buying AI software, a shop or restaurant should check five things: run the trial on your real busy-day cases, read the term and renewal clause, test a data export, get the overage rate in writing, and find the cancellation steps before you pay. If any answer is unclear, don't sign yet.

The reason is simple. AI tools for small businesses are cheap to start and awkward to leave. A $150 monthly phone tool that renews annually, charges per call beyond its allowance and holds your customer conversations is a larger decision than its sticker price suggests. This checklist is built for an owner who has to decide on a Tuesday afternoon between jobs.

Follow me on Instagram@sagnikteaches

Start with the job, not the product

Write down the single job you want done and how you will know it is done. "Answer the phone during the Friday dinner rush so we stop missing bookings" is testable. "Use more AI" is not. A job statement gives you a pass mark for the trial and a number for the budget.

Connect on LinkedInSagnik Bhattacharya

Also check whether you already own the feature. Many point-of-sale systems, website builders and booking tools now include an AI assistant at no extra cost; Toast's base assistant, for example, is included with its POS, and Shopify says Sidekick is included with your Shopify plan, with features and usage limits varying by plan. The tutorial on POS-built AI versus add-on tools is worth five minutes first.

Subscribe on YouTube@sagnikteaches

The trial test: what to run before you pay

A trial that you poke at casually proves nothing. Prepare ten test cases from your real week before you start, and run them all.

Ten cases for a restaurant

1. A booking for 6 at 7:30pm on your busiest night.
2. A change of booking time by phone or message.
3. A question about opening hours on a public holiday.
4. A question about a dish containing nuts (the tool should hand over to a person, not answer).
5. A request for a menu item you have run out of.
6. An angry complaint about a cold dish.
7. A caller who speaks fast and gives a name that is hard to spell.
8. A request in another language your customers use.
9. A call at 3am, when nobody is there.
10. A question the tool should not know the answer to, such as the owner's mobile number.

Ten cases for a shop

1. "Is this item in stock in my size?" for an item you do have, and one you do not.
2. A return request past your return window.
3. A delivery question for an order placed yesterday.
4. A request for a discount code that does not exist.
5. A product question where your listing is incomplete.
6. A complaint with an upset tone.
7. A question about a competitor's product.
8. A gift request that needs a note added.
9. A message with a typo-heavy, vague question.
10. A message that tries to make the tool say something rude or promise a refund.

Score each case: right and safe, right but clumsy, wrong, or wrong and harmful. Any "wrong and harmful" answer, such as inventing a refund policy or giving allergen advice, should halt the purchase until the vendor explains how to prevent it. For a deeper trial script, the twelve restaurant AI vendor questions add more.

What the log looks like when filled in

Trial log - phone assistant, 14 days, restaurant (illustrative)
Calls handled by tool:        62
Booked correctly:             44
Passed to staff correctly:    11
Wrong time or party size:      4   <-- reason: name/number misheard
Invented an answer:            2   <-- both about opening hours
Hung up on caller:            1
Decision rule: 2 invented answers in 62 calls = fix before buying

Here 44 of 62 calls booked correctly and 11 were handed over properly, which sounds good, but "invented an answer" twice is the fact that matters. Ask the vendor how to lock opening hours into a fixed source, then rerun that test.

Contract length, renewal and price rises

Read four things in the terms, every time.

• Minimum term. Monthly, annual or multi-year? Is the free trial converted to paid automatically with a card on file?
• Renewal. Does it renew automatically, for how long, and how much notice do you need to give? Put the notice date in your calendar the day you sign.
• Price changes. Can the vendor raise the price mid-term? Are prices fixed for the first term?
• Refund policy. If it does not work, what comes back and by when? Some vendors do not refund annual payments; ask in writing.

Small vendors in particular change plans often. Seat counts and allowances move, and a plan you chose for one allowance may stop being sold. The lesson from several tool shutdowns and plan changes this year is that a monthly contract is the cheapest insurance a small business can buy.

Data: what goes in, what you can get out

Ask four plain questions and expect plain answers.

1. What data does the tool see? Customer names, phone numbers, order history, card details, conversation recordings?
2. Is it used to train models? Business and API plans from the big vendors usually do not train on your content by default, but smaller vendors vary. Get the answer in the data terms, not from a sales call.
3. Can I export it? Customers, conversations, settings, prompts, knowledge base. In which format, free or paid?
4. What happens when I leave? How long is your data kept, and can you request deletion?

Test the export during the trial. Download it, open it in a spreadsheet, and check that it is complete and readable. If the vendor says "contact support" for exports, that is a yellow flag; if the export is impossible, that is red. The tutorial on keeping your data portable explains what a good export looks like. If you have customers in the EU, the GDPR covers the personal data you share with the tool, so ask the vendor for its data processing terms as well.

Per-minute, per-call and per-contact overage

The headline price is rarely the price you pay in a busy month. Many AI tools bill a base fee including an allowance, then charge more beyond it. The unit varies: calls, minutes, conversations, contacts, messages, tasks, or credits.

Some real examples of how differently vendors count: Smith.ai's free plan includes 25 calls and then $3 a call, while its Pro plan starts at $150 a month; Botpress's free plan covers 100 conversations a month; Zapier bills per task, and its plans page says overage runs at 1.25 times the task cost on your plan, with opt-in required. Those are the shapes to look for. For each tool, ask: what is the unit, what does the plan include, what happens past the limit (extra charge, or the tool stops), and is there a cap?

A two-vendor cost comparison

An illustrative comparison for a 40-seat restaurant that expects about 300 calls a month, rising to 450 in December. Neither vendor is real; the shapes are common.

On sticker price Vendor A looks $50 cheaper. At your real volume, it is about $1,100 more expensive across a year. But Vendor B needs a year's commitment and a set-up fee. If the trial reveals that Vendor B misses the cases from your test list, you have locked in a failure. Sensible choice: ask Vendor B for a monthly or a ninety-day paid pilot, and make the decision on the trial log, not the table. Rerun the sum with your own volumes; the arithmetic is a minute's work.

Cancellation: find the steps before you pay

Cancellation should take no more steps than signing up. Before you buy, find out:

• Where the cancel button is, or whether you must email or phone.
• How much notice is needed, and whether the cancellation takes effect at the end of the paid period.
• Whether the phone number the tool uses belongs to you or the vendor. If the vendor owns it and you advertise it, cancelling could cost you the number. The tutorial on protecting your number, data and exit covers this.
• Whether integrations (website widget, booking link, POS connection) stop working at once, and who removes them.

Try cancelling during the trial. Many vendors let you start a cancellation without finishing it, so you can see how many steps it takes. If the process hides behind a "talk to us" wall, factor that in.

How a missed notice date shows up

An illustrative case. A café signs up for a review-reply tool on a twelve-month term that renews automatically unless cancelled 30 days before the end. The owner stops using it after five months but never cancels, assuming the card charge will simply be stopped when the card expires. The vendor bills the renewal to the updated card the bank issued, and the café finds a full year's fee on its statement two weeks after the notice window closed. The terms allowed it. The two-minute fix would have been on the purchase sheet: a calendar entry 45 days before renewal, with the cancellation steps written next to it, and a screenshot of the confirmation email once it is done.

Support, uptime and what happens when it breaks

A tool that works 98 per cent of the time still fails on the busiest night. Ask what support covers, when, and how fast a fault gets looked at. Ask what a customer experiences if the tool is down: voicemail, a busy tone, a wrong message? Ask for the status page, and read what past incidents look like. For a shop, check whether the chat widget goes quiet or shows an error to a shopper. A fallback you can switch on in two minutes, such as forwarding calls to a mobile, is worth more than any uptime promise.

A one-page purchase sheet

Tool: __________   Job it must do: ______________________
Trial length: ___ days   Card needed? Y/N   Trial log passed? Y/N
Test cases run: ___/10   Harmful wrong answers: ___ (must be 0)
Price per month: $___    Billing: monthly / annual
Allowance: ___ per month    Overage: $___ per ___    Capped? Y/N
Peak-month cost (my busiest): $___
Term: ___   Renews automatically? Y/N   Notice needed: ___ days
Cancel steps: _______   Notice date in calendar? Y/N
Data export tested? Y/N   Format: ____   Fee: $___
Trained on my data? ______   Deleted after exit in: ___ days
Phone number / domain owned by me? Y/N
Support hours: ______   Fallback if down: ______
Decision: buy monthly / negotiate / walk away

A filled-in example for a small shop

A homeware shop is considering a chat assistant for its website at $32 a month with no free plan. It runs its ten test cases in a trial on a free tier of another tool first, since it wants to know what the job looks like. Nine come out fine, one invents a returns policy. The shop adds its actual returns page to the tool's knowledge, reruns the test, and gets ten out of ten. It then buys the paid plan on a monthly term, notes the cancellation page address, and sets a calendar reminder for day 60 to compare hours saved with the fee. The shop spent two hours on the test and avoided buying on the basis of a demo.

A per-contact example for a shop

Restaurants meet per-call pricing; shops more often meet per-contact pricing in email and messaging tools. Say a boutique has 1,800 customers on its list and a tool charges by contact band: up to 1,000 for $30, up to 2,500 for $55, up to 5,000 for $95. The shop pays $55. A busy autumn sign-up campaign takes the list to 2,600, which tips it into the $95 band, a $40 jump for 100 extra people. Before you buy, ask where the bands sit, whether unsubscribed and bounced contacts count, and whether the tool bills on the day you cross a band or at the next renewal. Then check whether you can pre-empt it by pruning inactive addresses. These details are written in the pricing notes, rarely in the sales page.

Ask for a pilot, and ask in writing

When a tool passes the trial but the vendor wants an annual term, propose a paid pilot of one to three months at the monthly price. Many small vendors agree because a pilot is a sale. Put the request in an email so the answer is on record. An illustrative message:

Hi [vendor contact first name],
We've finished the trial and the phone assistant handled most of our test
calls. Before committing, we'd like a 3-month paid pilot on the monthly
plan, with the right to move to annual at the annual rate afterwards. Could
you confirm in writing: (1) the monthly price and call allowance, (2) the
overage rate per call, (3) that we own our phone number, (4) how to export
our call logs and settings, and (5) the notice needed to cancel.
Thanks, [your name]

Vendors who answer all five points clearly in one reply are usually vendors you can work with. Vendors who dodge two of them have told you something too.

Ask someone who already uses it

A reference from a similar business is worth more than a testimonial on a website. Ask the vendor for two customers with a shop or restaurant of a similar size, and ask those customers three things: what went wrong in the first month, what they pay in a busy month compared with the quote, and whether they tried to cancel. Do not accept a reference who is a partner of the vendor without knowing it. If the vendor cannot name anyone, look on public review pages and read the three-star reviews first, since they tend to describe real problems rather than praise or rage. The tutorial on checking an AI vendor's customer references has a short script for the call.

A 90-minute buying routine

An owner has 90 minutes. Here is how I would spend them. Spend 10 minutes writing the job and pass mark. Spend 15 minutes checking whether your POS, booking tool or website builder already offers the feature. Spend 20 minutes reading the pricing page and terms for the six items on the purchase sheet. Spend 30 minutes building and running the first four trial cases. Spend 10 minutes emailing the vendor the pilot request. Spend 5 minutes putting the trial end date and the cancellation notice date in your calendar. That is a decision process, not a research project, and it covers nearly every risk in this checklist. Larger decisions deserve more time, but this much is the minimum for any tool that touches customers or costs more than a few hundred dollars a year.

After you buy: the first thirty days

The purchase is not the end of the checking. In the first week, read a sample of what the tool did every day. In the second week, compare the bill with the quote; if usage is higher than you expected, find out why. In the third week, ask staff what annoys them about it. At day 30, compare hours saved with the fee and decide to keep, change plan or cancel before any auto-renewal catches you. Write the finding on your purchase sheet. A record like that makes the next purchase faster and helps you spot which vendors give you a fair deal.

Who gets access, and who can change what

A tool that speaks to customers should have an owner inside your business. Decide who can edit its instructions, who can see conversations and who can switch it off. Ask the vendor whether accounts can have different permission levels, whether shared logins are allowed (some terms forbid them), and whether you can see a log of changes. In a restaurant, a manager on shift should be able to pause the phone assistant in one click when the kitchen is overwhelmed; in a shop, whoever runs the website should be able to hide the chat widget during a stock error. If the only person who can change anything is the vendor's support team, every correction costs you a day.

Red flags that should stop you

• No way to try it without a sales call or a card.
• Prices "on request" for a tool aimed at tiny businesses, with no range given.
• Claims about savings with no method behind them. You can test claims on your own data; do so.
• An annual contract with no refund window and a new product.
• Vague answers on where data is stored or whether it trains models.
• A salesperson who dislikes your test list.

The tutorial on evaluating an AI software vendor gives a scorecard you can combine with this sheet. If you would rather read the terms with someone, that is what my AI implementation consultation covers.

Buying questions owners ask

How long should an AI software trial be?

Long enough to see two of your busiest days and one quiet one, so usually 14 days at least. If the trial is shorter or needs a card, ask for an extension in writing. A trial that ends before you have tested a hard case, such as an allergen question or a refund, has not tested the product.

Is a monthly contract always better than an annual one?

Not always. Annual plans often cost less per month, but only make sense once the tool has proved itself for a full quarter. Start monthly where it is offered. If only annual is available, ask for a refund window, check the renewal date, and put it in your calendar.

What is an overage charge?

It is the extra fee when you use more than your plan includes, for example calls, minutes, conversations or contacts. Ask for the rate in writing and work out your busiest month, not your average one, because a Saturday rush or a sale week can double usage.

Can I get my data back if I cancel?

Only if the terms say so. Before buying, ask what you can export (customers, conversations, prompts, settings), in what format, whether it costs extra, and how long the vendor keeps your data after you leave. Test an export during the trial rather than trusting the promise.

Further reads

• AI Software for Retail Stores: Five Checks Before You Buy — Five retail-specific checks to run alongside this list.
• What AI Costs a Small Retail Shop in Its First Year — A first-year cost picture for a small shop.
• What to Check in an AI Vendor's Data Processing Agreement — What to look for in the data terms before you sign.
• What If Your AI Vendor Shuts Down? Checks Before You Commit — A contingency plan if your vendor closes or changes plans.
• What Uptime and Support Should an AI Vendor Promise You? — What uptime and support promises should actually say.
• Questions to Ask an AI Vendor Before You Sign Anything — The full list of questions to put to any AI vendor.
• Use the AI Already in Your Practice Software Before Buying More — Use the AI already in your tools before buying more.
• How to Start a Business Using AI: Tools and Costs for a Small Shop — A costed one-shop starter plan: idea test, name, store, first customers and admin, with monthly tool budgets at three levels and the break-even orders.
• Repair Shop Software for Bike Shops: Service Bookings and Quotes With AI — Service tiers, intake questions, a spring-rush booking cap worked out in bench hours, and a quote prompt that only uses your own price list.
• What Toast IQ Can and Cannot Tell You About Sales and Labour — Toast IQ's real reach on sales and labour: example owner prompts, the limits Toast's pages skip, and a five-minute check before you act on a number.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: vendor pricing pages for Smith.ai, Chatbase, Botpress and Zapier read in September and October 2026; the two-vendor comparison is an illustration, not real vendors.