Size the market

Map your total addressable market account by account

A TAM number in a deck is not something you can sell to. TAM mapping here produces named accounts in rows, split into segments you can count, tier, and work through in order.

try
Start freeRead the docs

Market sizing usually gets done twice: once with a top-down number for the board, and again a month later. That is when somebody asks which companies are inside the number, and nobody can answer. That question decides where the sales team spends the next quarter.

A TAM here is rows. You build it in slices, mark each slice in a column, and count what you hold rather than what a report claims. Because the map is a table, it can be tiered, deduplicated, enriched where it matters, and reused as the source for every campaign that follows it.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • Price a slice before you buy it

    what would it cost to pull every UK company selling HR software to mid market employers

    The plan names the lanes, or data sources, that fit. The free preview shows the first 50 matches and, where the source publishes one, the total count. The dry run then prices the pull before you buy.

  • Split the market into tiers

    tag the accounts over 200 people as tier one and everything under 50 as tier three

    Tiering is a column on the row, which is what keeps a large map workable for a small sales team.

  • Find the gap in your coverage

    which segments of our market do we have zero contacts for right now

    A free lookup column counts the contacts you hold at each account's domain, so a slice filtered to zero shows where the map is theory.

Plays

Three motions you can run this week

Each one is a chain of OXYGEN primitives: the same hosted objects your workspace already has, composed.

  • Build the map one slice at a time

    A market arrives as countable segments instead of one undifferentiated list of companies.

    1. Tables
    2. Tags
    1. 1Source each segment into the same table and mark the slice on the row with a select column.
    2. 2Put one tag on the table and on the sequences, knowledge pages, and workflows built from this market.
    oxygen columns add

  • Tier before you pay for contacts

    Enrichment budget lands on the accounts somebody would actually work this quarter.

    1. Tables
    2. Records
    1. 1Score fit and size on the account rows, then rank the whole map in a single pass.
    2. 2Bind the top tier to company records, promote the fields worth keeping, and leave the rest as a map you keep.
    oxygen tables promote

  • Watch the map move

    Companies newly hiring for a slice's roles land in the map each cycle, with no rebuild.

    1. Workflows
    2. Tables
    1. 1Bind each hiring-defined slice as a feed with a per-cycle ceiling; each cycle asks only for job posts since the last one.
    2. 2A firmographic slice (size, industry, location) is a fixed list: its feed pages through once and stops. Count each slice with a table query.
    oxygen feeds bind

Capabilities

What you get

  • A market you can count

    Each slice is a value on the row. The size of a segment is then a query, not an estimate somebody has to defend in a meeting.

  • Tiers that survive the quarter

    Fit and size live as columns on the row. When the strategy changes you rescore the map instead of rebuilding it from nothing.

  • Enrichment only where it pays

    Sizing needs company rows. Contacts and addresses are a separate step you run on the tier you are actually working now.

  • One map, many campaigns

    Sequences, workflows and dashboards can all start from this one table, so the market definition does not fork into private copies.

Boundaries

What Tables does not own

TAM mapping is Tables holding a working map of a market. A slice is a select column on the row, not a workspace Tag. The accounts you commit to become Records.

Data sources

Data sources and CRM connections

  • Blitz API

    The default lane for building a slice from size, industry, and geography filters, paging up to 50,000 companies per query.

  • Crustdata

    On your own Crustdata key, headcount and funding movement, so a slice can be split by stage instead of by a static size band.

  • TheirStack

    The named alternative for hiring-defined slices, and the lane behind Blitz API when its job search misses.

  • Apollo

    Not routed by default: name it to run the firmographic pass on your own Apollo key and account. Connecting a provider key needs OXYGEN's $99 plan or above.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

Limits

Where this stops

  • A map built from databases undercounts small private companies and non-English markets. Treat the count as a floor, and say that it is a floor when the number reaches a board deck.

FAQ

Questions people ask first

Is this market sizing or list building?
Both, in that order. The map is named accounts, so the count and the working list are one object. A sizing exercise that produces no rows tends to get argued about rather than used.
How large can the table get?
Each plan caps the rows one table holds, and the pricing page lists the cap. Holding rows costs nothing. The searches that source them and the enrichment and AI columns you run across them draw credits, which is exactly why tiering comes before enriching.
Can a segment be defined by something other than industry?
Yes. Hiring text, detected technology, funding stage, location, and self-description all work as slice definitions. Each slice carries its own value in the column, so it stays countable on its own.
How do I keep the map from going stale?
A hiring-defined slice can run as a feed. Each cycle asks only for job posts since the last one, under a ceiling you approve, and companies you hold update instead of duplicating. If 5 cycles in a row bring no new company, the feed stops until you resume it. Re-run a firmographic search after 30 days for fresh rows, since an identical search inside that window replays the saved result.
What actually goes into the CRM?
What you bind and promote, plus people who reply to your outreach. The map stays a working set, so the CRM holds accounts you chose or that answered, not companies nobody has looked at.
Can I compare two definitions of the market?
Yes. Make the slice column a multi-select, give each definition its own value, and count them side by side. A company inside both carries both values, so the overlap is a query, not a manual comparison done twice.

Try Tables in your own workspace

Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.

Start freeSee pricing