Behind the Scenes: How I Built the Batch Run Planner (and What I Cut)
The design decisions behind our most popular template — and why I removed half the features I originally built.
When I first started designing the Batch Run Planner, I made the classic mistake: I built it for the maker I thought I was, not the maker I actually am. I added capacity tracking, cost-per-unit formulas, supplier databases, and a whole dashboard with charts. It was impressive. It was also unusable at 11pm when I was trying to figure out how many candle tins to order.
This is the story of what I cut and why — and what the final template actually does.
The original version had 14 properties. The final has 7.
My first draft of the batch database had fields for batch ID, date started, date completed, product type, quantity planned, quantity produced, quantity failed, unit cost, total cost, supplier, cure time, packaging status, and notes. It looked thorough. But when I tested it on my own batch of 40 soy candles, I realized I was spending more time filling out fields than actually pouring wax. Half the fields were things I'd never look at again.
The final version keeps: batch name, product, quantity planned, quantity produced, start date, status, and notes. That's it. The cost tracking lives in a separate pricing calculator where it belongs. The supplier info lives in inventory. Each template does one job.
I killed the charts.
I love a good dashboard, but charts in Notion are slow to load and rarely actionable for a solo maker. A bar chart of "batches per month" doesn't help me decide what to make next week. What does help is a simple filtered view: "batches in progress" and "batches planned but not started." Those two views answer the only questions I actually have on a Monday morning.
The status field does more work than any formula.
If there's one design principle in every template I build, it's this: the status field is the engine. For batches, my statuses are Planned, Materials Ordered, In Production, Curing, Ready, and Done. Each status implies a next action. When a batch is in "Materials Ordered," I know I'm waiting on a delivery. When it's "Curing," I know I can't touch it for 48 hours. The status field is a checklist disguised as a dropdown.
I added a "restock trigger" field after a failed market.
I did a holiday market last December and sold out of my most popular mug in the first two hours. I had no plan for restocking mid-market because I hadn't tracked how many I needed to bring. After that, I added a simple number property: "restock trigger" — the quantity at which I need to start a new batch. For that mug, it's 12. When inventory drops below 12, a new batch gets planned automatically. It's a small field, but it's the difference between scrambling and being ready.
The template ships with example data, not empty.
Every template I sell comes pre-filled with three example batches — a candle batch, a ceramics batch, and a fiber batch — so you can see how it's meant to be used before you enter your own data. I found that empty templates are intimidating. Seeing a filled-out example makes the system click faster.
What I'd still like to add (and why I haven't).
I've considered adding a simple production calendar view, but Notion's calendar views are clunky on mobile. I've considered integrating with a time tracker, but most makers I've talked to don't track time per batch — they track it per product type. I've learned to resist features that sound good in theory but add friction in practice.
The Batch Run Planner is available now, and it comes with lifetime updates. If you buy it and find a missing field that would genuinely help your workflow, email me. I read every message, and several of the features in the current version came directly from customer suggestions.
