Material Signal

Material Signal Workspace

Describe the customer you want. Get a ranked list of accounts, and the reason each one is on it.

Material Signal Workspace is the application behind that. You define what a good account looks like; it scores every account in your book against that definition, shows which rule put each one where it is, and routes what qualifies to a named person with the history attached.

What you give it

A description of the accounts worth selling to, in plain language

Your own scoring rules: what makes an account eligible, what disqualifies it, what counts as fit, and which signals matter

Your accounts, by upload or from a connected provider

Your enrichment, outreach and CRM subscriptions, which stay yours

What you get back

Every account ranked, with the rules that produced the rank visible on it

A search specification you approve before anything runs, and a record of what each run executed

The accounts that clear your threshold, as opportunities with an owner and an attribution window

An activity log per account, so the next person can see what has already been tried

The problem

A prospect list is much less useful when nobody can explain why each account is on it.

The harder part is deciding which rows deserve a person’s attention and preserving the reason each one is there: the rule that fired, the signal behind it, the search that produced it, and who has already tried.

01
Why is this account on the list, and which rule put it there?
02
What was the search actually asking for, before it ran?
03
Who is working this account, since when, and under what window?
04
Which provider produced this contact, and what did it cost to get?
05
What has been tried on this account, and what happened?
06
Which of these is worth a person's morning, and which is a candidate?

What it does

Four screens, in the order the work happens.

The workflow is the product. Each step records what it decided, so the next one does not have to guess.

Searches

Describe the accounts you want in a sentence. It is parsed locally into a structured specification - criteria, signals, personas, and the things the parser was unsure about - and nothing reaches a provider until someone approves it. A run records the specification it executed.

Accounts

Every account ranked by the active scoring profile, and the rank explained rule by rule: which eligibility rules passed, which fit and signal rules fired, and what each contributed. A score with no visible reason is a number an operator has to take on trust.

Opportunities

What qualified, who owns it, and what has happened on it. Accepting an opportunity starts an attribution window, creating a dated record for later commission or ownership review. Every activity is attributed and timestamped.

Integrations

Which providers are connected, when each last proved it, and why one failed. Last tested and last succeeded are separate columns, because a connection that tested five minutes ago and last worked a week ago is a broken integration.

How it is built

Multi-tenant from the first line, with providers isolated behind connectors.

Tenant isolation is enforced server-side

The organisation a request works in is derived from the signed-in user’s authenticated memberships rather than from a client-supplied identifier, and role checks run before a protected resource is returned. A request outside them is refused rather than filtered.

Providers are connectors, not dependencies

Each tenant supplies its own enrichment, outreach and CRM subscriptions. Replacing one means changing a connector, not the scoring core. Provider credentials stay server-side and are not returned in application responses.

Every score is designed to be explainable

Scoring is configured rules with visible points, not a model nobody can question. The profile is a tenant’s own, versioned, and changing it does not require code.

What it does not do yet

The shape of V1.

Current V1 boundaries are listed below.

Self-serve signup
Access is granted by invitation. There is no public registration.
Billing
No subscription management inside the application.
Vendor OAuth
Tenants currently supply their own API credentials. Vendor OAuth is not part of V1.
A managed secret store
Credentials are encrypted in the application database under a deployment-managed key.
Fully asynchronous research
Job and retry metadata is durable, and some provider work still runs synchronously.
Automated contact selection
Candidates are ranked; enriching one is a human decision.

Access

Access is by invitation.

The workspace is currently in use inside Material Signal. External access is by invitation as it moves beyond its first internal tenant. If your team has a prospecting process that produces lists that are difficult to explain or prioritize, that is the conversation worth having.