I shipped five Markdown packs last week. Prices sit between $5 and $12. No ads. No launch thread storm. No waitlist. Just files on Payhip, itch.io, and a Ko-fi tip jar.
This is not a “I made $X in 7 days” post. Sales are quiet. That’s fine — I wanted distribution practice more than a vanity screenshot. Here’s what I learned, what I’d change before week 2, and one tip you can use today even if you never buy anything from me.
What I actually shipped
Five small digital downloads for indie makers and freelancers who already live in ChatGPT / Claude:
- AI Writing Brief Pack — fill-in briefs for blog, LinkedIn, landing, email
- Freelance Quote & Invoice Kit — Markdown + print-friendly HTML
- Weekly Planner Pack — Markdown/CSV that also drops into Notion
- LLM Prompt Pack: Productivity — 30+ copy-paste prompts with clear brackets
- One-Pager Resume Outline Pack — structure first, fluff second
All plain files. Personal & commercial use of the templates; no resale of the pack as-is. Nothing fancy — on purpose.
Why Markdown (and why cheap)
I write for people who already have too many SaaS tabs open. A .md file you can paste into Notion, Obsidian, or a model chat is more useful than another locked template marketplace SKU.
Cheap pricing ($5–$12) was a deliberate bet: lower guilt to try, faster feedback loop, less “is this worth it?” friction. It also forced me to keep scope tiny. If a pack needs a 20-page PDF to explain itself, I overbuilt it.
The free tip: put audience + must-avoid + CTA in every AI brief
Most vague ChatGPT / Claude outputs come from vague inputs. Before you ask a model to draft anything (blog post, landing section, client email), force yourself to fill three lines:
Audience: who this is for (role + constraint)
Must-avoid: words, claims, or tones that break trust
CTA: the single next action you want
Example for a freelance landing rewrite:
Audience: solo designers who hate writing proposals
Must-avoid: “disrupt,” fake urgency, competitor shade
CTA: book a 20-minute scope call
Then add your actual content goal. That’s it. Those three fields alone cut rewrite loops for me more than fancy prompt frameworks. (The AI Writing Brief Pack is basically that idea expanded into four reusable templates — but the three lines work without buying anything.)
What I’d change before week 2
1. Ship one public sample page sooner.
I launched with product pages and zips. I should have posted one stripped sample brief (or one invoice HTML screenshot) on day one. Trust beats feature lists for cold traffic.
2. Pick one channel and repeat.
I scattered soft mentions. Next week: one DEV.to-style lesson post (this), a few short X notes with the free tip, and stop pretending “everywhere lightly” is a strategy.
3. Measure replies, not just downloads.
With zero ads, the useful signal is “did someone say this solved a real friction?” A single thoughtful DM beats ten silent visits. I’ll ask one question in every post: What’s the last AI draft you threw away because the brief was mushy?
4. Keep packs boring on purpose.
Temptation after launch: add Notion sync, a custom GPT, a “pro” tier. Resist. Week 2 should be clearer descriptions and one free sample — not scope creep.
5. Write the README like a human, not a storefront.
Buyers skim. The first screen of each pack needs: what this is, how to use it in 60 seconds with ChatGPT/Claude, and what not to expect. I underwrote that on one pack; I’ll fix it.
Soft promo (skip if you’re here for the tip)
If you want the full packs:
- Payhip store: https://payhip.com/NobbyDigital
- itch.io: https://nobbydigital.itch.io
- Tip / support: https://ko-fi.com/nobbydigital
No countdown timers. No “only 3 left.” Files you can open in a text editor.
Closing
Week 1 taught me something simple: shipping five small things with zero ads is less about revenue math and more about whether your product language survives contact with strangers. Mine needs tighter samples and one louder free tip.
What’s the last AI draft you threw away because the brief was mushy?
Top comments (0)