Custom Software for Small Manufacturers and Job Shops: Quoting, Work Orders, and Shop Floor Tracking
Off-the-shelf ERP is built for plants ten times your size, and QuickBooks plus spreadsheets stops working the day you run more than a few jobs at once. Quoting from routings, work-order travelers, shop-floor status, real material and labor cost, and on-time delivery all live in different tools. Here is when custom software for a small manufacturer or job shop starts to pay for itself.

A small manufacturer lives and dies on the gap between the quoted price and what the job actually costs to make. A quote goes out at a number that felt right — so much material, a few hours on the mill, a pass through welding and finishing. Then the steel runs long, a setup takes twice the time it should, a part gets scrapped and rerun, and the job that looked like it had margin closes at break-even or worse. The frustrating part is that nobody knew until the invoice was cut, because the estimate lived in a spreadsheet, the hours lived on a paper traveler, and the material cost lived in the head of whoever went to the rack.
Most shops start on QuickBooks, a pile of spreadsheets, and a whiteboard on the wall by the floor. It works — until it does not. The day you are running eight or ten jobs at once, quoting from operations instead of a price list, and fielding calls asking where an order is, the whiteboard stops keeping up. The usual advice at that point is to buy a full ERP or MRP system. For a plant of a few hundred people that is the right call. For a fifteen- or thirty-person shop, it is often a six-figure implementation of a system built for a company you are not, with modules you will never switch on.
This post covers what custom software for a small manufacturer or job shop actually looks like, where the off-the-shelf tools stop short, and the kind of shop that benefits most from building rather than buying a system that does not fit.
Why a job shop is different from a generic business
On paper, a shop looks like any other business — a quote, an order, a shipment, an invoice. Underneath, the operation has a shape that generic business software and lightweight ERP tools model poorly. The differences that matter:
- A quote is a routing, not a price. What a part costs to make depends on the sequence of operations it goes through — cut, machine, weld, finish, inspect — the setup and run time at each one, the material, and the outside processes like plating or heat treat. Two parts that look similar on a drawing can differ by hours. A flat price list cannot hold that, so quoting ends up in a spreadsheet only the estimator understands.
- The job moves through the floor, not to one destination. An order is not done in one place — it flows across machines and departments, waits in queues, and sits at bottlenecks. Knowing where every open job is right now, and what is stuck behind what, is the difference between a promised ship date you can keep and one you are guessing at.
- Cost is captured in pieces, as the work happens. Real job cost is material pulled from stock, labor and machine time at each operation, scrap and rework, and outside-process invoices — collected across days on the floor, not entered once in an office. If that capture is on paper, the true cost of the job is never actually known.
- Material and inventory drive whether you can promise a date. You cannot commit to a delivery you do not have the stock or the purchased components to hit. Raw material on the rack, work-in-process, and long-lead purchased parts all have to be visible, or the promise date is a hope.
- On-time delivery is the number the customer grades you on. For a shop that supplies other manufacturers, on-time-in-full is not a nicety — it is how you stay on the approved-vendor list. That metric has to be measured and defended, and generic tools do not track it.
- Every shop makes something different. A machine shop, a fabricator, a contract assembler, and a make-to-order product company share a shape but not a workflow. The routings, the terminology, the inspection steps, and the paperwork are specific to what you build — which is exactly what boxed software forces you to work around.
What the off-the-shelf tools get right — and where they stop
There is capable software in this space. QuickBooks handles the accounting a small shop needs and should usually stay right where it is. Dedicated shop systems like JobBOSS, E2, Global Shop, and Fishbowl were built for manufacturing and cover quoting, scheduling, and job costing in a way general business tools never will. For some shops one of them is the right answer. The trouble shows up at the two ends of the market:
The lightweight tools stop at the floor. QuickBooks and spreadsheets quote and invoice fine, but they have no concept of a routing, a work-in-process job, or a shop-floor status. Everything about how the job actually gets made lives outside the software, on paper and on the whiteboard, and none of it flows back into cost.
The full ERP systems fit a bigger company. The manufacturing ERPs are powerful, but they are built around the processes of a larger, more departmentalized plant. Implementation runs long and expensive, the screens carry fields your shop does not use, and getting the system to match how you actually run means months of configuration — or bending your shop to fit the software. Many small shops buy one, use a third of it, and go back to spreadsheets for the rest.
Reporting answers the vendor’s questions, not yours. You want margin by job, by part number, and by customer; quoted hours versus actual at each operation; scrap and rework cost; and on-time delivery by customer. Boxed tools report on invoices and inventory values; the owner wants reports on which jobs, which parts, and which customers actually make money.
What custom software for a small manufacturer typically includes
Most builds we scope cluster around the same core set of modules. The exact mix depends on whether you run a machine shop, a fab shop, an assembly operation, or a make-to-order product line, how many jobs are open at once, and whether you want to replace a shop system or build a layer around the accounting you already trust. The recurring pieces:
- Quoting from routings — an estimate built from the operations a part goes through, with setup and run time, material, and outside processes priced in, so a quote carries its own reasoning instead of a bare number, and every estimator prices the same part the same way.
- Work orders and travelers — a job packet that turns an accepted quote into a routing on the floor, printed or on a tablet, that follows the job through every operation and captures who did what, when, and how long.
- Shop-floor status board — a live view of every open job and which operation it is sitting at, so the office can answer where an order is without walking the floor, and bottlenecks are visible before they blow a ship date.
- Material and inventory tracking — raw stock, work-in-process, and purchased components with reorder points and long-lead visibility, so you only promise dates you have the material to hit and you are not surprised at the rack.
- Labor and machine time capture — real hours logged against each operation from the floor, so quoted time sits next to actual time and the true cost of the job is known when it closes, not guessed.
- Scrap, rework, and inspection tracking — non-conformances, rework loops, and quality sign-offs captured as part of the job, so the cost of a scrapped part is counted and a repeat problem is visible instead of buried.
- Purchasing and outside processes — POs for material and for plating, heat treat, or coating, tied to the job so outside-process cost and lead time land against the right order.
- Customer order portal — a place for your customers to see order status, ship dates, and documents without calling the office, which for a supplier shop is often the feature that wins the next contract.
- Owner reporting — margin by job, part, and customer; quoted versus actual hours by operation; scrap and rework cost; and on-time-delivery by customer, so you can see which work and which accounts actually pay.
None of these features is unique to custom software in the abstract. The point of building custom is that all of them work the way your shop runs — your routings, your material, your inspection steps, your customers’ paperwork — in one system, without the re-keying and reconciliation that comes from stitching QuickBooks, a quoting spreadsheet, and a whiteboard together.
The quote-to-cost gap is where a shop wins or loses money
Ask any shop owner where the profit leaks and the answer is the distance between the quote and the actual cost. A part is quoted on an estimate of setup, run time, and material. Then the job runs, and the hours, the scrap, and the extra material never get compared back to what was quoted — so the same part gets underquoted again the next time it comes through, and a steady customer becomes a steady loss without anyone noticing.
Custom software closes that loop without adding a full accounting department to do it. The quote is built from the routing, the floor captures real time and material against that routing as the job runs, and when the job closes the quoted numbers sit next to the actual ones. The owner can finally see which parts are quoted too thin, which operations always run long, and which customers’ work does not cover its cost. Over time the quotes get tighter, the repeat jobs get priced on real history, and a new estimator has actual data to learn from instead of a gut feel.
Knowing where every job is turns promise dates into kept dates
The other daily pain in a shop is the status question. A customer calls asking about their order, and the answer requires someone to stop and walk the floor to find it. Multiply that by a dozen open jobs and a schedule that shifts every time a machine goes down, and the office spends its day chasing information the shop already knows but has not written down anywhere.
A shop-floor status board fixes that. Every open job shows which operation it is at, what is queued behind the bottleneck, and whether it is tracking to its ship date. The office answers the status call in seconds, the scheduler sees the pileup at a machine before it costs a promised date, and the owner walks in each morning to a picture of the whole floor instead of a whiteboard that was accurate yesterday. Promise dates stop being hopeful and start being defensible — which, for a shop that supplies other manufacturers, is what keeps you on the approved-vendor list.
Who benefits most from a custom build
Not every shop needs custom software. The ones that benefit most have at least two of the following:
- Enough open jobs at once that tracking status on a whiteboard has become a real daily problem, and the where-is-my-order call takes a walk across the floor to answer.
- A quoting problem — estimates that live in one person’s spreadsheet, parts that come in over the quote too often, and no way to check a quote against how the job actually ran.
- Real job costing questions the accounting system cannot answer: margin by job, part, and customer, and quoted versus actual hours at each operation.
- Material or purchased-component lead times long enough that promising a ship date without visibility into stock is a regular way to miss.
- Customers who grade you on on-time delivery and expect status visibility — a metric your current tools do not measure.
- A boxed shop system or ERP you bought, use a fraction of, and work around with spreadsheets for everything it does not fit.
If a shop is small enough that one person quotes every job and knows the status of all of them by memory, spreadsheets and QuickBooks are almost always the right answer. Custom software earns its keep when the job count, the routing complexity, the material lead times, and the customer expectations are real enough that the workarounds start costing real margin — and real orders — every month.
What a build looks like in practice
We start with the workflow, not the screens. Before any code is written, we map the actual operation: how an RFQ becomes a quoted routing, how an accepted quote turns into a work order on the floor, how the job moves through each operation and captures time and material, how scrap and rework get counted, how outside processes and purchased parts land against the job, and where the office loses time re-entering the same information. The custom software is built around that map.
Most manufacturing builds ship the core loop first — quoting from routings, work-order travelers, and the shop-floor status board — and add material and inventory tracking, machine and labor time capture, on-time-delivery reporting, and a customer order portal in later phases. That sequencing keeps the project tight and puts the business value into quoting and floor visibility early, where the daily money is made and lost.
Fixed price. No hourly billing. The scope and cost are agreed before any code is written, and we build against that scope.
Frequently asked questions
What software do small manufacturers and job shops usually run, and where does it fall short?
Most small shops run QuickBooks for the books, spreadsheets for quoting and scheduling, and a whiteboard or a stack of paper travelers on the floor. Once they outgrow that, the usual next step is a full ERP or MRP system like NetSuite, Fishbowl, JobBOSS, Global Shop, or E2 — powerful, but expensive, slow to implement, and built around workflows a fifteen-person shop does not run. The cracks show up in the middle: when a quote depends on a routing of operations rather than a price list, when a job has to be tracked through cutting, machining, welding, and finishing across the floor, when you need real material and labor cost against the quoted price, and when a customer asks where their order is and nobody can answer without walking the shop.
Do I need a full ERP, or can custom software cover a small shop?
For most shops under about fifty people, a full ERP is more system than the operation needs and more disruption than it can absorb. The value of custom software is that it covers the handful of things that actually run your shop — quoting from routings, work orders and travelers, shop-floor status, material and labor tracking, and job-cost reporting — in one place, in your language, without the modules you will never turn on. It can also sit on top of the accounting system you already trust instead of forcing you to replace it. The goal is not a smaller ERP; it is software shaped like your shop.
How long does it take to build custom software for a manufacturer?
A focused first build — quoting from routings, work-order travelers, and a shop-floor status board — typically ships in eight to twelve weeks once the scope is defined. Adding material and inventory tracking, machine and labor time capture, on-time-delivery reporting, and a customer order portal extends the timeline. We scope the project before any code is written, so the timeline and cost are known up front.
If your shop has outgrown the spreadsheets and the whiteboard but a full ERP feels like the wrong fit, start with a conversation. We will scope the workflow before talking about a build.
Ready to talk about your project?
Tell us what you're building. Brad reviews every submission personally.
Start Your Project