Founder Note: Why ImgKit Archived the Builder Case Study Offer

ImgKit almost sold desktop software first.

That was the obvious path on paper. The product had free browser image tools, local batch workflows, a protected download system, and an Electron desktop app. A paid desktop app sounded like the natural next step.

But when I looked at the real buyer promise, it felt too early.

The Desktop App Is Real, But The Case Study Is The Product

The ImgKit desktop app exists to prove local image workflows:

• batch conversion;
• target-size compression;
• local background removal;
• reports for handoff;
• source files staying on the user’s machine.

That is useful work. But useful early software is not the same thing as a product I should sell broadly.

A paid desktop app creates expectations around signing, installation trust, updates, support, compatibility, bug fixes, and long-term maintenance. Those expectations are fair. If someone pays for software, they should feel confident installing it and relying on it.

ImgKit was not ready to make that promise yet.

The Temptation To Overpackage

It would have been easy to dress the app up as more mature than it was. A nicer landing page, a stronger pricing table, a few confident claims, and the product might have looked ready.

That would have been the wrong kind of launch.

The honest story is more useful: the desktop app helped validate the workflow, but the first public paid product should be something I can deliver clearly today.

The Build Process Was Already Valuable

While the software was still maturing, the build process had become a real asset.

ImgKit now had a working path through:

1. Astro content and product pages.
2. Browser-side image tools.
3. Supabase login and access state.
4. Stripe checkout foundations.
5. Cloudflare Functions and R2 protected downloads.
6. Electron desktop app packaging lessons.
7. Codex-assisted development, review, and product iteration.
8. A pricing pivot from software sales to paid education.

That path is valuable to builders because it shows the middle of a product, not only the polished screenshot at the end.

So The First Paid Product Changed

Instead of selling the desktop app as the first public paid product, ImgKit briefly launched the Builder Case Study.

It was a source-code and tutorial package for builders who wanted to study how the product was made. It included the source snapshot, written modules, setup notes, AI workflow notes, launch decisions, and protected delivery flow.

That was a cleaner promise at the time.

The buyer was not buying a finished signed app. The buyer was buying the build record behind a real MVP.

This Is Not A Polished Theory Course

The point is not to pretend ImgKit is a perfect template.

The point is to show decisions in context:

• why the public tools came first;
• why protected downloads were built before broad checkout;
• why subscriptions were paused;
• why the desktop app stayed behind the case study;
• why the build process became the first paid asset;
• how AI coding helped without replacing product judgment.

That kind of material is hard to capture after a project becomes polished. The messy middle is the useful part.

The Rule I Am Using

Sell the part that is already valuable.

Do not sell the part that still needs trust, support, or maturity you cannot honestly provide yet.

For ImgKit, that means the desktop app can mature carefully while the active paid path stays focused on Gift Studio.

That is a cleaner current offer: smaller, clearer, and more useful to the right buyer.

Archived Case Study

If you are building with AI assistance, working on a small SaaS, testing a desktop app, or thinking about selling source-code education before your software is fully mature, the archived ImgKit Builder Case Study page shows the thinking behind this pivot. It is no longer sold.

Häufige Fragen

Why not sell the desktop app first?

The app is useful, but public paid desktop software needs signing, update confidence, support docs, and stronger buyer trust. ImgKit tested the build-process angle first, then retired it as a standalone offer.

Is the Builder Case Study a course?

It was not a polished theory course. The archived page now documents the source-code case study direction without offering checkout.

Will ImgKit sell software later?

Possibly. The desktop app can mature carefully while ImgKit focuses current paid energy on Gift Studio.