How to Get People to Pay You With No Audience: The Post For Me Playbook

The most useful part of Chris Koerner's interview with Caleb Panza is not the headline number. It is the sequence.

Caleb and his cofounder did not start with a giant audience, a perfect launch, or a glamorous product category. They started with a problem they understood, posted honest MRR updates when the numbers were still small, answered customer questions manually, and turned those questions into resource articles that search engines and AI tools could understand.

Source Note

Credit for the interview goes to Chris Koerner and The Koerner Office. The episode page is titled "He Lost His Job, Then Built a $11K/Month App" and describes Caleb Panza's path from job loss to a SaaS product that crossed $10K MRR.

Caleb Panza is publicly listed as a cofounder at Day Moon Development and building Post For Me. The revenue figures, churn remarks, and timeline in this post are attributed to the interview and podcast page, not independently audited financials.

Caleb's tool-stack notes come from the transcript and user-provided episode notes. I checked the public product pages before adding them here. One useful distinction: Unkey is positioned publicly as API infrastructure with key issuance, rate limiting, and analytics; Vercel is the deployment/hosting layer in this stack.

Link Map

The Main Lesson

The strongest takeaway is not "post screenshots and people will pay you." The stronger takeaway is this:

If you do not have an audience, turn every real customer interaction into a public proof asset or a searchable answer.

Caleb says the first launch did not explode. The transcript describes a slow first stretch: a few hundred dollars in MRR, friends and family, and not much traction. Then the team started posting milestones, responding to replies, and using customer questions as source material for resources.

That is a much more repeatable playbook than "go viral."

No Audience, Still Useful

Post For Me solves a narrow, painful problem: integrating social posting across many platforms is annoying. Every platform has different auth, media requirements, rate limits, and API behavior. Post For Me packages that into one developer API.

That matters because a small SaaS does not need to be broadly interesting at the start. It needs to be sharply useful to the people who already feel the pain.

Caleb's own suggested first step in the interview is simple: find a problem you have personally experienced, whiteboard the solution, reduce it to the smallest launchable version, and improve it daily based on how customers actually use it.

Public Proof Updates

The build-in-public move worked because it was specific and credible. Caleb did not start by announcing a massive company vision. He posted each MRR milestone as the product moved forward.

The transcript notes that around the early $500 MRR mark, he began posting updates for each additional $100. Later, larger milestone posts drove more attention, replies, and trust.

For a founder, the lesson is not that every number must be public. The lesson is that customers need proof. If you cannot show revenue, show shipped features, case studies, integration guides, customer questions answered, uptime improvements, or support speed.

Customer-Question SEO

This was the best part of the interview.

Caleb says they kept the website chat human-run instead of relying on an automated chatbot. That gave the founders raw customer language. When the same question appeared more than once, they treated it as a signal and turned it into a resource article.

That is customer-led SEO:

1. Talk to customers manually.
2. Log repeated questions in a system such as Linear.
3. Write a resource page that answers the question clearly.
4. Structure the page so Google and AI systems can understand it.
5. Use the article to help current users and attract future users.

Caleb's line of thinking is right: one customer who asks a question may represent many more who silently leave because the answer was not obvious.

AI Search Visibility

The episode also connects directly to AI discovery. Caleb says customers reported finding them through GPT, Claude, and similar tools. That is not magic. It is what happens when a product has clear pages that answer specific questions in customer language.

The JQ AI SYSTEMS angle is simple: AI search does not remove the need for useful content. It raises the value of precise, well-structured answers.

A good resource article for AI discovery should answer:

• What problem is this solving?
• Who is it for?
• What platforms, tools, APIs, or constraints matter?
• What is the step-by-step solution?
• What are the limitations or alternatives?
• What should someone do next?

Pricing And Churn

The honest part of the interview is that growth did not solve everything. Caleb talks about churn increasing and the need to focus on onboarding, product value, telemetry, analytics, and understanding why users cancel.

That is where many SaaS stories become more useful. Acquisition is only half the system. A recurring product eventually hits a churn ceiling unless the team improves activation, onboarding, feature fit, and expansion paths.

Post For Me started with a low entry price and later guided users toward higher plans. That is a classic SaaS motion: start accessible, learn who gets value, then build expansion around the users who need more volume or capability.

The Stack

Caleb's stack is worth spelling out because it is the opposite of fantasy founder tooling. It is the stack of a small team trying to ship, charge, measure, and not lose the code.

The exact stack matters less than the workflow: ship, listen, log, publish, measure, improve. But the stack Caleb shared is a good example of the minimum serious SaaS skeleton: code in GitHub, deploy on Vercel, charge with Stripe, measure with PostHog, keep the UI clean with shadcn/ui, and use a real API layer when the product itself is API-driven.

The SaaS Playbook

Here is the practical version of the Post For Me playbook:

1. Pick a pain you understand. Personal experience creates better product judgment.
2. Launch the smallest useful version. Avoid waiting for the perfect SaaS architecture.
3. Do manual support early. You need customer language more than automation at the start.
4. Turn repeated questions into articles. Every good support question is a possible acquisition asset.
5. Share progress credibly. MRR, users, shipped features, lessons, failures, and churn work can all become proof.
6. Measure activation and churn. Growth without retention is a leaky bucket.
7. Use AI after you understand the manual process. Caleb's team wrote manually, learned the pattern, then used AI to speed up the repeatable parts.

Sources

• Chris Koerner interview with Caleb Panza
• The Koerner Office podcast episode #312
• The Koerner Office podcast
• TKOPOD newsletter
• TKOwners community
• Chris Koerner website
• Lazybooks
• Caleb Panza on X
• Caleb Panza on LinkedIn
• Post For Me
• Post For Me API docs
• Post For Me blog and resources
• Post For Me GitHub repo
• Day Moon Development
• Day Moon Development: Caleb Panza profile
• Linear
• NotebookLM
• Unkey
• React Router
• shadcn/ui
• Stripe
• PostHog
• Vercel
• GitHub
• GitHub Docs: About Git