TrueCompanyOS documentation

TrueCompanyOS helps founders turn scattered company knowledge into one approved company brain and reusable business assets.

Instead of re-explaining the company in every sales call, investor meeting, or team update, you build approved company knowledge once — then reuse it across pitches, playbooks, briefs, and stakeholder outputs.

• Not just a writing tool — it separates raw material, structured inputs, approved knowledge, and finished assets.
• Not just a notes app — source material stays separate until you approve what is true.
• Not only a form builder — structured fields and approved conclusions both feed the same approved knowledge layer.

• Founders preparing for sales conversations
• Founders raising capital who need a consistent investor narrative
• Solo founders or small teams without a full marketing agency
• Founders onboarding salespeople, hires, or advisors
• Anyone tired of being the only person who can explain the company clearly

TrueCompanyOS learns in two ways. Both paths feed the same approved company knowledge layer. Neither path replaces the other.

The most direct way to teach the system. You manually complete and approve structured areas:

• Company Specs
• Customer Profiles
• Positioning
• Pitch Library
• Proof Library
• Objections
• Competitors
• Sales Readiness
• Investor Narrative
• Stakeholder Management (Team plan)

You add raw source material to Company Knowledge Base — documents, call transcripts, notes, website copy, decks, strategy files, customer feedback, investor notes, and competitor research.

1. TrueCompanyOS extracts suggested conclusions from source material.
2. You review, edit, reject, or approve them.
3. Only approved conclusions from source material can strengthen the company brain and assets.

Approved company knowledge feeds Company Overview, Source of Truth, Company Brain Map, Assets Engine, and sales, investor, customer, proof, objection, competitor, and stakeholder outputs.

1. Structured fields (Company Specs, Customer Profiles, Positioning, Pitch, Proof, Objections, Competitors, Sales Readiness, Investor Narrative)
2. Company Knowledge Base approved conclusions
3. → Source of Truth
4. → Company Overview
5. → Company Brain Map
6. → Assets Engine
7. → Sales, Investor, Customer, Proof, Objection, Competitor, and Stakeholder outputs

1. Raw source material
2. → Extracted suggestions
3. → Approved conclusions
4. → Approved company knowledge

Your dashboard is the command center. It shows readiness across Company Specs, structured modules, Knowledge Base review, and Assets Engine — plus the single most important action to take next.

Company clarity

How clearly your core company information is defined and approved.

Pitch clarity

How ready your pitches are for different audiences and contexts.

Sales readiness

How prepared your company is for repeatable sales conversations.

Investor narrative

How complete your investor story is across key topics.

Proof strength

How much approved proof backs up your claims.

Team transferability

How easily someone else could explain and sell your company without you.

• Approved structured records (Company Specs, Customer Profiles, Positioning, and more)
• Approved language and one-liners
• Approved positioning and pitches
• Approved proof, objections, and competitor differentiation
• Approved conclusions from Company Knowledge Base source material

Approved knowledge tells TrueCompanyOS what is safe to reuse in Source of Truth, Company Overview, and Assets Engine. Unapproved drafts and raw source material stay out of finished assets until you approve them.

Approved conclusions are reusable insights extracted from source material in Company Knowledge Base. They are the bridge between raw material and approved company knowledge.

They are not the only way the system learns. Structured fields are equally important. Approved conclusions matter when you add documents, transcripts, notes, decks, website copy, investor notes, customer feedback, or competitor research.

If source material is from another company or context, keep conclusions reference-only or reject them. Do not approve conclusions that do not belong to your company.

Company Knowledge Base is the source engine. It stores raw source material separately from Source of Truth. TrueCompanyOS extracts suggested conclusions; you decide what becomes approved company knowledge.

• Pasted text
• Call transcripts
• .txt and .md files
• .docx files
• Website copy pasted with URL reference
• Strategy notes, pitch deck text, investor notes
• Customer feedback, competitor research, agency briefs

1. Add source material
2. Extract conclusions
3. Review suggestions
4. Approve, edit, or reject
5. Approved conclusions can strengthen company knowledge and assets

Added

Source material saved, not yet extracted.

Extracted

Conclusions suggested, ready for review.

Needs review

Extractions waiting for your decision.

Approved conclusions

Conclusions you approved for reuse.

Archived

Retired source kept for reference.

Source of Truth contains approved reusable company knowledge. It is the approved layer — not the raw notes area.

• Approved structured fields
• Approved one-liners and positioning
• Approved pitch versions
• Approved proof, objections, and competitor differentiation
• Approved conclusions from Company Knowledge Base

• Company Overview
• Company Brain Map
• Assets Engine
• Sales, investor, and customer assets

Company Brain is the strategic area where TrueCompanyOS shows what it understands about your company. It is a container and control area — not a missing input field.

• Company Specs
• Company Overview
• Source of Truth
• Company Brain Map
• Links to Company Knowledge Base and other inputs

Company name

Your official company name.

Main product/service

What you sell or build.

Category

How the market would classify you.

Main problem solved

The core pain you address.

Core value proposition

The primary outcome you deliver.

Primary customer

Who you primarily serve.

Main market

The market you target.

Why now

Why this problem matters today.

Why customers buy

The trigger to purchase.

Why customers switch

What pulls them from alternatives.

Market misunderstanding

What people get wrong about you.

Current priority

Your top company focus right now.

Current bottleneck

The main thing slowing you down.

Missing

Not enough to generate useful assets.

Basic ready

Assets can start, but missing strategic fields make outputs weaker.

Strong

Key strategic fields are complete for stronger assets.

Customer Profiles define who the company serves, what they struggle with, what they want, and what messaging resonates.

• Sales One-Pager
• Customer Profile Brief
• Sales Playbook
• Marketing Messaging
• Investor Brief (where customer focus matters)

Category

How buyers classify your offer.

Buyer

Who buys or uses your product.

Problem

The pain or need you address.

Difference

What makes your approach unique.

Benefit

The outcome the buyer gets.

Proof

Evidence that backs your claims.

One-liner

A single sentence that explains the company.

• Company Overview and Source of Truth
• Sales One-Pager, Investor Brief, Demo Script
• Pitch assets

• One-sentence pitch
• 30-second pitch
• Sales pitch
• Investor pitch
• Demo intro
• Email intro
• LinkedIn intro
• Partner pitch

• Sales assets and Demo Script
• Follow-Up Emails
• Investor assets
• Customer Profile Brief

• Evidence, examples, and claims support
• Before-after examples, product and customer proof
• Internal proof, metrics, and testimonials
• Proof gaps — what evidence is still missing

• We already have docs.
• We can use ChatGPT.
• This sounds like another system to maintain.
• We do not have time.
• We are not ready.

• Objection Guide
• Sales Playbook
• Demo Script
• Follow-Up Emails
• Sales One-Pager

• Direct competitors
• Generic AI chats, docs, and spreadsheets
• Agencies and internal processes
• Doing nothing — the status quo

• Differentiation and Competitor Map assets
• Investor Brief and Sales One-Pager
• Objection Guide

1. Sales Call Inbox — add transcripts or notes
2. Extracted Sales Insights — review suggestions
3. Sales Readiness Summary — approved selling system
4. Sales assets — Playbook, One-Pager, Demo Script, Follow-Up Emails

• Sales Playbook
• Sales One-Pager
• Demo Script
• Follow-Up Emails
• Objection Guide

Problem & solution

Market pain and your approach.

Market & business model

Opportunity and how you make money.

Traction & proof

Evidence of progress — only what you provide.

Risks & use of funds

Honest challenges and capital deployment.

Milestones & investor FAQ

Targets and common investor questions.

• Investor Brief
• Pitch Narrative
• Investor FAQ
• Traction & Proof Summary

Team is for role-based collaboration around one approved company brain. It includes Founder Pro depth, stakeholder and team outputs, and workspace seats for people who contribute expertise or use approved truth in their work.

• Founder — owns strategy and final company truth
• Salesperson — adds sales calls, objections, qualification signals, and follow-up insight
• Marketer — adds messaging, campaign, audience, and content insight
• Business consultant — adds strategic input, audits, positioning, and operating recommendations
• New employee — uses the company brain to understand the business and ramp faster

Owner

Billing, members, roles, approvals, and full workspace access.

Admin

Can manage members (except owner restrictions), approve workspace content, and contribute fully. Cannot manage billing.

Member

Can add drafts, sources, and generate assets if allowed. Cannot manage billing or team seats.

Stakeholder Management is available on the Team plan. It helps create stakeholder updates, internal alignment briefs, advisor updates, and agency or partner communication.

Assets Engine is the production layer. It uses approved company knowledge to generate finished business assets — not new inputs.

• Company One-Liner and Company Clarity Snapshot
• Sales One-Pager, Sales Playbook, Demo Script, Follow-Up Emails
• Objection Guide and Customer Profile Brief
• Investor Brief, Pitch Narrative, Investor FAQ, Traction & Proof Summary
• Competitor and differentiation assets
• Stakeholder and team assets (Team plan): Stakeholder Update, Salesperson Onboarding, New Employee Onboarding, Agency Brief, Partner Brief, Marketing Messaging

Asset previews may show what they used: Company Specs, Customer Profile, Positioning, Pitch, Proof, Competitors, Sales Readiness, Investor Narrative, and approved Knowledge Base conclusions.

Founder Pro can use deeper approved Knowledge Base context in assets. More approved conclusions and richer structured inputs produce stronger source coverage.

Not ready

Missing required approved inputs.

Usable but thin

Usable output, but missing proof, investor evidence, market evidence, or deeper context.

Ready

Enough approved knowledge for a solid asset.

Strong

Rich approved knowledge across key inputs.

1. Complete Company Specs.
2. Add a Customer Profile.
3. Add Positioning.
4. Add your first Pitch.
5. Generate Company One-Liner and Clarity Snapshot.
6. Add Proof, Objections, and Competitors.
7. Generate Sales One-Pager or Investor Brief.

1. Add source material to Company Knowledge Base.
2. Extract conclusions.
3. Review, edit, approve, or reject conclusions.
4. Check Source of Truth.
5. Generate assets.
6. Add proof and objections to strengthen outputs.

1. Add a Customer Profile.
2. Add Positioning.
3. Add Objections.
4. Add a sales transcript.
5. Approve sales insights.
6. Generate Sales Playbook, Demo Script, and Follow-Up Emails.

1. Complete Company Specs.
2. Add Positioning and Pitch.
3. Add Investor Narrative.
4. Add Proof and market evidence.
5. Add relevant Knowledge Base sources.
6. Generate Investor Brief and Investor FAQ.

1. Add new calls, notes, feedback, or strategy docs to Knowledge Base.
2. Extract and approve conclusions.
3. Review Source of Truth.
4. Regenerate assets when needed.

Manual clarity path and a small taste of intelligence. Limited Knowledge Base sources, drafts, customer profiles, pitches, and assets.

Core company brain and Founder assets. Includes Proof, Objections, Competitors, Sales Readiness, Investor Narrative, and full core assets.

Depth tier for founders with more existing material. Higher Knowledge Base source capacity, more extractions and drafts, deeper source coverage, and richer use of approved conclusions. Better for decks, docs, calls, feedback, and strategy material.

Role-based collaboration tier. Includes Founder Pro depth, stakeholder and team outputs, and workspace seats for founders, salespeople, marketers, business consultants, and new employees who contribute to the approved company brain.

Thinking source material automatically becomes truth

Correction: source material must be extracted and conclusions approved first.

Approving conclusions from the wrong company or context

Correction: keep them reference-only or reject them.

Completing fields but not approving final reusable language

Correction: approve what should feed Source of Truth and assets.

Generating investor assets without proof or traction

Correction: the system will show gaps, not invent evidence.

Treating Founder Pro as a team tier

Correction: Founder Pro is depth and capacity. Team is stakeholder and team communication.

Adding only direct competitors

Correction: alternatives include docs, AI tools, spreadsheets, agencies, internal processes, and doing nothing.

Ignoring proof gaps

Correction: proof gaps tell you what evidence to collect next.

• Extract suggested conclusions from Knowledge Base source material
• Organize messy input into structured drafts
• Generate draft content based on approved company knowledge
• Suggest improvements and fill gaps where information exists

• Invent fake proof, testimonials, or customer quotes
• Invent traction, revenue, or market size
• Approve content on your behalf
• Replace founder judgment on what is true

1. Draft or extraction → status: needs review
2. You read, edit, and decide
3. Approve to make it official, or reject to discard
4. Only approved knowledge feeds Source of Truth and Assets Engine

• English
• Spanish
• Portuguese

• The UI may show translations based on your locale preference.
• Draft output follows your workspace working language.
• Assets Engine uses workspace language where supported.

If sign-up fails, check that Supabase is correctly configured in your deployment environment. Verify that auth is enabled and email confirmation settings match your setup.

This can happen if your user account was created before the profile trigger completed. Try signing out and signing in again. If the issue persists, contact support.

Possible causes:

• Draft provider key is missing or invalid in the server environment
• You have reached your monthly plan draft limit
• A server error occurred — try again in a moment

Possible causes:

• Stripe webhook is not configured in your deployment
• Webhook secret is incorrect
• Subscription event was not received — check Stripe dashboard logs

Existing approved content remains as written. Language changes affect new draft generations and UI translations. To update old content, edit and re-approve items in the relevant modules.