Pulp and Paper Mill Production Software: Custom Build or Off-the-Shelf
Buy Greycon. If your problem is squarely trim optimisation and your constraint set is conventional, opt-Studio is a proven specialist product and commissioning your own cutting stock solver would be an expensive way to arrive at the same answer.
On this page
Buy Greycon. If your problem is squarely trim optimisation and your constraint set is conventional, opt-Studio is a proven specialist product and commissioning your own cutting stock solver would be an expensive way to arrive at the same answer. Build only when the workarounds either side of the optimiser cost more than the benefit inside it, which usually means converting rules, tolerance policy and grade sequencing.
What Greycon, ABB, Honeywell and Valmet actually do well
Nobody in this category is selling snake oil, and the mills that assume otherwise usually end up commissioning a worse cutting stock solver at four times the price.
Greycon is the genuine specialist. opt-Studio and X-Trim solve the cutting stock problem properly, with people who have spent careers inside paper and board mills and who will recognise your order book from the first meeting. If your trim is high because nobody is optimising it at all, buying that product is the correct decision and it will pay back faster than any build.
On the process side, ABB, Honeywell with Experion MX, and Valmet with IQ and DNA cover quality control, sheet measurement and production reporting to a standard no bespoke project should try to reproduce. Basis weight, moisture and caliper control against TAPPI and ISO test methods is their ground and it is not yours. SAP for Mill Products handles the commercial layer for larger groups, including the variant configuration and catch weight handling that ordinary enterprise systems fumble.
Most mills should buy. A machine running long campaigns of a handful of standard widths is already close to its trim floor, and the money belongs in reliability or in reducing quality variability rather than in an optimiser. We say that in scoping calls and it costs us projects, but a mill whose planner spends an hour a week on sets rather than a day will not see a return.
Where they stop: the constraint your winder has and their model does not
Two gaps, and they compound.
The first is that trim and grade sequencing are one problem solved separately. A better trim solution may require running two orders together at different basis weights, which forces a grade change, which costs broke, machine time and a period of off specification production. Optimise trim alone and you can produce a schedule with excellent millimetres and terrible economics. Most tools address one side, the scheduling discussion happens in a meeting, and the interaction between the two lives in the planner's judgement, which is fine until the planner is on holiday.
The second is your own constraint set. Maximum knives on the winder. Minimum roll width the winder handles reliably. Maximum set count. Roll diameter limits at the customer. Whether a particular account accepts a splice. Which orders share a core size and can therefore go on the same set. Whether the sheeter downstream takes a given width without a changeover. Generic optimisers accept a handful of these as parameters and leave the rest as rules the planner applies afterwards, which is exactly the manual work that makes the optimiser only partly useful.
Then there is tolerance. Most paper and board orders carry a delivery tolerance agreed with the customer, commonly around plus or minus ten percent. That tolerance is an optimisation asset. Producing slightly over on one order can enable a far better set, and slightly under can avoid a grade change. Because tolerance is filed as a contractual footnote rather than a variable, planners use it accidentally rather than deliberately, and no packaged tool asks them to do otherwise.
Finally, certification. If you hold Forest Stewardship Council or Programme for the Endorsement of Forest Certification chain of custody, and increasingly if you sell into the European Union under its deforestation due diligence rules, the certified fibre claim has to follow the order through production and onto the delivery document. That is a data lineage requirement, and it sits outside the trim solver entirely.
The arithmetic: licence per machine against a millimetre of trim
This category is not priced per seat, so do the sum in tonnes.
Take your deckle and your typical trim. A hundred millimetres of trim on a 6.2 metre deckle is about 1.6 percent of production. A machine at 300 tonnes a day over 350 days makes 105,000 tonnes, so that trim is roughly 1,700 tonnes a year going to broke, repulped, carrying fibre, steam, energy and machine time that produced nothing sold. Multiply those 1,700 tonnes by your own contribution per tonne. That is the annual prize, and it is a number nobody in the mill would approve as a line item if it were presented in a meeting.
Now put the two paths beside it. A specialist licence plus annual maintenance for one machine is a modest fraction of that prize, which is why buying is usually correct. A custom first release runs $90,000 to $190,000 with support at 15 to 20 percent a year, so a $140,000 build costs roughly $259,000 across five years.
The crossover is order book variety rather than tonnage alone, but tonnage sets the floor. Below roughly 100,000 tonnes a year on one machine with a narrow width range, buy the specialist product or do nothing. Above roughly 150,000 tonnes a year with a varied order book, frequent grade changes and tolerance that is never used deliberately, the combined trim and sequencing gain typically clears a build inside two years. The cheapest diagnostic: count how many minutes your planner spends redoing downstream work after trying an alternative set. If trying a second option is too expensive to attempt, you are accepting the first one every week.
What a custom build actually costs
A first release covering order intake from your enterprise system, the full constraint model for one machine, combined trim and sequencing optimisation against a money objective and a planner interface with alternative comparison runs $90,000 to $190,000 in 14 to 20 weeks. That is a system your planner uses for next week's schedule, not a study. A full platform adding converting and sheeting constraints, roll and parent reel inventory, multi machine allocation, order promising, quality system linkage and plan versus actual attribution runs $250,000 to $600,000 phased over 9 to 18 months.
Then the lines nobody quotes. Migration runs 10 to 25 percent of build cost, and here it is not really data movement. It is capturing the constraint set, which lives in the heads of two people on the machine floor and in the exceptions a planner applies without thinking. Budget it as facilitated workshops with the winder crew present, not as an extract. Year two onward runs 15 to 20 percent of build cost annually, and in this category that budget has a standing job: constraints change when you rebuild a winder, add a customer or requalify a grade, and a stale constraint set produces schedules the crew quietly ignores.
What drives the number up: the count of machines and whether orders can be allocated between them, since multi machine allocation is materially harder than single machine trim; owned converting operations, which roughly double the model; grade structure complexity, meaning how many basis weights, coatings and colours run and how constrained the transitions are; and how deep the enterprise integration goes, particularly if order promising is handed back to the sales system.
The four situations where building wins
- Regulatory fit. Chain of custody claims that must follow a specific order through trim, winding and dispatch, plus energy reporting under ISO 50001 if your site is certified. When the compliance record is produced by the same plan that runs the machine, it stops being a quarterly reconstruction.
- Scale economics. Above roughly 150,000 tonnes a year on a varied book, the combined trim and grade sequencing gain clears the build inside two years. Do that sum with your own contribution per tonne rather than a vendor's percentage claim.
- A workflow that is your competitive advantage. If you own converting, scheduling the mill and the converting plant as one system is the thing your competitors cannot copy by buying a licence. Scheduling them separately means one of them permanently absorbs the other's inefficiency.
- Integration sprawl across three or more systems. The enterprise system for orders, the quality control system for actual production and off specification tonnes, the warehouse for roll inventory, and dispatch. When four interfaces each need a vendor change request, the interfaces become the project.
One signal alone is rarely enough. Two together is the tipping point, and the most common pairing is owned converting plus a tolerance policy that never reaches the optimiser.
How to decide in a week
Do not commission a study. Run a bake-off on one real week.
Take next week's order book exactly as it stands. Have your planner build the schedule the way he always does and record how long it takes and how much trim it carries. Then ask every vendor and every developer on your shortlist to produce an alternative from the same data, and require each to state the objective they optimised. If anyone answers minimise trim, they will hand you a schedule the mill cannot run, because the objective has to price grade changes, lateness, tolerance usage and plan stability in money alongside trim.
Second, hand over three constraints that are not in any standard model. Your minimum reliable roll width, the customer who refuses a splice, and the core size rule. Ask how each is maintained after go-live. If constraints live in code rather than in data your planning team can edit, the model is stale within a year and the crew will start ignoring it.
Third, ask what happens when Wednesday's break wipes eight hours from the plan. A rebuild that takes minutes lets you re-plan daily. A rebuild that takes an afternoon means you will not, and the schedule will drift every day it is not refreshed.
Then buy a paid discovery phase that ends with a written specification you own: the full constraint model, the objective function with its cost terms, the integration points named by system, the stability penalty, and acceptance criteria measured against a real week. Take it to every other firm on your list. That document is what makes four quotes comparable and what keeps a fixed price fixed.
Digital Heroes will not write code without a signed product requirements document. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under law your own counsel already reads, and you own the repository, the infrastructure and the constraint model from the first commit. Over fifty specialists, more than 2,000 projects, a named team you meet before signing, checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
We are the wrong firm for a mill running long campaigns of a few standard widths, and wrong for anything inside the quality control loop, which belongs with your automation supplier. Buy from ABB, Honeywell or Valmet for that and do not let anyone tell you otherwise.
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) →
- Across 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
Frequently asked questions
How much does trim optimisation software cost for one paper machine?
Specialist products are licensed per machine with annual maintenance, and the figure is normally a modest fraction of the trim you are currently accepting, which is why buying is usually correct. A custom first release covering the constraint model, combined trim and sequencing and a planner interface runs $90,000 to $190,000 in Digital Heroes delivery experience, with 15 to 20 percent annually thereafter.
How long does it take to build custom mill planning software?
Fourteen to twenty weeks for a first release covering one machine, the full constraint model, combined trim and grade sequencing against a money objective, and a planner interface. Nine to eighteen months for a full platform with converting, multi machine allocation and roll inventory. The schedule risk is constraint capture rather than code, because the awkward rules live with the winder crew rather than in a document.
Who owns the constraint model if an outside firm builds it?
You should own the repository, the infrastructure and the constraint definitions themselves, with an unrestricted right to hire anyone else to continue. Settle it before kickoff. At Digital Heroes the client owns the code from the first commit. The constraint model encodes years of knowledge about your machine and your customers, and it should never sit somewhere you cannot take it.
What happens if the planner does not trust the optimised schedule?
Expect several weeks of parallel running where the planner builds the schedule the usual way and compares it with the system output. Their objections during that period are the most valuable input in the project, because each one is usually a real constraint nobody wrote down. Trust arrives when the system reproduces a plan the planner would have built, then shows a better alternative with the reasoning visible.
Can we keep our existing optimiser and build only the sequencing layer?
Sometimes, and it is worth asking, but it depends on whether the incumbent will accept an externally supplied objective or return alternative solutions rather than one answer. If it will not, you end up chaining two optimisers that disagree. Where the incumbent is doing the cutting stock work well, the cheaper build is often the constraint editor and the plan versus actual attribution around it.
Should converting be scheduled in the same system as the paper machine?
Eventually yes if you own the converting operation, because scheduling them separately means one always absorbs the other's inefficiency. It roughly doubles the model, so it belongs in a second phase. Prove the constraint model and the planner workflow on the machine first. Mills without owned converting can treat downstream requirements as customer constraints rather than as a scheduling problem.
What is the difference between trim optimisation and production scheduling?
Trim optimisation solves a cutting stock problem: which orders combine into which sets across the deckle with the least waste. Production scheduling decides the order in which those sets run, which determines grade changes, broke and off specification tonnes. They trade against each other, so solving them separately produces plans that look good on one measure and cost money on the other.
Can a custom system read our quality control system and enterprise software?
Yes, and both matter for different reasons. Order intake from the enterprise system is what makes the plan real, and reading actual production, breaks and off specification tonnes from the quality control system is what makes re-planning automatic rather than manual. Ask any developer to name the specific systems and mills they have integrated, because reading Experion is not the same job as reading an older mill system.
We run long campaigns of a few standard widths. Do we need this?
Probably not. A narrow product range in long campaigns is usually close to its trim floor already, and the money is better spent on machine reliability or quality variability. The build case comes from order book variety: many widths, frequent grade changes, a varied customer mix and tolerance nobody uses deliberately. If your planner spends an hour a week on sets, the return will not justify a project.
What happens to the plan when a machine breaks mid week?
In a properly built system the current progress is already in the model, so a rebuild takes minutes and you re-plan the remainder of the week rather than nursing a stale schedule. It should also show the crew what changed between plan versions and carry a tunable penalty for churn, because an optimiser that produces a completely different schedule on every run gets switched off within a month.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Is custom supply chain software cheaper than SAP over five years?
For small and mid-size operations it usually is, because SAP costs compound through licensing, implementation partners, and per-user fees, while custom costs are front-loaded. SAP Business One's published list price has run roughly $3,200 per professional user as a perpetual license plus annual maintenance near 20 percent, and the S/4HANA proposals Digital Heroes clients share are typically in the hundreds of thousands before any customization. A $60,000 to $100,000 custom build with 15 to 20 percent annual upkeep often costs less by year three for a 10 to 30 user company, and you stop paying per seat as you hire.
What tech stack is best for custom supply chain software?
Boring and mainstream wins: a typed backend such as Node with TypeScript, Python, or C#, PostgreSQL for transactional inventory data, a React web frontend, and hosting on AWS, Azure, or GCP. Real-time needs like scanner feeds or live shipment tracking add a message queue such as Redis or RabbitMQ. Be wary of any agency pitching an exotic stack; in Digital Heroes handover work, systems built on niche frameworks are consistently the hardest and most expensive for a new team to take over.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
Who can build a custom supply chain software system?
Digital Heroes builds custom supply chain 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 supply chain 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 .