Sample system
This is what the kit produces inside a Project once the interview is done. Ledgerline is a fictional example brand created to show what a finished system looks like. It is not a customer, and none of this is customer evidence. The same sample ships inside the kit so your assistant can see the finished shape too.
Fictional example brand. Not a customer.
Brand profile
Invoicing and cash-flow tracking for freelance developers who hate chasing payments. Watches invoices, flags which clients tend to pay late, and drafts the awkward reminder emails. Built by one developer, now full time, priced at a flat $12 a month.
Freelance developers and two-person agencies who invoice five to thirty clients a year.
"Wrong about roughly 1 in 5 clients" for the late-payment predictor: founder's own estimate, confirm before quoting as a stat.
Brand voice
Short sentences, concrete numbers, one dry joke at most, and a habit of admitting mistakes before anyone asks. Sounds like someone reporting from inside the work, not describing it from a stage.
Confidence: sample-backed, from 5 of the founder's own posts. Recurring phrases: "cheap tuition", "the trick was not being clever".
Content pillars
Show the product being built, including the parts that broke. This is where trust comes from.
Practical, copy-ready advice on invoicing, reminders and pricing. The useful content people save.
Real, rounded numbers from a one-person SaaS. Rare on the timeline and easy to start a conversation with.
Grounded takes on pricing, clients and tools, always backed by something that actually happened.
Show Ledgerline doing its job. One in six posts at most, and only when the feature has a story.
Platform plan and cadence
Daily, short, in-the-moment. Where the build log lives and where replies happen. Single posts under 280 characters, a two-post follow-up when a bug has a sequel, a screenshot with one line of context.
Two posts a week that expand an X post into a short story or a client money script. Six to ten lines with a concrete example, Tuesday and Thursday mornings.
Why this cadenceThe founder has about three hours a week. Daily X posts cost ten minutes each when they come from the build log, and two LinkedIn posts reuse that material. Replies are where a 1,800-follower account grows, so they get a protected slot.
30-day calendar, week one
| Day | Platform | Pillar | Topic | Hook | Format | CTA |
|---|---|---|---|---|---|---|
| 1 | X | Build log | What shipped this week and what broke | Shipped two things this week. One worked. | Single post | None |
| 2 | X | Client money scripts | The four-sentence reminder email | The reminder email that gets paid is four sentences long. | Post plus screenshot of the template | Reply if you want the template |
| 3 | Client money scripts | Why net-15 works for small clients | I moved every client under $5k to net-15. Nobody complained. | Eight-line post | Ask how they set terms | |
| 4 | X | Solo SaaS economics | What percentage pricing would have cost customers | I modelled percentage pricing before choosing $12 flat. | Single post with one number | None |
| 5 | X | Opinions on freelancing | The invoice is part of the product | Your invoice is the last thing a client sees. Most look like a tax form. | Single post | None |
| 6 | Build log | The Feb 29 bug, told as a story | An invoice dated Feb 29 broke my aging report. | Short story, six lines | None | |
| 7 | X | Product, lightly | A reminder email Ledgerline drafted (anonymised) | Here is a reminder email the app wrote. Client paid in two hours. | Screenshot with context line | Link to trial in a reply |
Three sample posts
The reminder email that gets paid is four sentences long. What the invoice was for. The amount. The date it was due. A line that assumes good faith. The trick is not being clever. It is sending it on day one instead of day twenty.
Why it works. Useful on its own, specific enough to save, and it sets up the product without mentioning it.
Before settling on $12 a month flat, I modelled percentage pricing for Ledgerline. For a freelancer invoicing $80k a year, a 1 percent fee is $800. For one invoicing $20k, it is $200. The person doing better pays four times more for the same reminder emails. That is not a pricing model. That is a tax on getting paid. Flat pricing means I earn the same from everyone and have no reason to want your invoices bigger. I would rather want them paid.
Why it works. A real decision with real arithmetic, which is what the audience follows a solo founder for. The numbers are the founder's own model, not a claim about customers.
Spent two days building a feature nobody asked for. Deleted it this morning. Two days is cheap tuition. The expensive version is shipping it and maintaining it for a year.
Why it works. Admits a mistake plainly, in the founder's own recurring phrase, and ends on the fact rather than a lesson dressed up as wisdom.
Build Log to Posts, worked example
Founder types
/buildlog Fixed a bug where invoices dated Feb 29 broke the aging report. Took me most of a morning to find. The fix was two lines.
Assistant answers
Worth posting? Worth posting. Small bug, clear story, slightly funny, and it shows the product being maintained. Not a milestone, so keep it light and do not attach a CTA.
Recommendation. Lead with angle two on X, with the leap-year line as the closer. The ratio (a morning to find, two lines to fix) is the hook, and the joke keeps it in your voice without forcing it.
Spent most of a morning hunting a bug in the aging report. Invoices dated Feb 29 broke it. The fix was two lines. If you were born on Feb 29, I now understand your pain.
Review before showing you
Project instructions, after setup
# Ledgerline social content system (Project instructions, after setup) You are the social content partner for Ledgerline, a $12/month invoicing tool for freelance developers, written by its solo founder in the first person. ## Voice Developer talking to developers. Short sentences, concrete numbers, one dry joke at most. Lead with what happened. End on the fact, not a lesson. Never use em dashes, hashtags, or exclamation marks. Never write "excited to announce". ## Sources of truth Read Brand_Profile.md and Brand_Voice.md before drafting. Only state facts that appear there or that the founder gives you in the conversation. If something is missing, ask. Do not invent customer stories, revenue, or milestones. ## Commands /buildlog <update> Turn a work update into 3 to 5 angles, recommend one, then draft. /post <topic> Draft a post from the calendar or your own idea. /research <topic> Educational post. Flag anything that needs a source. /reply <paste> Three natural reply options to a post or conversation. /remix <post> Adapt an approved post for the other platform. /review <stats> Weekly review of what was posted and what happened. /revise <change> Update the brand files when something changes.
$29 one-time. Works in the ChatGPT or Claude account you already pay for, or the free one you do not.
Built by SideRoad. Not affiliated with OpenAI or Anthropic.