Built where we stand.

Puget Bindery has been making books in the Seattle area since 1919. Saddle stitching, perfect binding, folding, coating — the trade work that happens after the press and before the reader. Until recently, our software looked like a lot of shops our size: a green-screen system from the nineties, spreadsheets around the edges, and too much of the business living in the heads of the people who'd been here longest.

I own the bindery. I also write software. For years I did what every shop owner does — I went shopping. The serious ERP path turned into a six-figure project once implementation, cleanup, training, and the person to keep it fed were counted. The smaller tools each solved one room of the building: a quoting tool here, a scheduling app there, accounting in its own world. None of them talked, and every gap between them was someone retyping a job they'd already typed.

So I built where I stood — not a product at first, just the system our shop needed, tested every morning against incoming RFQs, that day's run list, and a floor that has no patience for software that slows it down. Today it handles quoting, job tickets, production scheduling, and job costing at Puget Bindery, carrying thirty-four years of imported shop records — over a hundred thousand quotes — while we finish cutting over from the old system for good.

The expensive question in a job shop isn't "did we ship it?" — it's "did we make money shipping it, and what should we charge next time?"

What closed-loop actually means

Most shop software is an open loop: quotes go out, jobs get done, and whether any of it was priced right gets discovered at year-end, in aggregate, too late to change anything. Plyworks closes the loop on every job. The RFQ becomes the quote becomes the ticket becomes the schedule becomes the shipment becomes the cost report — one record, never retyped — and the cost report teaches the next quote. When a customer asks for the same booklet next spring, the draft opens with what you charged, what it actually cost, and what margin you made. Pricing becomes a record you can argue with, not a guess you have to defend from memory.

Why pilots, not signups

One shop runs this today: ours. That means the proof is deep, not broad — we know it works under the pressure of one real floor. I don't yet know which parts transfer cleanly to every kind of job shop, and I'm not going to pretend otherwise. That's what the pilots are for: find the common spine, adapt the shop-specific edges, and prove the loop outside our building before we sell it like finished software.

So we're taking five pilot shops, not five hundred signups. You bring your real quotes and your real chaos; we onboard with you and shape the spine around how your shop actually runs. You leave with a working system shaped around your jobs — and we leave knowing what belongs in the product instead of guessing from demos.

If you quote custom work, run a floor, and ship physical things — and you're tired of being the integration layer between your own tools — fill out a ticket.

— Ron Diver
Puget Bindery · Plyworks · Kent, Washington