The mental decision you want to avoid at 9am the morning you hit $5K MRR is "what should this image look like." That decision belongs in a Tuesday afternoon when nothing urgent is happening, not the moment the milestone lands and the tweet is already written.
Most founders think about visual content reactively: open a design tool when something happens, figure it out then. The founders who post consistently do not work that way. They have already decided which five types of images they will make, what each one looks like, and where the templates live. When a moment arrives, they fill the form, export the PNG, and post. The creative work was done weeks ago.
Here are the five image types worth setting up before you need them.
Quick Reference
| Template | Best for | Typical timing |
|---|---|---|
| Milestone card | Number or threshold crossed | Day of milestone |
| MRR meter | Revenue progress update | Monthly or quarterly |
| "We shipped" post | Feature or product launch | Day of launch |
| Testimonial card | Strong user quote received | As quotes arrive |
| Tweet beautifier | High-engagement tweet | Within 48 hours |
1. The Milestone Card
This is the bedrock image of build-in-public. A milestone card takes a single number or achievement and renders it clearly, with context: what the number is, why it matters, and who you are. Hitting $1K MRR, first 100 users, six months of consecutive growth; these moments deserve a card that says "I documented this."
What a milestone card should include
The core elements are the number itself (prominent, readable), a short label (what the number represents), a one-liner of context ("six months since launch"), your avatar or company name, and a brand color background. Milestone cards fail when they try to say too much. Pick the one number, make it undeniable.
The pre-set approach
💡 Pre-decide your milestones: List the next 5 milestones you are likely to hit in the next year. Set up a card for each one now. When the moment arrives, all you change is the number.
When to use it:
- Crossing a subscriber or user threshold (100, 500, 1K, 10K)
- Revenue milestones ($1K, $5K, $10K MRR)
- Streak or consistency milestones (90 days shipping, one year of build-in-public posts)
2. The MRR Meter
The MRR meter is a recurring post, not a one-time milestone. It shows revenue progress over time on a cadence, which means consistency compounds: the tenth MRR update carries more authority than the first because it is evidence of a pattern, not just a moment.
What separates a good MRR meter from a plain number
A good MRR meter shows movement. Where you were, where you are, and optionally where you are going. A progress bar toward a target, or a simple month-over-month comparison, turns a static figure into a story. The best ones add a data point below the main number: percentage growth, or the months it took to double.
The cadence question
Monthly is common for MRR updates, but what matters is consistency over frequency. A quarterly update posted every quarter beats a monthly one published seven times in eight months. Pick the cadence you will hold, set the template once, and ship it on schedule.
*Photo by Radoslav Bali on *Unsplash
3. The "We Shipped" Post
Every feature, fix, or product moment that took meaningful effort deserves a public record. The "we shipped" post is that record. It is brief by design: what shipped, one sentence on why it matters, and one number that proves it works if there is one. This is the closest thing build-in-public has to a press release, written for a feed instead of a wire service.
What makes it work
The format lives or dies on specificity. "We shipped better search" is weak. "We shipped full-text search across notes: 8 weeks of indexing, now under 200ms" is strong. The image card should mirror that specificity: the feature name, the outcome, your logo. Vague claims do not earn follows; concrete ones do.
Timing is most of the post
"We shipped" announcements belong to the day the thing ships. Not a week later when the sprint is done and the team has moved on. The post that goes live while the feature is fresh carries the enthusiasm of the work with it. A week later, it is an announcement. On the day, it is a moment.
4. The Testimonial Card
The testimonial card is the one image type that is both social proof and content simultaneously. When a user says something specific and true about your product, that sentence belongs on a card, not buried in a reply. On a card, with your brand, it travels.
What makes a testimonial shareable
Specific language beats superlatives. "This saved me 45 minutes every week" beats "this is amazing." The specificity is what makes other people recognize the problem and believe the solution. Find the line in the feedback that does that, strip the rest, and put it on the card.
How to build a testimonial pipeline
Build the habit of capturing strong lines when they arrive. A shared doc, a starred DM, a running Notion page. It does not matter where, as long as you look there when you need a testimonial card. One folder of captured quotes beats searching through months of DMs every time.
📋 Set up the template now: Before a quote arrives worth posting. When the good line lands, you should be filling a form, not figuring out the format.
*Photo by Microsoft 365 on *Unsplash
5. The Tweet Beautifier
The tweet beautifier is the simplest template and the most underused. It takes a tweet that resonated and renders it as a standalone image card. Same text, just designed. The effect is disproportionate to the effort: an image with text gets more reach than the same text as a tweet, and it makes the original thought feel more deliberate.
When to reach for it
Use the tweet beautifier for any text-only thought that earned genuine engagement. If a tweet landed well, it is worth a card. The image version reaches people who do not follow you yet, via repost and discovery, while the tweet reached people who already do. One thought, two audiences.
*Photo by Garrhet Sampson on *Unsplash
Putting the System Together
Having five templates is not the system. Knowing when to reach for each one is. The milestone card goes up when a threshold is crossed. The MRR meter ships on its cadence. The "we shipped" post goes live the day the feature is out, not a week later when the momentum has cooled. The testimonial card drops when the right quote arrives. The tweet beautifier extends the life of anything that resonated.
The setup work that makes it effortless
Most of the friction in founder social images happens one level above the template, at the brand level. If your colors, logo, and common data points are not stored somewhere that fills in automatically, there are micro-decisions every time you post. Store the brand kit once: primary color, secondary color, logo, X handle, avatar. Store the reusable data once: current MRR, product URL, tagline. Every subsequent post pulls from stored state, not from memory.
| Template | When to use | Cadence |
|---|---|---|
| Milestone card | Threshold crossed | As it happens |
| MRR meter | Revenue update | Monthly or quarterly |
| "We shipped" | Feature launch | Day of launch |
| Testimonial card | Strong user quote received | As quotes arrive |
| Tweet beautifier | High-engagement tweet | Within 48 hours |
Lemtika has templates for all five. Pick the one, fill the form, export the PNG. The free tier covers unlimited exports. Pro ($19/month) adds brand kit and saved data so every future card auto-fills from stored state.
*Photo by bruce mars on *Unsplash
Do I need all five templates, or can I start with fewer?
Start with the two that match your most frequent posting occasions. For most pre-launch founders, that is the milestone card and the "we shipped" post. Add the MRR meter when you have revenue to track, and the testimonial card when the first strong quote arrives. The tweet beautifier is useful once the other four are in place.
How far in advance should I set up these templates?
Before you need them. Ideally, before your next milestone. When the moment happens, the image should be a form fill, not a project. Even a basic version of each template, set up in advance, is worth ten polished designs that do not exist when the moment arrives.
What's the biggest mistake founders make with these post types?
Designing each one fresh every time. The whole point of a template library is that the design work is done once. If you are opening a design tool from scratch each time, you are doing ad-hoc design at the moment of highest distraction. The template removes the decision.
How often should I post milestone cards?
Only when the milestone is real. The credibility of milestone posts comes from the fact that they mark genuine events. Posting one every two weeks dilutes the signal. Post when something actually crossed a threshold worth documenting, and make it look consistent when you do.
Should all five templates use the same visual style?
Yes. Visual consistency across post types builds recognition over time. A follower who sees your milestone card should immediately recognize your "we shipped" post three weeks later. The brand kit (colors, fonts, and logo) is the common thread across all five.
What's the difference between a testimonial card and a screenshot?
A screenshot is raw evidence. A testimonial card is curated signal. The screenshot shows platform chrome, notification counts, and timestamps that distract from the quote. A testimonial card strips all of that, extracts the best sentence, and presents it in your brand. It looks intentional because it is.
Can I use these templates before I have revenue?
Yes. The milestone card and "we shipped" post do not require revenue — they require a real thing that happened. First 10 beta users, first GitHub star, first week of consecutive shipping. The MRR meter and testimonial card become relevant later, but the other three are useful from day one.
*Cover photo by Andrew Neel on *Unsplash