Case Studies

Four engagements. Numbers we can stand behind.

Most "success stories" round their numbers. Most case studies skip the part where the work was unglamorous. These four don't. Each one is a specific engagement, with specific stakes, and the proof is the math.

Before you read further: three of these are commercial general contractor engagements; one is a hospitality firm. Three involve automation. One is an org-design and vendor program build. We don't pretend automation is the answer to every problem, and you'll see that here.

Client names are held back by mutual agreement. The numbers, the stack, and the work are not.

Case Study 01

An ESOP-owned contractor needed an operating system, not another report.

A founder facing a leadership transition. A vendor list nobody had ever pulled apart. $1.15M in sole-source exposure no one had named out loud.

Client
Commercial GC, Arizona
ESOP-owned, ~50 employees
Stack
CMIC ERP, Microsoft 365
Subcontractor spend data
Audience
Founder, incoming COO,
operations leadership
Engagement
Org design, accountability,
vendor program build
The Problem

A leadership transition was coming. The owner could feel what was wrong; he couldn't put numbers on any of it.

The contractor was profitable, ESOP-owned, and on a $30M revenue target. The founder was preparing for a leadership transition. What he didn't have: a clear picture of who owned what across the leadership team, a comp structure built on more than a handshake, or any visibility into where the firm's vendor spend was actually concentrated.

Hundreds of subcontractors. No tiered relationships. A vendor list that grew when a job grew and shrank when nobody was looking. Somewhere in there was risk; nobody had bothered to pull it apart.

What Iron River Did

Sat across the desk from the founder. Pulled the data. Built the picture.

  • Documented the org's actual accountability structure. A 14-page Executive Operating System document with an ARCI matrix (Accountable, Responsible, Consulted, Informed). Not aspirational; what the firm actually does, who actually owns it, where the gaps actually sit.
  • Built a financial model for the comp structure. Three scenarios: base, 10% revenue decline, 15%+ stress. The comp structure had to survive a downturn, not just a good year. The model gave the founder a defensible answer to the questions the new COO would ask.
  • Pulled apart the vendor list. Top 20 vendors at 61% of spend. 53% of vendors used on a single job. Sole-source exposure named for the first time, in dollars, by category.
  • Designed a four-tier vendor program. Strategic, preferred, qualified, transactional. Each tier with its own engagement model. The kind of structure most GCs talk about; few actually run.
The Proof
$1.15M
Sole-source landscaping exposure, named for the first time.
  • 14-page Executive Operating System with ARCI matrix delivered
  • 4-tier vendor program built from actual subcontractor usage data
  • 3-scenario financial model (base, 10% decline, 15%+ stress) supporting new comp structure
  • Top 20 vendors representing roughly 61% of total spend
  • 53% of vendors used on only a single job

Iron River is willing to do the org-design and operator work most automation firms will not touch. That is the point.

Most consultants in this space lead with software. We led with the org. The software conversation came after the operating model was on paper, where it belonged. If you're facing a leadership transition, an ESOP cycle, or a vendor program that's never been examined, that's the call to book.

Case Study 02

The COO was running inbox triage between sips of coffee.

40 inbound emails before 8 a.m. Two daily briefings. A single API call architecture that cost the same whether the inbox had 20 emails or 200.

Client
Commercial GC, Arizona
$30M revenue target
Stack
Microsoft 365 + Make.com
+ Claude API
Audience
COO running daily ops
+ executive team
Engagement
Workflow automation,
executive briefings
The Problem

The COO's attention was the bottleneck. The inbox was just where it showed up.

The COO opened Outlook to 40 inbound emails before he'd finished breakfast. By the time he'd sorted what mattered from what didn't, the morning was half gone. Nothing was technically wrong with the email system; the volume was the volume. The system was the COO.

The owner didn't want a better inbox. He wanted his COO doing the work only the COO can do.

What Iron River Did

Built two daily workflows that turn the inbox into a written briefing.

  • Mapped the COO's actual triage logic. Which senders need attention, which threads can wait, which keywords flag escalation. Captured the rules before automating them so the system mirrored the operator, not the other way around.
  • Built a morning recap and an afternoon prep workflow. Make.com orchestration, Claude API on the back end. The morning briefing summarizes overnight email; the afternoon prep flags what's coming for tomorrow. Both delivered before the COO opens Outlook.
  • Architected for one API call, not forty. A naive build calls the API per email; cost scales linearly with volume. The right build batches the inbox, calls once, returns a written briefing. Cost stays flat as volume grows. Automation is easy to demo and hard to operate; this one was built to run every day.
  • Set up monitoring and a kill switch. If the workflow fails, the COO knows. If it produces something off, the COO can shut it off without help. Both workflows have been in production for months.
The Proof
40
Inbound emails before 8 a.m., triaged into one written briefing.
  • Two daily workflows live in production (morning recap, afternoon prep)
  • Single API call architecture; cost stays flat regardless of inbox volume
  • Monitoring + kill switch the operator can hit without engineering help
  • Briefings delivered before the COO opens Outlook

Automation is easy to demo and hard to operate. Iron River builds for the second.

If your executive's attention is the bottleneck and your team's solution has been "we need to hire someone," the inbox is the wrong thing to staff up. Book a call; we'll tell you whether this approach fits.

Case Study 03

Leadership knew what they wanted. The dev team couldn't estimate it.

A construction ERP. A leadership team. A reporting gap that wasn't a technology gap; it was a translation gap. We sat in the middle and shipped a spec the developer could build from.

Client
Commercial GC
with internal IT team
Stack
CMIC ERP, Power BI,
Microsoft 365
Audience
COO, internal developer,
executive team
Engagement
Requirements translation,
dashboard architecture
The Problem

The COO was running a $30M revenue plan off reports he couldn't read.

The firm had CMIC, an internal developer who could build in Power BI, and a leadership team that knew what decisions they needed to make on a Monday morning. None of those three pieces was speaking the same language. The developer kept asking what the report needed to do; the COO kept describing the answer he needed without the structure to specify it.

Discovery meetings stalled. Estimates couldn't be made. The work didn't move.

What Iron River Did

Sat in the requirements call. Translated. Handed the developer a spec he could build from.

  • Sat with the COO and captured his decision logic. Not "what report do you want"; what decision are you trying to make, what data does that decision require, and how would you know if the answer was wrong. The right questions, asked once.
  • Translated executive priorities into 13 defined KPIs. Safety first, schedule second, budget third; the priority order leadership already lived by, finally written into the dashboard's structure. Each KPI had a definition, a source field, and the actual DAX formula behind it.
  • Built a 3-page dashboard layout to match the priority order. Page one mirrored what leadership reviewed first; page two and page three followed the order of attention, not the order of data convenience. Decisions, then numbers.
  • Handed the spec package directly to the developer. Copy-paste DAX. Defined sources. Layout decisions made. The developer estimated the build the same day. No discovery meetings. No re-litigating the business rules.
The Proof
13
Defined KPIs with copy-paste DAX, delivered to the developer on day one.
  • 3-page dashboard layout built to executive priority order: Safety, Schedule, Budget
  • Zero discovery meetings required for developer estimation
  • Source fields and DAX formulas defined per KPI
  • Internal IT freed to build, not to facilitate

Internal teams can build. Leadership knows what they want. The translation layer between them is where Iron River sits.

If you have internal IT and a leadership team that aren't shipping reports together, the problem is rarely technology. It's translation. Book a call and we'll talk about whether we can sit in the middle for you.

Case Study 04

A CRM with 20,623 contacts and a sales team that didn't trust it.

A hospitality performance management firm. Years of accumulated contacts. A list that read big and worked small. We cleaned it, verified it, and pulled the compliance violations out before they cost more than a fine.

Client
Hospitality performance
management firm
Stack
CRM with contact records,
verification + enrichment APIs
Audience
Sales operations,
outbound team
Engagement
CRM cleanup,
data verification, DNC audit
The Problem

The list was big. The list was wrong. The sales team had stopped believing it.

20,623 contact records accumulated over years of trade shows, downloads, and partner introductions. Nobody knew which ones were current. Nobody knew which ones had asked to be removed. The outbound team ran campaigns from the list anyway, because it was the list they had.

27 of those contacts had registered Do Not Contact requests. The list kept emailing them. That's a compliance violation; it's also a trust problem inside the firm.

What Iron River Did

Verified every record. Pulled the violations. Handed back a list the team could actually use.

  • Ran every record through verification. Email validation, phone validation, employment status checks, LinkedIn coverage cross-reference. 20,623 in, 7,734 verified out. Contacts that couldn't be verified got archived, not deleted; the firm kept the history without running outbound on it.
  • Identified and removed the 27 DNC violations from active outreach. Each one logged with its registration source and removal timestamp. A defensible audit trail; the kind of thing the compliance team needed and the sales team had been quietly avoiding.
  • Enriched the verified records with current role, company, and channel coverage. LinkedIn coverage and email coverage both improved measurably across the verified portion of the list. The sales team got back a smaller list they could actually believe.
  • Documented what was kept, archived, and removed. The cleanup was reversible, auditable, and explainable to anyone who asked: legal, the board, a future ops hire.
The Proof
20,623
Contacts cleaned to 7,734 verified, with 27 DNC violations removed.
  • 20,623 contact records audited, 7,734 verified and retained
  • 27 DNC violations identified and removed from active outreach
  • Measurable improvements in LinkedIn coverage on verified records
  • Measurable improvements in email coverage on verified records
  • Auditable cleanup trail: kept, archived, and removed records each logged

The list was bigger before. The list works now. That trade is worth making every time.

If your CRM is a graveyard and your sales team has stopped trusting the list, the answer isn't a new platform; it's the cleanup work nobody wants to budget for. Book a call and we'll talk about scope.

Tell us what's broken. We'll tell you whether we can fix it.

A 30-minute call. No deck. No pitch. By the end, you'll know whether we're the right partner; if we're not, we'll point you toward someone who is.

Book a Call Take the AI Readiness Assessment

The AI Readiness Assessment is delivered with our product partner, Brainforest.

0
Skip to Content
Iron River Technologies
About
AI Training
Executive Diagnostic
Case Studies
Services
Technical Services
Blog
Pricing
Contact
Book now
Iron River Technologies
About
AI Training
Executive Diagnostic
Case Studies
Services
Technical Services
Blog
Pricing
Contact
Book now
Folder: Services
Back
About
AI Training
Executive Diagnostic
Case Studies
Services
Technical Services
Blog
Pricing
Contact
Book now

IRON RIVER

Privacy Policy

Contact Us

Services

Case Studies

About Us

How We Think

Blog

Technical Services

Location

2113 East Rio Salado Parkway
Tempe, AZ 85288

Contact

info@ironriver.io
(602) 492-1074‬