Riggwell

Ship's papers

The manifest.

Plain answers to the questions a careful buyer asks, including the ones that start with “why wouldn't I just…”. We'd rather you find the edges here than after you've come aboard.

Why not just get an ERP?

An ERP wants to become your system of record. That means a migration, a new data model to learn, and a good year of somebody's life. Between roughly $500K and $10M in revenue you're in an awkward gap: too complex to run on nothing, too small to justify NetSuite's bill or its implementation.

Riggwell doesn't ask you to move house. Your books stay in QuickBooks, your mail stays in your mailbox, and the crew works the lines between them. If you do outgrow us into a real ERP one day, you leave with your ledger intact. It was never ours to hold.

Why not Cin7, Katana, or one of the light inventory systems?

They're good at what they do, and we mean that. If what you need is a dedicated inventory system of record, buy one, and we'll connect to it. Some of them have strong demand forecasting that we have no intention of trying to out-model.

What they don't do is read your inbox. The work that eats your week usually lives in the supplier email with revised terms, the confirmation that doesn't match the purchase order, the reconciliation nobody has time for, not in the inventory table. An inventory system has no reason to go looking there. We do.

Why not Doss?

Doss is building the adaptive ERP, a better system of record aimed at people who are ready to run their operations inside a new platform. If that's you, they're the better fit.

We're making close to the opposite bet: that most businesses our size don't want another platform to live in, and that the pain isn't the absence of a system so much as the absence of anyone to work it. Doss replaces the system. Riggwell staffs the one you've got.

Why not just point Claude or ChatGPT at my email?

If you already know how to connect a model to your mailbox, write your own prompts, and keep the context organised enough that you trust what comes back, you can do a fair amount of this yourself. Plenty of sharp operators do exactly that, and we'd never tell them otherwise.

Riggwell is for everyone else: one button per account, a crew that already knows what a purchase order is, and a memory that builds itself instead of one you have to feed. The difference is posture, too. A chat window answers when spoken to. A crew works the routine on schedule and brings you the paperwork.

Why not Zapier, or the automation rules in the tools I already have?

Rules are exact, and they're blind. “When stock drops below 1,000, draft a purchase order” works right up until the supplier writes to say the price moved, the lead time slipped, or the container came up short. A rule can't read that email. It will cheerfully order the wrong quantity at last year's price.

The crew reads what came in, works out what changed, and shows you the proposal with its reasoning before anything happens. Rules do what you told them a year ago. A crew notices.

Why not a spreadsheet, or a part-time bookkeeper?

Because you already have both, and that's rather the point. The spreadsheet is where your business runs, kept up by hand, usually yours, late at night. Riggwell doesn't ask you to abandon it; it takes over the keeping of it, and shows you the tables it keeps.

And where a bookkeeper closes your month several weeks after the fact, the crew keeps the entries square as they happen, then hands them to you, or to your bookkeeper, already sorted.

Where does my data actually live?

Where it lives now. Your books stay in QuickBooks, your mail stays in your mailbox; Riggwell reads and writes through connections you can cut at any time.

What Riggwell keeps is the ship's log: the structured record of suppliers, SKUs, terms, costs and stock that it learns along the way. That's kept in plain tables you can open, sort and export, and every row carries a note saying where it came from: which email, which sync, which answer you gave. There is no filing cabinet you aren't allowed to look inside. If a fact can't say where it came from, it isn't allowed to drive a financial action.

Does it do things without asking me?

Not until you say so, and never all at once. Every routine starts in shadow mode, watching only and showing you what it would have done. When you've seen enough, you promote it to drafting, and its proposals land in your approval queue. Promote it again and it stands its own watch on schedule.

Anything irreversible (money leaving, mail going to a customer, an entry posted to your books) waits for your stamp regardless of how much trust a routine has earned. Trust is granted per routine, by you, and it can be taken back the same way.

What if it gets something wrong?

It will, sooner or later. That's why the approval queue exists, and why the risky half of the work is deliberately not left to judgment. The crew interprets (reading a supplier's email into a structured quote) and proposes; the arithmetic that follows (a reorder quantity, a balanced journal entry) is computed by ordinary, testable code, not guessed at.

Every action carries its sources, so you can check the reasoning before you stamp it rather than discovering it a month later.

I run a service business, not a goods business. Is this for me?

Most of Riggwell isn't about inventory at all. The mail, the books, the routines, the approval queue and the log work much the same whether you ship pallets or hours.

But we're starting with businesses that move real goods, because that's where the back-office pain is sharpest and where a single catch (one stockout avoided, one mispriced container caught) pays for the year. We'd rather be good for one kind of business than passable for all of them. If you run a service business and this sounds like your week, leave your address and say so. You'll be first when we cast off in that direction.

Plain dealing

What Riggwell is not.

Every product's marketing page tells you what it is. Here's the other half, so you can rule us out quickly if we're wrong for you.