Paste a target list and press the button.
Roughly 90 seconds per organisation, one at a time.
queued
Turn rows into personalised videos optional
Each video opens by naming what research
found on that company. Rows with no signal have nothing to open
with, so they are unticked β tick one anyway if you know better.
About two minutes a video.
What to talk about
A topic plan drawn from a playbook β what is changing in
that niche's world, not what we would like to say about ourselves.
Before filming anything, check where the subject is
actually searched. Compliance topics are read, not watched β the tool
will say so rather than letting you make videos nobody looks for.
Script
What came back
Sorted by what each reply is actually saying. The two that
matter are otherwise buried among the automatic ones.
Loadingβ¦
What has been researched
Every city you have run, kept between sessions. Choose one
to read and correct what will be sent before any of it goes.
Choose a city.
Conversations
Where each one actually reached β counted from what has
left, not from what was planned. Nothing goes without your approval.
Sending re-checks five things at the last moment: the
account may send, a person approved it, the date has arrived, the
address has not asked to stop, and the sender is under its daily cap.
Loadingβ¦
Describe a niche
One sentence. The rest β what to search for, which
columns to record, what counts as a buying signal, which rivals to look
for, how to grade a fit β gets written for you, and you can change any
of it before it runs.
Saved playbooks
Pick a playbook to see how it finds, records and grades organisations.
What you sell
Written once. The one-line summary goes into every
message, the proof points are the only claims the sequence writer may
make, and the rivals become names research looks for on a prospect's
own site.
Add a product on the
Demos tab by uploading a spec β then describe it here.
Pick a product to describe what it does
and what you are entitled to claim about it.
Product
Where the knowledge lives
Your site, product pages, case studies, demo
videos, LinkedIn. The system reads them and writes down what they
actually claim β you approve it before anything is kept.
What are you making?
Pick a scenario and I'll set the options and list the
steps for it.
Progress
Nothing running. Submit a job to see live progress.
queued
Job history
Loadingβ¦
People
Everyone who can sign in to this account. An
operator runs campaigns; an administrator can also add people and
manage keys.
Invite someone
They sign in with this email and password. Ask
them to change it β you will both know it until they do.
Client companies
Every company Technogroup sells for. Each one's
playbooks, registers and contacts are separate β nobody sees another's.
Add a client
Creating a company does not create anyone who can
sign in to it. Add its first administrator from the People tab once
it exists.
Engine
Stopping the local engine cancels running jobs and shuts
down the local model server, returning its memory to the system. The
control API stays up so you can start it again from here.
Saved products
Loadingβ¦
A saved product keeps its spec and every linked
asset together, so future demos need only the client research.
Outbox
Every drafted message waits here for you. Nothing leaves
until you approve it, and approving records your name against it.
Loadingβ¦
Sending checks five things again at the last
moment: the account may send, a person approved it, the date has
arrived, the address has not asked to stop, and the sender is under
its daily cap. A reply that arrives after you approve still cancels
the send.
YouTube channel
Loadingβ¦
Connect a channel
You create the OAuth client in your own Google Cloud
project, and you approve it on Google's own screen. We never see a
password, and the upload permission is the only one requested β not
the one that can also delete videos.
Uploads are always private. Making a video public
is something you do on YouTube, having watched it.
What model use cost
Per client, per provider, over the last 30 days. What an
invoice for the local-model tier is made from.
Loadingβ¦
Mailboxes
Loadingβ¦
Connect a mailbox
Finished drafts are written straight into this mailbox's
Drafts folder, where you review and send them yourself. Nothing here
can send mail β it only appends.
Check replies reads the inbox and
cancels the remaining touches for anyone who answered β and suppresses
them everywhere if they asked to stop. Run it before each new batch.
It only reads: nothing is moved, deleted or marked read.
On Plesk the host is usually
imap.yourdomain.com or mail.yourdomain.com on
port 993. The password is encrypted before storage and never returned
to this page, not even masked.
LLM providers
Loadingβ¦
Add or replace a key
Model per step
Each stage of a run can use a different model. Leave a
row alone to use its default β every default is a hosted provider, so
a run never depends on the Mac being awake.
Loadingβ¦
Routing
Keys are encrypted on the Mac and never sent back to
this page β only a masked hint. With none configured, decks are still
produced by the deterministic composer.