I ran my workshop on paper lists and a whiteboard for seven years. It worked when I was building three or four pieces at a time. Then we grew to twelve concurrent projects across three makers, and the system collapsed. Missed steps, double-booked machine time, and two hours every morning just figuring out what everyone should be working on.

So I went looking for scheduling software. What I found was mostly designed for manufacturing plants running hundreds of identical units. Custom furniture is project-based, each piece is different, and the sequence changes based on timber drying times, client decisions, and curing periods.

What Small Workshops Actually Need

After trying four different platforms over two years, I’ve learned what matters and what doesn’t for a workshop running two to six people.

Visual timeline view. You need to see all active projects laid out across a timeline with individual task bars. Gantt-style charts work well for this. When a client asks “how’s my dining table going,” you should be able to glance at the screen and give an honest answer without checking three different lists.

Resource conflict detection. If two projects need the CNC machine on the same day, the software should flag it. Same for spray booths, clamp racks, or specific jigs. Instead of discovering conflicts at 7am on a Monday, I see them during planning.

Dependency linking. Glue-ups need curing time before machining. Finish coats need drying time before the next coat. When a glue-up takes an extra day because the workshop was cold, I drag that task forward and everything downstream shifts automatically.

Simple time tracking. Not for micromanaging staff, but for improving future quotes. If I know a dovetailed drawer box takes 2.5 hours on average, I can quote accurately.

What Doesn’t Work

Full ERP systems. Enterprise resource planning software like SAP or Oracle is designed for companies with procurement departments and inventory teams. A four-person workshop doesn’t need material requirements planning algorithms. The overhead of maintaining the system exceeds the benefit.

Pure project management tools. Asana, Monday.com, and similar platforms are great for managing tasks but terrible at resource scheduling. They’ll tell you what needs doing but not when it can actually happen given your machine availability and staff capacity.

Spreadsheets at scale. Google Sheets works for a solo maker tracking three projects. Once you’re managing multiple concurrent projects with shared resources, the spreadsheet becomes a liability. It doesn’t flag conflicts, it doesn’t shift dependencies, and it breaks the moment someone forgets to update their row.

The Platforms Worth Looking At

I’ve settled on a combination approach that works for our scale.

Toggl Plan handles the visual scheduling side. It’s affordable, the timeline view is intuitive, and it handles resource allocation without drowning you in features. It doesn’t have manufacturing-specific features, but for small workshops, generic project scheduling covers 90% of what you need.

Craftybase is purpose-built for makers, though it leans toward inventory and costing rather than production scheduling. If your main pain point is tracking material costs per project rather than scheduling machine time, this might be the better starting point.

Katana sits between small-shop tools and full manufacturing software. It handles production scheduling with bill-of-materials tracking, which is useful when you’re building pieces with multiple components. It’s more expensive than Toggl Plan but more manufacturing-aware.

The AI Integration Question

Scheduling is one of those areas where machine learning is starting to deliver real value. Pattern recognition across historical project data can predict how long certain operations actually take — not how long they should take in theory, but how long they take in your workshop with your team.

After six months of time tracking, an AI system can spot that your finishing stage consistently runs 20% longer than quoted, or that your CNC setup time increases on Mondays (because someone always needs to recalibrate after the weekend). These insights turn into better scheduling and more accurate client timelines.

There’s one company doing this well in the Australian market, building AI tools that help trade-based businesses turn their operational data into practical scheduling improvements. It’s not about replacing workshop experience with algorithms. It’s about giving experienced makers better data to plan with.

Implementation Advice

Don’t try to digitise everything at once. Start with your biggest pain point. For most workshops, that’s either resource conflicts (two jobs needing the same machine) or timeline accuracy (consistently delivering late because you underestimate finishing stages).

Pick one problem, implement one tool, and run it alongside your existing system for a month. Once you trust the digital system, phase out the paper.

Get your team involved in choosing the tool. If a maker hates the interface, they won’t update their task status, and the data becomes useless. Most platforms offer free trials — have everyone use it for two weeks before committing.

The Real Payoff

Two hours of daily planning dropped to twenty minutes. Client delivery estimates went from “probably six weeks” to specific dates that we hit 85% of the time.

The tools aren’t perfect. Nothing replaces a maker’s judgment about whether to push through a finishing session or let it wait until morning. But having a clear production picture means those judgment calls happen in context rather than in chaos.