Build-in-public LinkedIn strategy for indie hackers

A build-in-public LinkedIn strategy for an indie hacker is a weekly disclosure policy. You publish a short record of work you already did, on your personal profile, with the numbers, refusals, and unknowns still attached. The reader who can pay is an operator who has the same problem, reading between meetings. Other indie hackers will applaud a streak. Applause is a side effect. The post still has to survive a person who has never heard the phrase "build in public."

The policy has four rules. One artifact per post, taken from this week. A disclosure filter before any number, customer, or roadmap line leaves your notes. A fixed writing block, then a queue on a clock you set in advance. Comments you type yourself, on a short list of people whose work you can add a fact to. Skip the day-count diary, the company Page changelog nobody follows, and a model asked to invent the week because the repo was quiet.

Boykli is the writing and publishing layer for that policy. Create posts drafts from a note, a YouTube URL, an article, a document, or series source text, and the writer has to keep your nouns and 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. That boundary 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.

Four ways indie hackers "build in public"

	A day-count diary on X	A company Page changelog	A topic calendar labeled "build in public"	An artifact log on the personal profile
What the reader sees	"Day 47. Shipped something small. Who else is building?"	A product update from a logo, often with no person attached	Pillars: lessons, mindset, a hot take, a carousel	One change, one cost, and one thing you did not measure
Who replies	Other builders keeping the same streak	Almost nobody, until the Page has an audience you do not have	People who like founder advice	Operators who recognize the constraint, plus a few builders
What you can defend on a call	The streak length	The feature list, if it matches the product	A sentence that sounds like the calendar	The number, the refusal, or the unknown, because it was in the note
What a buyer still needs	A reason your product fits their job	A path from the Page to a person they can trust	A noun that is yours, which the topic did not contain	The post already contains the point. The link is optional
Where Boykli fits	It does not import a tweet URL or post to X	The queue has no company-Page destination	Create posts will draft the topic, and the draft will be thin if the note is thin	Paste the week's note. Edit. Queue the personal profile
How it fails	The diary continues after the product stalls, because the streak is the product	The Page stays quiet. You rewrite the same update as a personal post with no new fact	The month is full of posts you would not sign	The note is empty. Thin is editable. An invented metric is not

The left column is a real distribution channel for other builders. It is a poor default for LinkedIn, where the person who can expense a tool reads during the workday and forwards a sentence, not a streak. Turning an X thread you already wrote into a LinkedIn document is a separate job, covered in repurpose a Twitter thread to LinkedIn. This page is the strategy for posts that start on LinkedIn from the product week.

A company Page is the wrong home for a one-person build log. Boykli's queue publishes to the personal profile only. The difference between that path and Page tools is in the personal profile scheduler guide.

The middle column is what a prompt returns when you ask for "build in public ideas": labels with no incident. Labels become posts when each one names a fact. A working list of those shapes is on LinkedIn post ideas for founders and indie hackers. If the company is a bootstrapped SaaS with a buyer, a price, and a support queue, the weekly operating plan is the LinkedIn growth strategy for bootstrapped SaaS founders. This page stays on the disclosure policy: what a public build log may say.

Draft this week's build log from a real note

Create posts and Voice Agent sit on a paid seat. BYOK is $29/month with your keys. Managed is $88/month with platform models and monthly caps.

boykli.com →

The disclosure filter

Build in public is a choice about what leaves the repo. Indie hackers get hurt in two directions. They hide every number and the post becomes advice. Or they publish a revenue screenshot, a customer name, and a half-built security note because the format rewards confession. Use one filter before the draft exists. If a row fails, the line stays in your notes.

Item	Publish when	Hold when	Leave out entirely
Revenue or MRR	The figure is yours, the window is named, and refunds or exclusions are in the same sentence	You are mid-change on price and the old number would mislead a buyer who asks tomorrow	A rounded "about 10k," a chart with no dates, or a peer's number you saw on X
A customer	You have permission to use the words, or you paraphrase without a name, logo, or identifying detail	The ticket is open, the person is identifiable in a small niche, or legal has not seen it	An invented testimonial, a fake company, or "a user once said" with a quote you wrote
A shipped change	A user can see the new behavior, and you can say what they could not do before	The change is on a branch, behind a flag nobody outside can hit, or you are unsure it stays	A commit list, a version number with no behavior, "shipping fast"
A failure	You can name the constraint, what you tried, and what you will not claim worked	The failure exposes a customer, a key, an unfixed hole, or a contract term	A humiliation arc written to collect comments
A roadmap line	The date is one you will keep, and the limit is explicit	You are still choosing. Say the constraint and the options, and stop before a date	"Coming soon," a public promise you need as marketing, a competitor's roadmap
A stack or cost choice	The bill, the limit, and the alternative you declined are yours	The number is a vendor's list price you have not been charged	A tool roundup that is a referral post with no decision in it
A competitor	You used the product for a named job and can state where you stayed or left	You are angry, or you only know their marketing site	A dunk, a fabricated benchmark, a "they are dying" claim

The writer in Create posts will not invent the missing cell. If the note says "have not counted whether tickets dropped," that sentence can lead. A smoother line that invents the result is a liability the moment a buyer asks for the sheet. The same standard is why a topic-only prompt fails, which is the teardown in why raw ChatGPT LinkedIn posts fail.

A note that is allowed to become a build log

This is an example of source text, written so you can see the shape. It is not a record from Boykli's customers, and it is not a number you should copy.

Thursday: shipped CSV export with three columns support kept pasting by hand — email, plan, last invoice date. Six hours. Did not add filters. In October, 2 of 14 trial accounts asked for an export. Have not counted whether paste-into-sheets tickets dropped. Price stays $19 a month. No annual plan.

Medium mode can hold that note. The draft should keep Thursday, the three columns, six hours, no filters, 2 of 14, October, the uncounted ticket change, and $19. It should not add an industry export benchmark, a quote from a "head of ops," or a claim that the export reduced churn. "Have not counted" is a stronger line than a percentage you do not have.

Short mode is the same note cut to the behavior change and the cost. 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 the objection plus the 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. Under ten characters, Create posts stops you and asks for more context. Ten characters is a floor. A usable note still names the situation.

Six post types a build-in-public week can fill

Three posts a week is enough. Skip a type in any week you lack the artifact. A seventh post that exists only to protect a streak is how the diary column wins.

Post type	Why an indie-hacker week contains it	What the note must include	Mode that fits	What to leave out
Behavior change	Someone can now do a thing they could not do on Monday	Monday's limitation and today's behavior, plus the hours	Short	The commit list
Cost of the choice	You picked a vendor, a price, or a scope cut	The bill or the hours, the alternative you declined, the limit you accepted	Medium	A sponsor line with no decision
Failed experiment	You ran something and stopped	What you tried, the window, the result you will stand behind, what you did not measure	Medium or long	A moral about "failure" with no setup
Support sentence	You answered it yourself	Their wording or a close paraphrase, the wrong assumption, the fix or the refusal	Short or medium	A named customer without permission
Pricing line	Someone asked, and you answered with a number you charge	The price, who asked, what you changed, what you refused	Medium	"Charge more" with no price of yours
Distribution note	You watched where a previous post went, in plain language	What you posted, what kind of reply came back, what you will repeat	Short	A claim that a tactic "beats the algorithm"

A carousel is a reading format for one of these memos, not a separate growth channel. One lesson, 2 to 8 slides, each slide one field. The caption still states the point. Dimensions and the safe zone are in the carousel dimensions guide. If the only number sits on slide six and the caption says "building in public," the document post hid the artifact.

Series mode fits a sequence you already lived, such as a price test across a month. Post 1 sets the premise. The last post concludes. "Part 2 of 5" is not allowed to be the only opening line. Each part still needs its own artifact.

The week, in one block

Do the writing in one sitting. An indie-hacker week will steal any plan that depends on a morning feeling. The content calendar is the month view. This is the week view.

Write three lines in a note (about 20 minutes). Line one is the behavior change. Line two is the cost or the refusal. Line three is the unknown. If you only have one line, publish one post. Do not stretch one fact into three essays. If the week produced no line you can sign, skip the queue. A quiet week is a better public record than a day-count.
Run the disclosure filter (about 10 minutes). Walk the table above. Strip customer names you do not have permission to use. Put the window next to every figure. Delete roadmap dates you are not willing to keep. If a line fails, it does not go into the prompt.
Draft one post per surviving line (about 35 minutes). Paste the line as the core idea. Pick the mode from the post-type table. Read the draft for nouns that were not in the note and delete them. If you would rather talk, use Voice Agent and treat the transcript as the only source. Three drafts come back. Keep the one that still sounds like the afternoon you shipped. A model that is asked to "write a build-in-public post for an indie hacker" with no note will produce the diary column. That is the failure mode in LinkedIn thought leadership automation: automation of a decision you already made, never a substitute for the decision.
Read it on the feed width (about 15 minutes). Check the draft the way it will sit on a phone and on a desktop feed. The post preview is that check. Replace a first line that could open a hundred other build logs ("Consistency compounds") with the behavior or the number. Hooks are a control. They are not a substitute for the artifact. The hook guide is the catalog. Your note is the filter.
Queue the posts on one clock (about 10 minutes). Put the approved drafts on the personal profile. Pick days you are deep in the product, so writing and publishing are not the same hour. Public datasets on timing are a window, not a promise that a specific minute multiplies reach. Use the best time to post page to choose a repeatable hour, then leave it alone for a month. The queue is the LinkedIn scheduling tool path: an approved draft, sent through the official publish path. It is not a browser session that types into LinkedIn. That difference, and the restriction risk of the second path, is covered in automated LinkedIn posting.
Comment on five posts you can add a fact to (about 10 minutes a day). Keep a list of ten people: five who do the job your buyer does, five who build in public and ship work you have actually used. One comment a weekday. The comment contains a fact from your week or a precise question about theirs. No "great build," no signup link, no automation. Boykli will not do this step. Commenting is distribution you do by hand.
Count three things on Friday (about 10 minutes). Drafts you were willing to sign. Posts that left the queue. Replies that named a product fact, a price, or a missing feature. Ignore follower count until you have a quarter of this habit. Boykli does not include a LinkedIn analytics suite. You read the replies in LinkedIn. The distribution model behind an impression is the algorithm guide. It explains retrieval and in-network versus out-of-network. It is not a lever you pull with a pod. Pods and comment swaps are the failure mode in grow a LinkedIn audience without pods.

A month of the same block, done in one sitting, is the batch scheduling workflow. Batch the queue only after the weekly note exists. A month of "Day 12" through "Day 40," written in advance, is thirty posts with no artifact.

What the block is not for

A public commit every day so the streak counter moves.
Rewriting the quiet company Page as a personal post that adds no new fact.
Connect requests sent in bulk to people with "Indie hacker" in the headline. The Meet Alfred alternative page is the argument against that motion.
Publishing another founder's MRR screenshot with your commentary on top.
A framework carousel whose only product noun is "my SaaS."

Ninety days of the same policy

Window	What you repeat	What you add	What you stop	Evidence you keep
Days 1–30	Up to three posts a week that pass the filter, same profile line	Nothing. Learn which of the six types you can fill without inventing	Day-count diaries, daily posting, pods	A Library of drafts you would still sign, and the Friday count
Days 31–60	The types that produced a reply about the product	One carousel from the strongest memo, and the five hand-written comments	Any type that only draws other hackers trading streaks	Replies that mention the limit, the price, or a missing behavior
Days 61–90	The two types a buyer actually answered	One profile line that states who the product is for, if the headline is still "building in public"	Revenue posts that drew founders and no buyer question	Calls or trials where the person can name a post

There is no follower target in this table. A public "10,000 in 90 days" goal pushes the strategy back into the diary column or into a pod. If a type produces buyer replies, do more of that type. If a type produces only builder applause, retire it even when the impression count was higher.

The 220-character profile line and the first line of a post are different jobs. The profile line has to stay true after the build log scrolls away. "Building in public" fails that test because it names a format, not a product. Who it is for, the constraint you accept, and the surface you sell on can stay for a quarter. How those two lines are written is in the LinkedIn headline guide.

Where the tool budget goes

One writing surface and the official publish path to your personal profile. Splitting the week across a general chat, a design tool, and a Page scheduler spends the block on glue.

Job this week	Where it happens	What you bring	What you do not get
Draft the posts that passed the filter	Create posts, or Voice Agent if you talk the note	The three lines, after the filter	Invented MRR, quotes, or customer logos
Turn one memo into slides	Carousel, 2–8 pages, your brand kit	The same note as the text post	A company-Page document, a slide that hides the only number
Hold the queue	Schedule, on the connected personal profile	Drafts you already signed	Comments, likes, connection requests, or a Page target
Find a source that is not your week	Radar or Algorithm, if you want an external article	A link you have read	A build log. An article about someone else's launch is a different post
See what you signed	Library	The drafts	A ranked list of other hackers' posts, or an analytics suite

Radar is allowed to suggest a draft from a public article. That draft is not a build-in-public post unless the note also contains your own decision. Mixing the two is how "I read a thread about pricing" becomes a post that sounds like you ran the experiment.

FAQ

Do I have to post revenue to build in public on LinkedIn?

No. Revenue is one row in the filter, and only when the figure is yours, the window is named, and the exclusions sit in the same sentence. A behavior change with a cost in hours is a complete build log. Indie hackers who lead every post with MRR train an audience of other founders comparing screenshots. That audience replies. It is a weak buyer list unless your product is sold to them.

Will a public build log hurt sales?

It hurts sales when the post promises a date you miss, names a customer who did not agree, or describes an unfixed security issue. It helps when a buyer can forward one sentence that matches the constraint they already have. Run the filter. If you would not say the line on a sales call, it does not go in the queue.

How often should an indie hacker post?

Up to three posts a week, and only for lines that survive the filter. A quiet week gets zero. Consistency is the queue leaving on time with posts you can sign. It is not a count of days with a post. Daily posting is how the day-count diary replaces the product.

Should the build log live on a company Page?

Put it on your personal profile. A one-person company Page has no audience to inherit, and Boykli's queue does not target a Page. People follow a person who was in the decision. The Page can exist for the product name. It is the wrong place for the weekly artifact.

Can I automate comments to other build-in-public posts?

No. Coordinated engagement and comment bots are the tactic this strategy refuses. Boykli does not comment, like, connect, or message. You write five short comments a week by hand, each with a fact, on posts by people you actually follow. The reach argument against pods is in grow a LinkedIn audience without pods.

What does Boykli cost for this workflow?

A paid seat is required to write, create carousels, use Voice Agent, publish, or schedule. BYOK is $29 a month: your OpenRouter key for chat and image, and your Google AI Studio key for Voice Live. Managed is $88 a month: platform models with monthly caps. Logged-in visitors can browse Radar and Algorithm without a plan. Prices are the public list on boykli.com. An approved draft is what the queue sends. The product does not supply the week's artifact.

How is this different from posting "lessons" as an indie hacker?

A lesson is the sentence after the artifact. "Small exports beat configurable ones" means nothing until the note holds the three columns, the six hours, and the filters you refused. Publish the artifact. The lesson can be the last line, and only if it follows from the lines above it. The idea shapes that can hold that artifact are on LinkedIn post ideas for founders and indie hackers.

Queue a build log you can still sign on Friday

Personal-profile publishing on a paid seat. BYOK is $29/month with your keys. Managed is $88/month with platform models and monthly caps.