[ Pricing ]
Three plans.
One gate that never moves.
Every deployment is its own isolated instance on your infrastructure, with your identity provider and your bid sources, so the amount is quoted rather than listed. Everything else on this page is specific.
Plans
- One DeskOne or two estimators carrying every pursuitReads the setQuoted per deployment
Every document and addendum read and cited before anyone starts pricing. It never drafts.
- Tender intake from Outlook and connected bid sources
- Close calendar and pursuit workspace opened for you
- Every finding cited to its document and page
- Dates, conflicts, LDs and alternates flagged
- Most estimating teamsThe DepartmentAn estimating team working several pursuits at onceRuns the bidQuoted per deployment
The whole cycle drafted end to end, stopping at a person before anything leaves the office.
- Everything in One Desk, plus Bid / No-Bid scoring
- Cited equipment BOM with installed labour hours
- Vendor RFQ packages, and follow-ups on every open quote
- Leveling with each stated total reconciled
- Budget workbook, proposal and readiness check
- The Whole YearPreconstruction run as a portfolio, not a queue of jobsRuns the yearQuoted per deployment
Keeps running after you submit, so buyout, debrief and history feed the next number.
- Everything in The Department, through submission and past it
- Buyout drafts, purchase orders, bonds and turnover
- Loss debrief and bid-to-win gap across pursuits
- Cost library, GC scorecard and vendor history
What each one covers.
Nineteen lines, not a spreadsheet. The last group is identical on every plan, which is the point.
| What it covers | One Desk | The Department | The Whole Year |
|---|---|---|---|
| Reading the set | |||
| Intake from Outlook and connected bid sources | Included | Included | Included |
| Every document and addendum read, cited to page | Included | Included | Included |
| Bid / No-Bid scored against your own history | Not included | Included | Included |
| Pricing the job | |||
| Cited equipment BOM with installed labour hours | Not included | Included | Included |
| Vendor RFQ packages and automatic follow-ups | Not included | Included | Included |
| Quote leveling and total reconciliation | Not included | Included | Included |
| Approved values mapped into the Excel workbook | Not included | Included | Included |
| Submission | |||
| Proposal assembled: scope, clarifications, exclusions | Not included | Included | Included |
| Readiness check on bonding, addenda and alternates | Not included | Included | Included |
| After award | |||
| Buyout drafts, purchase orders and bonds | Not included | Not included | Included |
| Turnover package | Not included | Not included | Included |
| Loss debrief and bid-to-win gap | Not included | Not included | Included |
| Cost library, GC scorecard, vendor history | Not included | Not included | Included |
| Deployment | |||
| Isolated instance, your own subdomain and database | Included | Included | Included |
| Your branding throughout the product | Included | Included | Included |
| Microsoft Entra ID single sign-on | Included | Included | Included |
| ControlIdentical on every plan | |||
| Nothing auto-sends | Included | Included | Included |
| Money computed as deterministic integer cents | Included | Included | Included |
| The agent never holds a credential | Included | Included | Included |
| Every allowed and denied request written to the audit log | Included | Included | Included |
How deployment actually runs.
Six steps from the scoping call to a real bid running through the cycle. What we need from you is named at every one.
- 01Scoping call
Confirm the plan, which bid sources to connect, and which Entra ID tenant signs in.
From youWhoever owns estimating, and someone from IT.
- 02Instance stood up
Your isolated deployment, database and document store on your own subdomain, branded as your company.
From youYour subdomain preference and brand assets.
- 03Identity connected
Microsoft Entra ID single sign-on, so your estimators use the credentials they already have.
From youA tenant admin for one approval.
- 04Connectors authorised
Outlook, OneDrive and Excel natively; the bid sources on your plan connected and tested.
From youMailbox access and bid-source logins.
- 05History loaded
Closed pursuits imported so the cost library and scorecards have something to reason from.
From youAn export of past bids, in whatever shape it exists.
- 06First live pursuit
You run a real bid through the cycle alongside your current process and compare the two.
From youOne live pursuit, and an estimator to approve the sends.
Timing depends on your IT approvals and how much bid history you load. It is confirmed on the scoping call, not promised here.
What the quote is built from.
Four questions on the first call. None of them is a feature you have to buy back.
- Estimators on the seat
How many people work a pursuit, and how many need to approve a send.
- Pursuits a year
Volume sets the document load, not the feature list.
- Bid sources to connect
Which of BuildingConnected, Dodge, PlanHub, ConstructConnect and SmartBid feed your intake.
- Deployment and identity
Where the isolated instance lives and which Entra ID tenant signs in.
01
02
03
04Exclusions.
Stated the way your own proposals state them, so nothing arrives as a surprise at buyout.
- Takeoff
Trimble AutoBid, STACK, McCormick and FastEST stay exactly where they are. ArosBid runs the bid around them.
- Autonomous sending
There is no tier that removes the approval gate.
- Predicted numbers
No plan prices a job by model. Every extension and reconciliation is code.
- Your data as training material
Your deployment is isolated. Your documents stay in your store.
Asked before the number.
Why is there no price on this page?
Every deployment is its own instance, on your infrastructure boundary, with your identity provider and your connected bid sources. A published seat price would be a number we would have to re-quote on the first call anyway. Ask and you get a real one.
How long does deployment actually take?
The six steps below are the whole sequence. Timing depends on how quickly your IT team can approve the tenant connection and how much bid history you want loaded, so it is confirmed on the scoping call rather than promised here.
Can we start on one plan and move up?
Yes. The three are rungs on the same ladder. Moving up grants the agent more of the cycle to draft; it never changes what has to be approved before anything leaves your office.
Is there a pilot?
The last rollout step is a live pursuit run alongside your current process, so you compare the two on your own job before committing further.
What happens to our data if we leave?
It is your database and your document store in your own deployment. Export is not a feature we gate.
Who signs in, and how?
Your team, through your Microsoft Entra ID tenant. ArosBid does not hold a separate password for your estimators.
Get the number on
your own pursuit.
Bring a live tender to the call. We run it through the cycle in front of you, on an instance branded as your company.
Book a live demo