Insight

How EatCookJoy scaled to $1M ARR with zero marketing

EatCookJoy—the chef marketplace founded by Zainab Ghadiyali—was running on spreadsheets, manual coordination, and a brittle codebase no one fully owned. This is a grounded, non-speculative look at how the team hardened the platform, automated the manual work, rebuilt the bookings flow, shipped a white-label offering, and crossed $1M ARR in seven months with effectively zero marketing spend.

Written by Aravind Srinivas, Former Head of Engineering at PyjamaHR, early engineer at Rupa Health (acquired by Fullscript), and Founder & CEO of HyperNest Labs. This article reflects public information and operator perspective—no speculation on confidential details.

Table of contents

The bottleneck: a business held together by hand

EatCookJoy had built real demand: private chefs and clients wanted the marketplace. But the operational backbone was spreadsheets, manual text-message coordination, and a patchwork of no-code tools that broke whenever volume spiked. The ops team was spending more than 40 hours a week confirming availability, sending booking confirmations, and reconciling payments by hand.

Underneath the operations sat a brittle, unowned codebase. Booking logic, payments, and ad-hoc automations were tangled together, so every change risked breaking something else—and there was no path to offering the product as a white-label platform to partners. The goal was not just to clean things up, but to build a system that could sustain national scale.

Rebuilding the marketplace: what changed under the hood

  • Taking ownership of the codebase and establishing clean boundaries between booking, payments, and automations so the team could ship without fear of breaking something else.
  • Replacing brittle, spreadsheet-driven workflows with durable booking, payouts, and scheduling systems—and automating the manual ops work that had eaten 40+ hours a week.
  • Rebuilding the bookings flow around real-time chef availability, so matches confirmed instantly instead of through a human texting chefs and waiting for replies.
  • Shipping a white-label offering: the platform was parameterized for theming, per-tenant fees, and provisioning so partners could run their own branded chef marketplaces without a code change.
  • Wiring analytics and observability into every critical surface so issues showed up in dashboards, not in support queues.

HyperNest's role was to act as fractional CTO for the marketplace: take the existing system, make it solid, automate the manual work, and turn internal tooling into a product the business could grow on.

The growth curve: $550K ARR → $1M ARR with no paid marketing

As Zainab has highlighted publicly, EatCookJoy went from roughly $550K ARR in five months to crossing $1M ARR in seven months—all while in beta and without paid marketing. That growth came from execution, community, and a product that made it easier for chefs to earn more while working fewer hours.

Technically, that looked like: faster booking flows, reliable payouts, a maintainable codebase the team could keep shipping on, and a white-label platform that opened a new line of business. The engineering work supported a narrative where AI runs behind the scenes and humans stay at the center.

Playbook for founders scaling a manual marketplace

  • Take ownership of the codebase early: establish clean boundaries so changes stop being scary and the team can move fast.
  • Bring in operators who can both automate today's manual work and architect for tomorrow's scale; this is where a fractional CTO for startups changes the trajectory.
  • Turn internal tooling into a product: a white-label layer can open an entirely new line of business from work you've already done.

For a more structured breakdown of the engagement, see the EatCookJoy case study or talk with us about fractional CTO support for your own marketplace.

Related reading