Lesson 2 of 87 min read

The founder account and the company account

Split the jobs between people and brand: the founder tells the story, the company ships product news, and the team amplifies without chaos.

In this lesson you will

  • Decide what the founder account and the company account each post
  • Give teammates a clear, low-effort way to amplify
  • Set roles and one approval step so nothing goes out unseen

Small SaaS teams usually make one of two mistakes. Either the founder posts everything from a personal account and the company page sits empty, so prospects who check the brand find a ghost town. Or the company page posts everything in a polished, faceless voice and nobody engages, because people follow people, not logos.

The fix is not "post from both". It is giving each account a different job, so neither one has to do everything. This lesson splits the work between the founder, the company account and the rest of the team, and adds just enough process that a new teammate can help without a post going out that nobody checked.

Why both accounts exist

People and brands earn attention for different reasons.

  • A founder account earns trust. Readers want the reasoning behind decisions, the mistakes, the opinions about the market. A founder can say "we got this wrong" and it reads as honest. A company page saying the same thing reads like a press statement.
  • A company account earns reliability. It is where a prospect checks that the product is alive: recent releases, docs links, status updates, how-to posts. It is also what customers tag when they need help.

Most B2B buyers will see both before they start a trial. The founder post gets them interested; the company account confirms the product ships. If one is missing, the other has to work twice as hard.

Split the jobs

Here is the split we recommend for a team of one to ten people. Adjust the networks to where your buyers are, but keep the jobs separate.

Founder accountCompany accountTeammates
Main jobThe story and the opinionsThe product and the proofAmplify and add detail
Typical postsWhy we built it, decisions, lessons, market takes, behind the scenesReleases, how-tos, docs links, customer wins you have permission to share, eventsReposts with one line of their own, the detail behind a feature they built
VoiceFirst person, "I""We", plain and helpfulTheir own
Best networks for B2B SaaSLinkedIn, XLinkedIn page, X, Bluesky, your community (Discord or Slack)Wherever they already post
Cadence to start3 posts a week3 to 5 posts a weekWhen they want, with a nudge on launches

Two rules keep this from collapsing:

  1. The same news, two angles. When you ship something, the company posts what changed and how to use it. The founder posts why it was built, or what was hard about it. Never the same text on both.
  2. The founder never becomes the support desk in public. If a support question lands on the founder's post, answer briefly and point to the company account or the docs. Otherwise the founder account turns into a ticket queue.

What teammates actually do

Asking teammates to "post more" does not work. Asking them to do one small, specific thing does. Give each teammate a short menu:

  • Repost with one line. Not a bare repost; one sentence on what they personally care about in the release.
  • The detail post. The engineer who built a feature writes the post only they could write: the edge case, the tradeoff, the screenshot of the debugging session.
  • Reply in threads. When a company post gets a technical question, the person who knows the answer replies from their own account.

Make it opt-in, and never write posts for teammates' personal accounts. Ghost-written posts on someone's personal profile read as ghost-written, and they put your colleague's name on words they did not choose.

Worked example: one release, two accounts

Here is how we treat a real release from our own changelog: support for GIFs in the composer. Our company account posts the "what and how". The founder-style post, which on our side we write in the team's voice because we keep personal names off our channels, posts the "why".

The company post on our LinkedIn page:

The composer now handles GIFs.

Search for one or add your own, or cut a GIF from a video you already
uploaded.

Networks that only take video get a looping video at publish time, so your
library keeps the original. Where a network can't take a GIF at all, the
pre-publish check says so before you schedule.

Changelog: [link]

The story post, written for X:

Every network treats an animated image differently. Some take a GIF as is,
some only take video, some take neither.

That's a lot to remember for a reaction GIF.

So the composer now remembers it for you: it converts where it can, warns
where it can't, and keeps one original in your library.

And a Discord version for our community, which is shorter and invites a reply:

GIFs are in the composer. If you hit a network where one doesn't behave,
post it here with a screenshot and we'll look.

Same release, three jobs: inform, explain, invite. Notice that none of them repeats another's wording. That is what stops a follower who sees all three from feeling spammed.

A note on our own setup: we are a team, not a single named founder, and our house rule is that our channels speak as "we". If you are a solo founder, you have an advantage we chose not to use: your face and name. Use them. The split still applies; your personal account is the story, your company account is the product.

Roles and one approval step

Once more than one person can post for the company, you need two things: roles and one approval step. Not a committee. One step.

Roles. Decide who can do what before you invite anyone:

  • Owner or admin: connects accounts, changes settings, approves posts.
  • Member: drafts and schedules, but posts wait for approval.
  • Viewer: sees the calendar and reports, cannot post. Good for an advisor or a contractor reviewing work.

The approval step. Any post from a member waits for one admin to approve it. The rule for the approver is simple: check facts, links and tone, then approve or send it back with one comment. Do not rewrite it yourself; tell the author what to change, or the team stops drafting.

What always needs approval, whatever the role:

  • Anything mentioning a customer by name
  • Anything about pricing, security, outages or legal topics
  • Replies to an angry public complaint
  • Anything posted during a launch week

What never needs approval: a teammate's own personal account. That is theirs.

Budget: an approver should spend about 10 minutes a day on the queue. If it takes longer, the drafts are not close enough, which usually means the positioning from lesson 1 is not written down where the team can see it.

A starting week for both accounts

If you are starting from nothing, here is a week that fits in about two hours across both accounts, including writing. Treat it as a starting shape, not a law.

DayFounder accountCompany account
MondayA lesson or decision from last weekHow-to post from a doc page
TuesdayReply to three posts from buyers or peersProduct update or changelog post
WednesdayA take on something happening in your marketRepost the founder post if it is about the product, with one line
ThursdayBehind the scenes: a screenshot, a tradeoffA customer question answered in public (no names without permission)
FridayNothing, or a short reply threadRecap of the week's shipped work, with links

Two things to notice. The founder's Tuesday is replies, not a post: in B2B, a thoughtful reply on a buyer's post often does more than another post of your own. And Friday is deliberately light, because a rhythm you can keep beats a rhythm that burns you out by March.

Common mistakes

The company account reposts every founder post. It looks like the founder is the only person who works there. Fix: the company account reposts only posts about the product, and adds its own line.

A faceless brand voice on the founder account. "Excited to announce" from a person sounds like a press release. Fix: first person, past tense, specific. "We shipped X because Y" beats "Excited to share X".

Everyone has admin rights. Then nobody owns the approval queue, and a draft goes out with a broken link on launch day. Fix: two admins at most; everyone else is a member.

No rule for replies. A prospect asks a question on the founder's post and nobody answers for three days. Fix: the company account owner checks the founder's posts for questions once a day.

Recap

  • The founder account tells the story and the opinions; the company account ships the product news and proof.
  • Post the same news from both, but with different angles and never the same text.
  • Give teammates a small menu (repost with a line, the detail post, replying in threads) and keep it opt-in.
  • Set roles before you invite anyone, and route every member's post through one approval step.
  • Some posts always need approval: customers by name, pricing, security, angry replies and launch week.

Exercise

Draft one release for two accounts

  1. Pick your most recent release or update from your changelog or release notes.
  2. Write the company version: what changed, how to use it, one link. Format it with the LinkedIn post formatter so the line breaks survive.
  3. Write the founder version: why you built it, or what was hard. Format it with the X post formatter and check that it does not repeat a single sentence from the company version.
  4. Write a one-paragraph "who posts what" note for your team using the table above: which accounts, which jobs, which networks.
  5. Write your approval rule in two lines: who approves, and which kinds of posts always need it.

Done looks like: two formatted drafts of the same release with different angles, and a short team note covering accounts, jobs and the approval rule.

Go further

Workspaces, roles and approvals

In FoPost, invite a teammate from team with the role that matches the table above: admin, member or viewer. Then turn on Require Approval in your workspace settings, so posts scheduled by members are held until an admin approves them; they wait in approvals. See Workspaces for how a workspace keeps accounts, calendar and team together.

Check yourself

  1. 1What is the main job of the founder account compared to the company account?

    The founder account earns trust with the story, decisions and opinions. The company account earns reliability with releases, how-tos and proof.

  2. 2Why should teammates never have posts written for their personal accounts?

    Ghost-written posts read as ghost-written and put a colleague's name on words they did not choose. Teammate posting should be opt-in and in their own words.

  3. 3Which posts should always go through approval regardless of role?

    Posts naming a customer, anything on pricing, security, outages or legal topics, replies to angry complaints, and anything during a launch week.

Academy

Keep reading, free

Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.

What describes you best?
Where do you post today? Pick any that apply.
What do you want most right now?

We use your answers to suggest lessons and to improve the Academy. They are never shown publicly. Read our Privacy Policy.