You hit a number, or you shipped the thing, or a customer sent you a message that stopped you mid-scroll. The moment is there and the tweet almost writes itself, and then you open your design tool and the momentum stalls: no ready template for this specific situation, and by the time you've improvised something close enough, the feeling that made the post worth writing has cooled.
Most founders operate with exactly one milestone card in rotation — the MRR number. The user milestone, the testimonial, the feature ship, the 90-day streak all go into a mental folder called "I should post about that eventually." It's a folder that almost never gets opened.
This is the playbook for building all five cards before you need them.
What Makes a Milestone Worth a Card
Not every milestone needs an image. A card signals something specific: this moment was documented, this founder has a system, this update is worth stopping for. The moments that earn a card are the ones that give your audience a reference point: a revenue number they can track next time you post, a user count that marks where you are in the journey, a testimonial that shows the product is working for someone real.
The test is simple: if your audience could screenshot this post and share it with a founder who's six months behind you, it earns a card.
💡 The card test: Ask whether this moment gives your audience something to track forward. If yes, make the card. If it's a process update or an opinion, text usually carries more weight.
The 5 Cards Worth Having Ready
| Card type | When to post | Primary element | Must include |
|---|---|---|---|
| Revenue milestone | First $, $1K MRR, $10K MRR, $100K MRR | The number | Number, time to reach it, what drove it |
| User milestone | First 10, 100, 1K, 10K users | Count | Count, how you got there, next target |
| Feature ship | When a real capability ships | Feature name or one-line description | What it does, who asked, where to try it |
| Testimonial | When a customer says something specific | The quote | Full quote, attribution, your handle |
| Streak/time | 30/90/365 days; anniversaries; streaks | The duration | Time period, what shipped, one honest lesson |
Card 1: The Revenue Milestone
When to post it
This applies when you land your first paid customer, cross your first dollar of MRR, or hit the next clean number: $1K, $5K, $10K, $50K, $100K. Post it the day it happens — within 24 hours at the outside. Revenue milestones carry urgency because the number is tied to the moment, not a general trend. The post that goes up three days later isn't wrong, but it's missing the energy that made the number matter.
What the card needs
The number, front and center. Add the time it took to reach it: "from $0 to $1K MRR in 47 days" lands harder than "$1K MRR" on its own. Include a brief note on what changed: the channel that clicked, the pricing shift, the feature that moved the needle. Your brand colors and logo should pull in automatically so you're not reconstructing your palette from memory while the moment is live.
📋 Tweet pairing: The card shows the number. The tweet earns it: explain the how, not just the what.
Card 2: The User Milestone
When to post it
This applies at every order-of-magnitude jump: your first 10 signups, first 100, first 1,000. Not because the absolute number is impressive, but because each one marks a stage in a story your audience can follow. Early user counts are some of the most relatable posts a founder can make, because most of your audience is in an early stage too. A post that says "100 people have now signed up for something I built in my spare room" speaks directly to every founder who has wanted to make that exact post.
What the card needs
The count and what it represents: signups, active users, paying customers, or something more specific. A line of context about how you got there. A brief note on who these people are, if you can characterize them. The next milestone you're aiming for: this turns one post into a thread your audience can follow forward, not just backward.
*Photo by Centre for Ageing Better on *Unsplash
Card 3: The Feature Ship
When to post it
Something new is live that changes what the product can do, not a bug fix or an internal refactor, but a feature a user asked for or a capability that makes the product meaningfully different from what it was yesterday. The bar isn't every deploy. It's something a user would notice. The feature ship card also solves a specific build-in-public problem: features that ship without an announcement are features half your audience doesn't know exist yet.
What the card needs
The feature name or a one-line description of what it does. A note on who asked for it: "you asked for this" is more powerful than "we built this." Where to find it: a URL, a note that it's live for all users, a prompt to update. The card shouldn't need the tweet to explain itself; someone who sees it reshared should understand what shipped in under five seconds. Lemtika has a "we shipped" template built for exactly this format: pick it, fill the form, export.
Card 4: The Testimonial
When to post it
A customer says something specific and real: not "great product!" but something that names the problem they had, the moment it was solved, or the outcome they got. Specificity is the signal. Generic compliments don't make good testimonial cards; pointed ones do. The message you screenshot before you even think about whether to post it is the one to use.
What the card needs
The full quote, unabbreviated. Attribution that makes it credible: even a first name and company matters more than an anonymous blurb. Typography clean enough that the quote is the first thing the eye lands on, with your handle and logo secondary. One quick message to the customer before you post: "Mind if I share this?" costs thirty seconds and builds the kind of trust that generates more testimonials.
💡 Ask before you post: Most customers are happy to be amplified if you ask. The ones who say yes will often share the post themselves.
*Photo by Vitaly Gariev on *Unsplash
Card 5: The Streak or Time Milestone
When to post it
Streak cards mark staying power: any consistent pattern that runs long enough to feel earned, from a month of daily shipping to a product anniversary to the hundredth weekly update. Most founders underpost this type because it feels self-congratulatory. It's not. A founder who shipped something new for 90 consecutive days is telling a story about reliability and commitment that no feature announcement can convey, and that story has a specific audience of founders who've tried and stopped.
What the card needs
The streak number and time period, clearly stated. A rough summary of what shipped during that window, not a comprehensive list but a representative line. One honest observation about what you learned, not a highlights reel of wins. The streak card works best when it's equal parts milestone and reflection, because reflection is what separates the interesting build-in-public founders from the ones who are just reporting numbers.
Building the Rotation Before the Moment Arrives
The trap is treating each card as a one-off project, built from scratch each time a milestone hits, with design decisions made at the moment of highest momentum and lowest available attention. The alternative is setting up the five templates before any of the five moments arrive: pick a format for each card type, store your brand kit once, and have a template ready to fill rather than a canvas to start from. When the milestone hits, the workflow is three steps: open the template, fill the form, export the PNG.
Lemtika is built for this rotation. Set up your five card types, store your brand kit and reusable values (current MRR, your X handle, your avatar) once, and every future milestone pulls from the stored state automatically. The free tier exports unlimited PNGs; Pro removes the watermark and saves the brand kit permanently. The goal isn't beautiful images. It's having the right image ready the moment the milestone happens, so the post goes up the same day and not the day after you've moved on.
Do I need all five card types if I'm pre-revenue?
No. The two that matter most before revenue are the user milestone card and the feature ship card. Those carry you through the pre-launch and early-traction phases without waiting for a revenue number.
How often should I post milestone cards vs. text-only posts?
Cards go with moments that have a specific, shareable number or quote at their center. Most build-in-public content should still be text: observations, decisions, lessons learned. Cards are punctuation, not the whole paragraph. A rough ratio: one card for every four to six text posts.
What if I don't have a testimonial yet?
Skip Card 4 until you do. Don't manufacture a quote or use something vague. When a customer says something real and specific, you'll know immediately: it's the message you screenshot before you even think about whether to post it.
Does the order I post the cards matter?
Post in the order the milestones actually happen. The narrative of a build-in-public thread is chronological. Posting a 1,000-user card before you've posted a 100-user card breaks the arc your audience is following.
Can I repost the same card format with updated numbers?
Yes, and you should. A founder who posts their MRR card every time the number moves gives their audience a recurring reference point. The consistent format is part of what makes the number trackable over time. Updating the number and reposting the same template is a feature, not repetition.
How do I decide when a streak is long enough to earn a card?
When the streak number surprises you as much as anyone else. If hitting 30 days felt routine, a text post is fine. If it felt like something you almost didn't make it to, make the card.
What's the single biggest mistake founders make with milestone posts?
Posting too late. The milestone card that goes up the same day hits differently from the one posted three days later, after the founder has mentally moved on to the next thing. The whole point of building a template rotation is to remove the friction that makes posts go up late or not at all.