Notes

An OPC is not a smaller company. It is a rewritten collaboration.

2026-11-14 · Liu Gang's OPC

The phrase “one-person company” is easy to hear as “a smaller company.” The design desk becomes me. The video desk becomes me. Sales is still me. A person starts to imitate a small company’s org chart, with the same name in every box. It does not last. Not because of a lack of diligence, but because the way of collaborating has not been rewritten.

I have done print and poster design, mini-programs and websites, SaaS rollouts, and management consulting. If those experiences are only stacked on a name card, it looks as if I can do everything, and in practice I spread myself thin. For an OPC to stand, past trades should not all be kept as departments. They should be gathered as callable capabilities, and then you decide which layer you will actually deliver this season.

The rewrite starts in three places.

First, the split between judgment and drafts. The tone of a poster, the line in a tour script that must not be wrong, whether a price can be promised — those judgments stay with a person. Three layouts, a press release compressed into a spoken script, a work order turned into steps — those drafts can go to an agent. A one-person company is not a company that does everything itself. It is a company that knows which layer must not be handed off. Writing that layer into a skill brief is more reliable than reminding yourself every day to “be careful.”

Second, drop the pretence of a complete set of departments. Legal text, on-site construction, and work that needs a licence were never meant to be shouldered alone. Find a partner when you should. Refuse a project when you should. On a business canvas, “what I will not do” often protects you more than “what else I can do.” When the boundary is written in the open, clients can decide more easily. They do not need a person who agrees to everything. They need a principal who knows the edge of their array.

Third, the capacity gate. A calendar that still has a white space does not mean you should take another project this week. However tidy one person’s array is, attention is still singular. When the warehouse is full, keep promises first, then talk about new work. That is not timidity. It is how a delivery loop actually finishes. Saying “I cannot take this now” looks more like a real company than quietly delaying after you have said yes. Promises and payments that live only in chat are easy to lose when you are busy. Seeing projects, promises, and capacity on one screen is infrastructure for yourself, not a way to look busy.

So the point of an OPC is not to live as a hidden team. It is to write judgment, drafts, and collaboration into a repeatable array. Once the array is lined up, you are still one person. You are no longer using one body to fill in a company’s org chart. A one-person company that lasts will look more restrained than its publicity, and more like a company that actually delivers.

Back to notes