Sales

Know which new trials to call first

Each weekday, Aestus reads new trial signups in HubSpot, reads each company's own site, and ranks them by how well they fit who you sell to.

Join the waitlist See what it produces

Sales

Research new trial signups

Who it is for: Founders and sellers who get more trial signups than they can look up by hand.
What starts it: Weekdays at 09:00, in your workspace's time zone, and when you ask Drop; On a schedule

Coming soonResearch new trial signups is built, but not ready yet, so it cannot be turned on today. In Aestus you can ask to be told when it is ready.

A new trial is the best lead most teams get, and it is usually handled in the order it arrived: open HubSpot, open a tab for the company, guess whether it is worth a call. On a good week that is ten tabs a morning; on a busy one, nobody gets to it.

This use case does the looking up once, every weekday morning. It reads the contacts created in HubSpot since the previous weekday, reads each company's own website, and ranks the signups by how well they fit the one line you wrote about who you sell to. Each row says who they are, what their company does, why they fit or do not, and the next step.

Nothing is guessed. A company whose site could not be read is marked unknown, with a question to ask them instead. Someone who signed up with a personal address has no company to read, so they are kept out and listed with the reason. Every name and role is copied from HubSpot, every fact from the page it came from, and a list that does not reconcile with what was read is not delivered.

The run changes nothing in HubSpot. The list is kept on the run, and it is posted to Slack only after someone approves it.

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

Trial signups — since 2026-09-23

Produced by: Run EXAMPLE-TS-01 · 10 sources · document on the run · Slack post after approval · demo values

New signups: 1. Dana Ruiz, Northwind — strong fit. A 140-person software company whose site says its teams plan work across four offices. Call Dana this week — a multi-team rollout matches the mid-market plan. 2. Priya Shah, Lumen Labs — possible fit. A software team, but the site names one product team of about 15 people. Send the self-serve onboarding guide and check back after the first week. 3. Tom Becker, Becker Bakery — weak fit. A two-shop bakery; the site shows no software team to run projects for. No call — leave them on the automated trial emails. 4. Sam Lee, Orbitly — unknown fit. Their site could not be read (blocked), so fit is not judged. Ask Sam in the welcome email what their team does before judging fit.
Kept out: Alex Kim — Signed up with a personal address, so there is no company site to read. Jordan — No company, website or usable email domain on the contact.
What I checked: 6 HubSpot contacts created since 2026-09-23; 3 company sites read and 1 that could not be read.

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

01It reads the new signups
The contacts created in HubSpot since the previous weekday, or since the day you pick. Only one lifecycle stage counts when you name one. It reads contacts and changes nothing.
02It reads their companies
Each signup's company website, on the company's own host, a few pages at most. A personal email address has no company to read, so that person is kept out and listed, never researched as a mail provider.
03It ranks them by fit
Strong, possible, weak or unknown, judged against the one line you wrote about who you sell to and what the company's own pages say. A site that could not be read is unknown, never a guess from the company's name.
04It checks the list
Every name, email and role is checked against HubSpot, every fact against the page it came from, and every contact read must appear once. A list that fails the check twice is not delivered.
05You approve the post
The list is kept on the run. It is posted to your Slack channel only after someone approves it.

By hand, and on Aestus

The same job, on either side.

By hand
Opening HubSpot, then a tab per company, every morning.
On Aestus
One ranked list, waiting when you start.
By hand
Calling in the order people signed up.
On Aestus
The best fit first, with the reason and the next step.
By hand
A guess about a company nobody could look up.
On Aestus
Unknown, said out loud, with a question to ask them instead.
By hand
A gmail.com signup researched as "Gmail".
On Aestus
Kept out and listed, with the reason.
By hand
Signups from the weekend nobody looked at.
On Aestus
Monday reads from Friday, so no day is skipped.
By hand
A list in one person's head.
On Aestus
A document with 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 list
A document with numbered sources: each HubSpot contact and each page, with the instant it was read.
The approval
The Slack post is an external write, so it waits for a person. Declining keeps the list and sends nothing.

What it connects to

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

Questions teams ask

Does it change anything in HubSpot?

No. The step that reads HubSpot can only read contacts. It never writes a field, a note or a lifecycle stage.

Can a sign-up form or a website tell Aestus to do something?

No. A person types their own name and company into a form, and a website is written by someone else, so both are read as data. The step that reads HubSpot holds nothing but HubSpot reads, and the step that reads the web holds no workspace tool.

Why a weekday schedule and not the moment a trial starts?

HubSpot does not send Aestus an event when a contact is created, so the nearest honest trigger is a morning run that reads everything since the previous weekday. You can run it any time from Drop.

What does it need connected?

HubSpot to read the new contacts and Firecrawl to read the company websites. Slack is only needed if you want the list posted.

All use cases How access is governed

Sources

lib/domain/use-cases/research-new-trial-signups/seed.ts
lib/domain/use-cases/research-new-trial-signups/prompts.ts
lib/domain/use-cases/research-new-trial-signups/reader.ts

Hand over Research new trial signups.

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

Talk to us

Research new trial signups

Who it is for

Founders and sellers who get more trial signups than they can look up by hand.

What starts it

Weekdays at 09:00, in your workspace's time zone, and when you ask Drop

On a schedule

Coming soonResearch new trial signups is built, but not ready yet, so it cannot be turned on today. In Aestus you can ask to be told when it is ready.

Questions teams ask

Does it change anything in HubSpot?

No. The step that reads HubSpot can only read contacts. It never writes a field, a note or a lifecycle stage.

Can a sign-up form or a website tell Aestus to do something?

Why a weekday schedule and not the moment a trial starts?

HubSpot does not send Aestus an event when a contact is created, so the nearest honest trigger is a morning run that reads everything since the previous weekday. You can run it any time from Drop.

What does it need connected?

HubSpot to read the new contacts and Firecrawl to read the company websites. Slack is only needed if you want the list posted.

Sources

lib/domain/use-cases/research-new-trial-signups/seed.ts

lib/domain/use-cases/research-new-trial-signups/prompts.ts

lib/domain/use-cases/research-new-trial-signups/reader.ts

Know which new trials to call first

Research new trial signups

What you get

Trial signups — since 2026-09-23

How it runs

By hand, and on Aestus

What Aestus records

The run

The list

The approval

What it connects to

Questions teams ask

Other use cases

Hand over Research new trial signups.

Know which new trials to call first

Research new trial signups

What you get

Trial signups — since 2026-09-23

How it runs

By hand, and on Aestus

What Aestus records

The run

The list

The approval

What it connects to

Questions teams ask

Other use cases

Hand over Research new trial signups.