The gap after Artisan: when the hobby becomes a roastery

There's a moment almost every commercial roaster remembers. It isn't first crack on the first sample roast, and it isn't the first wholesale order. It's the Sunday night you find yourself with a spreadsheet open in one window, a folder of .alog files in another, and a legal pad covered in arrows — trying to work out whether you have enough of the Colombian to cover next week, and whether the batch that tasted off on Thursday was the green or the gas.

That's the gap. This post is about why it exists and why the software industry has mostly ignored it.

Artisan deserves its reputation

Let's start with credit where it's due, because the roasting community is rightly protective of Artisan. It's free, it's open-source, and at the thing it does — live roast logging and curve visualization — it's genuinely excellent. Bean temp, environment temp, rate of rise, event markers, development time ratio: it captures the roast with a fidelity that commercial products have spent years trying to match. Hobbyists trust it. Professionals keep using it years into running real businesses.

But Artisan is, by design, a local logging tool. It knows everything about the roast in front of you and nothing about your roastery. It doesn't know how much green you have left. It doesn't know that your house blend has three components and one of them is six roasts from empty. It doesn't know that Fern Cafe's order needs four days of rest before it ships Thursday. It doesn't compare this morning's Ethiopia to the last ten — you do that, by eyeballing overlaid curves and remembering.

None of that is a flaw. It's a scope decision, and a reasonable one. The problem is what's on the other side of that scope line when roasting becomes your livelihood.

The day the job changes

Somewhere between a few hundred pounds a year and a few thousand, the job quietly changes underneath you. Roasting — the part you learned, the part you love, the part Artisan handles — becomes maybe a third of the work. The rest is a different discipline entirely:

• Green buying. Not "do I have coffee" but "when does this lot run out at my actual production pace, and how long does a replacement take to land from this importer?" Get that wrong in one direction and you're air-freighting green at a panic premium. Get it wrong in the other and cash is sleeping in bags you won't roast for eight months.
• Blend continuity. Your flagship blend is a promise to your customers, and its components are lots that end. Every changeover is a small crisis managed by taste memory and trial batches.
• Production planning. Orders, subscriptions, machine capacity, rest windows, delivery days — a constraint problem you're solving on a whiteboard.
• Quality records. Cuppings scribbled in a notebook that never quite make it into anything you can trend.

The tooling for all of this exists — one tier up.

The enterprise ceiling

Cropster is the name everyone knows, and it's genuinely complete: inventory, blends, planning, QC, reporting. It's also priced and shaped for operations far larger than a two-person roastery. The forms assume a lab. The workflow assumes staff. And the pricing model — this is the part that grates — scales with per-machine volume tiers. Roast more, pay more. The software bill punishes exactly the growth you're trying to fund.

So the graduating Artisan user looks up and sees a ceiling they can't justify, looks down at a logger that's finished its job, and settles into the gap: Artisan at the machine, spreadsheets for inventory, a whiteboard for the schedule, a notebook at the cupping table, and Sunday nights with the legal pad.

We think that gap is where most of the interesting small roasteries in North America actually live — somewhere between five thousand and a hundred and fifty thousand pounds a year, one to three people who roast, no one whose job is data entry.

What the gap actually needs

Not a smaller Cropster. The forms-and-fields model doesn't shrink well — a two-person roastery doesn't need more structure, it needs fewer decisions. What the gap needs, we'd argue, is software that behaves less like a lab instrument and more like a knowledgeable colleague:

• It should ingest what you already have — your .alog files, your CSV exports — not ask you to re-key history.
• It should read the numbers so you don't have to: tell you in plain language what happened in the batch, what's drifting, what's about to run out, and what to do about it.
• It should know that inventory, blends, planning, and QC are one connected problem, because in a small roastery they are. The roast log is the inventory movement. The cupping note is the blend-planning input.
• And its pricing should not tax growth. Flat means flat.

That's the brief we set for ourselves when we built Droptime. But whatever tool you use — even if it's the spreadsheet and the legal pad — the diagnosis stands: the gap after Artisan isn't a skills problem or a discipline problem. It's a missing category. The roasters living in it deserve software built for the size they actually are, not the size a sales team wishes they were.