Accounts

An account is a business. Contacts are the people inside it. Everything on this screen is either a fact you or an import supplied about the company, or a number rolled up from the contacts linked to it — Leed does not buy firmographic data, and it does not guess at revenue.

Accounts is the default section of the Engage workspace, so /engage lands here. It is absent from the feature catalog entirely, which means it works on every plan including Free. Two things on this page do carry conditions, and both are called out where they appear: the Site engagement block needs Starter, and the pricing page’s Account-based qualification row describes something else (see the end of this page).

What an account is

One row in your accounts table: a business name, a set of firmographics, and the contacts linked to it. Leed adds one computed layer on top — a rolled-up readiness, fit, intent and journey stage, averaged from the member contacts’ own scores.

Where accounts come from

There are three ways a company name reaches Leed, and the account’s stored source records which one it was:

A CSV import is the one you can drive yourself: map a column to name and Leed builds the account and links the contact for you. That is described in full on Importing contacts. A contact whose Source reads salesforce came in through a single inbound webhook rather than a configurable sync — CRM integration says exactly what is and is not connected.

Reading the list

Each row carries a generated company mark, the account name, its industry (or an em dash when the industry is unset), and a readiness dot. The list is sorted highest readiness first, under the group label By readiness · N.

The search box matches the account name and industry only. It does not search addresses, and it does not search the people inside the account — searching for a person is what the Contacts section is for.

The readiness dot

A gray dot is ambiguous on purpose: it covers both “scored low” and “never scored”. If every dot in your list is gray, nobody has run Recompute scores yet. What actually feeds these numbers is on Engage scores.

The header

The account’s mark and name, then a row of chips: the industry, or “Industry unknown” when it is unset; the employee count, shown only when Employees has a value; and the number of linked contacts. There is no ARR chip, because Leed never fabricates one.

Company details

The first card on the record is the firmographics, and every field on it edits in place. Click a value, type, move on — each field saves on its own. There is no edit mode and no Save button, so there is also nothing to forget to press.

Editing needs contact:write, which starts at the Content Publisher role. Without it the same card renders as read-only text.

Two fields behave differently from the rest. Revenue stores a plain number and displays a humanized one, so you type 12000000 and read back “$12 million”; opening it for editing shows the raw figure again. And Name cannot be blanked — clearing it and pressing enter leaves the previous name in place, because the name is the key the account is matched on.

The status strip

Below the details card sits a strip of five cells: a Readiness meter, the Journey stage as four dots plus a stage pill, Fit out of 100, Intent out of 100, and ARR potential.

ARR potential permanently reads — not modeled. That is not a value still loading and not a field waiting on a setting: Leed does not model deal value at all, and the cell exists to say so rather than to leave a suspicious gap in the row. Every other number in the strip is a roll-up of the member contacts’ scores, described on Engage scores.

Until the first recompute, all four computed cells render as dashes.

What Leed says about the account

The sentence under the strip is generated, but not by a model. It names the account’s stage, states how many of the six committee roles are identified, and adds one of two fixed next steps depending on whether the committee is complete. With no score at all it says so and tells you to run Recompute scores.

It is worth reading it as a summary of the two numbers above it, which is exactly what it is.

What they need

The What they need card is deliberately empty. Needs, interests and blockers are captured for contacts nowhere and for accounts nowhere, so the card says that rather than showing an empty list you might mistake for a data problem.

Site engagement

Above Starter, this block rolls up every linked contact’s real sessions and page views:

• Sessions, Pages viewed, Form fills and Last active, across all history rather than a rolling window.
• Content consumption — the six most-viewed pages, each with a bar and a view count, and a +N more pages tail.
• Recent sessions — the six most recent, each with its date, duration, page count, the contact it belongs to, and an entry source. Entry source is the referring host of the session’s first page view; when there is no referrer it reads Email for a session that started from an email link and Direct otherwise. A session row is clickable and jumps to the contact it belongs to.

Because this is a roll-up, it only covers the contacts Leed managed to link — see the cap noted under the facet rail below.

The buying committee

Six cards under a N of 6 roles identified label. A card fills when a linked contact’s inferred committee role matches it; where two contacts share a role, the first one found takes the slot. Filled cards are clickable and jump to that person’s record in Contacts; empty cards are dashed and read Not identified.

The role is never asked for. It is inferred from the contact’s job title by pattern match during the score recompute.

A contact with no job title gets no role at all, and therefore fills no card. If your committee looks emptier than it should, the fix is usually filling in titles on the contacts, then running Recompute scores. The exact patterns live on Engage scores.

The facet rail

Targeting a whole account with a sequence of outreach is what Campaigns and deliverables is for; accounts are one of the two kinds of audience a campaign can address.

Accounts from an AI client

Two Operator MCP tools cover accounts: list_engage_accounts returns every account with its firmographics and its score, and update_engage_account edits one by id, changing only the fields you supply. There is no create-account tool, which matches the UI exactly — an AI client can read and correct accounts, and cannot conjure one. Both gate on the same contact:* privileges as the screen. See MCP tools for contacts and accounts.