Opportunities › Enterprise manufacturing software implementation and support › Proposed app
Benchfloor
Source-open ERP for small plants moving off Dynamics GP and add-on shop software
- Score
- 39
- confidence 42
- Evidence
- 5
- items on the page
- Rivals
- 3
- named in sources
- First version
- 90 d
- estimate
- Type
- Desktop and mobile
- PWA: on computers and phones alike
- Market since
- 2005
- Mature market · AI estimate
ScreensConcept
Desktop and mobile: Planners work on orders and inventory at a desk, but shop-floor workers count stock and release work orders from the floor on a phone. Sample screens on a computer and a phone, in the proposed brand. Their numbers are sample data.
Import check
118 items need review94%
About this appAI proposal
Benchfloor is a manufacturing ERP that puts orders, inventory, bills of materials, work orders and the general ledger in one place. It is meant for plants that run an older ERP such as Dynamics GP next to separate shop-floor software and want to consolidate.
Setup is guided. An import checker maps your item, customer and ledger data, flags gaps, and lets you rehearse the cutover before going live, so you need less outside consulting. The source code is readable on every tier, including the lowest.
Core manufacturing modules are not held back for higher plans. Tiers differ by support and hosting, not by whether you can plan production or track stock.
- Tagline
- One system for the whole plant, with the code in plain view.
- Voice
- PlainPracticalOpenSteady
- Why this name
- A bench and a floor are where manufacturing work happens. The name is two plain words that say the software sits where the work is.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Guided data import
Upload exports from your old ERP and shop software. Benchfloor maps fields, flags mismatches and shows what will break before anything goes live.
No member yet
Rehearsal cutover
Run a full practice migration in a sandbox, compare balances to your old books, and repeat until the numbers match.
No member yet
Bills of materials and routings
Build multi-level BOMs and routings, then release work orders that reserve stock and schedule steps.
No member yet
Inventory and lot tracking
Receive, move and count stock by location and lot, with counts done from a phone on the floor.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F4D45Forge Green · primary#F6F3ECPaper · surface#1E2321Graphite · text#C4672DCopper · accent#A9B8B3Steel Mist · data
Typography
Aa
Benchfloor
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
One system for the whole plant, with the code in plain view.
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test, built on the claim that core features are gated behind premium tiers elsewhere.
Community
Free
- Full source code
- Core manufacturing modules
- Self-hosted
- Community forum
Plant
$600 a month
- Hosted for one plant
- Guided import and rehearsals
- Email support
- Backups and updates
Managed
$1800 a month
- Up to 3 plants
- Named support contact
- Customization layer review
- Priority fixes
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. An ERP is a back-office system used by one company's staff. Its own use does not reach other companies, so growth comes from sales, content and implementation partners.
- Do they become customers?
- Test whether plant managers will pay for a rehearsal migration before committing. Open source users may also self-host and never convert, so paid conversion needs measuring.
- First customers
- Small discrete manufacturers (20 to 100 staff) in one vertical, such as metal fabrication, running Dynamics GP plus separate shop-floor software.
- Where to reach them
- Dynamics GP user communities: Offer a free import check of a plant's own export and show what would move cleanly.
- Hacker News and open-source forums: Publish the source and a migration write-up to reach technical operators and consultants.
- Independent ERP consultants: Give them a fixed-price path so they can implement without long projects.
- First milestone
- Five plants in one vertical pay for a rehearsal migration, and two go live within 90 days.
Why people already pay for this
- AI inferenceManufacturing businesses are evaluating ERP switches to consolidate multiple systems and reduce support contract costs.
- Public claimEnterprise ERP implementations require specialized expertise that may be difficult to access.
- Public claimProprietary competitors do not offer source code visibility, creating differentiation opportunity.
- Public claimCore manufacturing features are gated behind premium pricing tiers in leading products.
- Public claimOdoo states on its own website: 28 million users
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Background jobsQueue worker for imports and cutover rehearsalsLarge data imports and balance comparisons run too long for web requests.
- This app · File storageObject storage for uploaded exportsLegacy exports and import reports need to be kept and re-run.
RisksAI inference
- TechnicalERP scope is huge. Costing, ledger rules and multi-level BOMs must be correct before a plant trusts it with its books.
- CommercialPlants switch ERPs rarely and slowly. Sales cycles may be long and need a person to guide the first customers.
- DataLegacy exports vary widely. Import mapping for Dynamics GP and shop software may need much hand work at first.
- CommercialOpen-source ERPs already exist, and the material says one offers source to paying customers. Differentiation rests on easier setup, which is untested.
- RegulatorySome plants need audit trails, lot traceability or tax rules for their sector. Gaps could block adoption.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.