The zero-budget product flywheel I’m building with plain files

The zero-budget product flywheel I’m building with plain files

I’m building JERICCO as a simple product and content engine before spending money on hosting, schedulers, or storefront software. The current rule is blunt: prove the loop works first. Then upgrade the stack.

The loop looks like this:

• Find a small audience with a real problem.
• Ship a useful free resource.
• Publish a guide that explains the resource and the thinking behind it.
• Turn the guide into social-safe assets that point back to the guide.
• Watch what gets clicks, saves, replies, or signups.
• Package the useful part into a low-ticket product only when the free version has a reason to exist.

Right now the public hub is just static files on GitHub Pages: https://heishk.github.io/ophelia-reset-systems/ No paid hosting. No fancy CMS. No tracking stack. No affiliate shorteners. That limitation is useful. It forces the product to carry the weight instead of hiding weak work behind tools.

The first resources are intentionally boring:

• a 7-day home reset system
• a 30-day budget reset planner

Boring is not an insult here. Boring problems are where people spend money because they keep coming back: messy homes, leaking subscriptions, unclear routines, scattered notes, unfinished plans.

The content engine

The next layer is the content engine. For each topic, I’m using a two-phase process:

Phase 1: signal harvest

Before writing, collect the signals:

• who the audience is
• what they already want
• what words they use
• what posts get saved or shared
• what search intent exists
• what product could naturally help

The point is to avoid guessing. If the audience wants a checklist, don’t write a manifesto. If the audience wants proof, don’t give them vibes. If the audience wants relief, don’t spend five paragraphs describing the pain.

Phase 2: triple draft and ship

Draft three angles:

• the safe version, which is clear and useful
• the curiosity version, which is built for clicks and saves
• the revenue version, which has the cleanest path to a product or email signup

Then score them and ship the winner. This is slower than posting whatever comes to mind, but it creates reusable assets. A blog post can become a Pinterest pin, a checklist, a product page, an email sequence, or a paid template. That is the real goal: one good idea should produce more than one artifact.

The stack today

The stack today is deliberately small:

• GitHub Pages for the public hub
• DEV for build-in-public posts
• local scripts for packaging and publishing
• Obsidian for the operating brain
• Discord for operational logs
• KDP and digital product platforms when the account side is ready

I’ll keep adding the boring pieces: better landing pages, email capture, Pinterest assets, more useful resources, and product listings. If the system works, the paid tools come later. If it doesn’t work without paid tools, the tools were never the answer.