The Process Is An Heirloom, Too
Ours is an industry of multi-generational companies, and you can tell. Not only from the names over the doors, or the photographs in the office hallway — the founder at the bench, the next generation at the same bench. You can tell from the processes. They haven't changed in generations either.
The ledger became a spreadsheet. The telex became a fax, and the fax became an email with the same document attached. The notebook where a salesman kept everything he knew about his buyers became a newer notebook. Somewhere along the way the tools were electrified, but the process underneath them was inherited intact: the spec re-typed at every border it crosses, the quote requested by phone and chased by email, the proposal assembled by hand from the freshest version anyone can find. We modernized the surfaces. We inherited the structure.
I want to be careful here, because this is not a lecture about seriousness. Nobody needs to tell this trade to take itself seriously; we do that plenty. We take the craft seriously — the apprenticeships, the grading discipline, a floor specification held across ninety stones and three suppliers, a pricing grid negotiated over years and honored to the line. We take the relationships seriously, tending them across decades and handing them down like the business itself. That reverence built everything we have.
But a family firm passes down two kinds of things: the craft, and the back office. We have treated them with the same reverence, and they deserve opposite treatment. Inherited craft is an asset — it compounds. An inherited process is a cost — and it compounds too, quietly, every year, in hours.
Why did the process escape the scrutiny we apply to everything else? Partly identity: in a heritage business, "the way we've always done it" is nearly a virtue. Continuity is the brand, and it is hard to revere continuity in the showroom while questioning it in the back office. And partly because software never earned a seat at our table. The generic CRM has no field for a memo — no way to hold the idea that goods can be out of the vault, in a customer's hands, and still ours. The project tool thinks a diamond is an attachment. The accounting package can book the invoice, but it has no idea the stones on it were specified as minimum floors, or that half the parcel might come back. Every one of those tools asked the trade to translate itself into someone else's vocabulary, and the trade, sensibly, declined. The refusal looked like tradition. It was actually good judgment about bad options.
So the work runs the way it has always run. A salesperson comes back from a customer meeting having done the hard part — the relationship, the read on what the buyer wants — and begins the second shift: transcribing, re-keying, chasing. A quote takes nine days and four emails, most of them spent decoding the request. A proposal goes out assembled from version twelve of the spreadsheet, and someone discovers later which line carried last month's rate. And the deepest knowledge in the company — which buyer will never touch yellow gold, what was promised in March — lives in one person's memory. In a multi-generational business, that last one should worry us most. A name over the door transfers cleanly. Memory doesn't.
None of this shows up on a P&L as a line item. It shows up as cycle time, and cycle time is money: the collection that took eleven weeks instead of seven, the proposal that landed after the buyer's open-to-buy had closed. It shows up as errors, and errors are margin. Mostly it shows up as a ceiling — every additional collection multiplies the re-keying, the chasing, and the reconciling right along with the revenue, so the capacity of a good team quietly caps the size of the business.
And the next generation is watching. The chains consolidate and expect faster turns. Buyers reward the supplier who has it together. The daughters and sons coming into these firms look at the second shift and ask a fair question: why is this part of the inheritance? The companies that keep the craft and replace the process will out-cycle the ones that inherit both — same taste, same relationships, more collections, fewer errors, faster answers. Taking the work as seriously as we take the legacy is not a betrayal of the legacy. It is how the legacy gets a fourth generation.
What would it take? Not another generic tool wearing a jewelry-themed coat of paint — we have declined those before, and we were right to. A system would have to speak the language natively: floors and exact stones, memo, per-customer grids, the quote that crosses a company boundary without either side showing its hand. It would have to treat discretion as architecture, not as a permissions checkbox. And it would have to hold the whole path in one place, so that a collection travels from a salesperson's meeting notes to a priced proposal in a retail buyer's hands without being re-typed at every crossing. Everything that used to be re-keying, email chains, and spreadsheet archaeology — in one place.
I spent twenty-three years inside this trade, in companies exactly like these, doing the work I came for and a great deal of the work that came with it. I built LinkStudio because I believe the distinction matters: the craft deserves to be inherited. The process deserved to be retired.
If you run one of these companies and this reads like your own hallway, I would like to hear from you. The early-access list is one sentence and one field, and it is where this begins.
-Lindsey
