Furniture Manufacturing Software: Katana, or a Custom Configurator?
One question settles this: is your product catalogue or configurable? If a dealer orders a fixed model in one of six finishes and you build to stock or near stock, buy Katana or Fishbowl Manufacturing and spend the difference on a second machining cell.
On this page
One question settles this: is your product catalogue or configurable? If a dealer orders a fixed model in one of six finishes and you build to stock or near stock, buy Katana or Fishbowl Manufacturing and spend the difference on a second machining cell. The tell that you have outgrown them is a stock keeping unit (SKU) count in the hundreds representing what are really variants of thirty products, which means your item master is fighting your product. At that point a configurator with a real constraint engine, bill of materials (BOM) resolution and a dealer portal runs $60,000 to $130,000 in 12 to 16 weeks. Below roughly $8M of revenue, or with an order book thinner than your capacity, buy regardless.
When is off the shelf genuinely the right call here?
Buy if your product is genuinely catalogue. A dealer orders a fixed model in one of six finishes, you build to stock or near stock, and Katana or Fishbowl Manufacturing on their published plans is the correct answer. A custom configurator at that profile is vanity, and the money returns more in a second machining cell.
Buy under roughly $8M of revenue, and buy whenever your constraint is the order book rather than operations. Software does not fill an empty schedule, and a six figure build servicing a thin backlog is how shops end up with excellent systems and no work.
Buy the accounting under all circumstances. Nobody should be paying to rebuild a general ledger. Sage 100, QuickBooks Enterprise and NetSuite are cheaper, better tested and audit friendly, your controller already knows them, and any custom system should post to one of them rather than replace it.
Buy your nesting and cut list software too. Cabinet Vision, Microvellum and Mozaik do real work driving your machining cells, and rebuilding that is not a project any furniture manufacturer should fund. The question in this category has never been whether to replace them. It is whether the rules that decide what can be built belong in a product or in your own system.
When does a custom build actually pay off?
The signals arrive together and most owners recognise three of them immediately. A human being is effectively the configurator, meaning there is a person whose retirement would be an operational crisis because the rules live in his head. You have created hundreds of SKUs to represent variants of thirty products. Quoted margin and actual margin diverge on custom work and nobody can explain it by option. The finish room or another batch resource is your constraint and your scheduling tool cannot represent batching or cure time. Order entry headcount grows with revenue, which means you are scaling typing.
The configurator case is the sharpest. Furniture rules are not flat. They are dimensional and conditional: joinery valid only above a given thickness, a finish not certified over a given substrate, a drawer slide rating that changes when depth exceeds a threshold, a stain that reads differently on rift white oak than on plain sawn. Encoding that in a rules grid built for flat attribute lists means you either simplify your product line or push the truth back into somebody's head.
The costing case is quieter and it is often what pays for the whole thing. Standard costing rolls the finish room in as an overhead allocation per unit, so you learn that an order made thirty one per cent and never learn that it is forty four on the standard configuration and four on the custom stain. You keep quoting the custom stain at an uplift you set years ago, and it keeps losing money precisely because it is your differentiator.
How do they compare on the things that matter in this industry?
Rule expression. Katana and Fishbowl model options as flat attribute lists with include and exclude rules. That is a genuine configuration ceiling rather than a missing feature, and it is why conditional joinery and finish over substrate restrictions end up in a spreadsheet or in an engineer's memory.
Scheduling model. Off the shelf schedulers treat the finish room as a work centre with capacity in hours, the way they would treat a machining cell. Furniture finishing is a batch resource with sequence dependent changeover plus cure time that consumes rack space regardless of labour. Nothing packaged understands that spraying dark after light is nearly free while light after dark costs a purge.
Cost attribution. No packaged system carries the causal chain from a configuration option to consumed booth minutes to yield loss. Option level margin needs that chain, and it is the report that reprices two or three options and kills one.
Integration burden. Nesting packages are file driven rather than interface driven, so a build writes part lists or exchange files into watched directories. It works reliably once built and it is the single most common place a project slips, which is a cost of building rather than a criticism of the tools.
Where the products win. Inventory, purchasing, standard costing and years of encoded behaviour, at a monthly price you can cancel. That is real and it is why most shops should stay.
What does total cost of ownership look like at your scale?
A focused first release covering the configurator with a constraint engine, BOM resolution at quote time, quote to order and a dealer portal runs $60,000 to $130,000 in 12 to 16 weeks. A worked $45M case goods maker with two plants, roughly fifty base models and eight option dimensions lands at $114,000 across fourteen weeks. Phase two, adding finish room batch scheduling with a changeover matrix, shop floor scan events, piece level identity, option level costing, purchasing against long lead items and a posting interface, is $163,000, so the platform totals $277,000. Drop upholstery and one plant and the same shop lands near $190,000.
Option tree depth drives that number more than revenue, headcount or plant count. Forty base models with four independent option dimensions prices near the bottom. The same forty with twelve conditional dimensions roughly doubles the configurator work.
Running costs are 15 to 20 per cent of build for the first two years, so $17,000 to $23,000 against a $114,000 release, settling lower as the rules stabilise. It covers hosting, a retainer for seasonal rule changes and new species or hardware lines, and re testing the accounting and nesting interfaces after vendor upgrades. Two lines get missed: label printers and scanners wear out in a dusty building, and somebody has to own the option model as a named responsibility.
The comparison against a subscription is not the licence line. It is the payroll that exists only because the software cannot do the job, plus the orders that bounce to engineering and restart, the expedited freight on late ship dates, and the options quoted at an uplift nobody has revisited.
There is a third number that never appears in a proposal, and it is the rebuild. If the configurator is scoped as a flat attribute list because that looked cheaper in month one, you buy the constraint engine again in year two. In our delivery experience that redo costs more than the original, because by then you have live dealers, live orders and several thousand historical configurations that all have to be migrated onto the corrected model rather than typed into an empty one.
What does the hybrid look like, and when is it the honest answer?
The hybrid is the default in this category and it is not a compromise. Keep Sage or QuickBooks Enterprise for the money. Keep Cabinet Vision or Microvellum for nesting. Build the configurator, the BOM resolution and the dealer portal, and let the resolved BOM be the object that drives purchasing and the cut list so nothing gets retyped downstream.
Ship the revenue side first. The configurator stops orders bouncing back to engineering for rule violations and stops your order entry team retyping dealer purchase orders, and both are visible within a quarter. It also produces the resolved BOM that everything downstream depends on, so the shop floor and costing phases cannot be built well without it.
Inside phase two, take finish room scheduling first because it is the constraint, then scan events and piece identity, then option level costing last. Costing needs several weeks of real scan data before its numbers mean anything, so building it early spends the money twice.
Two scope decisions keep the total down. Prune before you scope: pull last year's order lines by option and retire the ones nobody ordered, because every retired option is a rule that never gets modelled, tested or maintained. And limit dealer document ingestion in phase one to the handful of dealers sending most of your lines rather than mapping sixty forms at once. The remaining dealers keep sending paper for another few months and nothing breaks.
Where the hybrid is not the honest answer is a single plant with a stable catalogue and a healthy backlog. In that shape the packaged tools genuinely fit, and a build would give you a more precise version of a process that is already working. Say no to yourself before a developer has to.
Which should you choose, by operator size and stage?
Catalogue product, build to stock, any size: buy. Katana or Fishbowl, tuned properly, and put the money into machinery.
Under $8M with a configurable line: buy, and prune. Retiring dead options and writing the rules down is work you can do this quarter at no capital cost, and it is the same exercise a build would start with. Revisit when the order book justifies it.
$8M to $30M, one plant, case goods only: build the first release. The configurator, BOM resolution and dealer portal is a $60,000 to $130,000 project, it holds the rules that currently live in one person's head, and it pays back through fewer engineering bounce backs and less retyping.
$30M or more, two plants, or upholstery alongside case goods: build in phases and scope upholstery as its own budget line. Yardage, railroad direction, pattern repeat and customer's own material handling form a subsystem with its own receiving and hold logic, and folding it into the main configurator estimate is consistently the line that overruns.
Anyone whose engineering lead retires within three years: build now, and treat the discovery workshop as the deliverable rather than the software. Getting the rules out of his head and into a typed option model is the asset. The system around it is how you keep it.
If you would rather someone argued with your brief than agreed with it, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- 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) →
Frequently asked questions
What does it cost to leave Katana or Fishbowl once we build a configurator?
Very little, because you are unlikely to leave. Most shops keep an inventory and purchasing product alongside the configurator and simply stop using its option handling, so the exit is a scope reduction rather than a migration.
The data that matters most, your option model and the historical cost by option, is created by the build rather than extracted from the incumbent. That is worth noting when negotiating: in furniture the option model and cost history are the real asset, often more valuable than the code itself.
What happens if our manufacturing software vendor changes its pricing?
Run it against three years and include the modules you pay for separately, the annual implementation or consultant retainer and the connectors between systems, because the headline subscription is rarely the whole bill.
Owning the configurator changes what a price rise costs you. The seats you keep paying for become inventory and purchasing seats rather than the system your dealers quote through, and the rules that define your product line no longer sit inside a product you might have to leave.
How long does a furniture manufacturing build take, and when can we go live?
Twelve to sixteen weeks for the configurator, BOM engine and dealer portal. Discovery and option modelling takes the first three weeks and needs your engineering lead genuinely available rather than nominally assigned.
The part that slips is migration out of the Excel pricing workbook, because rules buried in nested formulas surface as questions nobody has answered in years. Budget 3 to 5 weeks for that and run it in parallel from about week eight rather than treating it as a final step.
Is Katana or Fishbowl good enough for a configurable furniture manufacturer?
They are good enough if your product is genuinely catalogue, and they encode a great deal of inventory and purchasing behaviour for a monthly price you can cancel. Keep them for that.
They break when your configurations are conditional, because both model options as flat attribute lists and cannot express rules like joinery valid above a given thickness or a finish restricted by substrate. The tell is hundreds of SKUs faking variants of thirty products, at which point you are paying a subscription and paying people to work around it.
How much does integrating Cabinet Vision or Microvellum add?
Plan on $18,000 to $25,000 and several weeks of calendar time. These are design and nesting tools rather than systems of record, so integration means writing part lists or exchange files into watched directories and reading results back.
It is reliable once built and it is the single most common place a project slips, because the file formats have quirks that only appear against real parts. Ask any developer to name the specific mechanism and show you one they have shipped before accepting a fixed price on that line.
Why does adding upholstery raise the price so much?
Because cutting fabric is a separate subsystem rather than an extra option dimension. Yardage, railroad direction and pattern repeat all have to be validated against the frame's requirement before anyone cuts, and customer's own material arrives from the client with no replacement if it is cut wrong, which means its own receiving, hold and approval logic.
Scope it as a distinct phase with its own budget rather than assuming it rides along with case goods. Shops that fold it into the main estimate consistently find it was the line that overran.
Can we phase the spend instead of committing to a full platform?
Yes, and you should. Ship the configurator, BOM engine and dealer portal first for $60,000 to $130,000, run it for a quarter, and let the reduction in engineering bounce backs and retyping make the case for phase two.
Inside phase two, take finish room scheduling first because it is the constraint, then scan events and piece identity, then option level costing last. Costing needs several weeks of real scan data before its numbers mean anything, so building it early wastes the money twice.
What is the cheapest useful version we could build?
The configurator with a constraint engine and BOM resolution, without the dealer portal, sitting beside your existing inventory product. That is the bottom of the band and it takes the rules out of one person's head, which is the risk you are actually carrying.
Before spending anything, do the pruning exercise. Pull last year's order lines by option and retire what nobody ordered. Shops that do this before kickoff routinely take a fifth off the configurator scope without losing a single sale, and it costs nothing but an afternoon.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
How long does custom ERP development take?
Plan on 3 to 4 months for the first working module and 6 to 12 months for a full multi-module rollout. In Digital Heroes delivery experience the schedule risk is data migration and integration testing, not feature coding, so we stage go-lives module by module instead of one big-bang launch.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
What does it cost to maintain a custom ERP each year?
Budget 15 to 20 percent of the original build cost per year, so a $150,000 ERP needs roughly $22,000 to $30,000 annually for hosting, security patches, integration upkeep, and small improvements. Across Digital Heroes maintenance contracts, third-party APIs changing is the biggest recurring work item. That total still usually sits well under the license bill for a comparable NetSuite or Dynamics seat count.
What mistakes kill ERP projects most often?
The three we see most in rescue work at Digital Heroes: recreating the old system's broken process in new software, launching everything at once instead of module by module, and having no single internal owner with authority to decide. A fourth is skipping the parallel run on data migration to save two weeks, which trades a short delay for months of distrust in the numbers. None of these are technical failures, which is why vendor selection should weigh process discipline over demo polish.
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.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
What should I prepare before contacting an ERP development agency?
Bring a list of your current tools and spreadsheets, a rough map of how an order or job moves through the company today, your user count by role, and the three problems costing you the most hours. You do not need a formal specification; a good agency writes that with you during discovery. Companies that arrive with those four things typically cut two to three weeks off scoping in our experience.
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.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
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
More from Aisha.
Project Manager · UK · London · 3 posts on the site
Published · Last updated .
