Applied AI · Enterprise and financial services

Most AI programs stall before they reach production.

The models are fine. The data underneath has no shared meaning, so nothing built on it holds up. An answer you can't trace to a source is an answer you can't use.

Knowledge graphs and ontologies Agentic systems High-tech GTM and positioning

What we do

Four disciplines, one team.

Three build the system, the fourth takes it to market. We work directly with institutions, and behind the consultancies and vendors already on the program.

01

AI strategy and delivery

We scope where AI actually changes your numbers, then build it against your real data. If the honest answer is that you shouldn't build it yet, that's what we'll tell you.

02

Knowledge graphs and ontologies

A shared map of what your data means. It connects the facts across your systems to the documents behind them, so every answer traces to a source and means the same thing on every desk.

03

Agentic development

Agents with clear jobs, real tools, and guardrails. Built to run inside your workflow, with a person accountable for the decision at the end of it.

04

High-tech GTM and product positioning

Outside, we position technical products for enterprise buyers, tighten the pricing and set up the pipeline motion. Inside, we get product, sales and engineering telling the same story about why it wins. We've carried the number and sat on the buying side.

How we work

We start with the business problem.

Most firms here build the platform, then go looking for a use case. We work the other direction.

01

Find the value

The decisions that are slow or expensive, and what it's worth to fix them. If the number doesn't hold up, we say so before anyone writes code.

02

Build down to the data

We organize the data behind that decision so it has structure and one shared meaning. Built against your live systems, shaped by the problem rather than the tooling.

03

Put it to work

AI that works from those verified facts, inside your workflow. We stay until it holds under real load.

A working demonstration

We built the argument as a working system.

Highwater is our own demonstration, built on public records. It holds every flood insurance claim across six South Carolina coastal counties since 1978, all 26,531 of them, plus the 161 federal court filings and FEMA appeal decisions behind them. Our system read those documents and kept a link from every fact to the line it came from. Click any number and see the source.

Nothing in it is generated. It runs on the same patterns we'd build inside your walls.

Explore it at scflood.meridian7.io
26,531
Real flood claims, 1978 to 2026
161
Public documents extracted: federal filings and FEMA appeals
0.931
Extraction precision, against 0.839 for a single pass
6
Working applications on one graph

How we engage

Three ways in.

Fixed scope and a fixed price, agreed before anyone starts. You'll know what it costs and what it ends in before you commit.

Three weeks · Fixed fee

Diagnostic

We look at the problem, the systems and the data behind it, then tell you whether the value case holds up.

Ends inA decision brief you can take to your board, including the case for not building it.
Six to twelve weeks

Build

We design the layer and put it into production against your live systems. Your team works alongside ours the whole way, so it doesn't leave when we do.

Ends inA working system on production patterns, running against your live data, with your people operating it.

Enterprise rollout carries its own security, architecture and governance reviews. We name them rather than pretending they aren't there.

Ongoing · Retained

Standing counsel

Senior judgment on call for teams already building. Architecture reviews, vendor decisions, positioning, and the conversations you'd rather have before the board meeting.

Ends inNothing. That's the point. We stay as long as we're useful.

Perspectives

A century of claims documents, made to earn.

Carriers hold decades of claims files, adjuster notes and correspondence, most of it sitting in documents no system can use. Meanwhile the consortiums built on that same data run multi-billion-dollar businesses, and the contributing carrier is paid nothing.

We build the foundation that lets a carrier capture that value itself. We read the documents, organize them into twelve to twenty categories around one use case, and keep a source link on every fact. The product sits on top. Not six months of enterprise modeling with nothing loaded.

There is a regulatory line through this, and most of the value sits on the governed side of it. We know where it runs. Where it lands for you is the first conversation.

The data was there. One source of truth wasn't.

A Series A startup, seven months past launch, had reached most of the top twenty companies in its target market. It still couldn't say what its pipeline looked like without someone spending hours assembling the answer by hand. Calls sat in one tool, accounts in another, product usage in a third, and everything else in spreadsheets and a founder's inbox. Forecasting was a last-minute sheet, and investors asked at the worst possible times.

None of that is a process problem. It's a data problem wearing a process problem's clothes, and it shows up identically at a hundred-person company and a hundred-billion-dollar one. The fix is the same shape at both ends: one trusted source of truth, built on the systems already in use, that surfaces the answer without a person in the middle.

The firm

Executives who've built and sold this.

Matt Lucas leads architecture and delivery. Twenty years building data and AI systems inside global financial institutions. That includes graph systems at Morgan Stanley and compliance-grade pipelines for SEC-regulated and fiduciary environments. As Field CTO for financial services at Stardog, the enterprise knowledge-graph platform, he advised banks and insurers on data programs across risk, finance and compliance.

Sara Golbourn leads commercialization. Two decades of enterprise go-to-market across VMware, Cisco, OneTrust and UiPath, where she built and scaled the financial services business through the run to IPO and past $1B ARR, inside compliance-heavy procurement cycles.

We won't take on a program where nobody on your side can validate the output. That surfaces in week eight otherwise, and we'd rather find it in week one.

Sectors
Capital markets, wealth and asset management, insurance
Built
Knowledge graphs and agent systems in regulated production
Buyer's seat
Platform evaluation and budget inside a global investment bank and a Fortune 50 technology firm
Depth on call
An extended team of data-modeling and industry specialists, brought in when the work calls for it
Engagement
Three weeks to a decision, six to twelve to a working system

Roles and outcomes above were held in prior positions, not Meridian7 client results.

Contact

Tell us where it's breaking.

A short call is usually enough to know whether we can help. If we're not the right fit, we'll say so and point you somewhere better.

We reply within one business day.

Thanks. Message sent.

We'll be in touch within one business day.