Good shops. Bad software.

A letter from the founder of Grainwork.

I've spent the better part of a decade inside cabinet software.

I started on the shop floor in a high-end residential shop. Since then I've worked one-on-one with cabinet shops, fixing broken setups, untangling construction standards, writing scripts, and helping teams get control of systems they already paid for but still couldn't really use.

After enough years doing that work, one thing became impossible to ignore:

Cabinet software has spent twenty-five years training shops to need somebody else.

That is the part nobody says out loud.

You buy the software.
You pay for the setup.
You pay for the training.
You pay for support.
You pay again when your shop changes.

And somehow, after all that, you still cannot fully control the most important tool in your building.

You can build a standard cabinet.

But when you need to change a construction method, add a new drawer guide, create a custom door style, adjust a report, or handle something outside the box, now you need a consultant, a script, a support ticket, or a workaround.

The features are technically there.

The control is not.

That has been accepted as normal for way too long.

A cabinetmaker should not need permission to do their own work.

A shop owner should not feel like they are renting access to their own system.

A production team should not have to depend on one power user, one reseller, one IT guy, or one consultant just to keep the software moving.

That is not ownership.

That is dependency.

And the industry got used to it.

To be fair, some of that complexity used to be unavoidable. The geometry was hard. The engineering logic was hard. CNC output was hard. The early systems were difficult because the problems were difficult.

But the world changed.

Software got better.
Hardware got better.
Cloud became normal.
Modern tools became easier to learn, easier to run, and easier to change.

Cabinet software mostly didn't.

In too many shops, the software is still the one tool that demands a specialist to operate, a workstation to babysit, and a paid expert to translate what the shop already knows.

That is the old model.

I'm not interested in preserving it.

What Grainwork believes

Grainwork is built on a simple belief:

The cabinetmaker should be in control of the work.

Not the consultant.
Not the IT contractor.
Not the vendor's support queue.

The shop.

That belief drives everything.

Software should adapt to the shop.

The shop should not have to adapt itself to the software.

Setup should not take months.

Custom work should not break the system.

Changing a standard should not require a phone call.

Running your software should not require a server in the corner.

Using your own tools should not feel like asking permission.

That is what Grainwork is being built to fix.

What Grainwork is

Grainwork is the cabinet platform I kept wishing I could recommend to the shops I worked with.

A modern cabinet platform for production shops that want control back.

That means:

No consultant required.
Strong defaults. Real working setup. A shop should be able to get in and get moving without a paid implementation project.

No dependency-first design.
If you need to change a rule, update a standard, or adjust how the system works, you should be able to do it without chasing down a specialist.

Custom work should be normal.
Not an exception. Not a crisis. Not the point where the software falls apart.

No IT circus.
No dedicated cabinet computer. No server. No fragile install. No outdated license model. Modern software should work like modern software.

Manufacturing comes first.
Not just pretty pictures. Not just sales flow. The real test is whether the output works on the shop floor.

A note about consulting

I've made a living for years as a cabinet software consultant.

So yes, there's an obvious question here.

Why would I build software that makes that kind of consulting less necessary?

Because it should be less necessary.

The consulting work has helped a lot of shops, and I'm grateful for that. But the longer I've done it, the clearer it's become: this industry has too many jobs built around compensating for bad software.

I would rather build the tool that removes that dependency than spend the next decade supporting it.

Who this is for

Grainwork is not for everyone.

It is not for hobbyists.
It is not for design-only businesses.
It is not for shops that care more about renderings than manufacturing.
It is not for people who are happy with the dependency model.

It is for production shops.

Small to mid-sized.
Owner-led.
Running CNC or trying to.
Tired of outdated systems.
Tired of workaround culture.
Tired of paying extra just to stay functional.
Tired of asking permission from software they already bought.

If that sounds like your shop, you are who I'm building this for.

Where we are

Grainwork is being built in the open, with the shops who need it.

The first shops come in around August 2026 — a small, closed group, on purpose. I would rather a handful of shops trust it completely than have a crowd see it half-ready.

Right now the focus is the core workflow: layout, cabinet design, shop setup, and manufacturing output.

Deep before wide.
Working before flashy.
Useful before impressive.

The point

For a long time, cabinet shops have been told this is just how the software works.

I don't believe that anymore.

I think good shops have put up with bad software for far too long.

I think cabinetmakers should own their tools.

I think custom manufacturing software should serve the people doing the work.

And I think the next generation of shops is going to demand better.

That is what Grainwork is for.

If this resonates, consider this your invitation. Add your shop.

I'll share updates as we build. Honest ones. No hype. Just the work.

Cabinet software has spent twenty-five years training shops to need somebody else.

We're going to give shops back to themselves.

Myron Wittmer
Founder, Grainwork

A note, added after the first shops wrote back.

When I first wrote this, I did not know if it was just me.

I had my own frustration. Years of it. But when you sit with a problem that long, it is easy to assume it is just you.

So I sent the letter out. And shops wrote back. Owners, designers, production managers. People I had never spoken to about any of this.

They told me their own version of the same story. The specialist who finally learned the system, then left. The seats nobody else can use. The update that broke everything on a Monday morning.

They had never compared notes. They did not need to.

That is when I knew this was never just my frustration.

It is the industry's.

If this is your story too, you are not the only one. You never were.