Companies rarely fail because they lack information. They often fail because shared context breaks down. As organizations scale, decisions get buried in meetings, metrics live in disconnected dashboards, customer feedback disappears into Slack, and plans drift across docs. Teams end up spending more time reconstructing what's happening than acting on it.

After six years across Revenue Operations and Product, I've seen this from multiple angles. I build systems that pull these signals together—surfacing what changed, what matters, what was decided, and what needs attention next.

In practice, this shows up in Chief of Staff, Strategy & Operations, and Business Operations roles inside growth-stage and AI-native companies (Series B–E).

"Organizations don't lack information. They lack judgment infrastructure."
Thomas Meerschwam
ex-Braze · ASAPP · Artsy · NYC
Thomas Meerschwam
The Work

The Ground Truth Decisioning System

A pattern I've seen across companies: teams don't lack tools. They lack a connected layer that turns fragmented signals into shared operational context.

01
Signal · What happened? (performance + metrics)
WBR Generator
Live
02
Decision · What was agreed? (meetings + ownership)
Meeting Intelligence
Live
03
Forecast · What will happen? (pipeline + risk)
Pipeline Synthesizer
Live
04
Execution · What is being worked on? (roadmaps + tasks)
Initiative Intelligence
Live
05
Attention · What matters now? (cross-system synthesis)
Executive Attention Synthesizer
Live
Five tools. One argument.

Each tool addresses a different gap in how organizations process operational signal into executive judgment. Together they constitute a complete decisioning layer — from what happened, to what was decided, to what will happen, to whether execution still reflects intent, to what all of those are collectively trying to say.

These are working prototypes of an internal operating layer, not standalone products.

In practice, these capabilities would be embedded directly into the systems teams already use — Salesforce, Linear, Notion, Slack, and meeting systems — surfacing insights inside existing workflows rather than as separate applications.

01
WBR Generator
What happened?
Live

Most companies already have the data they need to understand performance but not the structure to interpret it consistently. This tool separates signal from interpretation so leadership decisions don't rely on narrative drift.

"The bottleneck isn't data — it's interpretation. Dashboards can't solve a judgment problem."

WBR Generator — Decisions Required output
02
Meeting Intelligence
What was decided?
Live

Meetings produce decisions in theory, but in practice they produce discussion artifacts that decay immediately. This extracts durable decisions, ownership, and unresolved tension and tracks what keeps getting deferred across sessions.

"Anyone can summarize a meeting. The judgment is in knowing what a decision actually looks like versus a discussion."

Meeting Intelligence — Blockers output
03
Pipeline & Forecast Synthesizer
What will happen?
Live

Forecasts fail less from math and more from hidden structural risk concentration, stall patterns, and dependency on individuals. This surfaces those patterns so leadership acts on the real constraint, not the reported number.

"3.2x coverage is a signal. 'The forecast risk is concentration, not volume' is judgment. This tool produces the latter."

Pipeline Synthesizer — Executive Summary output
04
Initiative Intelligence
Are we doing what we said we'd do?
Live

Every organization above fifteen people has two artifacts that are never compared: a strategy document and a project management system. This tool compares them — uploading a CSV from Jira, Linear, Asana, or Notion against five strategy questions and producing a structured audit of where execution still reflects intent, and where it doesn't.

"Organizations don't suffer from a shortage of initiatives. They suffer from an inability to distinguish motion from strategic progress."

Initiative Intelligence — Drift Analysis output
05
Executive Attention Synthesizer
What matters now?
Live

The first four tools create signal — performance, decisions, pipeline, execution. This one triangulates it to determine the most consequential drift. Upload outputs from any combination of the four tools and the Synthesizer identifies where multiple organizational domains are independently pointing at the same underlying problem — the pattern none of them can surface alone.

"Every system tells a different story. The job isn't collecting more stories. It's finding the one they're all trying to tell."

Executive Attention Synthesizer — What the Signals Suggest output
The Arc

Three companies.
One pattern underneath all of them.

Across Artsy, ASAPP, and Braze, the surface problems changed. The underlying pattern didn't.

Each company had strong people, strong tools, and strong data. And still struggled with alignment over time.

In every case, the constraint wasn't information or intelligence. It was that context lived in fragments. Different teams saw different versions of truth, and there was no system that continuously reconciled them.

Braze
2024 – 2025
Scale through complexity

Product Manager, SMS & RCS · $3.5B public company

Owned GTM strategy for a high-eight-figure ARR product line and led an 11-market RCS launch — 40 enterprise customers in 90 days, Google's first official RCS for Business partner, 50%+ YoY ARR growth.

The more durable proof point

Support volume was growing faster than revenue, and the team treated it as a resourcing problem. The real issue was structural: no one could see patterns across tickets. I built a lightweight tagging system that made those patterns visible in under 30 seconds per ticket. Once we could see the distribution of issues clearly, we identified a small set of root causes driving most of the volume — and fixed those directly. The system stayed in place after I left.

11Markets launched
40Enterprise customers, 90 days
6 wksText-only MVP vs. 4-month alternative
50%+YoY ARR growth
ASAPP
2022 – 2023
Align competing worlds

Product Manager & Strategic Advisor to CPO · Conversational AI, Fortune 500

At ASAPP, I worked on high-velocity enterprise AI systems where I first saw how fragmented context across teams and tools led to inconsistent decision-making even in highly data-rich environments.

The structural tension at ASAPP: enterprise customers needed deep customization; the product needed coherent architecture. I operated at that seam — making the product decisions that kept both sides intact. When a large F500 customer threatened churn over a critical configuration requirement, I worked with engineering to modularize the core product rather than build a one-off fix — virtualizing the state layer in a way that protected the account, closed the expansion, and created a reusable configuration pattern for future customers.

2MUsers in 30 days
F500Enterprise accounts retained and expanded
Artsy
2020 – 2022
Built the infrastructure from scratch

Revenue Operations & Product · Fine art marketplace

At Artsy, working across product and operations, I saw the same issue in a more ambiguous environment: teams were making strong local decisions, but lacked a shared system for translating information into coordinated action.

The revenue infrastructure had been patched for years — 15+ fragmented data sources, no single source of truth. Built three things that didn't exist:

Revenue intelligence dashboard — consolidated the data layer and cut board prep from days to hours.

Contract management system — automated approval logic that ended the Sales/Finance conflict and cut contract management time by 50%.

Commissions analytics — a daily ETL pipeline from Redshift into Salesforce that let 65+ reps model "if I close these three deals, I earn $X" in real time. Reps changed behavior because they could finally see reality.

15+Data sources consolidated
50%Reduction in contract mgmt time
100+Hours/quarter saved
The Argument

Why organizations accumulate execution debt despite having more information than ever

Over the last two decades, the tech industry treated organizational alignment as a data problem: if everything could be captured (tasks, metrics, customer data, meetings) then execution would follow. So we built systems of record for nearly everything.

Despite this, increasing levels of information did not produce proportional gains in decision quality or execution coherence. This is because the constraint was how the information is interpreted, how decisions are formed, how ownership is assigned, and how alignment is maintained as conditions change.

Organizations are therefore not limited by information, but by the absence of a reliable system that converts distributed signals into coordinated action. As complexity increases, direction fragments, decisions get re-litigated, ownership becomes implicit, and teams lose a shared, continuously updated picture of reality.

This accumulation of unresolved decisions and disconnected signals is execution debt. It forces organizations to operate on informal memory rather than durable systems of state.

And now, with the advent of advanced AI systems, this failure mode is bound to intensify.

By reducing the cost of generating analysis, text, and code, AI increases organizational output without improving coherence. More artifacts are produced, but they are harder to reconcile. The bottleneck shifts from production to synthesis: the ability to integrate fragmented signals into a single, actionable understanding of reality.

When information becomes effectively infinite, coherence becomes the scarce resource.

Across my career in RevOps and Product at Artsy, ASAPP, and Braze, the pattern has been remarkably consistent: strong teams with strong data repeatedly lost alignment as complexity scaled. Internal systems failed to continuously connect signals, decisions, ownership, and intent into a coherent operational model.

My work focuses on building a connected decisioning layer that turns fragmented organizational signals into structured reality — infrastructure for organizational coherence embedded directly into the systems companies already use, so alignment is continuously maintained rather than periodically reconstructed.

Get in touch.

I enjoy working on problems that sit at the intersection of organizational design, execution, and decision-making.

If you're building through complexity, scaling cross-functional teams, or trying to create better organizational alignment, I'd love to connect.

The fastest way to reach me is by email.

Send an email