Before you build your data infrastructure, you need to draw a map. Here's how.

Here's a scene that plays out at startups constantly.

A product manager asks an engineer to "track the checkout flow." Three weeks later, the engineer delivers the instrumentation. The PM pulls the data. It doesn't match what anyone expected. Was it product events? Marketing touchpoints? Server-side transactions? The definitions don't align. The data doesn't reconcile. And two people who both worked hard end up in a frustrating conversation about who built the wrong thing.

The root cause is almost never technical. It's conceptual. No one drew a map of the business before building the tracking.

The Business Ecosystem Framework is that map.

What Is the Revenue Roadmap?

The Revenue Roadmap is a structured representation of all the people and things in your business, along with the relationships between them. It's not a database schema. It's not a product spec. It's a shared mental model — a common language for everyone who needs to understand, discuss, or build on top of your data.

It has three components.

Actors are the people or groups of people involved in your business. Customers, employees, suppliers, partners, competitors — anyone who interacts with your product or operations. At Allbirds, the direct-to-consumer shoe company, actors include shoppers, retail store staff, and materials suppliers.

Objects are the tangible or transferable things those actors interact with. Products, websites, cash, marketing campaigns, stores, apps. At Allbirds: the shoes themselves, the e-commerce site, individual store locations, the email marketing program.

Interactions are the relationships between actors and objects — the moments when something happens. A customer sees an ad. A customer visits the website. A customer adds a shoe to their cart. A customer completes a purchase. These interactions are, not coincidentally, the things you'll want to track as events in your database.

Why Build This Before You Build Anything Else?

Most data infrastructure gets built bottom-up: an engineer starts tracking whatever seems relevant, an analyst creates whatever reports get requested, and the whole thing gradually expands into a patchwork that nobody fully understands. The Revenue Roadmap Framework forces a top-down view before any of that happens.

It creates a collectively exhaustive picture. When you map your actors, objects, and interactions systematically, you're forced to account for every meaningful dimension of your business. Nothing important gets accidentally omitted because you didn't think to ask about it.

It aligns top-down and bottom-up perspectives simultaneously. Executives think about the business in terms of customer relationships, revenue streams, and competitive positioning. Engineers think about it in terms of tables, schemas, and foreign keys. The Revenue Roadmap Framework bridges these levels — strategic concepts map directly to data structures.

It makes cross-functional conversations more precise. When a PM says "track the checkout flow," the conversation is vague. When a PM says "we need to track the interaction between the Shopper actor and the Basket object, from the moment an item is added through transaction completion," the engineering team knows exactly what to build. The framework creates a shared vocabulary.

Building a Revenue Roadmap: The Allbirds Example

Let's walk through a concrete mapping, using Allbirds as the case company.

Step 1: Identify Your Actors and Objects

Start by listing every significant group of people involved with your business. For Allbirds:

• Actors: Customers (online and in-store shoppers), Employees (store staff, corporate), Suppliers (wool farmers, manufacturers)

• Objects: Products (shoes, socks, apparel), Website, Physical Stores, Marketing (email, social, paid ads)

Industry terminology: these groupings are often called entities. Your actors and objects, formalized, become entity tables in your database.

Step 2: Map the Interactions (Relationships)

Now trace the connections. Who does what with which objects?

• Customer → Marketing content = Impression (sees an ad or email)

• Customer → Website = Visit (browses the site)

• Customer → Product = Cart Addition (adds item to cart)

• Customer → Basket = Transaction (completes purchase)

• Supplier → Product = Fulfillment (provides materials)

Don't aim for perfection at this stage. Aim for comprehensiveness. A map with a few imprecise interactions is more valuable than no map at all. You can refine as you learn more.

Step 3: Identify Attributes (Properties)

Each actor and object has attributes — the properties that describe it. These become the dimensions you'll use to slice and analyze your data later.

Product table attributes (from the Allbirds website): Product name, Price, Customer rating, Size, Material, Category (shoes/apparel), Gender

Customer table attributes: Registration date, Acquisition source, Country, Gender, Email opt-in status

Pageview table attributes: Cookie ID, Account ID, URL visited, Page load time, Session start/end timestamp

These aren't arbitrary — they're the specific dimensions that will eventually answer business questions. Which product categories are growing fastest? Where are our most loyal customers coming from? Are there patterns in the sessions that convert?

From Revenue Roadmap to Database Architecture

Here's where the framework reveals its real power: it translates directly into data architecture.

• Actors and Objects → Entity tables (dimension tables in your warehouse)

• Interactions → Event tables (fact tables in your warehouse)

The entities describe what things are. The events describe what happened. This is the core structure of any analytics database.

This means that when you and your data team disagree about how to structure a table, the Revenue Roadmap Framework can resolve the dispute. The disagreement is usually a sign that you haven't finished mapping the ecosystem yet. Finish the map, and the structure follows.

How to Run a Revenue Roadmap Mapping Session

You don't need software for this. You need a whiteboard, sticky notes, and 90 minutes with the right people in the room.

Who to include: At minimum, one person from product, one from engineering, one from analytics, and one who thinks strategically about the business (founder, COO, or a senior operator).

How to run it:

1. List all actors on one axis, all objects on another

2. Walk the interactions — for each actor, ask: What does this person do with each object? What actions can we observe or should we track?

3. For each interaction, write a one-sentence trigger description: What specifically has to happen for this interaction to be logged?

4. For each entity, list the 5–10 most important attributes you'd want to know about it

Questions to keep the conversation productive:

• Which actors are internal to the company vs. external?

• Which objects relate to revenue generation vs. marketing vs. operations?

• Which interactions are already being tracked? Which ones aren't?

• Which interactions, if optimized, would have the biggest impact on business outcomes?

What Gets Built Better When You Start Here

Organizations that invest in a Revenue Roadmap map before building data infrastructure consistently produce better outcomes across the board.

Instrumentation plans that engineers actually trust — because they were designed around a shared conceptual model, not retrofitted onto an ad hoc one.

Metric definitions that align across teams — because everyone agreed on what the actors, objects, and interactions are before anyone wrote a SQL query.

Data dictionaries that stay current — because they're anchored to a stable conceptual framework, not to whatever a particular analyst happened to track last quarter.

Forecasting models with defensible assumptions — because the causal relationships between actors, objects, and interactions are explicit, not implied.

Map Before You Build

You wouldn't build a house without architectural plans. You wouldn't launch a product without a spec. But most companies build their data infrastructure without ever drawing a map of the business it's supposed to represent.

The Revenue Roadmap Framework doesn't need to be exhaustive on day one. It doesn't need to be a perfectly formatted document. It needs to exist, and it needs to be shared. A whiteboard photo pinned to your Notion wiki is infinitely better than nothing.

Build the map. Then build the data.

The Revenue Roadmap Framework is one of the core tools covered in The Data Strategist course, alongside instrumentation planning, metrics design, and organizational structure. Start with the foundation.