What We Build
Margin, visibility, estimating, invoicing, inventory, SCM, and fleet.
Dashboards, automations, and AI-assisted workflows are how we build. The service offering is wider than one review: we scope the first deliverable around the place your time, people, or cash are getting stuck.
The work fits into five lanes: MSA Margin Check, Mission Control, Estimating & Bidding, Invoicing & OpenInvoice, and Inventory, SCM & Fleet.
The first build is not a generic AI roadmap. It is one scoped deliverable tied to the bottleneck your operators already know is costing time, cash, or margin.
MSA Margin Check
Payroll export, field ticket data, and MSA rate sheets for the clients in scope. A representative sample, not every row you have. We agree on the sample window together.
Reconcile hours worked to hours billed. Cross-check premiums, travel, consumables, and equipment line items against your rate sheet. Flag the deltas. Validate the largest ones with you.
A specific dollar figure of revenue earned and not billed. The flagged jobs that produced it. The methodology so your team can run the check themselves after we leave, if you want that.
What You Can Expect
The Margin Check is designed to produce operational evidence your team can validate, not a generic AI roadmap.
| Leakage Type | Signal | Estimated Impact | Next Action |
|---|---|---|---|
| Premium hours | OT worked, straight-time billed | $24,800 | Validate ticket coding against MSA clause |
| Travel | Eligible trips missing from invoice lines | $18,125 | Rebuild invoice package with source support |
| Consumables | Material issued, no recoverable line item | $17,250 | Confirm client approval path before rebill |
Illustrative figures only. Actual findings depend on your MSA, client rules, source data, and approval path.
Service Lanes
The MSA Margin Check is detailed above as lane 01. The other lanes are the operating systems around it: visibility, bidding, invoicing, inventory, SCM, and fleet.
One view of your business. Margin by job, AR aging, crew utilization, cash flow, and the operational metrics that matter most to you. Built on the data you already have, with daily or faster refresh where the source systems allow.
What changed this week, why, and what to do about it before the monthly meeting.
Faster, more consistent competitive bids with less revision risk. AI assistance for repetitive spreadsheet work. Historical cost data surfaced where it exists. Professional output that makes your shop look like the most serious option on the list.
Fewer manual revisions, clearer assumptions, and a margin you can defend.
Invoice status tracking and exception flagging across the client portals you use. Know where every billable dollar is in the approval chain. Cut the rework cycle on rejected invoices. Where submission can be automated safely, we automate it. Where it cannot, we make sure nothing gets dropped.
Same AR team, cleaner queues, and fewer silent delays.
Five-digit SKU counts under control. Stock visibility across yards and trucks. Fleet utilization, maintenance scheduling, and equipment earning-vs-sitting visibility. Reduce idle time and predict wear before it costs you a job.
Know what is parked, what is working, and what is missing in one view.
Scope Boundary
This is the short list of things people sometimes expect us to build, and that we do not. Naming the fence up front saves everyone time.
Solhunde sits on top of whatever field ticket platform your shop already uses. We do not replace or compete with field ticket capture tools. Specifically:
These are multi-year product categories, not consulting engagements.
We take the data your existing tools already produce, and we turn it into margin. If your shop runs on Viewpoint, we work with Viewpoint. If it runs on another tool and a pile of spreadsheets, we work with those. If it runs on whatever the next thing is, we work with that.
The point of the engagement is to get more out of the tools you already pay for, not to replace them.
How We Work
First conversation, in person when possible.
As many conversations as it takes. Align on scope, data, success metrics, timeline.
First deliverable built. If it delivers, talk about next. If not, you walk away with something useful at no cost.
When the first build proves out, plan what comes next. Retainer or project-based.
Before We Start
A representative sample of payroll exports, field ticket data, and the relevant MSA rate sheets. We agree on scope before anything is shared.
You do. The first build should leave you with something useful: findings, methodology, and enough context for your team to validate the result.
Usually three to four weeks for a bounded sample, depending on data quality, availability, and how quickly the largest variances can be validated.
If the findings justify it, we scope the next build. If not, you keep the output and stop there.
One scoped first build. One concrete output. If it surfaces useful dollars, time savings, or a repeatable workflow, we decide what to build next.
Talk through your bottleneck (403) 561-9384Or email nathan@solhunde.com
Solhunde