Production Scheduling Software: Custom Build or Off-the-Shelf APS
Buy. If you run one plant, under roughly 150 open work orders and standard job shop flow, configure the scheduling module you already own or add PlanetTogether and stop there.
On this page
Buy. If you run one plant, under roughly 150 open work orders and standard job shop flow, configure the scheduling module you already own or add PlanetTogether and stop there. Building only pays once sequence dependent changeovers, shared tooling and a second site defeat a generic constraint model, or when customisation quotes pass $150,000 before you own a line of code.
What off-the-shelf production scheduling software actually does well
Your master scheduler exports open work orders into a spreadsheet before six every morning, and there is a quote on your desk for an advanced planning and scheduling (APS) package that costs more than the machine she is sequencing around. Before anything else: most manufacturers reading this should buy. We build custom software for a living and that is still the honest answer.
PlanetTogether, Siemens Opcenter APS and the scheduling modules inside Enterprise Resource Planning (ERP) suites such as Epicor Kinetic, NetSuite, SAP Business One and Dynamics 365 Business Central were built by people who have stood on a shop floor. What arrives on day one is hard to write from nothing:
- A finite capacity engine that refuses to book 130 hours into an 80 hour week, which is precisely what your material requirements planning run does every night.
- Work centres, shift calendars, alternate routings and labour pools already modelled and tested against thousands of plants.
- A drag and drop board where the downstream consequences recompute as the planner drops a job.
- Dispatch lists published to tablets, so nobody walks a paper traveller to a machine.
- Upgrades, documentation and a user community, which turns a departing planner into a hiring problem rather than an outage.
If you run one site, standard job shop flow and no constraint an APS vendor would blink at, buy the bolt-on or switch on the module you already pay for. At that size a build is capital better spent on a second CNC cell.
Where they stop: the rules that live in one planner's head
The gap is never capacity. It is the twenty or so rules that never made it into a routing record, because a routing record has no field for them.
- A sequence dependent changeover matrix, where running line 3 light to dark saves 25 minutes of purge per colour change and running it the other way does not.
- Shared tooling contention, where two nominally available machines are mutually exclusive because one fixture serves both.
- Operator certification with expiry dates, where only two people can run the five axis cell and one of them is on nights.
- Furnace batching that wants twelve metallurgically compatible parts before it fires.
- The 9:05 spindle alarm, and the reflow of 60 affected jobs into a customer impact list sorted by late penalty exposure.
APS vendors will quote every one of those, and that is the sentence to pay attention to. They quote them as configuration or customisation, and the version of your changeover matrix that survives implementation is the version their constraint model can express. We meet manufacturers in discovery who bought a licence four years ago and still schedule in Excel, because the last fifth of the rules never went in.
The second stopping point is writeback. Reading work orders out of Epicor Kinetic is about a week of work. Writing confirmed dates back safely, so that customer service quotes reality rather than fiction, is a subsystem with its own failure handling.
The arithmetic: licence cost at your scale versus the cost to build
Do this with the quote in front of you rather than a benchmark. Put five years on the clock for both paths, because that is roughly how long a scheduling system lives before somebody wants it replaced.
On the buy side, add the annual licence multiplied by named planner seats, the implementation fee, the paid change request every time a sequencing rule changes, and the internal analyst hours spent feeding the thing. Then add the cost of what it still does not do, which is usually the spreadsheet that survives alongside it and the 25 hours a week your planner spends on export, paste and reconcile.
On the build side, add the one time cost, the annual support percentage, hosting, and the fact that the number stops growing when you add a plant.
The crossover in this category sits at roughly 8 to 12 named planner seats, or at the second site, whichever arrives first. Below that the licence wins on arithmetic alone and you should take it. Above it, per seat pricing compounds against you exactly as you grow, and multi-site licensing usually means separate models per site, so you pay three times for three local truths and still cannot balance load between them. If the implementation quote alone has passed $150,000 before you own anything, you are already inside build territory and the licence was never the expensive part.
What a custom build actually costs, and what nobody quotes
A focused first release covering ERP work order sync, a finite capacity engine for one plant, the drag and drop board, dispatch lists and the parallel run tooling that lets you retire the spreadsheet with evidence rather than hope, runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding multi-site load balancing, capable to promise for sales, shop floor data capture through MTConnect or OPC UA, and run time learning that tightens standards against actuals, runs $150,000 to $400,000 phased across 6 to 12 months.
Two lines never appear on a proposal. Data migration and cleanup runs 10 to 25 percent of the build cost, and in manufacturing it lands at the top of that range more often than the bottom, because routings written in 2014 have standards nobody has re-timed and changeover times that exist only as a colour in a spreadsheet. You are not moving data. You are discovering what your master data actually says.
Then year two. Budget 15 to 20 percent of the build cost annually for support and enhancement if you want someone reachable when a solver run goes long during a hot week. Add hosting, which is small here, and a few days a year absorbing ERP upgrades that change an endpoint you depend on.
The four situations where building beats buying
- Regulatory fit. If you hold AS9100, IATF 16949 or produce under FDA record keeping obligations, the auditor's question is always who moved the job and why. Immutable schedule history with logged overrides and reason codes is cheap to design in and expensive to retrofit onto a product that treats the schedule as current state.
- Scale economics. Seats multiplied by sites is the only place where per seat pricing beats a fixed build, and it beats it in the vendor's favour. Past the second plant the licence line grows with your success.
- A workflow that is your competitive advantage. If how you sequence and how you promise is part of why customers choose you over the shop down the road, renting a generic approximation of it is the expensive option.
- Integration sprawl across three or more systems. ERP for work orders, an MES or machine signals under ISA-95 for floor reality, a maintenance system holding planned downtime, and a quote screen that needs a capable to promise answer. Four systems that must agree is where products stop and integration work starts.
None of the four true means buy. Exactly one true usually means buy the product and build the narrow piece around it.
How to decide in a week
Run this test rather than another demo cycle.
- Days one and two. Sit beside your planner for two full mornings and write down every decision she makes that is not in a routing record. You want a numbered list of rules, not impressions.
- Day three. Send the ten hardest rules to each APS vendor and ask them to configure those ten in a sandbox with a written price. Not a demo of their standard model. Your ten rules.
- Day four. Time the reflow. Take last month's worst breakdown and measure the hours from alarm to published revised schedule and first customer call.
- Day five. Count the systems that must agree on a date, and write down which one is authoritative when they disagree.
Eight of ten rules configured and a reflow under two hours means buy. Six quoted as customisation and a reflow that took until mid afternoon means you already know.
Then pay for discovery rather than accepting a free proposal. Digital Heroes runs a paid discovery phase that ends in a signed product requirements document covering the constraint model, the ERP writeback contract and the acceptance criteria, and you keep that document whether you build with us or hand it to another firm. That is what keeps a fixed quote fixed.
We are wrong for you if you want a mathematical optimisation solver treated as a research project, if you need an engineer physically on your floor every week, or if you are a single site under 150 work orders, where the licence is simply the better buy. What we are is more than fifty specialists across over 2,000 delivered projects, with a named team you meet before signing. We run our own products, ShopScore, HeroCheckout and Section Vault, so the people choosing your architecture live with those choices on their own revenue, and we hold India LLP, US LLC and UK LTD entities so the intellectual property assigns under your own law. Check us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S first.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
Frequently asked questions
How long does it take to replace our scheduling spreadsheet?
Twelve to sixteen weeks to a first release covering one plant, then two full schedule cycles running in parallel before you retire the file. The parallel run is not padding. Every morning your planner builds her sheet and the system builds its own, you compare them, and the differences expose rules nobody wrote down. Skip that step and the spreadsheet quietly comes back within a quarter.
Who owns the constraint model and the code if an agency builds it?
You should, in writing, before kickoff. That means the repository, the cloud accounts in your company name, and the unrestricted right to hire another firm. At Digital Heroes the client owns the code from the first commit. The constraint model matters more than the code here, because it encodes decades of your plant knowledge, and it should never sit in a vendor account you cannot reach.
What happens if our ERP vendor changes an API mid-project?
It happens, particularly on cloud editions with forced upgrade cycles. The protection is an integration layer that isolates every call behind your own interface, plus contract tests that run nightly against a sandbox tenant and fail loudly rather than silently returning stale work orders. Budget a few days a year for this permanently. A team that has not asked which ERP edition you run has not priced it.
Can we keep Epicor Kinetic and still build a custom scheduler?
Yes, and that is the normal shape. Your ERP stays the system of record for work orders, routings, inventory and financials. The scheduler reads open orders on a short cycle, decides sequence, and writes confirmed dates back. Nobody sensible rebuilds an ERP to fix scheduling. If a developer proposes replacing it in phase one, that quote is a different project wearing your problem as a disguise.
Should we buy an APS licence first and build later?
Often yes, and it is an underrated move. A year on a product teaches you exactly which rules it cannot hold, which is the requirements document you would otherwise pay to discover. The trap is signing a multi-year term with an implementation fee amortised into it, because then the sunk cost argues against a decision you already know is coming. Keep the term short.
What is the difference between MRP, APS and a finite capacity scheduler?
Material requirements planning explodes a bill of materials and schedules backwards from due dates assuming unlimited capacity, which is why every order looks on time. Advanced planning and scheduling adds finite capacity and constraints across a horizon. A finite capacity scheduler is the narrower job of sequencing what is already released onto specific machines this week. Most plants need the third thing and get sold the second.
Will our planners actually use it, or drift back to Excel?
They drift back when the system cannot express a rule they know matters, so they override it, the override is not recorded, and trust collapses. Two design decisions prevent that: every manual override is captured with a reason code, and those reasons get reviewed monthly as a backlog of missing rules. Adoption is a data model problem here far more often than a training problem.
Does AS9100 or IATF 16949 certification make a custom scheduler harder to audit?
It makes it easier if the history is immutable from day one. Auditors want to see who changed a sequence, when, and why, and they want the record to be tamper evident. A product that overwrites current state cannot answer that without an add-on. Specify append only schedule history, logged overrides with reason codes and retained dispatch versions in the requirements document, not after the first audit finding.
Can a custom scheduler give sales a realistic delivery date?
That is the capable to promise endpoint, and it is usually the module that pays for the build. The quote screen sends part, quantity and routing, and gets back the earliest achievable ship date against current load plus the cost of jumping the queue. Inside sales stops reading the laminated three week card, and rush work starts carrying a rush fee instead of an apology discount.
What happens to the schedule when a machine goes down at nine in the morning?
The work centre is flagged down from a machine signal, the MES or a button on the operator tablet, and the engine proposes a repaired schedule within minutes. The planner then compares options side by side: authorise overtime, move work to a slower backup cell, or slip three low margin orders to protect two carrying penalties. The customer impact list comes out sorted by exposure, so the first call is the right one.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
Why do companies replace NetSuite with custom software?
The three reasons we hear most at Digital Heroes are per-user license growth, SuiteScript customizations that became fragile, and workflows the platform cannot model without workarounds. A company adding 50 users to NetSuite takes on roughly $59,000 per year in extra licenses at the commonly quoted $99 per user rate, which is often the moment the custom math starts winning. Replacements usually keep the accounting structure intact and migrate module by module.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
Will a custom ERP scale as we grow from 50 to 500 employees?
Yes, if it is designed for that from the start, which mostly means clean database design, permissions that handle new departments, and modules that stay separable. Adding users to software you own costs nothing in licenses, the opposite of the per-seat scaling penalty on NetSuite or Dynamics. What does need budget as you grow is new modules and integrations, so keep a small standing development arrangement rather than restarting a vendor search every two years.
Can we keep our current ERP and just build custom modules around it?
Often yes, and it is frequently the smartest first move. Digital Heroes regularly builds custom scheduling, quoting, or warehouse tools that sit on top of SAP, NetSuite, or Odoo through their APIs, which fixes the painful 20 percent without a risky replacement. The hybrid route costs a fraction of a full rebuild and tells you within months whether a bigger migration is even necessary.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
How much does a custom ERP cost for a small business?
A small-business ERP covering two or three core modules typically runs $40,000 to $120,000, with inventory, ordering, and accounting sync being the usual starting set. Across 2,000+ Digital Heroes projects, integration count and user roles drive cost far more than screen count. A full mid-market ERP with six or more modules usually lands between $150,000 and $400,000.
Can a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
