Shipping a digital product as a solo founder

Four things decide whether a solo digital product ships and keeps selling: one distribution channel worked long enough to produce evidence, a checkout you can see inside, a refund flow that satisfies EU law, and a handful of posts that answer what your buyer types before they buy. Everything else is optional, including most of what founders spend the first month on.

I rebuilt this site in three weeks. The old version was a Next.js app that sent every buy click to Gumroad and gave me no visibility into what happened next, which turned out to be the expensive part rather than the fee.

I want to write down the playbook while it is fresh, because the same handful of mistakes keeps showing up in other founders' Discord posts and the answers are not as complicated as we make them.

The four things you have to own end-to-end

You can outsource everything else. These four are the load-bearing pieces:

1. Distribution. One channel, repeated, until it works or until you can prove it never will.
2. Payment infrastructure you can see inside. Whatever the gateway, the steps between buy click and receipt have to be visible to you.
3. Legal and refund flow. Especially if you sell to EU customers. The EU Consumer Rights Directive Article 16(m) waiver is real and you must collect dual consent at checkout.
4. Content gravity. Three to ten posts that answer the exact questions your buyer types before they buy. Indexed by Google. Quotable by ChatGPT and Perplexity.

That is the whole list. Design polish, a mascot, podcast appearances and a founder story page are all optional. These four are not.

1. Pick one distribution channel and stay there for six weeks

Picking one distribution channel and staying there for six weeks is the whole distribution strategy a solo founder needs. The menu is short: writing, short video, long video, X, or Reddit. Two posts a week, no skipping. Six weeks of reps tells you more than any analytics dashboard can.

Most solo founders fail at distribution because they try three channels half-heartedly instead of one channel fully. The "channel" is whatever you can show up on every weekday for six weeks without burning out:

• Long-form writing on your own site, syndicated elsewhere
• Short-form video (YouTube Shorts, Reels, TikTok)
• Long-form video (YouTube tutorials, in-depth product walkthroughs)
• Writing in public on X, with a real account
• Reddit posts in 2-3 relevant subs, no spam

That is the whole menu. Pick one. The choice matters less than the consistency.

Six weeks is the test. If you cannot do six weeks of two posts a week on your chosen channel, the problem is not distribution. It is focus, and that one has to be fixed first.

After six weeks you will know whether the channel is wrong, the message is wrong, or you just need more reps. Without those six weeks you cannot know any of those things, no matter what your analytics dashboard says.

2. Payment infrastructure: see inside the checkout

The requirement is visibility rather than ownership. A marketplace redirect is the fastest route to a first sale and the slowest route to understanding why the second one did not happen, because you can see the click and the receipt and nothing in between.

A Gumroad or Lemon Squeezy redirect is fine for the first three to ten sales, because it lets you validate the price and the product without writing any code. Past that point, once you have proven there is a buyer, the redirect starts costing you:

• Money. Marketplace fees run from 5% to about 16% once processing is counted, and the full itemization is here.
• Trust. Buyers wonder why your domain bounces them to a third party with a different visual identity.
• Signal. The dashboard shows completed orders. It does not show who reached the checkout, who stalled on a field, or who reached for a wallet instead of a card. That is the half of the funnel you would actually act on.

I built my own checkout on the Iyzico Checkout Form, which takes the global card networks and adds TRY pricing, taksit and an e-invoicing path. Stripe was not an option, because it does not onboard businesses registered in Turkey. As of September 2026 that checkout is switched off and sales run through Gumroad, which is the honest ending rather than the tidy one: owning the checkout answered the visibility question and did not answer the demand question. The gateway comparison is in Stripe vs Lemon Squeezy vs Paddle vs Gumroad.

I also put the gateway behind a PaymentGateway interface in the codebase so I can add a second provider later without touching the order flow. That took half a day. The peace of mind is worth more than the half-day.

3. Legal and refund: the EU consent waiver is non-negotiable

The EU consent waiver means a buyer of digital goods keeps a 14-day refund right until the download starts, and waives it only by expressly requesting immediate access and acknowledging the loss. I collect that as two unticked checkboxes at checkout and log the consent record with every order on ToolGenX.

If you sell digital goods to a single customer in the EU or UK, your refund flow must satisfy Consumer Rights Directive 2011/83/EU Article 16(m). The plain-language version:

• Before download starts: the buyer has 14 days to cancel for any reason and get a full refund.
• After download starts: the right of withdrawal is waived, but only if the buyer expressly requested immediate access and acknowledged that they lose the right to withdraw by starting the download.

This means two separate checkboxes at checkout, both unticked by default, with the exact text logged with the buyer's IP, user-agent, and timestamp. If you cannot produce that consent record when a buyer complains, the refund window stretches from 14 days to 14 days plus one year, and the burden of proof is on you.

I built this into ToolGenX before I built the actual checkout. It is not glamorous. It is the reason a credit-card chargeback does not turn into a regulatory complaint.

There is also a newer EU mandate, in force since 19 June 2026 under Directive (EU) 2023/2673: the withdrawal button. Every order eligible for cancellation must show a clearly-labelled button in the buyer's account that one-shot triggers the refund. I built that too. It costs me nothing because it auto-checks if the buyer downloaded anything before issuing the refund.

4. Content gravity that gets cited by AI

Content gravity is a small content layer, three to ten posts, that both Google and AI search engines like ChatGPT and Perplexity can cite. The mechanism is quotable passages: 40 to 60-word self-contained answers with a number and a date. The published GEO research measured up to 40% higher AI visibility for content structured this way.

Search has bifurcated. There is the old Google ten-blue-links search, which now shares its result page with Google's AI Overviews. And there is the AI search layer, meaning ChatGPT search, Perplexity, Gemini and Bing Copilot, which quotes from a much shorter list of sites.

Both layers reward the same thing: passages that can be quoted in isolation. A 40 to 60-word self-contained answer to a question you have phrased clearly. A specific number with a date next to it. A named author with a real social profile.

The GEO paper from Princeton, Georgia Tech and IIT Delhi reports that structuring content this way boosts visibility by up to 40% in generative engine responses. The advantage is structural rather than algorithmic. You either write quotable passages or you do not.

For my site:

• Every product page has a "Quick Answer" block under the hero.
• Every blog post, including this one, has a quickAnswer field in frontmatter and a FAQPage schema block at the end.
• The author entity is a real Person with a real sameAs list pointing at LinkedIn, X, YouTube, and Medium.
• robots.txt explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and Applebot-Extended.
• A public/llms.txt file at the site root gives AI crawlers a tour of the catalog without making them parse HTML.

None of this is glamorous either. It is the SEO equivalent of putting your name on the mailbox.

The mistake that costs the most

Every item above is cheap on its own. The expensive thing is the order people do them in, and the order is almost always wrong in the same direction.

Building comes first because building is legible. You can see progress, you know when a page is done, and nobody argues with you about it. Distribution has none of those properties: you post, nothing happens, and you have no way to tell week one from week five except by continuing.

So the site gets built, then rebuilt, then polished, and the distribution work keeps getting postponed by something that feels more urgent and is not. The tell is a founder who can describe their tech stack in detail and cannot name the last five people who read anything they wrote.

For calibration: published ecommerce conversion averaged 2.23% in August 2026, and that figure is carried by returning buyers on established stores. At the rates a new shop actually sees, the arithmetic is brutal and unambiguous. You do not have a conversion problem at zero visitors. You have an audience problem wearing a conversion problem as a costume, and no amount of building addresses it.

What I would do differently if I started over

If I started ToolGenX over, I would write the three to ten cornerstone posts before building the site. Not after, not in parallel, before. The posts are the cheapest test of whether anyone cares, and the whole build gets easier once they exist.

The posts force you to articulate who the buyer is and what they are trying to do. The site comes out cleaner, the product pages write themselves from the post outlines, and the SEO surface area lives on a content base that already passed the "would a real person care" filter.

I did it the other way the first time, site first and posts later, and the result was a site full of generic SaaS copy that I had to rewrite a year later. The cost of fixing that retroactively is roughly two to three times the cost of writing the posts first.

A workable order of operations

A workable order of operations for a solo digital product launch runs roughly seven weeks: pick one channel and outline posts in week zero, ship the posts with a Gumroad checkout by week two, watch and adjust through week six, then move to your own Stripe checkout once the sales are real.

If you are starting fresh:

1. Week 0: Pick the one channel. Write three post outlines on it.
2. Week 1-2: Write the posts. Ship them to a one-page site that links to a Gumroad checkout.
3. Week 3-4: Watch the traffic. Adjust the offer. Add product two if you have signal.
4. Week 5-6: Same channel, more reps. By now you have either six sales or six weeks of evidence about why not.
5. Week 7+: If sales are real, instrument the funnel properly, which usually means moving the checkout onto your own domain. If sales are zero, change the offer, not the channel.

You do not need a new framework. You need to ship the boring version of all four pieces.

That is the playbook.

Written by İsmail Günaydın, founder of ToolGenX and ModernWebSEO. Solo software engineer and SEO strategist out of Istanbul. The thinking behind this post is implemented in the ToolGenX refund flow and product pages.