Sales

Know the account before you take the call

Name a company. Aestus reads their site, the people who matter and the recent news, checks what you already promised them, and writes one cited brief.

Join the waitlist See what it produces

Sales

Research an account

Who it is for: Anyone who talks to customers and prospects, and who has ten minutes before the call rather than an hour.
What starts it: You ask Drop, from home, a ticket or a project; On demand

Turn it on in Aestus

Before a call with a customer, most people open the same tabs: the company's site, a news search, whoever posted about a new job, and then the board to remember what was promised last time. It takes twenty minutes, and it is usually done in five, badly.

This use case does the reading once and writes it down. Name the account, and Aestus reads the company's own pages, the people who matter and the recent news, then reads what this workspace already knows about them: open tickets, promises from the last call, escalations, and what was decided. The brief leads with the three things that most change what you say, then the company, the people, the news, the risks and a few questions worth asking.

Every line points at the page it was read from or the ticket it came from. A person appears only if a page printed their name next to this company, with the role as printed. News appears only if the page dates it inside your window. A page that could not be read is listed as unread, and the brief never describes it from its title.

The web is text someone else wrote, and some of it is written to be read by an agent. The steps that read it hold no workspace tool, and the step that reads your workspace has no way to reach the internet, so an instruction on a page has nothing to act with. The brief is checked against its own sources before it is delivered, and a brief that fails that check twice is not delivered at all. Nothing is posted anywhere: the run writes one document, so there is nothing to approve.

What you get

The artifact this use case produces, in the product view you would read it in.

Example — fictional team and data. Not a live run or customer result.

Worked example

document

Account brief — Northwind

Produced by: Run EXAMPLE-RA-01 · 5 sources · document artifact · nothing sent · demo values

Before you call: Dana Ruiz joined as VP Procurement on 4 Aug 2026 and leads vendor renewals. Northwind raised a $40M Series C on 12 Sep 2026. The SOC 2 letter promised on LIORHEBE-2771 is still not sent.
The company: Northwind makes inventory software for mid-size distributors. Its site says it serves 1,200 customers.
People: Dana Ruiz — VP Procurement since 2026-08-04 Omar Haddad — Chief Executive Officer Priya Shah — Head of Operations
News and signals: 2026-09-12 — Raised a $40M Series C led by Harbor Ridge Capital. 2026-08-04 — Named Dana Ruiz VP Procurement.
Risks: The SOC 2 letter request on LIORHEBE-2771 has waited 6 days. Procurement changed hands on 4 Aug 2026, after the renewal terms were agreed.
Already known here: The renewal is tracked on LIORHEBE-2771; the last call promised a SOC 2 letter.
Ask them: Who besides Dana Ruiz signs off on the renewal? Does the Series C change their seat plans for 2027?

How it runs

Each step is one node in the workflow graph the interpreter runs. Nothing here is a prompt chain hidden in a route handler.

Workflow steps

01You name the account
Type the company, or pick one Drop offers from the outside meetings on your own calendar this week. A name is looked up; a domain is read directly.
02It reads their own site
The home, about, customers and pricing pages, on the company's own host, copied rather than described. A page that is blocked or empty is listed as unread.
03It finds the people and the news
Only names printed on a page it read, with the role as printed. Only news the page dates inside your window. Nothing inferred from a title or a search snippet.
04It checks what you already know
A separate step, with no way to reach the internet, reads this workspace's tickets and memory for promises made to the account, open escalations and past decisions.
05It writes and checks the brief
Before you call, the company, people, news, risks, what to ask. Every line is checked against the page or ticket it came from, and a brief that fails twice is not delivered.

By hand, and on Aestus

The same job, on either side.

By hand
Twenty minutes of tabs before every call.
On Aestus
One brief, read in two.
By hand
A new buyer you learn about on the call itself.
On Aestus
People lists who joined and when, with the page that says so.
By hand
A promise from the last call that nobody remembers.
On Aestus
The brief reads your own tickets and says what is still open with them.
By hand
"I think they raised a round?"
On Aestus
The round, the date and the page it came from.
By hand
A guess about a page nobody could open.
On Aestus
An unread page is named as unread, never summarised from its title.
By hand
Notes that live in one person's head.
On Aestus
A document with its own address, its sources and the run that made it.

What Aestus records

Every run is auditable after the fact, which is what makes handing the job over survivable.

The run
Cost, tokens, duration and a failure code if it failed, on the same ledger as every other run in the workspace.
The brief
A document with its numbered sources: each page with the instant it was read, and each ticket it cites.
Nothing sent
The run reads and writes one document. It posts nothing to Slack or email, so it needs no approval.

What it connects to

Only the tools this workflow actually uses. Each one has a setup guide.

firecrawlRequired

Questions teams ask

Can a page tell Aestus to do something?

No. The steps that read the web hold no workspace tool, so a page that takes one over has nothing to take. The step that reads your workspace holds no way to reach the internet. A page that carries instructions gets one line in the brief saying so.

Where do the people come from?

Only from pages it read: the company's own team or leadership page, and news pages that name someone at the company. The role is copied as printed. It never guesses an email, a reporting line or who decides.

Does it send anything?

No. It writes one brief on the run, and a comment on the ticket when you started it from one. There is nothing to approve.

What does it need connected?

A Firecrawl connection reads the public pages. If your Google Calendar is connected, Drop also offers the companies you meet this week, but the run does not need it.

All use cases How access is governed

Sources

lib/domain/use-cases/research-an-account/seed.ts
lib/domain/use-cases/research-an-account/prompts.ts
lib/domain/use-cases/research-an-account/probe.ts

Hand over Research an account.

Tell us how your team does this today and we will set it up with you.

Talk to us

Questions teams ask

Can a page tell Aestus to do something?

Where do the people come from?

Does it send anything?

No. It writes one brief on the run, and a comment on the ticket when you started it from one. There is nothing to approve.

What does it need connected?

A Firecrawl connection reads the public pages. If your Google Calendar is connected, Drop also offers the companies you meet this week, but the run does not need it.

Sources

lib/domain/use-cases/research-an-account/seed.ts

lib/domain/use-cases/research-an-account/prompts.ts

lib/domain/use-cases/research-an-account/probe.ts

Know the account before you take the call

Research an account

What you get

Account brief — Northwind

How it runs

By hand, and on Aestus

What Aestus records

The run

The brief

Nothing sent

What it connects to

Questions teams ask

Other use cases

Hand over Research an account.

Know the account before you take the call

Research an account

What you get

Account brief — Northwind

How it runs

By hand, and on Aestus

What Aestus records

The run

The brief

Nothing sent

What it connects to

Questions teams ask

Other use cases

Hand over Research an account.