← All guides

One-day Kickstart for estimating teams: what “done” looks like

A useful one-day for estimating and ops is not a tool tour. It is one owned workflow you can run Monday. If you leave with slides, prompts, and no owner, you did not finish. You attended.

The job of this page

Define what “done” looks like for a one-day working session with estimating and ops leads. No invented ROI dollars. Soft path to a CAIO Kickstart if you want a room in a room. Clear picture either way.

What a useful one-day is (and is not)

It is not a product demo marathon. It is not “everyone tries the model.” It is not a backlog of 40 AI ideas with no ranking.

It is one workflow picked from the real leak: bid handoff that survives award, historical costs that get pulled before bid, precon brief that is not tribal memory, risk flags before award, field-to-estimate capture. One. Owned. Runnable after the day ends.

Define done without inventing dollars

You do not need a fake ROI slide to know the day worked. Done looks like this:

• One workflow named. Written in plain language. Not “AI for estimating.” Something like “bid handoff package that ops can open without calling the estimator.”
• Owner named. A person or role on estimating, and a counterpart on ops if the workflow crosses the wall. Two names max for the core path. Not “the team.”
• Artifacts defined. What gets produced, where it lives, what “good enough” means for Monday. Checklist, template, or short spine. Not a 40-page playbook.
• Monday path. The next real bid or next real meeting where this runs. Date or trigger. If it has no next use, it is still a science project.
• AI scope bounded. Where the model helps (summarize, draft, clean grunt) and where humans still own the call (pricing judgment, which risk flags matter, what ops must see).

If you cannot point at those five, the day is not done. More prompts will not fix that.

What you should refuse to count as done

A shared chat history. A list of tools to evaluate. Agreement that “AI is important.” A pilot with no owner. A dashboard nobody will open before the next bid. Those feel productive. They do not change Monday.

One concrete picture

Estimating lead and ops lead in a room for one day. Morning: name the leak (handoff dying in email). Midday: draft the short checklist of what must survive award, who fills it, where it lives. Afternoon: try AI only on the grunt (summarize a readable package into a draft brief), then cut it down by hand. End of day: owner named, checklist saved, next bid on the board marked as the first run.

They leave without a fake savings number. They leave with something they can run. That is done.

Scene is an illustrative pattern, not a named client case study.

Soft path if you want the room facilitated

Chief AI Officer runs a one-day Kickstart with estimating and ops leads. Same bar: one owned workflow, not a tool tour. Soft ask only. Book a conversation if the timing is right.

What “done” looks like

One owned workflow. Named owner. Artifacts good enough for Monday. Next real use on the calendar. AI bounded to grunt, humans still owning the calls that matter. No invented ROI required.