Custom ERP for Businesses That Have Outgrown Spreadsheets

A custom ERP is one system built around how your business quotes, makes, delivers and bills, instead of a packaged product you bend your process to fit.

It is the right call for some made-to-order manufacturers, fabricators and service firms, and the wrong one for many others. Answer seven questions to see which side you are on before you talk to anyone.

Should you build or buy? A 2-minute check

Seven questions about how you work today. The result says buy, build, or keep what works and build the missing piece, and you can print it or send it to your partner. No email needed.

1. How well do off-the-shelf systems match the way you quote, make and deliver?
2. What do you run this on today?
3. How many separate tools hold the same order or customer details?
4. How settled is the process?
5. How many people need a login?
6. Do customers, subcontractors or partners need to see their own orders or jobs?
7. Is the way you do this part of why customers choose you?

Build or buy check: custom ERP

Your result

Answer every question to see your result

0 of 7 answered. 7 to go.

Save your result

Example: a made-to-order shop running on six tools

A manufacturer makes every order to custom dimensions. The order details live in a CRM, an accounting package, a project board, a form tool and two spreadsheets, customers call to ask where their order is, and the way the shop quotes is why people buy from it. The same check gives this result.

Example result

A custom ERP is worth scoping.

Your process is settled, it does not fit packaged systems and the workarounds are already costing you. That is the case where one system built around how you work pays for itself.

Points toward custom

12

Points toward off the shelf

1

What points toward custom

  • Your quoting, production or pay rules do not fit the packaged systems you have looked at.
  • People keep spreadsheets beside the product you pay for, so it is not the real system.
  • The same details are typed into five or more tools that do not talk to each other.
  • The process is settled, so software built around it will not need rebuilding next year.
  • People outside the company need their own login and their own slice of the information.
  • The way you work is part of why customers choose you, so it is worth protecting in your own system.

What points toward off the shelf

  • With under 10 logins, per-user fees stay small.

What to do next

  1. Map one workflow end to end, for example quote to cash, with every handoff and every spreadsheet it touches.
  2. Decide what stays. Accounting software usually stays and gets connected, not replaced.
  3. Get a fixed-price proposal for a first version that runs that one workflow, then add the next one.
How we worked this out

Each of the 7 answers adds one to three points to one side: custom or off the shelf. A process that fits no product, spreadsheets kept beside the software you pay for, and a process that is still changing weigh the most.

The result is the custom points minus the off-the-shelf points. At -2 or lower the answer is buy. At 5 or higher the answer is build, but only when your process fits no product and is settled. Everything else is keep what works and build the missing piece.

The points are our own rule of thumb from scoping these projects, not a statistic. Treat the result as a starting point for the conversation, not a verdict.

Want this worked out for your own business? See the two fixed-price ways to start.

What a custom ERP is, in plain words

ERP stands for enterprise resource planning, which is a long name for the system a business runs on: orders, jobs, people, money.

A packaged ERP gives you someone else's idea of those things and asks you to work that way. A custom ERP starts from how you already work and puts it in one place, so an order is entered once and everyone, from the office to the shop floor to the customer, sees the same record.

For a small or mid-size business it is rarely a giant project. It is usually one workflow first, such as quote to cash, with the next one added once the first is in daily use.

When custom beats off the shelf

  • Your process is the productEvery job is different, and the way you quote and make it is why customers pay your price.
  • The spreadsheets are the real systemYou pay for software, and the truth still lives in a sheet someone updates by hand.
  • Five tools hold one orderThe same order is typed into a CRM, an accounting package, a project board and a form tool, and the automations between them keep breaking.
  • People outside need to see inCustomers, subcontractors or reps need their own login, and a packaged system makes that expensive or impossible.

When it does not

  • Your process is standardIf you work like most businesses in your trade, a product made for that trade will do it better and for less.
  • The process is still changingCustom software fixes today's workflow in place. If it will look different in a year, rent software until it settles.
  • You have not tried a product yetA two-week trial costs almost nothing and shows you exactly where the fit breaks.
  • You only need accounting or payrollThose are solved problems. Buy them and connect them.

BDC, Canada's business development bank, says off-the-shelf ERP is the better option for most small and mid-size businesses. For a standard operation we agree. Read BDC's comparison of custom and off-the-shelf ERP systems.

What a custom ERP includes for a made-to-order business

Not every business needs every part. The proposal lists exactly which of these the first version covers.

Quoting and order intake

An inquiry form and quote builder that use your own dimensions, materials, options and pricing rules, so a quote becomes an order without retyping.

Production and job tracking

Every job with its stage, owner and due date, and a shop-floor view where a status change takes one tap.

Customer and partner logins

Customers see their own quotes, order status and invoices. Subcontractors and reps see only their own slice.

Pay, commissions and time

Pay rules too specific for payroll software, such as commissions, overrides, piece rates and chargebacks, worked out by the system and itemized.

Invoices and accounting sync

Invoices and payments flow to your accounting software, which stays.

Reports from live data

Revenue, pipeline, average order size and workload from the same records that run the operation, not from a monthly export.

Every build also comes with user logins and roles, import of your existing data, a mobile-friendly layout, documentation and 30 days of support after launch.

Custom ERP systems we have built

Two builds, with only what the case studies state.

Field sales and installation

One ERP for sales, payroll and field operations

$25k+/Mo Savings

  • Miller Bros Sales runs sales, payroll, onboarding and field operations in one system for 800+ reps and installers.
  • Provider reports are matched against rep-submitted sales automatically, and only the true exceptions go to a person.
  • It replaced a $3,500 a month HR tool with an onboarding workflow inside the same system.
  • It is saving $25K+ a month by replacing spreadsheets and third-party tools.
Made-to-order manufacturing

Six tools replaced by one order system

  • Designed for a custom fireplace screen manufacturer running on ActiveCampaign, QuickBooks, Asana, Shopify, Jotform and spreadsheets, held together with Zapier.
  • One system runs the order from intake to production to payment.
  • Customers, staff and the shop floor each get their own view, and a status update on the floor shows up for the customer right away.
  • Revenue, pipeline value and average order size are reported from the same data that runs the operation.

This is a spec build with a live demo, not a client launch. The manufacturer was not ready to move forward.

How a custom ERP build runs

The first version covers one workflow end to end, not the whole business. In our ERP for a field sales company the first problem was commission tracking, and payroll, onboarding and field operations were added to the same system afterward.

  1. 1

    Short questionnaire

    You answer a few questions about how work moves through the business today. We read it before we talk.

  2. 2

    Discovery call

    A focused call on your specific problems, not basic questions.

  3. 3

    Fixed-price proposal

    Scope, timeline and deliverables in writing. You know the full number before any work begins.

  4. 4

    Build in stages

    We build to the scope and check in every two weeks, with video updates in between so you can see what has been built.

  5. 5

    Walkthrough, launch and support

    We go through every feature together before launch. Bug fixes and small adjustments are included for 30 days after.

How long it takes and what it costs

We do not publish a price for custom builds, because a number without your process behind it is a guess.

You get a fixed price and a timeline in a written proposal after we go through how you work today. That plan is a paid, fixed-price service, shown below, and the written plan is yours.

Because the first version covers one workflow, it is a smaller commitment than the whole-company projects the figures below describe.

What other firms publish

For reference, these are figures development firms state on their own sites. They are not our prices.

Common Questions

What is a custom ERP?

A custom ERP is one system built around how your business quotes, schedules, makes, delivers and bills, instead of a packaged product you adjust your process to fit. It replaces the spreadsheets and separate tools that each hold part of an order, so everyone works from the same record.

Is a custom ERP or an off-the-shelf ERP better for a small business?

Off the shelf is the better choice for most small businesses, and BDC, Canada's business development bank, gives the same advice. Custom wins when your process is settled, no product fits it and the workarounds already cost you hours every week. The check at the top of this page tells you which side you are on.

How long does it take to develop a custom ERP?

It depends on how much of the business the first version covers. ScienceSoft, a large development firm, publishes around 3 to 5 months for a first version. We scope the first version to one workflow, such as quote to cash, write its timeline into the proposal before you commit, and add the next workflow once that one is in use.

How much does a custom ERP system cost?

Published figures run from $50,000 to $250,000 and up (Cleveroad) to $200,000 to $500,000 for a single module (ScienceSoft). We do not publish a price for custom builds because the number depends on your process. You get a fixed price in a written proposal as part of the Build Plan and Fixed Quote, which costs $495.

Can a custom ERP work with QuickBooks and the tools we already use?

Yes, and it usually should. Accounting software is rarely worth replacing, so the custom system sends invoices and payments to it instead. Every build we scope includes one system integration, and more are priced in the proposal.

Do we have to replace everything at once?

No. The safer route is to move one workflow first, use it until the team trusts it, then move the next. Our ERP for a field sales company started as a fix for commission tracking, and payroll, onboarding and field operations were added to the same system afterward.

Is a custom ERP a good fit for custom manufacturing?

Made-to-order work is where packaged ERP fits worst, because it is designed around catalog parts and repeat runs while every job you make has its own dimensions, materials and finish. An ERP for custom manufacturing tracks the job, not the part number: the inquiry, the quote, approvals, production status and the invoice on one record.

What happens after launch?

Bug fixes and small adjustments are included for 30 days after launch. After that, many clients keep working with us on new features and maintenance, which is optional.

Two ways to start, both fixed price

Build Plan and Fixed Quote

Get the plan and one fixed price before you pay to build

We look at how the work runs today and tell you plainly what is worth building, what a ready-made product or a simple automation would cover, where an AI agent would help and what to leave alone. You get it in writing, with a fixed price for the first build, so you know the full number before any work begins. The plan is yours to keep, whether we build it, someone else does, or nobody does.

  • A short questionnaire about how the work runs today, reviewed before we talk. If you already wrote a scope of work, we start from it
  • A one-hour call that walks through the work you want off your plate
  • A written plan that says for each part: build it, buy a ready-made product, automate it, hand it to an AI agent, or leave it alone
  • What the recommended setup would cost to build and to run every month
  • A fixed-price proposal for the first build, with scope, timeline and deliverables, valid for 30 days
$495one time

Turnaround: Written plan within 5 business days of your call.

You pay on Stripe's secure checkout page. We never see your card number.

Prototype and Fixed-Price Scope

Turn your estimate into a prototype and one fixed price

You have a rough idea of what the software should do, and maybe a price range. We walk through it with you on one call, and build a clickable prototype of the main screens so you can see how it would work before you pay for a build. With it you get the scope in writing and a single fixed price to build it, yours to keep whether or not you build with us.

  • One 60-minute call to walk through the jobs, users and systems it has to cover
  • A clickable prototype of up to 4 main screens that you can open on your phone and share with your team
  • A written scope: every screen, user type, connected system and what is left out
  • One fixed price and a timeline to build it, valid for 30 days
  • A plain answer if a ready-made product would do the job instead
$950one time

Turnaround: 7 business days from your call.

You pay on Stripe's secure checkout page. We never see your card number.