B2B founder personal branding playbook and post types

A B2B founder personal brand is the set of posts a stranger on a buying committee can forward inside their company without rewriting your claim. It is not a color, a headshot treatment, or a follower count. The playbook is smaller than a content strategy deck: a short list of post types, the artifact each type is allowed to use, and a cadence on the founder's personal profile that survives a week of customer calls.

The company Page can announce a release. It cannot carry the judgment. Buyers who are also operators read the founder because they want the constraint behind the feature: why this price, why this integration was refused, what the last failed launch actually counted. If that judgment is missing, the profile is a brochure with a name on it. If the judgment is invented by a model, the post is a liability the moment someone on the call asks for the denominator.

Boykli is the writing and publishing layer for that playbook. Create posts drafts from a note, a YouTube URL, an article, a document, or series source text, and the writer is required to keep your nouns and to drop statistics, studies, quotes, and anecdotes that are not in the source. Voice Agent does the same job from a live interview: three drafts, and only facts that appear in the transcript. The queue publishes an approved draft to the personal profile you connect with LinkedIn OAuth. It does not post to a company Page, and it does not comment, like, connect, or message. The product decision is the same one in building Boykli: the words start from something you brought, and you read them before they leave.

Logged-in visitors can browse Radar and Algorithm without a plan. Writing, images, carousels, Voice Agent, publishing, and scheduling need a paid seat. BYOK is $29 a month. Managed is $88 a month. Prices are the public list on boykli.com.

Three ways founders try to "build a brand"

The middle column is what most "personal branding playbooks" actually ship: pillars, hooks, and a weekly theme. Pillars are filing labels. They become posts only when each one names a fact. A working list of shapes, each tied to a note, is already on the LinkedIn post ideas for founders page. This guide is the buyer-facing cut of that list: which type answers which question inside a B2B deal, and how to run the week so the types stay distinct. Independent consultants selling a scoped engagement use the same artifact rule and a different close. That operating plan is how independent consultants get high-ticket clients from LinkedIn.

Free LinkedIn Utilities: Turn plain text into clean 1080x1350 multi-page PDF slides using the Free LinkedIn Carousel Generator, and test your post hook and dwell score on the Free LinkedIn Algorithm Grader.

Eight post types a buying committee can use

Each type answers one question a champion gets asked after they share your profile. The "artifact" column is the minimum source. If you do not have it, skip the type this week. Do not substitute a general claim. The write mode is the Boykli control that fits the length: short is about 30 to 75 words and the page label says 45–400 characters, medium is about 100 to 250 words (400–1400 characters), long is the room for an objection plus a metric (1400–3000 characters). YouTube, article, document, and series (2 to 8 posts) are the other modes. Tone, hooks, and the call to action are separate switches.

These eight are enough for a year. A ninth type, the revenue screenshot, belongs only when the number is yours, the window is named, and the exclusions are in the post. The writer will not invent ARR. If the note says "$4,280 in March, all monthly, two refunds," that sentence can lead. If the note says "we are growing," the draft should stay thin.

Decision memo

This is the type economic buyers forward. They are about to make a similar call on price, packaging, or a vendor, and they want to see how you reasoned when you were the one spending the money or refusing the feature.

Example note, written as the kind of source you paste. It is not a record from Boykli's customers:

Annual plan was $480. Three buyers in the same week asked for a refund inside 11 days. We turned annual off. Monthly stayed at $49. We did not look at logo churn. We looked at whether the three refunds were the same complaint. They were: they needed a CSV export we did not have. Export shipped 18 days later. Annual is still off.

Medium or long mode can hold that note. The draft should keep $480, $49, three buyers, 11 days, CSV, and 18 days. It should not add a retention percentage you did not compute. "We did not look at logo churn" is a stronger line than a churn figure you do not have. That honesty is the brand. Polish is not.

A long post is the right room when the objection and the metric both need a paragraph. If the memo is a sequence of decisions over a quarter, series mode can split it: post 1 sets the premise, the last post concludes, and "Part 2 of 5" is not allowed to be the only opening line.

Operator arithmetic

Champions who have to justify a tool internally want a founder who can say what a number excludes. One number, one window, one denominator. "Support took 6 hours and 40 minutes last week across 14 tickets. Median first reply was under two hours. That excludes the two tickets we closed by shipping a fix the same day, which took longer and are not in the median." A reader can attack the definition. They cannot accuse you of borrowing a benchmark.

Short mode is enough when the sentence is complete. Medium mode is for the exclusion. Skip this type in a week when you did not compute anything. A vague "usage is up" trains the audience to ignore the next number you publish.

Customer sentence

Quote when you have permission, or when the line is already public in a review, a GitHub issue, or a forum thread you can point at. Paraphrase when you do not. "A buyer wrote that the export died on a comma inside a company name" is a paraphrase you can stand behind. "Our users love how simple it is" has no speaker.

Say what you changed because of the sentence, or say that you refused to change it and why. A sentence with no consequence is a testimonial block. A sentence plus a refusal is a product decision, which is the same muscle as the memo. If the source is a long ticket, upload it as a document. Document mode uses the file, not the filename.

Mechanism teardown

This is the type a technical evaluator reads before they book. They want to know if you understand the failure mode of your own system. Name two or three moving pieces, one limit, and what you will not pretend to solve.

The teardown can be a long post or a document carousel. A carousel is a PDF document post, not a stack of images. Designs and the brand kit (canvas, accent, logo, handle, type) live on the carousel page, covered in the LinkedIn brand kit guide. Each slide should hold one field from the artifact: the pieces, the limit, the refusal. The caption is still a post. Do not hide the limit on the last slide and write "a quick breakdown of how we think about infrastructure." The feed folds before the PDF.

If the mechanism is a talk or a written doc you already published, YouTube mode and article mode exist so you do not retype it. The LinkedIn post is a teaser that keeps the nouns. The long explanation stays at the URL. Turning a talk into a teaser is its own workflow. The rule here is the same: the post may not upgrade a title into a case study.

Build log

B2B buyers use this type as a liveness check. A founder who can describe one user-visible change is still close to the product. "Search on the library used to scan titles. It now scans the post body. A one-character query is rejected because it returned the whole account." That is a build log. "Shipped a lot this week. Building in public." is a status line.

Keep the log to one change. A digest of twelve tickets reads like a changelog paste, and nobody forwards a changelog into a buying thread. If you have twelve changes, pick the one a buyer would notice, and leave the rest in the release note on the company Page.

Category disagreement

This is the type people confuse with thought leadership. A disagreement needs a claim you reject and a constraint in your own product that makes the claim false for you. "Most teams should hire a LinkedIn agency" is a topic. "We will not hire an agency to post for the founder, because the posts that start conversations name prices and refusals only the founder was in the room for. The cost is that the cadence dies in a fundraising week." That is a disagreement. The cost has to be in the post. A point of view with no cost is an ad for your own seriousness.

The automation around this type is drafting and scheduling, not the opinion. How to keep a cadence without letting the model invent the point of view is the subject of LinkedIn thought leadership automation. Use that workflow when the disagreement is real and the week is busy. Do not use it to manufacture a disagreement you do not hold.

Working agreement

Buyers want to know how implementation will feel. Publish the rule you actually enforce. "The founder joins the first demo. A solutions hire does not exist. Custom fields are refused until two customers have asked for the same field in writing." Adjectives like responsive, white-glove, and founder-led fail this type because a champion cannot repeat them as a process.

This type also covers hiring and not hiring. "We did not open a support role. The founder still closes tickets on Fridays. The cost is a slower roadmap on Fridays." Name the cost or the post is a lean-startup slogan.

Proof carousel

Use a carousel when the artifact is a list of fields a reader will skim in a meeting: old price, new price, objection, what you measured, what you refused to measure. One field a slide. The caption states the decision in sentences, because some readers will never open the PDF. Portrait and square dimensions, and the type ramp, are a separate production problem. The branding problem is keeping the caption as specific as slide one.

The weekly playbook

Run this as a fixed loop. Three posts a week is enough if each one is a different type. Five posts of the same type, usually the build log, teaches the audience nothing about how you decide. One post a week is also enough during a launch or a fundraise, provided you do not fill the gap with topic posts.

1. Pick the artifact before you pick the type. Open the week with one of: a pricing or packaging note, a metric you computed, a sentence you may quote, a mechanism you can draw, a user-visible change, a claim you reject, or a rule you enforce. If none of those exist, do not write. A skipped week is cleaner than a pillar post.
2. Assign the type from the table. One artifact, one type. A pricing change is a decision memo, not also a category disagreement and a carousel, unless the carousel is the same memo split into fields. Double-publishing the same claim in two voices reads as a campaign.
3. Draft in the matching mode. Paste the note into Create posts, or talk it through Voice Agent if the artifact is still in your head. Voice Agent is an interview with a live transcript and three drafts. It is not a brief that says "write a personal brand post about our category." Read the draft against the note. Delete any number, customer, or anecdote that was not in the source.
4. Set the profile line separately from the post. The 220-character headline is the standing sentence under your name. The first line of the post is a different job. Mixing them produces headlines that sound like hooks and posts that sound like bios. The split is covered in the LinkedIn headline generator guide. Update the headline when the category or the role changes, not every time you publish.
5. Preview, then queue. Read the draft the way it will sit in a feed, on a phone width and on a desktop width, before it is approved. Schedule from the personal profile on the weekdays and the time of day you saved. The calendar habit, including what belongs in a queue versus a draft pile, is the LinkedIn content calendar. Company Page posts stay a manual announcement. Boykli will not move them for you.
6. Reply as the founder for the first hour you can. The brand is also the comment. A specific reply that adds a missing exclusion ("the median excludes same-day fixes") does more than a second post. A "great question!" reply trains people to treat the profile as a broadcast. You write the replies. The queue does not.

A practical week looks like this. Monday: decision memo from a pricing note, medium mode, queued for Tuesday. Wednesday: operator arithmetic, short mode, queued for Thursday. Friday: either a customer sentence or nothing. The mechanism teardown and the proof carousel are monthly, because they take a document and a brand-kit pass, and a weekly carousel of thin slides burns the format. The category disagreement is occasional. If you disagree on a schedule, the disagreement is a content pillar again.

Keep the drafts in the Library so next month's memo can point at last month's number without you hunting through LinkedIn. Series posts stay as separate items you can order. Do not collapse a series into one caption and call it a brand story.

What this playbook refuses

• A swipe file of other founders' posts, rewritten under your name. Their price, their refund count, and their customer are now claims you have to defend. Boykli does not supply a ranked pack of other people's posts.
• Engagement as a substitute for a type. Pods, comment prompts, and "agree?" closers can move a number on a post that still cannot be forwarded into a deal. The post has to contain the point before anyone reacts to it.
• Agency voice on the founder profile. An agency can run the company Page. The personal profile posts in this playbook name rooms the founder was in. If someone else was in the room, they can be the author, on their profile, with their artifact.
• Invented proof to make a thin week look busy. A missing denominator stays missing. The draft should sound unfinished until you paste the fact, which is the correct pressure.
• Posting to the personal profile through a website bot. Official publishing goes through the LinkedIn API on the connected profile, on a schedule you approved. Browser automation is a different product category and a different risk, and it is not this playbook.

The profile photo, the banner, and the About section still matter as labels. They are not the brand. A buyer who opens About and then finds six months of interchangeable advice will believe the About section less, not more. Spend the hour on one memo.

FAQ

How many LinkedIn posts should a B2B founder publish?

Three specific posts a week is a full cadence. One is a maintained cadence. Zero is fine in a week with no artifact. Daily posting is a different job, and it usually collapses the eight types into one repeating shape. Match the count to the number of real notes you can defend, then put the approved drafts on a clock so the count does not depend on you opening LinkedIn at the slot.

Should the company Page or the founder profile carry the brand?

Both exist, and they do different jobs. The Page distributes announcements to people who already follow the company. The founder profile carries decisions, numbers, and refusals. Boykli schedules the personal profile only, after LinkedIn OAuth. Plan the Page as a separate, lower-frequency surface. Do not mirror every founder post onto the Page. The Page voice is the company. The profile voice is a person who can be questioned.

Will specific posts sound like selling?

A price, a refusal, and a limit are more useful to a buyer than a soft post that never names the product. Selling is a pitch with no artifact: a feature list, a "DM me for a demo," a claim about outcomes you did not measure. A decision memo that includes the annual plan you turned off is not a pitch. Readers who are not buyers will scroll. Readers who are in a similar decision will forward it. Write for the second group.

Can an AI ghostwriter run this playbook?

It can draft. It cannot attend the decision. Paste the note, or speak the note into Voice Agent, then delete anything the draft added. A ghostwriter who interviews you and only uses the transcript is compatible with this playbook. A ghostwriter who is briefed with "make me sound like a category expert" will produce the middle column of the first table. The post generator page describes the controls. The source still has to be yours.

What if I am technical and dislike personal branding as a phrase?

Ignore the phrase. Publish the mechanism teardown, the build log, and the operator arithmetic. Those three types do not require a story about your morning routine or a lesson about resilience. They require you to explain a system you already run. Founders who hate "personal brand" content usually hate the middle column. The right column is operational writing with your name on it, which is closer to a design doc than to a creator funnel. If you are an engineer who is not the founder, the same idea has a tighter filter: the incident, the design, and the number still have to clear your employer's comms rules. That cut is the LinkedIn content playbook for software engineers.

Does the headline need to match the week's post type?

No. The headline is the standing description under your name, capped at 220 characters. It should say what you build and who it is for, in nouns a buyer searches. The week's post can be a refund story, a teardown, or a working agreement without the headline changing. Rewrite the headline when the product category or your role changes. Rewriting it to match a hook throws away the only persistent sentence on the profile.

Where does the carousel sit in the playbook?

As a proof format for an artifact you already wrote, not as a separate brand. If you do not have the memo, the carousel will be eight slides of advice. Produce the text first. Then split fields into slides with the brand kit so the document looks like the same company as the site. The caption repeats the decision in words. Schedule the document post the same way you schedule text: approved draft, personal profile, a slot you chose.