The useful question in an AI proposal is not just “what can the assistant do?” It is “what will we own, who will keep it working, and what happens if we leave?” These questions matter whether you choose a managed service, a freelancer, or someone on your own team.
This is a practical buying checklist for Canadian and North American small businesses. It does not assume a particular supplier, financing program, or contract model. Use it to make two proposals comparable before deciding on price.
Describe the outcome and its limits
Ask for the workflow in plain language: what triggers it, what information it reads, what it may change, and when a person takes over. “AI receptionist” is too broad. “Capture an after-hours plumbing enquiry and send it to the dispatch queue, without promising a price or emergency arrival time” is something you can test.
Write down exclusions as carefully as features. If the system cannot reliably book against your actual calendar, the proposal should say it collects a booking request rather than confirming an appointment.
Know which accounts you control
| Item | Question for the proposal |
|---|---|
| Phone number and messaging channels | Who is the registered owner, and can the number or account move to another provider? |
| CRM and calendar connection | Which permissions are needed, and can you revoke them without losing your records? |
| Hosting and model accounts | Are these yours or the provider's? Which charges and usage limits can you see? |
| Workflow and instructions | What configuration, documentation, or code will you receive on exit? |
| Customer records and logs | Can you export the data in a usable format, and what gets deleted when the engagement ends? |
A managed service can legitimately run on provider-owned infrastructure. The important point is a written explanation of what transfers, what does not, and what a replacement would require. Do not assume that paying an invoice automatically transfers every component.
Agree on acceptance tests
Ask the provider to demonstrate the workflow using your actual business rules and a safe test environment. Include an unavailable appointment, duplicate request, failed integration, unclear customer answer, and request for a human. Agree which failures block launch and who signs off.
Keep the test cases and results. Run them again after material changes to the workflow or underlying services. A screen recording of a successful demo is useful, but it is not a substitute for a repeatable test.
Price the work after launch
Separate initial setup from ongoing charges. Ask what the base fee covers, how voice or message usage is billed, what happens at a limit, and how changes are estimated. Make the currency explicit; do not compare a USD software price directly with a CAD service quote.
Name the tasks that continue every month: reviewing failures, changing instructions, fixing integrations, checking permissions, and reporting results. With a freelancer, these may be separate assignments. With a managed service, some may be included. Compare the responsibilities, not just the invoice totals.
Get a support and fallback plan
Who receives an alert when the integration fails? Who can turn off automated actions? What does the customer hear if the phone workflow is unavailable? Ask for response commitments by severity, the hours covered, and any additional support charges.
Test the fallback before launch. Someone on your team should know how to return to a manual queue or existing phone process. Store the instructions where they remain accessible during an outage.
Make customer-data handling explicit
Document the services receiving customer information, the purpose of that access, retention, deletion, and any use of the data for training. Limit access to the work being performed. For Canadian businesses, the privacy commissioners' generative AI principles explain why using an AI service does not remove the organization's own privacy responsibilities. Requirements depend on the sector, location, and activity.
Ask for a handover rehearsal
Before the final milestone, have someone other than the original builder follow the runbook: find the configuration, change a safe test rule, export a sample record, identify a failed run, and use the fallback. Record what they cannot do without help.
That exercise is useful even if you intend to keep the provider for years. It exposes missing documentation and makes support less dependent on one person's memory.
Choose the arrangement that fits your team
A defined freelance project can work well when you have an internal owner who can coordinate maintenance. A managed service can fit when you want one provider accountable for operation. In-house work can fit when the workflow is central to your business and you have the time and skills to maintain it.
Use the pilot checklist to test the business case first. Our cost guide explains the human oversight component and one route to sourcing independent expertise. You can use both checklists with any provider, including us.