Setup
Every variable the console runs on, in one place, each with what it does and what happens if you change it. Nothing here is hidden and nothing here is guessed at.
Every variable the console runs on, what each one does, and where the platform lives.
Every setting here is real — change it and the console behaves differently on the next screen you open. The four that matter are who you are, which mailboxes send your email, what a scrape looks for, and the shared database. Everything else is folded into Advanced at the foot of the page.
The bank account an invoice shows, chosen by where the client is, so they pay a local transfer instead of an international wire. Paste each account exactly as your bank or Payoneer gives it. These are kept in the shared database, never in the app's code.
Used in the console header and in anything it sends. Changing your reply-to address here does not change which mailbox sends — that is set under Domains and mailboxes.
Targets, not limits. The console counts what you did against them at the top of Leads, and points at what is next. Nothing acts on them.
How leads behave once they are in the Leads tab.
What a proposal asks for up front. Read by the proposal and invoice pages a client actually opens, and -- like the send window -- editable nowhere until now.
What is left today
Sign in to the shared database to see what is left.
Domains and mailboxes
Where your cold email actually goes out from. One mailbox per domain, capped at 40 a day — deliberately low, because that is the volume at which mail still reads as a person writing to people. When you need more, buy another domain and another mailbox, add it here, and it starts warming the same day.
Sign in to the shared database below to add a mailbox — these are stored there, not in this browser.
A new domain warms up over roughly a working month, from five a day to 40. Slower than most guides advise, on purpose: ramping too slowly costs time, ramping too quickly costs the domain and everything already sent from it. Passwords are stored in the shared database so the server can authenticate with them — anyone who can sign in can read them.
Shared database
Configured, but signed out — so this console is working on its own copy. Sign in with the Supabase account you created under Authentication and the pipeline becomes shared. The rules grant an anonymous caller nothing, which is why the public API key is safe to ship.
AI email writer
Status: checking…
Open a lead that has an email address and press Write. It reads that business’s own website, takes everything on the lead, and drafts from what we actually sell. Nothing is sent — you copy it and send it from your own mailbox, which is what keeps a first contact reading like a person rather than a campaign.
GEMINI_API_KEY=... # server-side only, never in the browser GEMINI_MODEL=gemini-3.5-flash # optional — this is already the default
- · Four models are tried in order. If the first is retired or overloaded the next takes over, and a rolling
-latestalias sits in the chain so a retirement cannot strand it. - · The draft tells you when a fallback wrote it, since the writing can read differently.
- · The free tier is rate-limited per minute. A rejection is usually that, not the key.
- · The website read happens on the server: a browser cannot fetch another site.
- · The draft is checked for leftover [placeholders] before you see it.
Your data
0 leads, 0 saved scrape runs and every setting on this page are stored in this browser only. No database, no monthly bill, nothing to leak — and clearing site data wipes all of it. Export before you switch machines or browsers.
Bank details for invoices, the links to every account behind this, what the server has configured, and starting over.