When we started building FabCommand, we wanted to disrupt something.
We still feel that there are parts of steel fabrication software that deserve to be disrupted. Too many disconnected systems. Too much duplicate entry. Too many spreadsheets filling the gaps between programs that were supposed to eliminate spreadsheets in the first place. Software that requires weeks of training. Software that seems to expect the shop to change the way it works just to accommodate the software.
That needs disruption. In less fancy words, it needs to change and get better.
Somewhere along the way, we realized something ironic. Our real goal is for FabCommand to become the least disruptive software in the steel shop.
A steel fabrication shop is not a controlled environment. Drawings change. RFIs come back late. Material shows up early, late, or wrong. A truck needs to leave tomorrow. A customer changes the sequence. The field needs an answer.
Someone needs to know where a piece is, whether it has been fabricated, whether it has been painted, whether it is on a truck, and whether the change that affected it was ever priced. That is not an exception. That is just a normal day in a steel shop.
The last thing anybody needs is software creating another problem to solve.
We think that is where a lot of fabrication software has missed the mark. The software may be powerful, but the implementation is painful. The training takes forever. The workflows are rigid. The shop has to adapt to the software instead of the software adapting to the shop.
When somebody searches for easy-to-use fabrication software for a steel shop, we doubt they are really asking for fewer buttons or a prettier dashboard. They are asking whether their people will actually use it.
What they are really asking
That is what easy to use means to us.
A change order should be tied to the project it belongs to. An RFI should not disappear into somebody's inbox. A truck list should make sense. Production status should be easy to find. Project financials should not feel elusive. The schedule, project information, changes, and shop activity should not all live in completely different places.
None of that sounds revolutionary, and that is kind of the point.
Good software should make the operation feel simpler, not make the software itself feel important.
The longer we build FabCommand, the less interested we are in creating software that feels impressive and the more interested we are in creating software that feels obvious.
Does somebody need a manual to figure it out, or does it mostly make sense? Does it interrupt how they work, or does it fit into how they already work? Does it create another place to manage information, or does it start eliminating some of the places they have to manage it now?
Nobody walks into the shop talking about how revolutionary the software is. The estimator just knows where to go. The project manager knows where to go. The shop knows where to go. Management can see what is happening without chasing somebody down.
The software starts to disappear into the operation. And that is success.
FabCommand keeps jobs, schedules, changes, and shop activity in one place, without the months of setup. Start free, no contracts and no sales calls.
Start Free Trial