How ARCIFAB Bid works

WHO MAKES IT

We already priced and won work.

We ran the shop and the business. We have sourced the job, built the number, sent the proposal, and lived with the ones that came back wrong. Bid comes out of that experience, by people who have had to sign a bid.

That is also why the evaluation comes first. We look at how you already win work and shape Bid around it. Your operation does not get bent to fit the software.

THE ORDER

Two parts, in that order.

Evaluate the operation

Where the leads actually come from. What the estimate is really built on. Who types the proposal, and what breaks when they are out. What happens to the pricing work after the job is won.

Stand up the system

Your own system, with your name on it, set up with your rates, your assemblies, and your proposal format. Then your people work in it and we keep it running.

We run the same steps for every product.

Bid is one of the three products we start from. The six steps we run, from evaluation through ongoing support, do not change depending on which one you need.

See how we work →

THE EVALUATION

What we look at first.

Where the work you are chasing actually lives.

Invitations land in an inbox, a folder, a shared drive, sometimes a whiteboard. We want to see the real one. What gets described on a call is never quite it.

Robotic pipe welding cell in a fabrication shop

How a number gets built today.

Which tool holds the quantities, which one holds the rates, and who moves the figures between them. We ask to watch a real bid go together rather than hear the process described.

Racked pipe stock and gas bottles in a fabrication shop

Who types the proposal, and from what.

Usually one person, usually the afternoon it is due, usually from a document that is already the second or third version of the same numbers. That is the step that tells us how much of this is a system and how much is one person remembering.

THE STEPS

Six steps, every time.

1

Initial Evaluation

We sit down and hear how the work actually moves. There is no feature tour.

2

Walkthrough

We document how you already bid, price, and build, from the first job you chase to the last piece that ships.

3

Roadmap & Proposal

A plan written for this operation and only this one, in place of a generic implementation deck.

4

Implementation

Your system, with your name on it and your data in it.

5

Go-Live

Two days on site at launch. We stand it up with the people who will use it.

6

Ongoing Support

Hosting and development. We keep the system running. You keep the work.

THE PATH

Same order, every operation.

Evaluate

Walkthrough

Roadmap

Stand it up

Go-live

Support

Bid gets set up after we have seen how you bid, not before.

WHAT YOU END UP WITH

A dedicated system, running your way.

Your own system

Your data sits in your own system, separate from every other shop’s. Nobody else is on it.

Your name on it

Your people open your system. The proposal that goes out carries your name, not ours.

We keep it running

In-house IT you do not have to train. You keep chasing and winning the work.

DAY ONE

What we will not do on day one.

No feature tour before we have heard how you chase work.

No price before we understand the bid.

No forcing your assemblies into a shared template.

No second brand on the login screen.

Evaluate the bid.
Then stand up the system.

We already priced and won work.

Two parts, in that order.

Evaluate the operation

Stand up the system

What we look at first.

Where the work you are chasing actually lives.

How a number gets built today.

Who types the proposal, and from what.

Six steps, every time.

Initial Evaluation

Walkthrough

Roadmap & Proposal

Implementation

Go-Live

Ongoing Support

Same order, every operation.

A dedicated system, running your way.

Your own system

Your name on it

We keep it running

What we will not do on day one.

It starts with the evaluation.

Lite

Why Bid