When the commercial ERP fits your shop about as well as a borrowed glove, and the real system lives in spreadsheets beside it, building your own can make sense. Norsoft is a small custom software firm that builds ERP systems with manufacturers, in stages, while the shop keeps running. You own the result.
First, check whether you should build at all
If a packaged ERP covers how your shop quotes, schedules, routes and ships, buy it. Building only pays off when your process is what sets you apart and the software keeps forcing you into someone else's. We'll tell you which side you're on before you spend anything. For a fuller comparison, see custom ERP vs off-the-shelf.
How co-development works
You know your shop and we know how to build software, so the work is split that way.
- Your side: someone who knows the process, often an estimator or engineer, explains how jobs really move through the shop, checks the data we bring over, and tests each piece before it's accepted.
- Our side: a partner leads the project, designs the system around your process, builds it, and moves your data.
- The plan: the system is broken into separate projects, and each one has an acceptance test you sign off on before the next begins.
- The cutover: your current system keeps running alongside the new one until the new one has proven itself, so production never stops. Here is how we run old and new side by side.
You own it
The code lives in a repository your company controls from day one. It can run on your own servers or in the cloud. If you later want to take it in-house or hire someone else, nothing stops you.
What it costs
Every project is scoped before it's priced. For a real example, here is the quote we sent a small manufacturer with the prices left in: a 12-month plan of 11 projects, at $8,000 a month for two projects at a time or $15,000 a month for four.
Work with manufacturers
- A manufacturer is replacing its commercial ERP with one it owns, on a 12-month plan built with us.
- A plastic extrusion manufacturer replaced an outdated ERP with a system we built that connects the front office to the shop floor, cutting downtime by 30%. Read it
Who you work with
Norsoft is three partners, and one of us is on your project from the first call to launch. When a project needs more hands, we bring in developers for that work, and the partner on your project stays responsible for it.
Questions manufacturers ask
Can a small firm really build an ERP?
An ERP is a set of connected pieces: quoting, jobs, routing, inventory, shipping, accounting. We build it one piece at a time, each with its own test, with a partner leading the whole plan.
How long does it take?
It depends on scope. The plan in our published quote runs 12 months, with the old and new systems overlapping before the old one is retired.
Will production stop during the switch?
No. Your current system keeps running until the new one has proven itself.
Can it connect to QuickBooks and our other systems?
Yes. Connecting to the accounting and shop systems you already use is part of the job, so orders aren't retyped.
Who owns the code?
You do, in a repository your company controls from day one.
Do you only work with Minnesota shops?
No. We're based in Mankato and work with manufacturers in other states.
More on the other problems we solve for plants is on our manufacturing page.
Tell us what your ERP gets wrong today and how your shop really runs. We'll tell you whether to keep it, buy a better one, or build your own. Reach out here or call (507) 388-4748.
Using an AI assistant? It can send this inquiry for you. How that works.