# Meridian: cited agent work for management consulting teams

Canonical: https://mudpie.ai/companies/verra/
Breadcrumb: [Home](https://mudpie.ai/) / [Companies](https://mudpie.ai/companies/) / [Meridian: cited agent work for management consulting teams](https://mudpie.ai/companies/verra/)
Author: Ali Abouelatta (https://mudpie.ai/authors/ali-abouelatta/)
Published: 2026-09-20
Updated: 2026-09-20
Research type: Company profile
Method: Public-source research. Official Speedrun and company pages checked September 20, 2026. Product claims are attributed to their sources.

Meridian connects a consulting firm’s prior engagements to research, drafting and delivery workflows with citations and permission controls.

## What it does

The company homepage says Meridian unifies engagements, decks and models. Its product page shows a workflow that searches prior work, drafts an assessment and delivers a deck, model and summary with citations. Security says each tenant is isolated and agents mirror existing permissions.

## Buyer and task

Consulting firms that want to reuse prior engagements while keeping permissions and source citations attached to deliverables.

## Workflow boundaries

The page example is illustrative product UI, not an audited engagement result. Pricing and implementation timeline are not documented.

## What I would ask

Ask what counts as comparable precedent, how citations are checked, and which deliverables remain human-owned before client delivery.

## Why it fits

Verra’s public product page describes Meridian as a way for consulting firms to search prior engagements, use that context in a new assessment and deliver a deck, model and summary with citations. The security page says tenants are isolated and agents mirror existing permissions. The useful idea is not “AI writes a deck”; it is that a firm’s prior work becomes a governed source for the next piece of client work.

That can fit a consultancy with repeated industry questions, reusable models and a painful search problem. A team could begin with one engagement where the relevant precedent is known, compare the generated answer with the original source and keep the final deliverable under a consultant’s control. The same workflow can fail if “similar” work is not comparable, if old assumptions are mistaken for current facts or if a citation is technically present but not useful to the reviewer.

The public UI is an illustrative product surface, not an audited engagement outcome. Pricing and implementation timing are not documented. The decision gate is therefore provenance: can a consultant tell why a piece of prior work was selected, correct it, preserve client permissions and remove confidential material before delivery? This profile uses the company’s current Meridian naming and the official Speedrun identity as listed in the official Speedrun profile.

## Quick facts

| Field | Sourced detail |
| --- | --- |
| Buyer | Consulting firms with reusable engagements and deliverables |
| Inputs | Prior engagements, decks and models |
| Outputs | Cited assessment, deck, model and summary |
| Controls named | Tenant isolation and permission-aware agents |

## Sources checked

[official Speedrun profile](https://speedrun.a16z.com/companies/verra) · [company homepage](https://trymeridian.dev/) · [source page](https://trymeridian.dev/product) · [source page](https://trymeridian.dev/security)

Sources checked — September 20, 2026.


## Author disclosure

I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.