Founder clarity resource

Company Source of Truth Framework

A practical framework for building one approved source of company truth so sales, marketing, investors, and your team stop describing the company differently.

Target question: How do I create a single source of truth for my company?

Last updated

Available as Markdown

Most companies don't have one wrong story about themselves — they have several, spread across decks, docs, and people's heads. This framework lays out how to turn scattered, unreviewed information into a small, approved set of facts that everyone can point to instead of guessing.

What 'company truth' actually means

Company truth isn't every piece of information anyone has ever said about the business. It's the specific set of claims — about who you serve, what problem you solve, how you solve it, and why that matters — that anyone in the company is allowed to repeat without checking with someone first.

Raw input
Anything anyone has said about the company at some point: a line from an old pitch deck, a founder's answer in an interview, a claim in a Slack thread from a customer call.
Approved fact
A claim that's been reviewed, is currently accurate, and is safe for anyone to repeat in a sales call, a pitch, or a public page.
Source of truth
The finite set of approved facts that overrides every other document when there's a conflict.

Raw input vs. approved fact

The most common failure mode isn't having bad information — it's treating raw input as if it were already approved. A founder says something once, someone writes it down, and three months later it's on a slide with no one remembering where it came from or whether it's still true.

  • A founder mentions a rough number in a call ('customers save a few hours a week') — that's raw input until someone confirms it's accurate and repeatable.
  • A sales rep describes a competitor comparison their own way — that's raw input until it's checked against what the company actually wants said.
  • An early customer quote gets pasted into a deck — that's raw input until someone confirms the customer is still using the product and still agrees with the quote.
  • A founder's answer to 'what do you do' in a podcast — that's raw input, not the approved one-liner, even if it sounded good.

Why a shared doc or deck usually isn't enough

A Google Doc or slide deck feels like a source of truth because it's centralized. In practice, centralization isn't the same as ownership.

  • There's no version control, so 'final_v3_ACTUAL.pptx' and the version a new hire copied from six months ago quietly diverge.
  • Nobody is assigned to flag statements that go stale as pricing, positioning, or the customer base changes.
  • Decks fork for individual investors or prospects, and the edited copy becomes someone's personal reference going forward.
  • New hires copy the collateral they're handed without knowing which parts are current and which are leftover from an earlier stage of the company.

A document becomes a source of truth only when someone actively maintains it as one — reviewing it, dating changes, and retiring what's outdated. Without that maintenance, it's just another place raw input accumulates.

The core categories a source of truth should cover

A useful source of truth doesn't need to be exhaustive. It needs to cover the categories that get repeated most often, in the most places, by the most people.

  • The one-liner — how the company describes itself in one sentence
  • The ideal customer profile — who the company serves, and who it doesn't
  • The core problem statement — the situation the product actually addresses
  • Differentiation — what's actually different about the approach, not just adjectives
  • Proof and evidence limits — what's currently defensible to claim, and what isn't yet
  • Pricing logic — the internal reasoning behind pricing, even if the number itself is public
  • Competitive positioning — how the company is described relative to alternatives
  • Common objections and approved responses — the recurring pushback and how to answer it
  • Terminology — the specific words used for the product category, customer segments, and outcomes

Assigning ownership and approval authority

Every category needs exactly one person who can say yes or no to a change. Shared ownership across a category is how contradictions survive — everyone assumes someone else checked.

Founder / CEO
Final approval on the one-liner, positioning, and anything that shapes how the company describes itself at a strategic level.
Head of sales (or founder, in a small team)
Owns objection responses and what proof points are safe to use live in a call.
Head of marketing (or founder)
Owns public-facing language: website, ads, and published content.
Operations / customer success lead
Owns terminology accuracy — making sure the words used externally match what the product actually does today.

A lightweight approval workflow

Approval doesn't need a committee. It needs a repeatable, small set of steps that anyone can follow before a new claim becomes official.

  1. Draft the claim in plain language — no adjectives that hide what's actually being said.
  2. Identify who owns approval for that category.
  3. Check the claim against existing approved facts for contradictions.
  4. Get explicit sign-off from the owner — not silence, not an assumption that no objection means yes.
  5. Record it in the source of truth with the date it was approved.
  6. Note where the claim is now allowed to be used (public site, sales calls, investor materials, or all three).

Versioning: tracking what changed and why

A source of truth that never shows its history is hard to trust — nobody can tell if a claim is current or three revisions out of date.

  • What changed, stated as plainly as the original claim
  • Why it changed — new pricing, a repositioning, a claim that stopped being defensible
  • Who approved the change
  • The date it took effect
  • Which existing materials referenced the old version and need to be retired or updated

Handling contradictions when they surface

Contradictions aren't a sign the system failed — they're a sign it's being used. What matters is having a routine for resolving them quickly instead of letting both versions keep circulating.

  1. Log where and how the contradiction was found, in the exact wording used.
  2. Determine which version is currently correct.
  3. Update the source of truth first, before touching any other material.
  4. Trace which collateral, scripts, or decks used the outdated version.
  5. Flag those materials for update rather than assuming someone will notice on their own.

Setting a review cadence

Most source-of-truth documents fail not because they were built wrong, but because nobody revisits them until something breaks.

  • A pricing change — review pricing logic and any claims tied to it
  • A new competitor entering the conversation — review competitive positioning
  • A funding round or investor update — review the narrative used with investors
  • A shift in who the ideal customer actually is — review the customer profile and one-liner
  • A scheduled quarterly review regardless of whether anything obvious has changed

A starter structure you can copy

Company source of truth — starter outline

  • Prompt: One-liner (approved wording, dated)
  • Prompt: Ideal customer profile (who it's for, and who it's explicitly not for)
  • Prompt: Core problem statement (in the customer's language, not internal language)
  • Prompt: Differentiation (what's actually different, not just adjectives)
  • Prompt: Proof and evidence limits (what's currently defensible to claim)
  • Prompt: Objections and approved responses (the recurring ones, not a hypothetical list)
  • Prompt: Terminology glossary (product category, segment names, outcome language)
  • Prompt: Pricing logic (the internal reasoning, kept current even if the number is public)
  • Prompt: Owner assigned to each category above

Signs your source of truth is actually working

  • A new hire can repeat the one-liner correctly within a week of joining
  • Sales and marketing use the same proof points without needing to compare notes
  • Contradictions get flagged and fixed within days, not discovered a quarter later
  • Founders aren't personally reviewing every deck before it goes out
  • Old collateral gets retired instead of quietly copied forward

If most of these aren't true yet, that's not a sign the framework doesn't fit — it usually means ownership or a review cadence hasn't been set, not that the categories themselves are wrong.

Keeping it current

A source of truth is a habit, not a one-time document. It stays useful only as long as someone keeps it accurate and everyone knows to check it before repeating a claim.

FAQ

Is a source of truth the same as a brand guide?

No. A brand guide typically covers voice, tone, and visual identity. A source of truth covers the underlying facts and claims — who you serve, what problem you solve, and what proof supports it — regardless of how it's styled.

Who should own the source of truth in a very small company?

By default, the founder or CEO, until roles specialize enough that ownership of specific categories — like sales objections or public-facing copy — makes sense to delegate.

How often should the source of truth actually change?

Rarely on a fixed schedule, but immediately whenever a fact stops being accurate — a pricing change, a new competitor, or a claim that's no longer defensible. The review cadence is for catching drift, not for making changes on a timer.

Looking for the product that puts this into practice? See pricing or return to the homepage.

Company Source of Truth Framework | TrueCompanyOS