For independent home bakers
CrumbCost turns the ingredient prices you actually pay into a batch cost, a cost per cookie, cake, or cupcake, and a clean customer quote. It runs in your browser — no account, no subscription, and your recipes stay on your device.
The demo opens a clearly labeled sample in a separate temporary workspace.
| Flour · 500 g of 1,000 g for ₹80 | ₹40.00 |
|---|---|
| Butter · 200 g of 500 g for ₹250 | ₹100.00 |
| Sugar · 100 g of 1,000 g for ₹50 | ₹5.00 |
| Labor · 60 min at ₹100/hour | ₹100.00 |
| Packaging + other costs | ₹55.00 |
| Batch cost | ₹300.00 |
Ingredients 48% · Labor 33% · Packaging 12% · Other 7%
Selling at ₹45: revenue ₹540.00, surplus after entered costs ₹240.00, margin after entered costs 44.44%.
Transparent sample numbers for illustration — not industry averages or pricing advice.
Step 1
Package size and price, like “Butter, 500 g for ₹250”. Optional usable yield for trimming waste.
Step 2
Amounts used, how many items you can sell, your labor time and rate, packaging, and other costs.
Step 3
See cost per item, a target-margin price, and your margin at the price you charge. Then print a clean quote.
Separate “usable yield” for ingredient waste and “sellable items” per batch, explained so you never count waste twice. Change a butter price once and every recipe using it recalculates, with the date you last updated it.
Slide a temporary ingredient price rise from 0–50% and try a different target margin. Baseline and scenario sit side by side. Only ingredient costs move, and your saved prices never change.
Copy a prompt into an AI tool you already use to structure a pasted recipe, paste the JSON back, and review every line before saving. CrumbCost makes no AI calls, and everything also works by hand.
No accounts, no analytics in the app, no cloud database. Recipes, prices, and customer names are stored only in this browser until you export them. Like any website, the host still receives normal page-request logs.
In your browser's local storage on this device. It isn't encrypted or synced, and clearing site data erases it — so download a JSON backup regularly. Anyone using the same browser profile can see it.
No. AI is an optional shortcut for typing in long recipes. CrumbCost never calls an AI service; if you choose to paste the prompt into one, that service's terms apply.
A cup of flour and a cup of sugar weigh very different amounts, so converting them would be a guess. CrumbCost supports g, kg, oz, lb, ml, L, and pieces. Weigh ingredients, or use ml for liquids. A recipe amount must use the same kind of unit as the package price.
Margin is surplus as a share of the selling price; markup is surplus as a share of cost. A ₹25 cookie sold for ₹41.67 has about a 40% margin but about a 66.7% markup. CrumbCost shows “margin after entered costs”, which is not net profit — overhead, delivery, fees, and taxes you haven't entered can reduce it.
No. There's no tax engine and quotes are not invoices. Each quote says: “Taxes, if applicable, are not calculated by this tool.”
Once the app page has loaded, all calculations run in your browser without a connection. It isn't an installable offline app.
