866 Visitors, 15 Checkout Redirects, 0 Sales: What I Changed

I maintain several small SaaS products. Recently, one of them looked healthy from a distance: people were arriving, creating videos, hitting the paywall, and opening checkout.

It still produced zero sales.

Here is the rolling seven-day funnel snapshot I pulled from PostHog on August 15, 2026 for StoryShort:

• 866 unique visitors
• 193 people started creating a video
• 225 people saw the paywall
• 18 people started checkout
• 15 people were redirected to the hosted payment page
• 0 completed purchases reported

This was not a theoretical teardown. I followed the same path in production, created a checkout, and verified that the hosted payment page loaded with the advertised first-month price.

The app-to-checkout handoff worked. The evidence did not tell me whether buyers rejected the offer, hit payment-provider friction, or abandoned for another reason.

The product was not being rejected at the top of the funnel

A zero-sales week makes every part of a product feel broken. The data narrowed the problem.

Visitors were willing to try the product. Almost one in four started creating a video. Fifteen people had enough intent to leave the app for checkout.

The sharpest measurable drop happened after checkout opened.

That left two hypotheses worth testing. The first was offer mismatch: people came to finish one video, while the checkout sold a recurring content workflow. The second was payment friction after the hosted page opened.

The funnel alone could not distinguish them. Until provider-confirmed orders appear, I treat the product as blocked at the offer/payment handoff and do not buy more traffic for it.

That is not a traffic-acquisition problem yet.

A smaller product showed the opposite signal

In the same snapshot, RemixViral had roughly 70 visitors and two people reached checkout. The payment ledger separately showed two recent buyers. I cannot prove the analytics users and buyers were the same people, so I do not report that as an identity-matched conversion rate.

That sample is too small to declare a durable conversion rate. It is large enough to show an important contrast:

More traffic did not create more revenue. The smaller funnel at least produced provider-confirmed cash, so it deserved buyer interviews before more acquisition spend.

The wrong reaction would be to buy another thousand visits for the zero-converting funnel. The useful reaction is to understand the two buyers, preserve the message that moved them, and fix the offer shown to everyone else.

What I changed

I stopped treating a portfolio of products as a portfolio of equal priorities.

For this sales cycle, ShipFast is the single offer.

The product is a Next.js SaaS starter, but that is not the outcome I lead with. The outcome is:

Launch a paid SaaS this week without rebuilding authentication, billing, email, admin, AI, and tests.

The founding offer is intentionally simple:

• $149 once, not another monthly subscription
• The production-ready source code
• Unlimited personal, client, and commercial projects
• Lifetime product updates
• A 14-day refund window
• One implementation setup review for orders completed by August 20, 2026 at 23:59 ICT

The first 20 completed orders receive the $149 founding price. After that, the price is $199. Both limits are explicit and tied to things I can actually honor; there is no invented activity feed or fake customer count.

The seven-day distribution reset

This is the operating plan I am using before spending on ads.

Day 1: Instrument the money path

Track page views, the primary CTA, checkout handoff, and completed purchases separately. A click is not a sale, but without the click event it is impossible to tell whether the landing page or checkout is losing the buyer.

Day 2: Write one outcome sentence

Remove the feature list from the first draft. Finish this sentence instead:

After buying this, the customer can ________ without ________.

For ShipFast: launch a paid SaaS this week without rebuilding the same infrastructure.

Day 3: Show proof that exists today

Use evidence a buyer can inspect. ShipFast currently has production documentation, a live checkout, more than 240 automated tests, and the same foundations used across a real product portfolio.

Do not wait for a large revenue screenshot. Do not invent one either.

Day 4: Publish one source-of-truth article

Write the full argument once. Turn that article into shorter posts, answers, and videos rather than creating disconnected content for every channel.

This article is that source for ShipFast.

Day 5: Record the shortest useful tutorial

Show one complete result: clone, configure, run, and open the paid SaaS flow. The tutorial should sit close to the job the buyer wants, not tour every component in the repository.

Day 6: Send 20 specific founder audits

Contact founders who are visibly building a Next.js SaaS. Mention one concrete launch gap, explain how it affects getting paid, and link to the relevant proof. No generic "love what you are building" opener and no bulk blast.

Day 7: Review conversations, not impressions

The first weekly scoreboard is:

• Qualified replies
• Product questions
• Purchase-intent clicks
• Hosted checkout visits
• Completed orders

Likes are useful only when they create one of those downstream signals.

The ad budget is zero until the offer earns it

Paid traffic should amplify a message that has already closed real buyers.

My threshold before a first paid test is either five manual sales, or at least one sale within ten qualified checkout visits from the same audience and message. Then the first experiment is capped at $100 total over five days.

At a $149 one-time price, that budget is large enough to reveal obvious mismatch without pretending it proves scalable acquisition. If it produces clicks but no qualified conversations or checkout intent, the campaign stops and the message changes.

The practical lesson

Software still matters. It is simply not the sentence the customer buys.

The customer buys the shorter path to a result, confidence that the path works, and an offer that fits the job they are trying to finish right now.

That is the reset: one product, one outcome, one measurable CTA, and one week of direct distribution before adding spend.

See the ShipFast founding offer and live checkout