Your planner, your real hot lists, 30 days
The quickest way to find out whether Unbrick helps your shop is to use it on the lists you are answering anyway. We measure it together, from your own records.
Connect
A sample export and one working session to map it, about an hour. The connector installs in under an hour.
Run real lists
Your planner answers each hot list in Unbrick and an approver signs off. A short weekly check-in with us.
Decide together
We go through the scorecard with you, and you decide whether to continue.
From your own records, not estimates
- Time per list: from import to approval, from timestamps.
- Was it useful? Asked of the approver at each approval.
- Did the dates hold? Each issued plan against what actually finished.
- What would the engines have done? A backtest of each plan engine on your own earlier days: deliveries, date error, day-to-day churn.
- Data quality and support: refused loads, rows that needed a person, the time we spent helping.
No borrowed numbers. We don’t quote demo-plant results as yours. The pilot measures your shop.
What we need from you
A sample export
Any CSV reports your ERP already produces, before the mapping session.
Your planner
An hour for the mapping and the first list, then about 30 minutes a week.
An approver
Someone who signs off each answer before it goes to the customer.
Your IT contact
To schedule the export and install the connector.
Is it a fit?
Who is Unbrick for?
Make-to-order machine shops with multi-level bills of material, lots moving through departments and outside processing, where labor sets the pace, and a big customer sends a weekly hot list.
Which ERPs work?
Any that can export reports to CSV on a schedule. The mapping is drafted from your files and confirmed by a person who knows your ERP.
Is it real-time?
No. It plans from a nightly snapshot that is checked before it is used. For answering a weekly hot list, a complete and consistent copy of last night’s data is what you want.
Does it optimize the schedule?
It plans finite capacity forward. Solver engines propose orders of work and staffing moves; each proposal is rerun on the whole plan and scored beside today’s, and a planner adopts it or not. The pilot’s backtest shows what each would have done on your data.
Do we get the plant map in the pilot?
Yes. Everything on the product tour runs on your data from the first good load, including the plant map, order journeys and plan engines.