--- title: "Questions to ask before paying for an AI build" description: "Check the result, scope, access, acceptance, costs, ownership, and payment terms before paying for an AI build, with a practical buyer decision sheet." canonical: "https://scalewithsearch.com/articles/questions-before-paying-ai-build" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Questions to ask before paying for an AI build Before paying for an AI build, ask what you are buying and how completion will be checked. Ask what your team must provide and what you will control afterward. Get the answers into the scope that accompanies the invoice. This guide concerns the decision to release payment. For detailed security and runtime evaluation, use the [AI agent vendor questionnaire](/articles/questions-before-buying-ai-agent-system). Here, the goal is to connect the sales discussion, written scope, invoice, and acceptance plan. Use one decision sheet. For each question, record the written answer, the evidence location, and any condition that remains unresolved. ## What exact result does this payment buy? Ask the supplier to name the first function and show an example of its expected output. Replace broad phrases such as AI transformation with a job your operator can recognize. For an illustrative internal reporting function, the result might be a draft assembled from approved weekly updates. State whether it includes identifying missing updates, producing a summary, and placing that summary in a review folder. State whether anything gets sent. Separate this first function from future ideas discussed during the call. Ask which ideas are included, excluded, or reserved for another scope. Keep the same function name on the scope and invoice so your budget owner can connect payment to delivery. ## Is the study included, and what does it return? Ask what the supplier needs to learn before choosing the build. The study should end with a decision you can inspect. Request the task list, proposed function, required inputs, and reasons for excluding other work. Ask whether the study is part of the first build or a separately purchased piece of work. If it is separate, identify the deliverable and whether a later build is optional. Avoid assuming a discovery call and a paid study have the same depth. Ask what happens if the study finds that the task should be eliminated or remain manual. Write down how that finding affects the scope and payment terms before you pay. ## Who accepts the result, using which checks? Name a person in your business who can judge the function. Give them the acceptance list before payment. Ask them to explain what a pass and a failure would look like. NIST's AI RMF Core includes documented testing and evaluation under conditions similar to deployment. Use that principle when requesting checks relevant to your actual job. [NIST AI RMF Core](https://airc.nist.gov/airmf-resources/airmf/5-sec-core/) (checked October 26, 2026). Request at least an ordinary case, a missing-input case, and a case requiring human approval. Define the expected behavior for each. The [build acceptance guide](/articles/what-a-build-acceptance-list-contains) provides more detail. Ask how failed checks are corrected and who records the final decision. ## What must our business provide? Ask for a buyer input list. Name the records, account access, process decisions, sample outputs, and staff participation the build requires. Assign an owner to each item. Identify anything unavailable today. A missing source file or unresolved approval role should remain a visible condition. Ask how missing inputs affect the schedule and whether the supplier can begin useful work without them. For example, your operator may know which report format is correct while nobody has approved a current template. Resolve that choice before expecting the builder to encode it. Do not ask a supplier to infer your business policy from conflicting examples. Record the approved choice where your team can maintain it. ## What access is needed before and after delivery? Ask the supplier to list each account, its access purpose, permission level, and required access period. Separate evaluation access from production access. Request a safe way to begin with sample data. If real business records are necessary, decide which records are authorized and who grants access. Keep that decision distinct from the decision to pay an invoice. At handoff, name the person who controls each account. Ask how temporary supplier access is removed and how your operator obtains help afterward. Have the supplier distinguish the files it delivers from the hosted services those files depend on. Record unresolved access or data-use questions before committing to the build. ## Which charges continue after the build? Request a cost list covering model usage, hosting, storage, connected services, and ongoing maintenance if offered. Ask which charges go directly to accounts in your business's name. For usage-based charges, request the assumptions behind the estimate. Ask what gets counted, when billing information becomes available, and how retries are treated. Do not treat an estimate as a fixed ceiling unless the scope provides an enforced limit. Name a spend limit and alert recipient for the function. Ask what happens when the limit is reached. The answer should identify whether the function pauses, reduces work under an agreed rule, or asks for a new decision. Keep the behavior explicit. ## What will we own, and what will we license? Ask for an inventory of delivered records, operating rules, code, tests, runbooks, and run history. Request the agreed rights for each item. Identify third-party components separately. Ask whether another provider can maintain the result. Have the supplier show how your business gets its facts and corrections back in readable form. A statement about data ownership should be accompanied by an access and export plan. Use the [ownership transfer checklist](/articles/ai-system-ownership-transfer-checklist) for operational proof. Before payment, establish what proof belongs in your acceptance plan. Ask which parts need replacement if you stop using a particular platform. Keep that answer with the recurring cost list. ## What happens when something changes? Ask the supplier to separate a defect from a new request. A defect might be failing an agreed check. A new request might add another input source or authorize a new external action. Use examples from your proposed function. Write down the correction process, support period, contact route, and any exclusions. Ask how a changed dependency is assessed. Avoid assuming that every future model, connector, or account change is included in the original price. Define how additional work gets approved. Request a written change describing the result, price, schedule effect, and acceptance checks. Keep ordinary corrections within the agreed scope and evaluate new functions as separate purchasing decisions. ## What payment and cancellation terms are written? Read the scope and payment terms together. Check the amount, currency, due date, payment schedule, and any stated cancellation or refund policy. Ask the supplier to resolve inconsistent wording in writing. Do not assume payment is tied to milestones. Do not assume a trial, refund, or ongoing support exists unless the terms state it. If a condition matters to your decision, have it resolved before sending payment. Keep any sales promise that influenced the purchase beside the terms for review. Ask whether the written scope includes that promise. This is a purchasing check, rather than a conclusion about contractual rights. Obtain appropriate professional review when your business needs advice on the agreement. ## Can the future operator explain the purchase? Give the decision sheet to the person who will run the function. Ask them to find the input list, expected output, approval rule, cost limit, and failure contact. Have them work without the salesperson’s help. Have the budget owner check the scope against the invoice. Have the acceptance owner check that the tests describe the promised work. Mark unanswered questions as conditions, then decide which must be resolved before payment. Record a clear decision: proceed under the written scope, request a revision, or defer the purchase. Keep the final version of the scope with the decision. That gives the delivery team and your operator the same reference when work begins. ## Connect payment to a defined function Scale With Search prices AI work per function, from $7,500. The first function includes the study and sort. Each function is paid in full before work starts, and all sales are final. The written scope states the result, required material, exclusions, price, and acceptance checks. Read [AI systems for your business](/ai-systems) for the current method and terms. To put a first function into writing, [send your brief](/work#send-your-brief). ## Related: Ownership and Migration - [Twenty Questions Before You Buy an AI Agent System](/articles/questions-before-buying-ai-agent-system) - [What a Build Acceptance List Contains](/articles/what-a-build-acceptance-list-contains) - [AI System Ownership and Transfer Checklist](/articles/ai-system-ownership-transfer-checklist) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```