Contact
12345
1 Learn the work2 Try a version3 Run it for two weeks4 Roll it out5 Train your team

ERP and PLM systems, built next to the people who use them.

Moving a business off spreadsheets and onto an ERP or PLM is a big decision, and it changes how whole departments work.

People rarely know what they need until they have something real to try. So instead of agreeing on everything up front, we build while we talk, and your team tries out different versions on the spot. Our aim isn’t to get everything perfect first time around – it’s to build something reliable that gets better as people use it.

Clients

Sourgrape / Belmont, our first client, has run on our system since 2019. Since then, all our clients have come to us by recommendation.

2024–
Phoebe PhiloOne ERP across 14 departments, from development and compliance to warehouse QC and finance.
2022
PritchBespoke outfits for private clients. A CRM that connects sales and making, with live costing.
2021
Sharp CutSample studio. Development, seamstress allocation, inventory and delivery notes.
2020
Albion KnittingLuxury knitwear manufacturer. Materials, yarn stock, purchasing and production planning.
2019
Sourgrape / BelmontLuxury CMT factory, London. From a clipboard to live work-in-progress, costing, purchasing, scheduling and despatch.

What we do

Building practical tools that help a business move faster, cut waste or improve quality.

01
Process discoveryUnderstanding how people actually work, before anything gets built.
02
Operational problem-solvingFinding the bottlenecks, the double entry and the things that get lost in handoffs.
03
Rapid low-code prototypingTrying several versions of a workflow in an afternoon, then keeping the one that works.
MoneySystemsPeople Whereto start Cost Time it takes Moving the old data Being locked in What to look for Getting the teamon board How to maintain Risk of implementation Touches all of them
Some of the questions floating around your head Money Systems People Risk, across all of them
A free hour with us

Where to start

Not every spreadsheet needs replacing. But once one becomes the way several departments talk to each other, it ends up doing a job it was never built for. That’s usually when people start looking at software.

So how do you begin? It helps to know which problems a system has to solve, in what order, and what can stay as it is. In a free hour with us, you’ll get an outside view of where to begin, the mistakes we see most often, and the ones we wish we hadn’t made ourselves. Whatever you decide afterwards, and whoever you choose, you’ll go in with your eyes open.

To book, write a few lines about the spreadsheet you rely on most: which teams use it, and what goes wrong with it most often. There’s no need to send files or anything confidential.

  • You may or may not need to move off spreadsheets. If you think you do, it’s worth knowing that a new system takes time to build. The first version usually takes two to six months, which is quick for this kind of work, and from there it grows one department at a time. If you’re looking for a quick fix, we’re probably not the right people to ask.
  • If you’d like an NDA in place first, just let us know.
  • We hold two of these a week, one per company.