Speak it. Saylume does the admin.
Talk through a site visit the way you'd tell a coworker. Saylume works out what you meant, turns it into exact updates in HubSpot, Gmail, and your calendar — and shows you every one of them before anything runs.
HubSpot firstGmail and Calendar next
Nothing sends or saves without your say-so.
“Alright, just wrapped the walkthrough at the Doe place. John wants to add a full bath on the second floor…”
The flow
One spoken update. Four exact actions. One question it won't guess at.
This is the whole product in one picture. You talk; Saylume resolves what you said against your real records, proposes a specific, typed action for each thing you asked for — and stops on the one detail it can't safely infer.
1 · You speak
19 seconds, hands full, standing in the driveway.
2 · Transcript
“Alright, just wrapped the walkthrough at the Doe place. John wants to add a full bath on the second floor — pull up his file, we'll need to redo the quote. He said match the flooring to downstairs. Tell him I'll have numbers to him Thursday.”
3 · What Saylume understood
- find_contactOpen John Doe — Doe Residence RemodelHubSpotready
- update_dealAdd second-floor full bath to the scopeHubSpotready
- create_taskRebuild the quote — v2 is now out of date, due ThursdayHubSpotready
- draft_emailDraft to John: “numbers to you Thursday”Gmail · draft onlyready
needs you · blocks update_deal
You said “match the flooring to downstairs.” Downstairs is LVP — but this is a bathroom, and every other bath on this job is tile. Which goes on the scope line?
4 ready · 1 question · 0 runNothing runs until you approve it. Change any line, drop one, or send it all through.
Illustrative — example workflow with sample data. Interface in development.
What you can say
It isn't a chatbot with your CRM bolted on.
Every phrase below maps to one named, typed capability with a fixed shape — not a free run at an API. That's why the same sentence gets you the same result twice.
“Smith's basement is leaking again — Mark needs to look at it tomorrow.”
create_ticketcreate_taskHubSpot — assigned to Mark, due tomorrow
“Move the Kowalski walkthrough to Friday morning.”
update_eventGoogle Calendar — asks which Friday slot
“Send Dana the revised scope and cc Ellie.”
draft_emailGmail — written and waiting in drafts. You press send.
“Who haven't we quoted this month?”
search_recordsHubSpot — read-only, scoped to deals you can see
“Log that the permit came through on the Doe job.”
add_noteHubSpot — timestamped on the deal
Why it does the right thing
The model reads you. It never touches your tools.
Saylume is loose about how you say things and strict about what actually happens. The model's only output is a proposal. Whether that proposal is valid, allowed, and yours to make is decided in code, every single time.
- Typed, not improvised
A fixed menu of actions
Saylume can only call capabilities we've written and versioned — each with a strict input shape. There's no “the model figured out an endpoint.” Unknown tools, extra fields, and bad values get rejected before anything happens.
- Checked in code
Your permissions, not the model's opinion
Who you are, what your CRM lets you touch, which records are in scope, and which changes need a second look — all decided in code immediately before every read and write. A prompt is not a permission system.
- Legible after the fact
You can always see what it did
Every action leaves a plain-English entry: what you said, what it proposed, what you approved, what came back. If something looks wrong next week, you can trace it to the sentence that caused it.
Straight answers
What Saylume won't do — today, on purpose.
Early access means a small, dependable surface. Here's the honest edge of it.
- Send anything on its own. Emails land in your drafts. Records change only after you approve the line.
- Roam your whole CRM. It sees the objects and records you switch on during setup — nothing else.
- Run long autonomous chains. One update in, a bounded set of actions out, reviewed by you.
- Estimate, invoice, or do your books. It moves information between the tools you have. It isn't one of them.
- Invent a detail to keep moving. When it can't infer something safely, it asks — like the flooring question above.
- Connect to everything yet. HubSpot is live in the prototype. Gmail and Calendar are next. We'd rather do four things dependably.
Early access
We're onboarding a handful of teams on HubSpot first.
We're onboarding a small group of teams who run their jobs out of a CRM and would rather speak an update than type it. Tell us how you capture job details today and we'll be in touch.
- Shape which capabilities ship first — early users guide the registry.
- A real person reaches out. No automated drip, no spam.
- Free during early access.