Skip to content
Build in Public

A new pricing page and 57 commits

Starter, Host+, Studio. Three tiers, a coupon system, and the kind of day where you forget to eat.

SD
Shubham Datarkar
· 3 min read
Updated

Fifty-seven commits today. I counted because git counted. That's not a brag -- it's a shape. It's what a day looks like when three different things need to be true by the end of it and none of them are small. Today was pricing, infrastructure, and the beginning of metrics. None of them could wait.

The pricing page -- the sixth rewrite, if you count the five from before launch. But this one's different because it's not just cosmetic. The model itself changed. What was a simple free/paid split is now three tiers: Starter (free, capped), Host+ (the working professional), and Studio (multi-staff, teams). Each tier has its own ceiling, its own unlock, its own answer to "why would I pay for this?"

Why three tiers now

Because real traffic taught me something the prototype couldn't: people arrive with wildly different scales. Yukta needs one calendar and a few services. Mukesh needs multiple staff members managing different rooms. A coaching collective needs team features, shared branding, a unified presence. One price for all three is either too expensive for Yukta or too cheap for the collective. Three tiers, each honestly scoped, each carrying its own weight.

Alongside it: a coupon system. Not discounts-as-marketing -- coupons as tools. An early adopter who helped me find bugs deserves a month free. A host migrating from the PHP version deserves a smooth transition without paying twice. Coupons are how I honour specific debts to specific people without making the pricing page lie about what things cost.

Redis and the speed problem

The other big piece: a Redis read-cache layer. The product was getting slower as traffic grew. Not dramatically, not broken, but that creeping latency that makes everything feel slightly heavier than it should. Database queries that were fine at ten users start to drag at a hundred. Redis sits in front of the expensive reads and serves them from memory -- the database does the hard work once, Redis remembers the answer for the next fifty requests. Pages that took 800ms now take 120ms. Nobody notices fast. Everyone notices slow.

North Star metrics

And the third thread, the one that ties the day together: I defined the metrics that actually matter. GMV -- gross merchandise value, the total money flowing through the platform. And host activation rate -- the percentage of signups that make it to their first real booking. Not vanity numbers. Not "page views" or "signups." The two numbers that tell me whether real money is moving and whether real hosts are succeeding. Everything else is decoration.

Fifty-seven commits. I forgot to eat until 9 PM. Some days the work doesn't come in a steady rhythm -- it comes in a flood, and you either ride it or drown in half-finished things. Today I rode it. Tomorrow my wrists will remind me that was a choice.

by Shubham DatarkarBuild in Public

Reactions

How was this article?

Newsletter

Never miss the next one

Get the latest playbooks, build logs, and the occasional unpublished idea straight to your inbox. One signal a week — no noise.