---
type: "Know post"
title: "How are business docs different from notes and a blog?"
description: "Tell notes, business docs and a blog apart by the job each one does, so a solo founder who changes one number fixes it in only one place."
resource: "https://cuongthach.com/business-docs-vs-notes-and-blog/"
tags:
  - "blog"
  - "en"
  - "Truth vault"
status: stable
generated:
  by: "process:cuongthach-okf-export"
  at: "2026-10-29T00:00:00Z"
---
# How are business docs different from notes and a blog?

You just changed the price of your yearly plan, then you open 12 old blog posts and dig through each one to fix a single number. When you finish, you still cannot be sure you did not miss one. This is not because you are careless. It happens because three different things are crammed into one place.

Notes are **what you think**. Docs are **what you have done and checked**. A blog is **the story of that journey**. When each one sits in its own place, changing a number means fixing one page.

## A blog cannot keep the truth

![A blog cannot keep the truth](https://cuongthach.com/_astro/illus-lech-quy-dao.en.DusLZ4w0_ZTKTiY.svg "A little off each day, far off after a year")

A blog was not made to **keep the truth**. It was made to tell stories to customers. When you make it hold your prices, your process and your specs too, sooner or later your posts will say different things.

### I once used my blog as my docs

In the early days, I also let my blog hold everything I knew about my business. I did not know about docs yet. I was afraid my journey would be forgotten, and that the research and ideas that had worked would be dropped.

So whenever I finished an idea, instead of writing it into docs, I wrote it as a blog post. The post kept the trail, the results and the research, with videos and pictures, so I could come back later and do it again.

Then the number of posts grew, and the content began to break into pieces.

Some posts I published long ago. 3 or 4 years later, I published a new post and forgot the old one.

I had to use my own site's search box to see that two posts repeated each other, or overlapped. The older the posts get, 1 year, 2 years, 3 years, the **easier this happens**. Old posts are also hard to update, and that is when I saw I needed a set of docs.

### Blog content drifts without docs

Solo founders often make this mistake: **there is no central source**, so information breaks into pieces. You change a price or a spec, and then you talk about them in your blog posts. The result is posts that do not agree with each other.

A number that changes 4 or 5 times over the years shows up in 4 or 5 different ways across many posts. Some posts are out of date and still sit there. When a reader sees two different numbers, they stop trusting you.

Now AI can fix many posts on your site for you, so fixing is less painful than before. But fixing all the time like this is still a problem.

If you have 30 blog posts and no docs, the next 30 will most likely not agree either. Each post adds or drops a little and slowly turns into something else. Your content **drifts off course**: a little each day, and after 1 year the course has changed and you did not notice.

## Notes think, docs do, a blog tells

![Notes think, docs do, a blog tells](https://cuongthach.com/_astro/illus-ghi-nghi-lam-ke.en.DCOYb4OX_ZTKTiY.svg "Three steps joined in one unbroken line")

These three things are just like **everyday life**. You come up with a guess and try it, and it works. You write the result in your notebook, then you tell the story of the road that led to that success. The guess is a note, the result that has been proven is a doc, and the road is a blog.

| | Notes | Docs | Blog |
| --- | --- | --- | --- |
| What it is | Thoughts, ideas, plans | What you have done and checked | The story of the journey |
| Where it lives | Digital brain, never made public | Website, public | Website, public |
| How to write it | As fast as you can | Short and true | Enough to lead the reader to the end |
| When it changes | Any time | Whenever the truth changes | Rarely |

Public does not mean putting everything out. Your digital brain keeps your knowledge assets, like a highly secure set of internal docs, so you always keep some secrets of your own. Entity docs share only what you are really doing and what is valuable to users. Your personal stories and your own skills do not need to go online.

When you run a business alone, you write and fix all three yourself. You take notes anywhere, then gather them all in one dumping ground, your digital brain. A note that gets verified becomes a doc. The journey of verifying it becomes a post to share. The three steps connect into **one continuous line**.

So docs are not something "split off" from notes. Notes come first, and docs are their next step: whatever you can do, you write down. If you have staff, you are still the last person to approve the [Truth vault](https://cuongthach.com/kho-su-that/). Posts must rest on the docs, so when you do the docs well, the writers below you have a base to follow and write great posts for you.

## From note to doc

A note becomes a doc only **when it is already true**. A notebook can hold plenty of feelings, thoughts and ideas. But not everything in it has been checked.

```mermaid
flowchart TB
  accTitle: A note becomes a doc and then a blog post only after it is done and checked
  A[Note] --> B[Do it for real]
  B --> C[Get a result]
  C --> D[Check it is still true]
  D --> E[Doc]:::focus
  E --> F[Blog post]
```

### A note must be done for real and checked

The first question for every note is: did you really do it, and if you did, did you get a result? The result can be a failure or a success. Once you have really done it to test that thought, only then do you write it into the [entity docs](https://cuongthach.com/docs/content-system/truth-vault/concepts/open-docs/): the result, the formula, the concept, your understanding.

One line of notes rarely becomes a doc. It has to be developed fully into a concept, a guide, a philosophy, a formula or a process. A single line of notes put on a site is thin content, and it cannot stand alone. A full docs page will have a high word count.

An opinion that is right because of past experience sits halfway between a note and a doc. Before you put it in the vault, you check once more whether it is still true today, with the internet, with AI, with any way you have. I always **verify everything** before it goes into the vault, so the vault stays fresh and the truth stays protected.

> [!TIP] This is normal
>
> Out of 10 or 20 notes, only 2 or 3 get done, checked and proven. Only those notes become docs. This is normal. It does not mean you are doing something wrong.

A note about your brand goes into the docs, to mark it: *"This is what I researched, and this is the truth I have done."*

If you only have 2 hours a week, pick one note and do it right away. Only by doing it can you verify the idea. Once verified, you have a result, and putting it into entity docs is the last step. Then your drive will be bigger, enough to do the second idea, the third, the fourth in your notebook.

If you do not do it, a note becomes a dead note. My [Capture and Share](https://brainnodeos.com/vi/capture-and-share/) challenge exists for that same reason: to turn notes from ideas into docs.

### Plans stay in notes

Plans always stay in notes. A feature you love but have not built sits in your notes. Once the new feature has launched, it is the truth, and you must write it into the docs.

Business docs are also not notes that have been tidied up. I have a frame for building my docs, and it sits in my digital brain: the groups and areas I will build for my entity docs. That frame is a plan, so it is a note. As far as I get through the plan, I write straight to the website, and only the part that is on the website is entity docs.

Other people's notes are even more dangerous. Notes have not been verified, and often you write down what someone else said. **That is not yours**, you cannot control it, so it is not your brand asset. Mixing it into your docs is already a mistake.

## One docs page, many blog posts

![One docs page, many blog posts](https://cuongthach.com/_astro/illus-mot-trang-nhieu-bai.en.CyE_Gobh_ZTKTiY.svg "One docs page, many ways to tell it")

A blog post is [derivative content](https://cuongthach.com/docs/content-system/distribution/concepts/derivative-content/) of a docs page, not a copy of it. The docs page must be the truth first, and then it becomes the official source for the posts that follow.

It is normal to have 10 docs pages and write 50 blog posts about them. Because posts are derived, you can share many different views, explore one page from many angles, and write many guides related to it.

The docs have already solved accuracy for you. You do it for real and you write for real, so what you say on the blog is already true and does not need proof again. Each post always has a source that points back to the docs, and has **your own verification** first.

It works the other way too. If you already have old blog posts that are true, do not build the vault from zero. Pick the posts that are true, [pull the truth out of them into docs](https://cuongthach.com/docs/content-system/truth-vault/guides/tutorials/build-the-first-vault/), and remember that you are the one who reviews it.


### Docs put the truth first

Docs put the truth first. A blog post puts customers and their feelings first. These two goals give two different structures.

A blog post serves the customer, so it has a structure that leads the reader, and an opening that draws them in. A post does not need to be as short as possible. It needs to be complete and engaging, so the reader reads your whole **work**. A post always has a core message, and it sits in the [Know - Trust - Love funnel](https://cuongthach.com/biet-tin-yeu/), so the customer's journey is easier to walk.

A docs page does not need an opening that draws the reader in. It says right away what this is, as briefly as it can. Docs have only a few types of pages, and you must follow those types.

On a blog, you can mix types:

- Explain and guide at the same time
- Put deep explanations inside a guide
- Tell your own story
- Give neutral examples from outside companies

The way they are read is different too. A docs page is read in a line from top to bottom like a book, with few links out to the blog so the reader stays inside the docs. A blog post sometimes looks like a page of a book, but the reader does not go through it in one straight line like that.

A behind-the-scenes diary is the clearest example. You build a feature, you keep a diary, then you publish that diary as a post. That post is one of a kind. The reader feels your story and **takes a lesson from it**, and customers love stories like that.

### Docs are living software

Docs are updated all the time, and a blog is updated less. **Entity docs are like living software**, and they may be updated every day, as long as you do not change their URL.

Blog posts drift along the timeline. How long until a post is out of date depends on your field. In a place like AI, a fact can be wrong after 2 months, 1 month, even 1 week. To keep a post as accurate as possible, you must update it all the time. If you do not update, you accept that the old post will age.

An out-of-date blog post is fine. Few people care much, because what you want to keep is the Truth vault. But when a customer opens the docs and finds them out of date, they will complain, because docs must follow the reality of the product and of the field.

> [!TIP] Numbers that change
>
> If a number changes often, do not write it into a post. **Link to the docs page that holds it.** When it changes, you fix it in only one place.

## Docs first, posts after

![Docs first, posts after](https://cuongthach.com/_astro/illus-tai-lieu-truoc.en.iiMN4Y7z_ZTKTiY.svg "Docs first, and everything bears your brand")

Docs come first, and **derivative posts come after**. Many people do it the other way around, simply because they do not know docs should come first. But the order of content, what comes first and what comes after, matters a lot.

### Docs are your brand asset

For a solo founder, business docs are your **brand asset**. They include docs about your product and docs about your brand. For CuongThach, the Content system is a brand asset like this. The docs protect that asset, and they tell Google that these are things you own, build and repeat, which is also your own niche.

Not everyone has a product to sell, and most people make content only to attract people. Without a Core product to anchor on, docs do not get built up, and the brand asset is never defined. That person writes in general terms, or writes for a niche that brings no brand asset, so what they own is only traffic, a set of keywords and a few posts.

When docs come first, **everything is stamped with your brand**. You made it, and you can protect a lot in your brand assets, products included. When you run a business alone, your resources are few, so do not build a big vault from the start. Build the vault as fast as you can from what you have right now.

### AI needs docs as the original

AI can read both notes and blogs, but **it needs to know what is true**. AI needs a knowledge base to verify against. You tell it what is true, and only then can everything else start to run.

Without a vault, AI will ask you about every point. You confirm, it asks again, you confirm again, and after a while of making content, you forget what you have confirmed.

And if you give AI the right to decide on its own, it will make wrong decisions and write wrong content for you. It goes wrong a little at a time, and then it gets your whole brand wrong.

### With docs, fewer refunds

I use a lot of software, and every product page has docs that show customers how to use it. Reading so many docs made me realize how important they are.

The digital products I sold all came with docs. The products became more trustworthy, and **the share of customers asking for refunds dropped a lot**. Since then, I have focused on docs instead of writing too many posts.

Once you have docs, writing posts gets much lighter, because it builds up over time. I spend more time on entity docs than on blog posts. Reading the docs again and again brings new angles, and writing derivative posts from them is very easy.

## Before launch, notes are enough

While your business is still on paper, notes are all you need. You are making a plan, you have just bought a domain, or you have not bought one yet. You are thinking about a website, a media channel, a product. Nothing exists on paper yet, and no truth has happened, so why spend money on entity docs?

But once the business is running, notes cannot replace docs. Notes are short and not public. You do not know if they are verified, and they have not become real.

If you write notes and do not act, and someone else does it before you, **you lose your trail** and the edge of the one who goes first. Those notes are not worth as much as daring to make your docs public.

## Give your docs a structure

The next time your price changes, you want to fix only one page. For that, everything you know about your business needs its own place in your docs. The next step is to [structure the docs of a one-person business](https://cuongthach.com/structure-docs-for-a-solo-business/).