How to Hire a Pulp and Paper Mill Production Software Development Company
Buy the firm that asks about your winder before it asks about your dashboard. Trim optimisation is settled mathematics; the project risk is your constraint set and whether the machine crew trusts the output.
On this page
Buy the firm that asks about your winder before it asks about your dashboard. Trim optimisation is settled mathematics; the project risk is your constraint set and whether the machine crew trusts the output. A first release covering order combination, trim and grade sequencing on one machine runs $90,000 to $190,000 in 14 to 20 weeks. Long campaigns of standard widths do not need this.
It is Tuesday afternoon and the planner is building next week for PM3. Deckle is 6.2 metres, the order book has nineteen live orders across four basis weights, and every set he builds carries 90 to 150 millimetres of trim. He knows a better combination exists. He also has an hour before the schedule goes to the machine, and trying an alternative means redoing everything downstream by hand. So the mill accepts a loss that nobody in that building would approve if it were presented as a line item in a meeting.
The hard part of buying here is that the mathematics is not the risk. Cutting stock is a solved problem and any competent firm can solve it. The risk is that you commission an optimiser whose constraint set goes stale in eight months, at which point the schedules stop matching what the winder can actually run and the crew quietly reverts to the spreadsheet. That failure is silent, it happens after the developer has invoiced, and it is how most mill optimisation projects die.
What a mill production software company actually does
The visible deliverable is a planning screen showing sets and trim percentages. Everything that determines whether it survives is elsewhere.
It is modelling your winder honestly: knife count, minimum reliable roll width, maximum set count, roll diameter limits at the customer, core sizes that let two orders share a set, and which accounts will accept a splice. It is the sheeter downstream and which widths force a changeover. It is delivery tolerance carried per order line as a real bound with a customer-specific policy, because some accounts are delighted with over-delivery and others will reject it. It is a single objective expressed in money, so trim loss, grade change cost, earliness and lateness are comparable and a planner can see that this set costs 40 millimetres more trim but avoids a basis weight change. It is order intake from your ERP (Enterprise Resource Planning) and schedule delivery to wherever the crew actually reads it. And it is a change penalty, because a plan that churns hourly is worse than a slightly suboptimal one the crew believes.
What a build really costs in 2026
These bands reflect Digital Heroes delivery experience. Hand the same table to every firm you are considering.
| Scope | Cost | Timeline |
|---|---|---|
| One machine: order combination, trim and grade sequencing, planner interface | $90,000 to $190,000 | 14 to 20 weeks |
| Full platform: converting and sheeting, roll inventory, multi machine allocation, order promising | $250,000 to $600,000 | 9 to 18 months |
| Plan versus actual attribution and order book scoring | Add $25,000 to $60,000 | 4 to 8 weeks |
| Support, constraint changes and machine rebuild updates | 15% to 20% of build per year | Retainer |
Two costs are almost never in the quote. The first is solver licensing. A commercial mixed integer solver carries an annual licence that renews on your invoice for the life of the system, and the developer rarely mentions it because it is not their line item. Open solvers exist and are genuinely capable at this problem size, but they trade solve time for cost. Make the firm state which solver the design assumes, what it costs annually and what the solve time looks like on your real order book, in writing.
The second is the last mile to the machine. Reading orders out of SAP is straightforward. Getting the schedule to the crew in the form they already use, whether that is a printed set sheet, a screen on the floor or an interface to the quality control system, is bespoke work at every mill and it is where projects quietly overrun. Ask what the crew sees on Monday morning and who builds it.
What separates a serious firm from a hopeful one
- They ask what your planner does after the optimiser runs. The manual work either side of the tool is the real problem, and a firm that does not ask has not seen a mill.
- They insist the planning team can edit constraints. A constraint set maintained by a vendor becomes stale, and stale schedules get ignored.
- They express the objective in money, not millimetres. Trim percentage alone produces schedules with excellent trim and terrible economics.
- They treat tolerance as a variable. Most orders carry a delivery tolerance and almost nobody uses it deliberately.
- They will tell you to buy Greycon instead when that is the right answer. If your problem is pure cutting stock with no awkward downstream constraints, opt-Studio is the specialist and it is good.
- They design for re-planning to be cheap. Daily rebuilds beat a weekly plan that drifts from the day it was made.
- They score the plan afterwards. Comparing achieved trim against computed best possible for the same order book is what eventually changes what sales accepts.
Red flags on a mill project
- A demo on synthetic order data. Ask them to run last month's real book. Awkward widths are the whole point.
- No questions about the winder. If the conversation stays on the machine deckle, they are solving a textbook problem.
- A fixed price quoted in the first meeting. Nobody can scope your constraint set from a phone call.
- Optimisation presented as a black box. If the planner cannot see which constraint bound the solution, they will not defend it to the machine superintendent.
- No plan for the day the optimiser is wrong. There has to be a manual override that logs the reason, or the crew builds a shadow system.
Nine questions for the first call
- Which solver does your design assume, what does it cost annually, and who holds that licence?
- Run our real order book from last month. What trim do you get, and how long did the solve take?
- How do you price a basis weight change in the objective, and where did that number come from?
- Show me how the planner compares two candidate schedules and sees the difference in money.
- Who edits the constraint set after handover, and what does that screen look like?
- Our tolerance is around plus or minus ten percent but two accounts refuse over-delivery. How is that modelled?
- What does the crew see on Monday morning, and who builds that output?
- How does the system behave when the machine breaks and eight hours vanish from the plan?
- What do we own on the last day, including the constraint model and the objective weights?
How to decide without a leap of faith
Do not buy a build. Buy a discovery phase and a benchmark. Pay two firms four to six weeks each and require the same deliverable: a written constraint model for one machine, an objective with each cost term sourced and justified, a solve against three months of your historical order book showing achieved trim against computed best possible, and a fixed quote against a work breakdown. That benchmark is the only honest evidence you will get, and the constraint document is worth having even if you never build.
Digital Heroes is the wrong partner if you run long campaigns of a handful of standard widths. Your trim is already near the floor and a project would be indulgent. We are also not the right answer if your problem is pure cutting stock with no converting complications, because a specialist product will beat a build on time to value. Where we fit is the mill whose constraints live outside every packaged tool. 50-plus team, 2,000-plus projects delivered, PRD-first so the written specification exists before code, Fiverr Vetted Pro, and contracting through an India LLP, US LLC or UK LTD so IP assigns under your own law. Verifiable through D-U-N-S, Clutch and Trustpilot.
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.
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
- McKinsey Global Institute estimated that about half of all work activities globally have the technical potential to be automated by adapting currently demonstrated technologies, though few occupations can be fully automated. Source: McKinsey Global Institute (2017) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
Frequently asked questions
How much does mill production and trim optimisation software cost to build?
A first release covering order book combination, trim optimisation against real deckle and winder constraints, and grade change sequencing on one machine runs $90,000 to $190,000 over 14 to 20 weeks. A full platform adding converting and sheeting constraints, roll inventory, multi machine allocation and order promising runs $250,000 to $600,000 across 9 to 18 months. Support runs 15% to 20% of build per year.
Should we buy Greycon opt-Studio instead of building?
If your trim problem is a clean cutting stock problem, yes. opt-Studio is the genuine specialist and it solves that well, and a build will not beat it on time to value. The case for building appears when your converting constraints, tolerance policy and order intake habits sit outside the tool, so the planner still does manual work on both sides of the optimiser and the benefit never fully lands.
What is the biggest hidden cost on a mill software project?
Two compete. Commercial solver licensing renews annually on your invoice for the life of the system and is rarely named in a quote. The other is the last mile: getting the schedule to the machine crew in the form they already use, whether that is a printed set sheet or a floor screen. Both are avoidable surprises if you make the firm write them down before you sign.
How do we stop the crew ignoring the optimiser?
Give the planning team the ability to edit constraints themselves, and make the system show which constraint bound each solution. A schedule the crew cannot interrogate gets treated as a suggestion. Add a manual override that records the reason it was used, then review those overrides monthly. They are the most useful list you will have, because each one names a constraint the model got wrong.
Who owns the constraint model and the objective weights?
You should, in full, with source code in your own repository and the constraint model held as editable data rather than compiled logic. The objective weights encode your commercial judgement about what a grade change actually costs, which is proprietary knowledge about your mill. Insist on written documentation of every cost term and where its value came from, delivered as a named milestone rather than at the end.
How much does custom supply chain software cost for a small business?
For a small business, a focused custom supply chain tool usually lands between $15,000 and $45,000, covering one core workflow like inventory tracking, purchase orders, or shipment visibility. Across 2,000+ delivered projects, Digital Heroes sees most small distributors and light manufacturers start in the $20,000 to $35,000 range for a first working version. Adding barcode scanning, multi-warehouse support, or carrier integrations pushes budgets toward $50,000 and up.
Will custom software scale as we add warehouses, SKUs, and order volume?
Yes, if multi-location support and your target volumes are stated requirements at design time, because a schema built for one warehouse is expensive to retrofit for ten. A well-built system on PostgreSQL comfortably handles millions of SKUs and tens of thousands of orders per day on modest cloud hardware, so scaling cost shows up in hosting bills rather than rewrites. Give your agency the 3-year growth picture upfront even if phase one covers a single site.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
What security and compliance requirements should supply chain software meet?
At minimum: role-based access control, encryption in transit and at rest, audit logs on inventory and order changes, and tested backups, because the system holds supplier pricing and customer purchase history your competitors would love to see. If enterprise customers connect to it, expect security questionnaires and possibly SOC 2 expectations; food, pharma, and aerospace add traceability rules like FDA lot tracking or ITAR data handling. Raise these in the first scoping call, since retrofitting audit trails onto a live system costs far more than designing them in.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
Should I hire a freelancer or an agency to build supply chain software?
For anything past a single-user internal tool, use an agency or an established team, because supply chain systems need backend, frontend, integration, and QA skills that rarely live in one freelancer. A solo developer can build a $10,000 inventory tracker; a system that talks to your ERP, carriers, and warehouse scanners fails badly when its only author is unreachable during a shipping cutoff. In the proposals Digital Heroes sees clients compare, agencies cost 20 to 50 percent more but give you continuity, code review, and someone answerable when order data stops flowing.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
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.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Should we start with an MVP or build the full supply chain platform at once?
Start with an MVP that fixes your single most expensive workflow, prove it in daily operations, then expand module by module. That gets working software onto the warehouse floor in about 12 weeks instead of debating a year-long spec, and real usage always reorders the roadmap; features that felt critical in planning routinely get cut after go-live. Digital Heroes typically scopes phase one at 30 to 40 percent of the total vision and lets measured results justify each next phase.
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 .