bunny.directory: Lost focus

bunny.directory was a launch directory built for indie makers to publish permanent product pages and climb daily rankings through streaks, carrots, and a builder leaderboard. It shut down because the founders lost focus polishing retention mechanics for a community that never materialized, instead of securing a compounding distribution channel to bring makers in the door.

The product mechanics: rankings, carrots, and a badge economy

The core loop centered on a daily leaderboard. Makers launched for free and kept a permanent profile page. To stay visible, they needed to show up daily — earning "carrots" (upvotes) from other builders, leaving helpful comments, and maintaining streaks that fed a builder leaderboard. The gamification was explicit: consistent activity bought homepage placement.

Monetization layered on top of this free tier. A Featured spot cost $29 for 30 days of homepage and site-wide placement; Premium cost $79 for the same duration with broader visibility. Free listings retained a dofollow backlink only while the bunny.directory badge remained embedded on the maker’s own site — a clever SEO incentive that tied the directory’s authority to the maker’s continued participation.

Technically, the stack was modern and lightweight: Next.js on the frontend, Supabase for database and auth, and Tailwind CSS for styling. The codebase reflects a team comfortable shipping polished interfaces quickly.

The traffic trap: spikes that never compounded

Every new product launch on the platform generated a traffic spike. The maker shared their page, their followers visited, and the daily active user count jumped. Then it flatlined. The directory had no organic discovery mechanism of its own — no SEO moat pulling in new makers, no viral loop where one launch begat the next, no content engine indexing the long tail of listed products.

The founders recognized the pattern: they kept shipping features for the makers already inside the room, but the door stayed locked for everyone else. Each spike was a rented audience, not an owned one. Without a channel that compounded — search, newsletter, programmatic SEO, or a partnership funnel — the business model relied entirely on the founders manually hustling each batch of launches. That doesn’t scale.

The feature trap: polishing retention before acquisition

The biggest mistake is stated plainly in the post-mortem: months were spent refining the daily ranking algorithm, streak counters, carrot mechanics, and builder leaderboard. These are retention features. They only matter if users exist to retain.

The team built a sophisticated loyalty program for a store with no foot traffic. Makers launched once, collected their backlink, and left. The streaks and carrots assumed a habit that never formed. A leaderboard is meaningless when the player count rounds to zero. The engineering effort invested in real-time ranking updates and streak persistence would have yielded higher returns if redirected toward a single, repeatable acquisition channel — even a manual one like cold outreach to 100 target makers per week.

Retention reality: gamification cannot manufacture habit

The data from their experiments is unambiguous. Makers launched once and rarely returned. The team tested every lever available inside the product: carrots as social currency, streaks as commitment devices, a public builder leaderboard as status signal. Repeat visits stayed low.

This is a common failure mode for directory and marketplace founders. They mistake the *structure* of engagement for the *cause* of engagement. Builders don’t return to a directory because a streak counter increments; they return because the directory sends them traffic, leads, or revenue. bunny.directory delivered a backlink and a moment of visibility. That is a transaction, not a habit. No amount of UI polish on the leaderboard changes the value proposition.

The strategic sequence: audience first, directory second

The lesson the founders extracted is the correct one: distribution beats features. Build the audience of makers first, then build the directory for them.

In practice, this means the first three months should have produced zero code for the directory itself. Instead, the effort should have gone into a newsletter curating interesting indie launches, a Twitter account amplifying makers daily, or a programmatic SEO play generating thousands of indexable pages for "best [category] tools for [niche]." The directory becomes the capture mechanism for an audience that already trusts the brand. Built in reverse, it is a ghost town with a polished leaderboard.

What a buyer gets

The asset package is concrete and technical. The codebase is a complete Next.js application backed by Supabase, styled with Tailwind CSS — clean, typed, and deployable on Vercel in minutes. The domain `bunny.directory` carries existing authority from the backlinks earned during operation. The database holds the historical record of every maker who launched, their pages, and the ranking history — a seeded content library that solves the cold-start problem for a relaunch. The pricing logic for Featured and Premium tiers is implemented and tested.

The primary lesson is baked into the architecture: the gamification system is there, but the distribution layer is not. A buyer acquires a high-quality engine without a fuel line. It is listed on Saasgrave and can be acquired or revived.