--- title: "An AI-Native Structure for a Company Under 20 People" description: "Map AI work in a company under twenty people. Assign source owners, reviewers, spending limits, and client boundaries without inventing new departments." canonical: "https://scalewithsearch.com/articles/ai-native-company-under-20-people" --- ## 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 should a company under 20 people organize AI work? For a company under twenty people, organize AI around a few explicit responsibilities: business direction, source ownership, function operation, review, and system maintenance. Assign those responsibilities to the people who already understand the work. One person can hold several of them. Start with one recurring function and its manual fallback. Keep the source record, task instructions, checks, and spending rules accessible to the authorized team. Train a backup before treating the handoff as complete. This is a proposed operating structure for a small company. It is not a claim that a particular headcount requires AI or that a smaller team should remove roles. Use it to decide who directs and checks the work you choose to build. ## Map responsibility before drawing a new organization chart Write the path of one current job. For example, imagine a fictional twelve-person service firm preparing weekly project updates. An employee gathers status, drafts the update, checks commitments, and sends the accepted message. Assign responsibility to each stage before proposing a function. Who knows whether the job status is current? Who can approve a change in scope? Who decides whether a customer-facing statement is accurate? Keep those responsibilities visible when the system begins preparing the draft. A function that assembles information still needs people who own the information and its use. Avoid leaving all exceptions with an unnamed owner. [NIST's voluntary AI Risk Management Framework](https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf), GOVERN 2.1, calls for clear, documented responsibilities and communication. This small-team design is one practical interpretation. Source checked 2026.10.26. ## Use five responsibilities for the first function Treat the following as responsibilities to assign, not five new job titles. Write a primary person and an authorized backup where the work requires absence coverage. | Responsibility | Main decision | Evidence to maintain | |---|---|---| | Business direction | Which job matters and what may be spent | Scope, priorities, spending authorization | | Source ownership | Which facts and rules are current | Source references and accepted corrections | | Function operation | When to start, hold, or retry the job | Runbook and run receipt | | Output review | Whether the result meets the scope | Checks, approval, unresolved questions | | System maintenance | Whether access and controls work | Configuration history and acceptance results | In a very small firm, the owner may hold business direction and output review. An experienced employee may own sources and operate the function. Name each duty even when the same person performs several. The [small-team approval matrix](/articles/ai-agent-approval-matrix) helps translate these assignments into action permissions. It is especially useful when a draft can lead to a send, purchase, publication, or account change. ## Keep one maintained explanation of how the business works Prepare a short business record that explains the rules relevant to the function. Include the current offer or service scope, source locations, approval responsibilities, and accepted corrections. Give each part an owner. Keep changing transactional facts in their controlled source system. The explanatory record can point to current project status rather than duplicate every status entry. State which source takes priority if records disagree. For the fictional project update, the function might read the active scope and the latest approved status. It should stop if either required source is missing. The reviewer should see the missing item with the draft. The [business-memory guide](/articles/business-memory-for-ai-agents-guide) explains the record in detail. Start with the information needed for the first function, then add material when a defined job requires it. ## Sort work across the existing team Ask each person to describe a recurring task they carry and the result it supports. Study the task before choosing a treatment. Put each step under eliminate, automate, augment, or outsource. Remove a duplicate report when its owner agrees it is unnecessary. Use a fixed check for required fields. Consider AI assistance for preparing a reviewable summary. Keep specialist judgment with the qualified person responsible. These are options to evaluate against the company's actual work. Do not set a target percentage of tasks to automate. Also avoid promising a headcount change or a fixed saving before testing the proposed process. The [AI systems method](/ai-systems) uses this study and sort before building a function. That order gives the owner a reason for the work and a defined result to accept. ## Build one function with a visible end For the fictional firm, begin with preparing project-update drafts. Define the reporting period, source records, expected format, reviewer, and stopping conditions. Keep delivery as a separately authorized action. Use the three-stage 10/80/10 design: a person sets direction, the system prepares the middle, and a person checks the result. Treat the numbers as a shorthand for responsibilities, rather than a promised division of time. Write acceptance cases before the first trial. Include an ordinary project, missing status, a disputed scope change, and an unavailable reviewer. State what the function should return in each case. Keep its initial permissions narrow. A draft-preparation function needs the ability to produce a draft. Do not give it unrelated account or payment permissions merely because the connection could support them. ## Set the review path for ordinary days and absences Name who checks the draft and where it waits. Define what approval covers. Permission to accept wording should not imply permission to change a price or promise a new delivery date. For absence coverage, give a backup access to the approved sources and checks. Practice the handoff with an example before relying on it. If the required reviewer is unavailable, hold the draft under the written rule. Keep the function's manual path in the runbook. An employee should know how to complete the customer update or explain why it must wait. Avoid requiring the original builder to answer every interruption. The [guide to testing before production](/articles/test-an-ai-agent-before-production) covers these failure cases. A small team should be able to inspect whether the handoff works, including when the normal person is away. ## Give each function its own cost and stop Assign a monthly AI spending limit and the person who receives alerts. State what happens at the limit. Require a receipt with sources, output, checks, model, and cost for each run. Keep the function's account ownership clear. Identify who can change its spending settings and who can stop new runs. Test that stop within the bounded trial before allowing wider use. Separate subscription charges from any usage charges in the budget. Review actual costs alongside the work produced. Avoid comparing arrangements using only the most visible subscription line. Use the [receipt guide](/articles/receipt-is-part-of-the-output) to make each attempt inspectable. Include stopped runs and retries. The record should show why work halted and who needs to resolve it. ## Keep client work within client boundaries For a firm running work for other businesses, assign a source owner and reviewer for each client function. Keep each client's material, permissions, and outputs separate. Identify where the client must authorize an action. Test the boundary with a request that asks for another client's information. The expected result should be a stop under the written access rule. Check the retrieval path as well as the final draft. Keep business records and runbooks transferable under the agreed scope. A client should know what it owns, who maintains it, and how it continues when a provider or model changes. Begin with the firm's own function when that is the agreed first scope. Use the resulting operating evidence to discuss a client build. Keep claims about performance tied to the tests and work you can show. ## Train the people who will carry the work Ask the primary employee to start the function, inspect its receipt, reject an incorrect output, and record an approved correction. Ask the backup to repeat the exercise using the runbook. Watch for instructions that exist only in someone's memory. Put them in the relevant source or procedure. Recheck the acceptance cases after changing the instruction or model. Expand only when the responsible people can explain the current function and its limits. The next function should have its own result, sources, reviewer, spending boundary, and handoff checks. Scale With Search studies the business, builds one function at a time, and trains the team to direct and check it. Read the [AI systems scope](/ai-systems), then [send the recurring job your team wants to change](/work#send-your-brief). ## Related: Agent Governance - [An AI Agent Approval Matrix for Small Teams](/articles/ai-agent-approval-matrix) - [The Complete Guide to Business Memory for AI Agents](/articles/business-memory-for-ai-agents-guide) - [How to Test an AI Agent Before It Touches Production](/articles/test-an-ai-agent-before-production) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```