How an Estimating Team Cleared a 40-Project Backlog with AI

An analyst hand-mapped every claims estimate into construction management software. A two-step Gemini layer now assigns the cost codes and cleared a 40-project backlog.
~$200K/yr
Analyst hires avoided per year
< 4 weeks
Implementation Time
Project Cost

the challenge

The client's estimators built estimates in claims estimating software, but projects ran in separate construction management software. An analyst moved each estimate across by hand, mapping every line item to the right cost code, and more than 40 projects had queued up behind that step. Keeping pace would have meant hiring two more business analysts.

what they built

BaseForge built an AI classification layer that maps estimate line items to the client's cost codes automatically. A smaller Gemini model summarizes each line item, and a larger Gemini reasoning model chooses the best match from the client's full corpus of cost codes. Results are cached, so the many repeat line items don't call the models again. A web application, signed in through the client's Azure tenant, pushes the coded estimates into the construction management system, Salesforce and the other estimating platforms the team uses.
BaseForge started with a two-week proof of concept. The team sat with the analyst doing the mapping by hand to capture the business logic, wrote a script to transform the estimate data, and layered in the AI step that classifies each line item into a cost code. That proof of concept cleared the 40-project backlog. Gemini was chosen after it performed best in internal evaluations, with a smaller model handling summaries and a larger reasoning model making the final cost-code choice, and caching added for the line items that repeat across jobs. The team then built a web application on the client's Azure single sign-on that pushes estimates into every system that needs them, and later connected Salesforce and other estimating platforms. The work ran across the year, but the build itself took about eight weeks: four for the web app, one for testing and three for new systems and logic.

best fit for

Contractors, restoration firms and estimating teams that move estimates between claims or estimating software and construction management systems, where line items have to be coded by hand and the backlog grows faster than analysts can be hired.
Ai ROLE
Classification. A smaller Gemini model summarizes each estimate line item, and a larger reasoning model picks the best-matching cost code from the client's corpus. Cached results handle repeat line items without another model call, and estimators review the coded estimate before it moves into downstream systems.

impact

40 projects

Backlog cleared during a two-week proof of concept

~$200K/yr

Two business analyst hires avoided at about $100K each, fully loaded

8 weeks

Build time for the full application: web app, testing and new system connections

implementation complexity

Medium: a two-model Gemini classification step with caching, plus a web application on Azure SSO integrated with construction management software, Salesforce and other estimating platforms.
Justin D'Iorio, BaseForge Advisors

Justin D'Iorio

Co-founder & Managing Partner at BaseForge Advisors
BaseForge Advisors
Co-founder of BaseForge Advisors, which pairs technologists with strategists to turn AI mandates into measurable projects for middle-market and PE-backed firms.
Get an intro
Talk to this team
industry
Construction & Engineering
business organization
Operations
AI TYpe
AI-Accelerated Custom Software
Document Processing & Extraction
Process Automation (RPA + AI)
value type
Cost Reduction
Time Savings
Headcount Avoidance

frequently asked questions

How did an estimating team clear a 40-project backlog with AI?

It added an AI step that codes each estimate line item automatically. A smaller Gemini model summarizes the item and a larger reasoning model picks the cost code, and a two-week proof of concept cleared the 40-project backlog.

What AI models were used to assign cost codes?

Google Gemini, chosen after internal evaluations. A smaller model summarizes each line item, a larger reasoning model selects the cost code from the client's corpus, and cached results handle repeat items.

What results did the AI cost-code layer deliver?

A 40-project backlog cleared in a two-week proof of concept, and two business analyst hires avoided, worth about $200,000 a year fully loaded.

How long did the AI estimating integration take?

Two weeks for the proof of concept and about eight weeks of build for the full application: four for the web app, one for testing and three for adding systems and logic.

Who is AI cost-code classification best for?

Contractors, restoration firms and estimating teams that move estimates between claims estimating and construction management software and code line items by hand.

Have a similar challenge?

Ask whether this would work for you, or describe what you're trying to solve.
TELL US WHAT YOU'RE EXPLORING