--- title: "Who owns an AI function built for a client" description: "Define who controls client AI records, source files, service accounts, approvals, costs, and support before an agency begins building a working function." canonical: "https://scalewithsearch.com/articles/client-ai-function-ownership" --- ## 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) # Who owns an AI function built for a client Agree on ownership before building an AI function inside a client's business. Name the records, source files, accounts, and operating controls the client receives. Identify reusable firm materials and third-party dependencies separately. Then test whether the client can run the agreed function without the builder. This is a recommended delivery structure, not a statement that every agreement grants the same rights. Put the allocation in the written scope and have the appropriate reviewer check the terms. A statement about ownership should match both the agreement and the access the client receives. ## Separate the things people call the system Start with an inventory. Include the business record, instructions, executable source, tests, service accounts, model connection, logs, backups, and operating guide. Give each item a current custodian and an intended owner at handoff. The business record contains the client's approved facts and corrections. The instructions describe how the function should use that record. The source implements the job. Service accounts grant access to the systems it reads or changes. Those are different assets with different transfer questions. For example, delivering a report template does not answer who controls the account that runs it. Delivering source files does not establish permission to reuse a licensed component. Keep each question explicit rather than compressing them into one sentence that says the client owns everything. Use the existing [ownership and transfer checklist](/articles/ai-system-ownership-transfer-checklist) for the operating proof. This article focuses on agreeing to the allocation before delivery. ## Put the client's business record under client control For this delivery model, make the client the owner of its facts, accepted instructions, and correction record. Store that material in a location the client can access and export. Give the firm the access needed for the agreed work. Keep the client's current prices, approval roles, exceptions, and accepted examples together. Record where each fact came from and who may change it. When a rule changes, retain the effective date so an old example does not quietly become current policy. Do not mix this record with the firm's private prospect notes or another client's work. A shared method can describe how to prepare an update. It should not carry the customer details from the last update the firm produced. The guide to [separating client context](/articles/separate-client-context-before-agent-work) explains the retrieval boundary. The ownership schedule should name who can approve changes to that boundary. ## Identify what the firm plans to reuse List any pre-existing templates, generic connectors, testing tools, and training materials the firm intends to retain. Explain what permission the client receives to use those materials as part of the function. Make the scope readable without requiring the client to infer the distinction. A useful schedule might distinguish a general report format from the client's report configuration. The general format may remain part of the firm's reusable method. The client-specific configuration and operating record should remain available to the client under the agreed terms. Do not decide ownership by file location alone. Putting something in the client's folder does not explain its license. Keeping something in a firm repository does not establish that the client can keep using it after support ends. State the practical consequence of each retained item. Can the client modify it, hire another maintainer, and continue running the function? If a restriction affects those actions, put it beside the item. ## Give account control its own row Name the owner of the hosting, model, storage, and notification accounts used by the function. Prefer accounts in the client's business name for a function sold as client-owned. Document any shared service the firm will continue to operate. For each account, identify an administrator, billing owner, recovery contact, and export path. Record where credentials are managed without copying secret values into the ownership document. Give the builder a named access role that can be removed through the agreed process. A client-controlled account still needs a working recovery path. During handoff, ask the client's administrator to locate the relevant settings and confirm their authority. A forwarded bill or a screenshot from the builder should not be the only evidence. Where a service cannot be transferred, name that limit before work begins. Agree whether the function will move to another account or remain dependent on a separately described service. ## Assign operating decisions to people Ownership of files does not tell the team who approves an outgoing message or changes a spending limit. Add operating roles for business rules, technical maintenance, output review, and budget control. One person may fill several roles. NIST's [Govern guidance](https://airc.nist.gov/airmf-resources/playbook/govern/) recommends documenting AI responsibilities and connecting them to organizational governance. Use that guidance to examine role gaps. The ownership schedule below is an editorial application, not a NIST-required form. Source checked October 26, 2026. | Item | Proposed control at handoff | Evidence to request | |---|---|---| | Current business facts | Client's business owner | Readable record and update procedure | | Function source and configuration | As written in the scope | Repository or export plus usage terms | | Connected service account | Named client administrator | Access and recovery check | | Outgoing action | Client's named approver | Approval test and run receipt | | Reusable firm method | Allocation stated in the agreement | Clear permission for continued use | | Support after handoff | Named provider or client team | Written support boundary | Fill the table with actual people and assets. Leave unresolved rows visible until someone with authority decides them. ## Make cost control part of control Record the function's monthly AI spending limit and who receives an alert. Specify who can approve a higher limit. Include a cost line and model identifier in each run receipt. The client should be able to inspect those receipts without asking the builder for a private dashboard export. Include a documented way to pause the function. Describe what happens to queued work during the pause and what the team does manually. Separate model replacement from ownership of the record. Test another supported model against the same source material and acceptance examples before changing it. A model may produce different wording while still meeting the defined output checks. Do not promise that every dependency can be replaced without work. Name the supported replacement path and any known limits. The ownership claim should remain narrow enough to test. ## Test the exit while the relationship is healthy Before acceptance, ask an authorized client team member to locate the current source and run the sample job. Have them inspect the receipt, correct a business rule, and repeat the test. Include the documented stop and recovery steps. Then identify what still depends on the builder. A private credential, missing configuration file, or inaccessible alert destination should become an open handoff item. Close it or record the exception before calling the function transferred. Use the [repository handoff guide](/articles/transfer-the-repo-client-handoff) when source control is part of delivery. The broader test includes records and runtime access as well as code. Keep the accepted transfer evidence in the client's record. Do not treat an exit rehearsal as permission to revoke live access during testing. Schedule account changes with the owner and maintain the recovery path described in the scope. ## Explain ongoing support before acceptance State which support continues, how the client reports a failure, and who may authorize changes. Distinguish fixing an agreed function from adding a new one. Keep a current list of known limitations with the operating instructions. Train the client's team to direct the work, check its output, and record corrections. Ask someone other than the builder to perform those steps. Update the instructions wherever that person encounters a gap. Scale With Search's [AI systems offer](/ai-systems) names the owned record, working function, approval rules, receipts, and training as handoff items. Use those categories to prepare a precise scope. [Send your brief](/work#send-your-brief) with the function and the control your client needs to keep. ## Related: Ownership and Migration - [AI System Ownership and Transfer Checklist](/articles/ai-system-ownership-transfer-checklist) - [Separate Client Context Before an Agent Touches the Work](/articles/separate-client-context-before-agent-work) - [Your AI System Is Not Yours Until You Can Transfer It](/articles/transfer-the-repo-client-handoff) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```