Story
Eight beats. One thesis.
The experience on the home page walks this narrative in 3D. Below is the same arc in plain text for decks and diligence.
Scheduled food infrastructure
The kitchen network that cooks to a calendar.
Hearthly turns demand booked in advance into fully utilised kitchen capacity and batched last-mile delivery. A structurally better margin model for prepared food.
01 · The problem
On-demand food runs on idle capacity.
Kitchens staff up for two daily peaks and sit underused the rest of the day. Couriers make one drop per trip. Commission-funded delivery leaves most operators on thin margins, with nothing to forecast against.
02 · The model
Demand, booked before the stove is lit.
Diners commit to meals one to seven days ahead. Kitchens get a firm production schedule, and Hearthly prices each delivery window to spread load evenly across the week.
03 · Logistics
One route. Many drops.
Fixed delivery windows let us plan orders into dense routes ahead of time, so each run makes many drops instead of one. Fulfilment cost per meal falls as neighbourhood density grows.
04 · The moat
Trust, engineered in layers.
Kitchen licensing and inspection, chef verification, cold-chain telemetry and verified reviews add up to a compliance stack that takes years to copy. Regulators and corporate buyers increasingly expect it.
05 · Network effects
Density compounds on both sides.
Every new kitchen adds choice within a delivery window. Every new subscriber makes routes denser and forecasts more accurate. Supply, demand and logistics strengthen each other block by block.
06 · Traction · illustrative
The metrics that matter, shown as placeholders.
These are the four numbers we will report against. The values below are illustrative placeholders, not results, and will be replaced with audited figures in the data room.
07 · The ask
Raising a $12M Series A.
Funding to grow from two launch cities to six, scale kitchen onboarding, and take the scheduling and routing engine to enterprise-grade reliability.