If you have no audience, do not post company updates. Post problem recognition, mistakes, proof, and workflow teardowns that make strangers feel understood before they know your product.
Abstract SaaS product card branching into multiple content ideas for a zero-audience founder.
The hardest moment in founder marketing is not writing the hundredth post. It is writing the first ten when nobody knows you, nobody knows the product, and nobody is waiting for an update. That is why most SaaS founders post the wrong thing: launch announcements, feature screenshots, and “we are excited to share” updates that only matter after trust exists.
When nobody knows your SaaS exists, your job is not to announce. Your job is to make the right person recognize a problem they already have. The product comes later. First, you need pain, context, proof, and a small enough idea that a stranger can understand it in three seconds.
Do not start with product updates
Product updates are useful for existing users and warm followers. They are weak for cold distribution because a stranger has no reason to care that you shipped version 0.4, added a dashboard, or improved onboarding. They do not know the old pain, so the new feature has no meaning.
Instead of “we launched analytics,” post “most founders measure signups but ignore the screen where users quit.” Instead of “we added templates,” post “the blank-page problem is why most founders never publish weekly content.” Same product truth, stronger angle.
The five content buckets
If you are starting from zero, use these five buckets before inventing more formats:
Mistake: name the costly behavior your buyer repeats. Example: “Your app launch content is too product-first.”
Before-after: show the old workflow versus the better workflow. This is the easiest way to explain software without sounding like an ad.
Objection: answer the thing that keeps people from trying your category. Example: “I do not have time to make content” or “TikTok is not for B2B.”
Proof: show a metric, screenshot, quote, teardown, or result. Proof makes cold content feel grounded.
Teardown: break down how a real workflow fails and how to fix it. This builds trust before the product pitch.
A calendar app should not start with “we built a smarter calendar.” It should post: “Your calendar is full but your priorities are invisible.” A user research tool should not start with “AI-powered summaries.” It should post: “You are making roadmap decisions from the loudest customer, not the most common pain.”
Slidetik should not only post “AI slideshow maker.” A better cold post is: “The reason founders do not post weekly is not ideas. It is turning ideas into visuals, hooks, and formats.” That framing makes the viewer feel the pain before they hear the product name.
Turn features into posts
Every feature has a story if you explain the old way first. The old way creates tension. The feature resolves it. That tension is the post.
Use this formula: old workflow, hidden cost, specific failure, better workflow, proof, CTA. A feature called “brand color extraction” becomes: “Your content looks inconsistent because every post starts from a blank template.” A feature called “URL import” becomes: “Your product page already has the content ideas. You are just not repackaging them.”
Your first 30 posts should not be random. Pick three core pains and create ten posts for each. For each pain, write two mistake posts, two before-after posts, two objection posts, two proof posts, and two teardown posts. That gives you enough repetition for the market to understand your category and enough variation for you to learn which angle works.
Do not judge the strategy after three posts. Cold distribution needs repeated exposure. The first month is about finding language that makes your audience say: “that is exactly my problem.”
Create the first deck
If you are blocked by production, use Slidetik to turn your product URL into the first short-form slideshow. Then repurpose that deck into LinkedIn, X, Reddit, and email. The faster you get from idea to published asset, the faster you learn what the market actually cares about.
Ship the slideshow this week.
Paste your URL. Slidetik generates a 9-slide TikTok deck with copy, AI visuals and your brand colors in 60 seconds. From €5/month.
What should I post if nobody knows my SaaS exists?
Post about the painful workflow your buyer already recognizes: mistakes, before-after comparisons, teardown posts, objection answers, and proof. Avoid product updates until the audience understands the problem.
Should early SaaS founders post product updates?
Only after they have built context. A product update works when people already know the problem and care about your progress. If you are starting from zero, problem-led education usually performs better.
How many content ideas does a new SaaS need?
You need 20-30 strong posts to learn which pain resonates. That does not mean 30 new ideas: one feature can produce 5-10 posts when framed as a mistake, use case, objection, proof point, comparison, and workflow teardown.
