“Software never fits how we actually work.”
Every plant says it — and after the last system, they earned the right to. So this page skips the pitch. Below are the four objections we hear on every first call, each one settled in front of you: live, on a settings screen, without a line of code.
What makes Bulk's platform configurable?
Bulk is manufacturing-ops software you shape to how your plant already works instead of the other way round. Job numbering, routings with rework loops, per-site setups, and new fields are all settled on a settings screen — live, by your own team, without a line of custom code or a consultant.
Four objections. Four live proofs.
These come up on almost every call. Each one is answered the same way it would be in the demo — by doing the thing, right here, while you watch.
“Our job numbers are sacred. Customers quote them back at us.”
“We have a rework loop nobody's software understands.”
“Site two works completely differently to site one.”
“Last time, every change cost us a consultant.”
- Add "Heat number" field to jobs
- Estimate: 6 weeks · scoped & quoted
- Deploy: next release window
Objection bingo.
Every square on this card has been raised on a real call — and settled on a settings screen. The middle one is yours.
“We walked in convinced our process was too weird. It was configured before the call ended.”
Questions, answered.
What makes Bulk's platform configurable?
You change how it works on a settings screen, not in code. Numbering schemes, routings, per-site setups, and fields are yours to adjust live — the same way they would be settled in a demo, by doing the thing while you watch.
Can we keep our own job numbering scheme?
Yes. You pick your scheme — prefixes, dates, counters — and the job traveller re-stamps itself to match. Your numbering is kept exactly, so customers still get the IDs they quote back at you.
Can it handle a rework loop our last software could not?
Yes. Loops, branches, and conditions per part and cert class are a routing you draw, version, and change on a screen. Fail an inspection and the routing branches back to an earlier step, no custom development required.
Our second site works completely differently. Can one system run both?
Yes. Boards, pillars, numbering, units, and downtime reasons are configured per site on the same engine. Neither plant blocks the other, and control stays at the top.
Will every change cost us a consultant?
No. Fields, forms, statuses, and templates are changed by your own team, live, with no release cycle. Adding something like a heat-number field is a setting, not a scoped-and-quoted change request.
Do we need to write code to configure Bulk?
No. Every objection on this page is settled on a settings screen without a line of custom code — from numbering and routing to per-site setups and new fields.
Stop paying the hidden invoice.
The workarounds, the shadow spreadsheets, the six-week change requests — send us your worst one and watch it become a setting.