Nobody Sells a Shared Brain: Own Your Files, Swap Any Model, Make Every Job Teach the Next One

Over the last few weeks, we set out to answer a question contractors, field operators, and growing businesses keep asking: does anyone actually sell an AI “shared brain”?

We wanted three things. First, a central company knowledge base holding our standard operating procedures, pricing schedules, safety protocols, and drying standards. Second, AI agents our whole team can query in plain language from a phone or desk. Third, an automated loop that takes the reality of every finished job—walkthrough videos, moisture logs, readings, photos, and voice notes—and distils lessons back into that knowledge base so the company gets smarter every week.

We spent weeks auditing vendor documentation, testing APIs, and checking rate cards. The short answer: nobody sells the whole system.

Meta, Google, Microsoft, OpenAI, and Anthropic each sell pieces of the puzzle, but none sells the complete loop. Even worse, each suite keeps your knowledge inside its own walls. Gemini answers from Google Drive. Copilot queries SharePoint and Microsoft Graph. ChatGPT and Claude work best when you upload files into their proprietary Projects.

If you build inside a vendor’s closed project, you haven’t built an asset you own. You’ve rented space in someone else’s walled garden. When that vendor changes pricing, alters terms, or falls behind a rival model, your architecture breaks.

The design that survives vendor churn is deliberately boring: keep your source files in a standard folder tree you own, run a lightweight distillation loop across any model API, and treat chat interfaces as porches that plug in and out. If your files live in ordinary formats on storage you control, you can swap models in fifteen minutes by changing one line in a script. The files, lessons, and team habits never move.

Meta, Untangled: Three Products and One Name

Much of the current confusion comes from Meta using the name “Muse” for three completely different offerings with three distinct price lists. Mixing them up will mis-budget your project from day one.

First is the Meta Muse app. Per Meta’s help pages, Muse is strictly a personal AI agent tied to individual Meta accounts, not a team platform. Meta offers a free tier with an unpublished usage limit, alongside two paid tiers: Power at $20 a month for 500 million Muse tokens a week, and Maximum at $100 a month for 3 billion tokens a week. These subscriptions buy additional usage rather than extra business features. Meta describes zero team seats, zero shared workspaces, zero admin consoles, and zero central billing. Knowledge in the Muse app lives in an isolated virtual machine for one person. It cannot serve as a company brain; at most, it is an owner’s personal chief of staff.

Second is Meta Business Agent. Rolled out globally in June 2026, this is a customer porch running on WhatsApp, Messenger, and Instagram. It handles inbound inquiries, qualifies leads, recommends catalog items, and hands off to human staff. Per industry reporting on Meta’s pricing documentation, Platform usage is listed at $2.00 per million tokens starting August 2026—roughly 4 to 5 cents per message exchange. Verify in your Meta console before budgeting.

Meta also sells in-app access via Meta One tiers, from Essential at $14.99 a month to Max at $499 a month per WhatsApp profile. The subscription price is published; the response volume per tier is not, so cost per conversation cannot be modelled. Furthermore, Business Agent carries a critical boundary: uploaded files have no update call. If you upload a revised policy without deleting the older file, the agent draws on both documents simultaneously and can quote obsolete terms to customers.

Third is the Meta Model API at dev.meta.ai, offering raw developer access to frontier models like Muse Wonder and multimodal workhorses like Muse Spark 1.3 Standard. On that Standard tier, pricing is listed at $1.25 per million input tokens and $4.25 per million output tokens, under strict terms stating data is not used to train Meta’s models. This is infrastructure you can build on, but it is raw API access, not turnkey software.

Seats Are the Real Bill, Not Tokens

When owners evaluate AI, they usually fear token consumption. They assume processing text, audio, and video will create runaway invoices. The reality is the opposite: token usage is a rounding error, while seat licenses dominate the monthly software bill.

Consider the math for a 10-person restoration company running 20 jobs a month. If technicians record a 45-minute audio walkthrough and voice note on every job, transcribing all 900 minutes using a dedicated speech-to-text API costs under $3 a month. Feeding those transcripts, drying logs, and photos into a multimodal model like Muse Spark Standard to extract lessons costs roughly $0.29 per job—about $6 a month. Even stepping up to a frontier model like Muse Wonder at roughly $1.00 per job, monthly distillation totals just $20. The entire automated distillation loop runs for $10 to $30 a month in compute.

The real financial bleed happens when companies stack overlapping user seats. Paying $20 or $25 per user each month for ChatGPT Business or Claude Team on top of an existing corporate email suite burns $200 to $250 a month for 10 users, and still leaves you with project file caps or isolated document silos.

If your company already pays for Google Workspace Standard, team AI is effectively bundled at roughly $140 a month all-in for 10 users, with Gemini and NotebookLM included. If you run a Microsoft shop, the Business Standard plus Copilot bundle runs approximately $235 a month all-in for 10 people. Don’t pay for a second $200 seat subscription on top of a suite you already license; use what you have as the reading interface, and keep the master brain in your own folder tree.

WhatsApp Is a Porch, Not a Warehouse

Because field crews live inside WhatsApp, owners naturally ask whether they can turn a company WhatsApp group into the knowledge base. The platform’s technical limits and legal terms rule that out.

First, WhatsApp enforces hard media file caps: videos are capped at 16 MB and images at 5 MB. A three-minute high-definition walkthrough shot on a smartphone easily runs between 100 MB and 1 GB. If a technician sends raw job walkthroughs through WhatsApp, the media is heavily compressed or blocked entirely.

Second, WhatsApp Business terms updated in January 2026 expressly prohibit general-purpose AI assistants, while permitting bots scoped to a company’s own customer support. Moreover, the WhatsApp Business Platform operates strictly in one-to-one chats; group chats do not synchronize to the API.

The rule for field operations is clear: WhatsApp is a front porch, never a warehouse. Customer conversations and quick field notifications can pass through WhatsApp, but raw media—walkthrough videos, moisture readings, and photo logs—must upload directly to the job folder in your cloud storage. WhatsApp carries the notification link; your owned folder stores the truth.

Field Proof and the Grace Rule

We did not invent the principle that structured capture must precede AI. One early field example to watch is TRUERESTORE’s Ripple platform, described as launched in October 2026.

Ripple places an AI project coordinator directly inside every job file. It operates over moisture logs, drying equipment readings, LiDAR room scans, 360 photos, and technician notes. It automatically flags missing documentation before a crew leaves a site and drafts loss summaries for adjusters. Most importantly, Ripple follows a strict operational rule: it changes nothing in the job record until a human confirms.

In our view, platforms like TRUERESTORE represent the chef’s kitchen. If an operator wants a fully managed, turnkey commercial solution tailored to restoration workflows, hiring the chef and buying into a proven platform is a smart decision. But if you want to cook your own dinner—to retain sovereign ownership over your files, prevent vendor lock-in, and build systems that adapt whenever new models arrive—the open, DIY architecture gives you that control. Both choices are valid. What fails every time is buying AI tools before establishing disciplined field capture habits.

As case studies from ATI Restoration, Ascendum, and regional contractors show, companies that clean up per-job documentation see immediate operational payback. Companies that dump unorganized photos into AI bots simply automate chaos.

The 30-Day Starter ($0 to $20)

You do not need an enterprise software contract or an expensive consultant to start building a company brain. A small company can deploy a functional version in 30 days for between $0 and $20 in month one.

Week 1 establishes the folder tree ($0). In whatever cloud storage you already use—Google Drive, Dropbox, OneDrive, or a local server—set up four root directories: 00-BRAIN for canonical company knowledge, 10-JOBS partitioned by year and job ID, 90-HOPPER for unreviewed field uploads, and 99-ARCHIVE for superseded policies. Populate 00-BRAIN with the 15 to 20 documents that already answer 80% of routine questions. If two conflicting price sheets exist, resolve them now.

Week 2 activates the reader ($0). Create a free NotebookLM notebook titled “Company Brain” using the documents in 00-BRAIN as sources. Share it with your technicians and office staff in chat-only mode. Because NotebookLM quotes only from supplied sources and provides passage citations, it cuts fabrication — but it can still misquote or miss, so test before you trust. Test it against the 20 questions your crew asks most often, and log missing information into a gaps document.

Week 3 establishes the field habit ($0). Tape a single-page procedure inside every service truck: after each walkthrough, the lead tech shoots a continuous video and records a three-minute voice note explaining what was found, what actions were taken, and what should be done differently next time. The media uploads directly into 90-HOPPER via the mobile storage app—never through WhatsApp. In the afternoon, the office moves reviewed job logs into 10-JOBS.

Week 4 introduces the distiller ($0 to $20). Designate one person—an office manager or senior estimator—using the single $20 chat seat you already pay for or a funded API balance. Using a standardized prompt template, the distiller runs weekly job transcripts to generate candidate operational lessons formatted as: situation encountered, action taken, result, and rule for next time. Every Friday, the owner and distiller spend 30 minutes reviewing candidate lessons. Approved one-pagers move into 00-BRAIN; outdated versions are dated and moved into 99-ARCHIVE. That weekly 30-minute human review is the brain. The AI only proposes; humans decide what becomes company policy.

Building in Public

We are developing this entire architecture in public as part of the Meta hackathon build. The complete operational playbook—a practical playbook for owners that any restoration firm or trade contractor can implement—will be open-sourced on GitHub with no paywalls or gated access.

As part of our commitment to transparent lineage, we are releasing the complete, un-redacted Research Brief behind this project as a free download. The brief contains the full model pricing tables, platform cap comparisons, architecture diagrams, and field gotchas. There is no email wall, no form to fill out, and no marketing capture.

— Will Tygart, Tygart Media

Want help installing this in your shop? Contact Tygart Media — the brief above stays free either way.

Updated October 30, 2026 — corrected the seat-cost math and starter budget figures; softened claims the page could not support.

Updated Nov 1, 2026 — added the free shared brain quick card, 30-day starter pack, and shared brain operator downloads to this guide.