--- title: "How to price client AI work per function" description: "Price client AI work around a defined working function, with written inputs, acceptance checks, ownership, exclusions, usage costs, and change rules." canonical: "https://scalewithsearch.com/articles/price-client-ai-work-per-function" --- ## 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) # How to price client AI work per function Price client AI work by defining a function the client can accept. Write what it reads, what it produces, who reviews the result, and which checks prove delivery. Quote the fixed price against that scope. Keep model usage, ongoing support, and later changes visible as separate terms. Here, result means a working function with agreed behavior. It does not mean a promised increase in revenue, a staffing reduction, or a guaranteed number of hours saved. The following method is a proposed way for agencies and service firms to write a priceable scope. ## Choose the unit before choosing the fee Name one recurring job from input to accepted output. A weekly client-report draft is a possible unit. A connected assistant or an AI transformation program is too broad for this example unless the scope defines its component functions. Identify the trigger, source records, output format, reviewer, and stopping point. For the report, the function might read an approved performance export and account notes, then prepare a draft for the account manager. Publishing and sending remain outside that scope. Ask the client to show the last accepted report. Record which facts it must contain and which errors would cause rejection. Those checks give the result a boundary that both parties can inspect. Keep the promised unit consistent throughout the proposal. Do not describe a draft-only function in the technical scope and imply unattended client delivery in the sales summary. ## Study enough of the business to price the right work Trace the current process with the people doing it. Identify required inputs, approvals, exceptions, and downstream readers. Ask why each step exists before deciding it belongs in the new function. Sort recurring tasks into eliminate, automate, augment, or outsource. A duplicated report may not need rebuilding. A fixed calculation may belong in ordinary code. Drafting a source-based explanation may suit AI with review. A specialist judgment may remain outside the function. Write the outcome of that study into the scope. If the client has not selected an authoritative source, record that dependency. Do not hide unresolved source or access questions inside an estimate that assumes everything will be available. Scale With Search's [AI systems offer](/ai-systems) includes the business study and task sort in the first function. That offer begins from $7,500 per function, fixed price. The published starting price is not a market average or a quote for every client. Source checked October 26, 2026. ## Write the acceptance line in business language Define the result in a sentence the client can use during review. For example: the account manager can prepare a report draft from the approved period's sources and verify each factual statement. Then add the conditions that must hold for acceptance. The sources should resolve to the correct client and period. Missing required inputs should stop the run. The output should distinguish a verified fact from a question for review. The reviewer should be able to find the draft and its run receipt. Use the [build acceptance list](/articles/what-a-build-acceptance-list-contains) to connect those requirements to observed tests. Include failures and boundaries as well as normal examples. An impressive demonstration should not replace the agreed evidence. Keep wording preferences separate from functional defects where that distinction helps review. Record the agreed style and revision terms so both parties can tell whether a request changes presentation or expands the function. ## Estimate delivery work internally A fixed price still needs an internal plan. Estimate the work required to study the process, prepare sources, build the function, test failures, train users, and hand over control. Include the known dependencies and a path for resolving them. Use that plan to decide whether you can deliver within the quoted scope. Do not manufacture a precision you do not have. If access or source quality changes the work materially, resolve that uncertainty before making a fixed commitment. The client-facing price should correspond to the written result and terms. Internally tracked effort can help the firm learn from delivery without becoming the acceptance criterion. A client should not need to infer completion from the number of hours recorded. Avoid calculating a fee from an invented value estimate. If the client supplies a business case, distinguish its assumptions from what the function itself will be tested to do. ## List inputs and exclusions beside the result Name what the client supplies: source access, accepted examples, current rules, an output reviewer, and an account owner. Specify when those inputs are needed and what happens if they remain unavailable. List exclusions that affect the result. For the report example, these might include repairing an underlying analytics setup, creating historical data, sending client messages, and adding another report type. Explain the boundary in ordinary business language. Do not bury those exclusions in a generic list disconnected from the proposal. Put the most relevant ones next to the function they limit. Ask the client to confirm the operating assumption behind each. For client work, include data authority and separation. The [client-context guide](/articles/separate-client-context-before-agent-work) provides the source-boundary checks. Access to one engagement should not become an unstated input to another. ## Separate the build price from running costs Name model usage, hosting, and third-party subscriptions in the scope. Identify the account that pays each charge. Explain whether the firm passes a cost through or the client pays it directly under the agreed arrangement. Set a monthly AI spending limit for the function and name the alert recipient. State the behavior when the limit is reached. Require a cost line and model identifier in the run receipt so the authorized owner can inspect usage. Keep the selected model in documented configuration. Test a replacement against the same acceptance cases before changing the live function. Do not promise that every substitution preserves behavior without verification. These controls make the running-cost arrangement inspectable. They do not establish a guaranteed monthly charge. Quote only the costs and terms you can support for the proposed setup. ## Define what ownership means in the price List the assets delivered at handoff. Include the client record, working function, instructions, acceptance checks, approval rules, receipts, and training promised in the scope. Identify third-party dependencies and any retained firm materials separately. Ask who can operate the function after the build. The client should know whether another maintainer can access the source, change a rule, inspect costs, and pause the job. Put restrictions beside the affected asset. Use the [ownership transfer checklist](/articles/ai-system-ownership-transfer-checklist) to test that operating control. A file delivery should not stand in for the access and instructions the agreement promises. Include training in acceptance when the client is expected to run the function. Ask the intended user to direct a sample run, check it, record a correction, and locate the receipt. Fix gaps in the guide before closing handoff. ## Put changes and support in writing Distinguish a correction to agreed behavior from a request for another result. If the report cites the wrong client's source, that is a failure against the boundary. Adding a new channel or recipient changes the requested function. Record new requests with their sources, output requirements, risks, and acceptance checks. Price the changed scope before implementing it. Keep the current accepted function usable while the client considers the expansion. State who handles broken connections, updates, and failed runs after handoff. Name the support term and the route for reporting a problem. Do not let a fixed build price silently imply indefinite maintenance. Keep an accepted exception visible if the client agrees to it. Explain its impact and owner. Avoid describing a function as complete while an unresolved critical boundary is hidden in a separate conversation. ## Use evidence to close delivery Test ordinary inputs, missing sources, wrong-client requests, duplicate requests, and the stop procedure. Have the client inspect the evidence against the acceptance list. Record which version and configuration passed. NIST's [Measure guidance](https://airc.nist.gov/airmf-resources/playbook/measure/) recommends testing fitness for purpose and defining acceptable limits. It supports a measured acceptance process, not a guarantee of a client's commercial results. Source checked October 26, 2026. Bring one function, its accepted output, and the person who will review it to [Scale With Search's AI systems scope](/ai-systems). The written proposal states the result, price, inputs, exclusions, and handoff checks. [Send your brief](/work#send-your-brief). ## Related: Ownership and Migration - [What a Build Acceptance List Contains](/articles/what-a-build-acceptance-list-contains) - [Separate Client Context Before an Agent Touches the Work](/articles/separate-client-context-before-agent-work) - [AI System Ownership and Transfer Checklist](/articles/ai-system-ownership-transfer-checklist) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```