Before launch, and for a while after it, grow the founder account first. That is the short answer, and it is not close. People follow people: a founder can hold opinions, admit mistakes, ask questions, and reply as a peer. A company account with 80 followers can do none of that convincingly, because a logo asserting an opinion into silence persuades nobody.
This is a sequencing decision, not an identity crisis. The company account still gets created on day one, because the handle matters and the profile is free real estate. The question is where the weekly posting effort goes, and the answer changes as the company grows.
The honest asymmetry
A pre-launch company account has nothing to say that anyone chose to hear. Its natural content, releases and announcements, does not exist yet, and manufactured content in a brand voice reads exactly like what it is. A founder, by contrast, has raw material every week: a decision with consequences, a customer conversation, a wrong assumption corrected. That material earns replies, and replies are the only distribution a small account gets.
There is a second, less discussed reason to lead with the founder. Early companies pivot, rename, and reposition. The founder account survives all of it. An audience built on one person's judgment transfers to whatever the company becomes; an audience built on a product name is mortgaged to that name.
The common objection is 'I do not want to be an influencer.' Founder-led does not mean personal-life content or a posting persona. It means professional judgment in public: the decisions you are already making, written down where the people you want to reach can see and answer them. Thirty minutes a day of that is enough, and none of it requires a photo of your breakfast.
What belongs on each account
The split is by job, not by topic. The same launch produces a founder post and a company post, and they should not be the same text.
The platforms reinforce the split. On LinkedIn and X, feeds and conversations are built around people, and a personal profile can reply anywhere a discussion is happening; a company page mostly cannot join without it feeling like an ambush. The same holds on Bluesky, where the culture reads brand accounts skeptically. The company account earns its keep on the channels people check for the product itself, and in formats meant to be found again rather than replied to.
- Founder account: opinions with reasons, build decisions and their tradeoffs, questions to peers, replies in other people's threads, lessons from mistakes, the human version of launch day.
- Company account: release notes and the changelog, how-to content, documentation links, support answers in public, launch announcements with the facts, hiring posts, customer stories once they are real.
Reference each other without going in circles
The failure mode is the echo chamber: every founder post ends with 'check out what we built' and every company post is a repost of the founder saying so. Two accounts pointing at each other create the appearance of activity and the reality of one voice wearing two hats.
The rule that prevents it: every post must stand alone on its own account. The mention of the other account is a footnote for whoever wants more, never the payload. On launch day, the company account carries the facts and the founder account carries the story of the decision; each links the other once, and both are complete without the click.
Circular
Big news from @acme today! We shipped something huge. Go read the announcement on the company page!
Standalone with a footnote
We rebuilt export twice before shipping it. The first version assumed people wanted CSV; support tickets said they wanted their data back in the tool they left. Release notes are on @acme if you want the details.
Company side of the same launch
Export is live for all workspaces: full data, original formats, no request queue. Docs and limits are linked below. Our founder wrote up why the first version was wrong, if you want the backstory.
The transition point
As the company grows, the company account accumulates real reasons to exist: customers who track releases, users searching old how-to posts, prospects checking whether the product is alive. The shift is gradual, but the signals are concrete. Strangers start asking the company account questions directly instead of routing everything through the founder. Support requests crowd the founder's replies. More than one person needs to publish, and the founder's phone stops being an acceptable publishing bottleneck.
When those signals appear, move the operational content over deliberately and let the founder account change jobs rather than shrink. Its new work is opinion, hiring, and trust: the things a logo will never do well. Founders who keep announcing every minor release personally are doing the company account's job with the wrong instrument.
The decision table by stage
Treat the splits as defaults to argue with, not laws. A developer-tool founder may stay personal-led far longer because the audience buys judgment; a product with a strong community may hand weight to the company account early because the community gathers there.
You can measure whether the split still fits. Once a month, look at where inbound actually arrives: questions, DMs, and replies per account. When the company account's inbound overtakes the founder's for two months running, the audience has already voted, and the effort split should follow it.
| Stage | Lead account | Company account's job | Rough effort split |
|---|---|---|---|
| Pre-launch | Founder | Hold the handle, complete the profile, post a monthly progress note | 90 / 10 |
| Launch to first customers | Founder | Release notes, launch announcements, docs links | 70 / 30 |
| Repeatable sales, small team | Both | Changelog cadence, public support, first customer stories | 50 / 50 |
| Growing team, known product | Company | Primary distribution; founder shifts to opinion, hiring, and trust | 30 / 70 |
Put the decision to work
Once the lead account is chosen, the remaining work is ordinary content operations: a calendar that matches your real capacity and a platform strategy for wherever your customers actually read. The founder-led stage usually concentrates on one or two channels done properly rather than eleven done thinly.