Why We Built an Environmental Intelligence Platform Inside Excel

← Back to Blog

We could have built a standalone web app. We almost did.

The initial concept for GRYD was a browser-based environmental data platform. Upload your lab results, run your analysis, download your reports. Clean interface, modern stack, responsive design. We had wireframes. We had a colour palette. We were two weeks into frontend development.

Then we went and watched environmental consultants actually work.

The Observation That Changed Everything

We spent a week embedded with two different environmental consulting firms in Alberta. Our goal was to understand the end-to-end workflow: from receiving lab data to submitting compliance reports.

Here's what we saw: everything happens in Excel.

Lab results arrive in spreadsheets. Guideline values are stored in spreadsheets. Analysis is done in spreadsheets. Report tables are built in spreadsheets. Even the final deliverable — the compliance report itself — gets its data from spreadsheets before being formatted in Word.

The entire environmental assessment workflow, from field sampling through to regulatory submission, revolves around Excel workbooks. This wasn't a temporary state or a legacy holdover. This was the deliberate, preferred tool of experienced professionals who'd tried alternatives and come back.

"I've seen three different 'environmental data platforms' come and go. Each one required me to upload my data, learn a new interface, and then export back to Excel anyway for the parts of my report they couldn't handle. I stopped bothering."

That quote came from a senior environmental consultant with 15 years of experience. It killed our web app plans on the spot.

Meeting People Where They Are

The tech industry has a bias toward building new interfaces. New platforms. New experiences. There's something satisfying about a clean slate — a purpose-built UI that does exactly what you designed it to do.

But there's a fundamental tension: the best-designed tool in the world is worthless if nobody uses it. And in industries where professionals have deeply established workflows, the adoption barrier for new tools is enormous.

Environmental consultants don't have time to learn a new platform. They're billing hours on tight project timelines. Their clients expect deliverables in familiar formats. Their colleagues need to open, review, and modify their work. The entire ecosystem runs on Excel.

So we asked ourselves a different question. Instead of "how do we get users to come to our platform?", we asked: "how do we bring our platform to where users already are?"

The answer was an Excel add-in.

What GRYD Does Inside the Workbook

GRYD lives entirely within Excel. It's not an external tool that syncs with spreadsheets. It's not a web app that imports and exports. It operates natively inside the workbook, adding capabilities that Excel can't provide on its own:

• Automated exceedance flagging. Import your lab data and GRYD instantly cross-references every parameter against the applicable guidelines — Alberta Tier 1, site-specific overrides, background comparisons, ND policy definitions. No manual VLOOKUPs. No copied-and-pasted guideline tables.
• Guideline scenario analysis. Evaluate your data against multiple configurations — Tier 1 defaults, Tier 1+ BG, pathway scenarios — without rebuilding your analysis. Switch scenarios and see the impact immediately.
• Environmental statistics. Non-detect handling, background comparisons, distribution analysis — statistical methods purpose-built for environmental data, not borrowed from a general-purpose stats package.
• GIS mapping. Plot your monitoring wells, visualize contamination plumes, overlay guideline boundaries — directly in Excel. No GIS software required for standard project mapping.
• Audit-ready output. Every analysis step is traceable. When a regulator asks how you arrived at a determination, GRYD provides the defensible audit trail.

The environmental consultant's experience is: open Excel, open your workbook, and GRYD is just... there. No context switching. No data import/export cycle. No new interface to learn.

The Technical Challenge of Living Inside Excel

Building inside Excel isn't the easy path. Let's be clear about that.

Excel has its own rendering constraints, performance characteristics, and API boundaries. We can't design pixel-perfect interfaces the way we would in a web app. We're working within the Excel layout system, which was designed for spreadsheets, not for environmental intelligence dashboards.

But these constraints turned out to be features, not bugs:

• Data stays in the workbook. The consultant's data never leaves their file system. No cloud uploads, no SaaS accounts, no data residency concerns.
• Collaboration works natively. Need a colleague to review your analysis? Send them the workbook. They don't need a GRYD account or a separate login. The analysis travels with the data.
• The output is the deliverable. The tables, charts, and maps that GRYD generates are native Excel objects. They go directly into reports without conversion or reformatting.
• Offline by default. No internet connection required for core analysis. Field offices in remote areas — where a lot of environmental work happens — aren't locked out.

What We Learned About Tool Adoption

The biggest lesson from building GRYD is one that applies far beyond environmental consulting:

The best adoption strategy is reducing the cost of adoption to near zero.

Every new tool asks its users to pay a cost: learning time, workflow disruption, data migration, colleague buy-in. Most tools try to justify this cost by offering dramatically better capabilities. "Yes, you have to learn our platform, but look how much better it is!"

We took a different approach: what if we delivered dramatically better capabilities with almost no adoption cost? What if the tool lived inside the environment the user already occupied, spoke the language they already spoke, and produced output they could already use?

The result speaks for itself. Consultants who tried GRYD didn't need training sessions. They didn't need to change their project file structures. They didn't need to convince their teams to switch platforms. They just had more powerful spreadsheets.

The Broader Lesson

There's a tendency in software development to build the interface you want to build rather than the one your users need. We nearly fell into that trap. A beautiful web app with a modern stack would have been more fun to develop. It would have made better demo screenshots. It would have looked more impressive to investors.

But it wouldn't have been adopted. And an unused tool, no matter how well-designed, has zero impact.

Sometimes the smartest technology decision is the one that looks the least impressive from the outside. Building inside Excel isn't sexy. But watching a consultant's face when they realize their entire exceedance analysis just ran in seconds, right there in their workbook — that's the moment that makes it worth it.

Meet your users where they are. The rest follows.