Before GaiaOps delivered anything to anyone, we did the research: a systematic review of 48 environmental consulting firms in the 5–25 employee range across the western US, supplemented by structured interviews with operations leaders in the industry and published industry surveys. This page summarizes what we found.
We're publishing it for two reasons. First, the statistics we cite across this site come from this work, and you deserve to see the basis for them. Second, if you run operations at an environmental firm, the patterns below will likely be familiar, and there's some comfort, and some direction, in knowing they're structural rather than personal.
How we did this
We examined publicly available information on 48 environmental consulting firms (technology footprints, hiring requirements, service models, and operational signals), concentrated in California (18 firms), Washington (6), and Oregon (5), with the remainder across other western states. Firm specialties spanned Phase I/II site assessments, NEPA/CEQA work, endangered species compliance, remediation, and sustainability consulting. We paired this with expert interviews, including a former COO who spent twelve years running operations at a 35–40 person consultancy, and cross-checked patterns against published industry surveys.
This is desk research plus interviews, not a controlled study. Where we cite a number, treat it as a well-sourced industry pattern, not a measurement of your firm. The rubric in our Resources section exists for measuring your firm.
Finding 1: The technical stack is sophisticated. The business stack is not.
The firms we reviewed are not technology laggards. They run serious specialized software: GIS platforms dominate (ArcGIS appeared in the overwhelming majority of technical job postings), alongside air dispersion modeling, groundwater modeling, and digital field data collection tools. Annual technology spending typically runs ten to fifty thousand US dollars per firm, around 15–20% of budgets.
But that sophistication stops at the business systems boundary. Project tracking lives in spreadsheets. Time capture is manual. The connective tissue between field data, project management, and billing is, at most firms, a person retyping things.
The implication cuts against the standard sales pitch in this market: these firms don't need more software. They need the software they own to talk to itself.
Finding 2: Data silos are the norm, not the exception
Three-quarters of the firms in our review showed evidence of data silos between their specialized environmental tools and their business systems. The symptom is redundant data entry: the same site visit logged in a field app, a timesheet, a project tracker, and eventually an invoice, by hand, each transfer a chance for error.
One operations leader described the compounding effect of failed fixes:
"We still need to track it here, we still need to do Excel, we still need a backup."
That's the shadow-system tax: when an integration attempt fails, the old system doesn't go away; it runs alongside the new one, permanently, as insurance.
Finding 3: Billing is where the money leaks
Published industry surveys, consistent with what we saw across the review, put revenue lost to manual time tracking and billing inefficiencies at 20–30% for small professional services firms. The mechanics are mundane: hours captured late or not at all, scope creep absorbed silently because nobody's tracking against budget in real time, and invoices delayed by the manual assembly required to produce them.
Environmental work makes this worse than average, because scope is genuinely uncertain. As one practitioner put it, you don't know what you'll find until you start sampling. That's an argument for better tracking, not a reason it's impossible.
Finding 4: The Excel reversion pattern
The most consistent story we heard about software adoption goes like this: a firm invests in an integrated platform, spends weeks configuring it, hits early reliability problems, loses trust, and quietly returns to spreadsheets, now paying for both.
"We eventually just went to Excel."
The lesson we took is about trust mechanics, not tool selection. Systems that demand heavy setup before delivering any value, or that produce a wrong number early, don't get a second chance with skeptical, technically trained users. And environmental scientists are exactly that. Implementations succeed when they start narrow, prove reliable on one workflow, and expand from earned trust. That finding shaped how we work more than any other.
Finding 5: The seller-doer squeeze is the structural constraint
At 5–50 people, almost nobody has dedicated business development staff. The same senior people who deliver projects also win them:
"We were always stuck in this push pull of doing the work and getting the work."
This is why operational inefficiency hurts small firms disproportionately. Every hour senior staff spend on coordination, re-entry, or document archaeology comes out of either billable delivery or pipeline development, the two activities that keep the firm alive. And it's why the highest-payoff improvements target non-billable time first: proposal assembly, onboarding, reporting logistics, admin. Improving those doesn't collide with time-and-materials billing models; it returns hours to the work that does get billed.
Finding 6: Nobody is building for these firms
Enterprise platforms are priced and architected for firms ten times this size. The specialized environmental tools that do exist tend to be deep but isolated: strong in their lane, weakly connected to everything else. The same operations leader was blunt about the gap:
"There's not a lot of innovation in this space as far as technology to operate the companies."
That gap is, candidly, why GaiaOps exists. But the finding stands independent of us: if you've concluded that no off-the-shelf product fits a 15-person environmental firm, you're not wrong, and the answer is less about finding the perfect platform than about systematizing workflows across the good-enough tools you already run.
What we'd do with these findings if we were you
Three moves, in order. First, locate yourself: the Digital Operations Maturity Rubric in our Resources section turns these patterns into a 10-minute self-score. Second, fix one flow, not five: pick the single handoff causing the most re-entry (usually time-to-billing or field-to-report) and systematize it end to end before touching anything else. Third, protect trust: whatever you implement, start narrow enough that it works the first week, because finding 4 is unforgiving.
If you'd rather have help with the sequencing, start with a 30-minute, data-driven diagnostic: we'll look at your firm's specific workflows and tool stack and map where the leaks are. No pitch deck, no obligation. The button below books it.