The engagement

Your 60-day pilot. No cost, no obligation.

Sixty days, built as thirty plus thirty, with a hard gate at Day 30 that either side can close. Long enough for your bids to resolve and a real loss to render with a dollar figure on it — short enough that you decide while the evidence is fresh. Give us the mandate and the officials. Your own data does the talking.

Talk about a pilot Run your number first

How it runs

Day 0 to Day 60.

Day 0

Two hours, one Google Meet

Every official credentialed and logged in. Industry project data imported. Success criteria and the adoption floor written down and signed by both sides — so nobody is arguing about what worked at the end.

Days 1–14

Officials enter, nobody chases files

Officials log bid data directly into ODIN from the field. No files, no folders, no spreadsheet for anyone to maintain. The first deliverable lands here: the jobs in your own jurisdiction nobody bid on — in writing.

Day 30

The gate — and it swings both ways

Not a check-in. If your officials are using it, the pilot continues. If they are not, it ends that day — you can walk, and so can we. Thirty more free days cannot fix a tool nobody opened, and neither side should pretend otherwise.

Days 31–55

The first rendered loss

A real job you were underbid on, with the gap quantified and the waiver or fund allocation that would have closed it — an instruction manual for the next comparable bid.

Day 55

The decision conversation

Dashboards built from your own entries. The scorecard shows coverage. Your losses have dollar gaps attached. You decide with numbers in front of you, not a pitch.

Day 60

Close

Sixty days, structured as thirty plus thirty. Long enough for bids to resolve and a real loss to render with a dollar on it — short enough that the decision gets made while the evidence is still fresh.

The terms, plainly

What you are agreeing to — and what you are not.

A mandate, not a budget

What the pilot needs from leadership is a clear instruction that officials will use it, and two hours on Day 0. That is genuinely the list.

Your data stays yours

The intelligence belongs to the local. You control access during and after the pilot, and you can take your data with you.

No IT project

No procurement cycle, no hardware, no installation. Officials log in from what is already in their pocket.

If the numbers don't speak, we shake hands and part friends. No invoice. No obligation. No pressure.

That is not a sales line, it is the actual term. The pilot either produces a market-share picture your leadership can use, or it does not — and if it does not, there is nothing to discuss and nothing to pay.