--- title: "Give AI your product specs and personas so SaaS docs start accurate" description: "Write a product context file with features, personas, pricing rules, onboarding, and API structure so AI drafts release notes and docs that match your product." canonical: "https://scalewithsearch.com/articles/ai-memory-for-saas" date: "2026-01-28" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [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) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Give AI your product specs and personas so SaaS docs start accurate. You ask an AI assistant to draft release notes. It returns a generic feature announcement template that does not explain what the feature does or why it matters. It does not know your product architecture. It does not know which users asked for this feature. It does not know how the feature fits your roadmap or which problem it solves. You rewrite half of it. You add context, fix technical details, and adjust the tone to match past announcements. You close the chat, and the context is gone. The next release note starts from zero. This page shows how to give the assistant a product memory: one maintained file that points to your specs, personas, and docs. ## What SaaS teams need the assistant to know A SaaS company produces documents constantly: feature specs, user personas, API docs, pricing tiers, onboarding flows, support articles, and roadmap priorities. For product communication or documentation, the assistant must refer to your product, not generic SaaS practice. It needs these facts: - your features: what each does, how it works, and which users need it; - your user personas and their use cases; - your technical architecture and integration points; - your pricing model and feature gates; - your onboarding flow and activation metrics; - your support doc structure and common issues. Today you explain the product each time you draft documentation or plan a launch. The assistant writes, and you fix the technical errors and tone mismatches. ## How a product context file works The memory is a file, not a browser extension. One Markdown file holds what the assistant needs about your product: feature specs, personas, architecture, pricing structure, support docs, and roadmap priorities. In Claude Code, that file is `CLAUDE.md`. Claude Code reads it at the start of each session in the folder or repository where you start it. You write it once and update it when the product changes. The file sits in a folder you control, such as your product repository or an Obsidian vault. It needs no vendor integration and no API setup. The model runs on the provider's servers, so the text Claude reads goes to the provider during a session. A SaaS team has one extra advantage. Claude Code works inside a repository, so the file can point to sources that already exist: the OpenAPI spec, the changelog, and the docs folder. The assistant then reads the spec instead of your summary of it. ```markdown # Product context ## Product - What it does: shared inbox for small support teams - Architecture summary: `docs/architecture.md` - Integrations: Slack, HubSpot, Zapier (`docs/integrations/`) ## Personas - Support lead: owns SLAs, wants reports without spreadsheets - Agent: wants fewer tabs, fast macros - Details: `docs/personas.md` ## Features - Current feature specs: `specs/` - Shipped changes: `CHANGELOG.md` (source of truth for release notes) ## Pricing and packaging - Tier names and feature gates: `docs/pricing-gates.md` - Never state a price in docs; link the pricing page ## Onboarding - Activation event: first macro used by 2 agents within 7 days - Email sequence: `marketing/onboarding/` ## Support docs - Structure and templates: `docs/help/_template.md` - Top 20 issues: `support/top-issues.md` ## API - Reference source: `api/openapi.yaml` - Auth: OAuth 2.0; rate limits and webhook events in the spec ``` [A CLAUDE.md template for business context](/articles/claude-md-template-business-context) covers the source order, exclusions, and stopping rules to add around these pointers. [Context file vs CLAUDE.md](/articles/context-file-vs-claude-md-business-project) explains when product facts belong in a separate file. ## Six product jobs the file supports With the file in place, each request starts from your product. ### Release notes You shipped a feature. The assistant reads the changelog entry and the spec. It knows what the feature does, who asked for it, and how it fits the product. It drafts release notes in plain language. You review them, add screenshots, and publish. ### Support documentation You document a workflow. The assistant knows your product terms, UI structure, and common user questions. It writes step-by-step instructions that match your docs template. You add the article to the knowledge base. ### Onboarding email You want a higher activation rate. The assistant knows your onboarding flow, key features, and activation event. It drafts a welcome sequence that guides users to that first win. You test and iterate. ### API reference pages You added endpoints. The assistant reads the OpenAPI spec, your auth method, and your common integration patterns. It drafts endpoint pages with example requests and responses. You run each example against a test environment before you publish. ### Feature comparison pages A prospect asks how your product compares with a competitor. The assistant knows your feature set, packaging, and position. It drafts a comparison that states your strengths without overselling. Check every claim about the competitor against their current public docs, with the date you checked. ### Persona research You refine your ideal customer profile. The assistant knows your user base, feature usage patterns, and churn triggers. It helps you find persona segments and drafts interview questions to test your assumptions. You run the interviews. ## What goes in a SaaS context file The file does not need every endpoint on day one. Start with what matters most: | Section | Contents | |---|---| | Product overview | What the product does, core features, architecture, integration points | | User personas | Who uses the product, their use cases, pains, and goals | | Feature specs | What each feature does, how it works, who needs it, roadmap status | | Pricing and packaging | Tiers, feature gates, upgrade paths, trial terms | | Onboarding flow | Steps, activation goals, common drop-off points, email sequences | | Support docs | Categories, common issues, escalation steps, reply templates | | Technical details | API structure, authentication, rate limits, webhook events | Expand it over time. When you ship a feature or update docs, add the context. When the assistant gets a fact wrong, fix the source it read. [Corrections become part of the system](/articles/corrections-become-system-memory) only when the next session can read them. ## Why project-tool AI features fall short Your project management tool probably added an AI assistant. It summarizes tasks. It does not know your product. It cannot draft release notes that explain features to users. It cannot write support docs in your terms. It cannot help with onboarding copy, API docs, or persona research. It is a task summarizer, not a product assistant. A product file gives the assistant product memory: your features, users, technical details, and doc style. It works across every product communication task. It needs no integration work. Claude Code itself needs a paid Claude plan. ## Keep secrets and customer data out of the file Never put API keys, tokens, or credentials in `CLAUDE.md` or any file the assistant reads. Name the secret by its environment variable instead. Customer names, account data, and support ticket contents stay in your support and billing systems. Export only what one job needs, and remember that the provider receives what Claude reads. Unreleased roadmap items are confidential. Mark them in the file, and add a rule that drafts for public channels never mention them. ## Test the file before the next release 1. Start a new Claude Code session in the repository. 2. Ask for release notes for the last changelog entry. 3. Check every stated behavior against the shipped code or a test environment. 4. Ask for the API reference page for one endpoint, and compare it with the OpenAPI spec. 5. Ask for a public blog outline, and confirm that no unreleased roadmap item appears. The test passes when every statement matches the shipped product and the spec. [Claude Code vs ChatGPT for a large codebase](/articles/claude-code-vs-chatgpt-large-codebase) covers how repository context changes this test on larger products. ## Who this setup fits This setup fits product managers who draft specs, technical writers who build docs, and customer success teams who write support content. It also fits founders who wear every hat. You do not need to be a developer or hold admin access to internal tools. You need to know the product well enough to document it. If you have written release notes before, you can write this file. ## Approval and stopping boundary The assistant drafts release notes, docs, onboarding email, API pages, and comparison drafts. The product owner approves every public claim about behavior, pricing, and competitors. The assistant does not publish docs, send email, or merge code. When the file conflicts with the shipped product or the spec, the product and the spec control, and you correct the file. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```