Schniffells, and the Build That Became Croft

Pete Carling is an artist from Exmoor. He works slowly, builds things with his hands, and gets the detail right — the kind of craft that doesn't shortcut well. He's also Max's father, and for the last year he's been doing the same thing with a different material: fresh ginger, turmeric, cassia cinnamon, black pepper, rosemary, cayenne, honey, lemon, and apple cider vinegar, infused into a botanical concentrate he calls Schniffells. Served hot or cold, brewed in small batches on the moors where he lives, sold to people who taste it once and come back asking where to get more.

A product like that doesn't need a website. It needs an operator behind it who isn't drowning in the admin that comes with actually selling something — tracking who ordered what, what's owed, what's left in stock, which batch a bottle came from if something ever needs tracing back. Pete's a brewer, not a bookkeeper. So the brief wasn't "build Pete a site." It was "build Pete a business he can run without a spreadsheet."

What went live is a full ops system sitting behind the public-facing story: a stockist finder that maps every shop and café carrying Schniffells, an order flow that turns an enquiry into a tracked sale, an Instagram content studio for the posts that actually move a small brand, and — doing the real work underneath all of it — batch logging and invoicing that runs off plain conversation. Pete doesn't fill in a form to log a brew. He says what he did, in normal words, and the system turns it into a batch record, updates what's in stock, and drafts the invoices that follow from it.

That conversational batch-and-invoice engine turned out to be the interesting part. Once it was built and working for a botanical concentrate, the pattern underneath it was obviously bigger than one product. A small-batch brewery has almost the exact same shape of problem as a botanical concentrate maker — batches instead of bottles of tonic, hops and grain instead of ginger and turmeric, but the same need to log what was made, know what's owed, and keep a stockist list without living in a spreadsheet. So does a cidery. So does a small gin distillery, or a kombucha producer, or anyone brewing something real in small enough volume that off-the-shelf software either doesn't fit or costs more than the batch is worth.

That's Croft — the platform Schniffells' backend grew into once we lifted the Pete-specific assumptions out of it. Same batch logging, same stockist management, same conversational order-and-invoice flow, but built to serve more than one producer without asking each one to compromise on how their product actually works. A brewery's batch has hop varieties and fermentation temps where Schniffells has ingredient ratios and infusion temp — different fields, same underlying discipline. Ruapehu Brewing, a craft brewery working out of Ohakune, is the next producer coming onto it, proving the platform holds up outside the product it was built for in the first place.

None of this happened because we planned a platform from day one. It happened because Pete needed a real system to run a real small-batch product, we built it properly instead of cutting corners on the admin, and the thing we built revealed a pattern worth generalising. That's usually how the good ones go — you solve one person's actual problem all the way through, and what you learn building it becomes the next thing.