Your next client,
found overnight.

No warmup wait. SignalEngine is the intelligence layer — not another sequencer — so it sends through your own sending: connect Google Workspace, Outlook, or your own SMTP and the engine starts drafting and sending at the pace your inbox already supports. There are no lookalike domains to register and no multi-week ramp to sit through. You own deliverability, so your sending stays paced to your inbox's limits. DM and social channels still follow a stricter draft-then-approve ramp because a DM ban can cost you the account — you approve every social post, and nothing gets auto-blasted.

Your inbox, your domain, your reputation. The engine never sends from our own reputation — we're the brain, not the pipes. It plugs into the inbox you already trust (Google Workspace, Outlook, or your own SMTP), so every send carries your real sender identity and you own deliverability end to end. Because the quality gate scores each message before it goes out, the weak ones never reach a real inbox to burn your domain. If you'd rather isolate your primary, bring your own sending — including warmed inboxes from a partner — and point the engine at those instead.

Compliance runs on the sending you already own. Because the engine sends through your connected Google Workspace, Outlook, or SMTP, your existing SPF, DKIM, and DMARC alignment carries every message — you keep your own deliverability posture, we don't sit in the path. Every outbound email still carries a List-Unsubscribe header (one-click compliant), and the engine runs MX-based ESP detection on each recipient so you can read Gmail vs Outlook deliverability splits in your stats. Keep your tools, add the brain.

Yes. Prospect records, message logs, and dossier data live in Convex hosted in eu-west-1 (Ireland). You are the data controller for prospects you import or that the engine discovers; we are the processor. A Data Processing Agreement is available on request. Authentication runs through Clerk, your outbound sends through the inbox you connect (your own Google Workspace, Outlook, or SMTP), transactional/system email runs through Resend, and your engine container runs on a Hetzner VPS in Nürnberg, Germany.

Yes. Delete an individual prospect from the prospect CRM. For a full wipe, the settings page has a Danger Zone: type your brand name to confirm, schedule deletion, and the engine flips to pending_deletion with a 7-day grace window in case you change your mind. After the grace ends, a daily cron cascades the delete across every related table (actions, stats, prospects, messages, campaigns) and schedules your Stripe subscription to cancel at period end.

We do not sell or rent prospect lists. The engine discovers prospects from public sources (Google Maps, LinkedIn, Indeed job listings, Firecrawl-driven web search) and enriches contacts through a verification cascade — the Apify Lead Finder and Prospeo return verified personal decision-maker emails, with website scraping, LinkedIn lookups, pattern-guessing and SMTP/Debounce verification as fallbacks. Because outbound goes through the inbox you connect, every email carries your true sender identity and an unsubscribe link, which keeps you CAN-SPAM compliant on the sending you already own. For UK and EU recipients, PECR's B2B carve-out applies; opt-outs are honoured immediately and stored in a per-instance unsubscribe table.

Not yet, natively. The engine runs as its own CRM today: a prospect table with dossier, signal score, and contact source, plus a Gmail-style email hub for replies. You can export prospects and conversations as CSV, and the HTTP API exposes prospect, action, and message endpoints to push them into your existing CRM. Native two-way HubSpot and Salesforce sync is on the roadmap. If it is a hard requirement, ask sales for the current status before you sign.

Phone, yes, today. The Engine App is a PWA you install from the onboarding email. When a prospect is marked HOT (a positive reply or a tracked click on a proposal page), the engine sends a Web Push notification to your home screen with a tap-through to that prospect. Slack is not a built-in destination yet, but the HTTP API and the HOT trigger hook make it a small piece of glue.

Yes — that's the whole model. SignalEngine is the brain, not the pipes: you bring your own sending (Google Workspace, Outlook, your own SMTP, or Litemail) and the engine sends through the inbox you already trust. We never send from our own reputation, so you own deliverability. Connect the mailbox once and the engine drafts and sends from it; you read and reply to threads inside the email hub, which groups conversations the way Gmail does. Prefer to isolate a mailbox for outbound? Plug in a dedicated one — or buy warmed inboxes from a partner — and point the engine at it.

Connect your inbox and send today — no warmup wait. The Stripe webhook provisions your container on a Hetzner VPS in minutes. The setup wizard takes about 10 minutes (website, niche, target cities, channels, ICP, plan, review) and you connect your own sending — Google Workspace, Outlook, or your own SMTP — instead of registering domains or pasting DNS. Discovery and enrichment begin in the first 20-minute cycle, and because the engine sends through the inbox you already trust, email goes out at the pace your own sending supports. Social drafts (Reddit, LinkedIn) land in your approval queue the same day for you to review and post from the app — you approve every social post.

The engine watches reply rate, bounce rate, and channel-level performance every cycle. If a channel drifts, the queen agent (a weekly cross-instance meta-agent) proposes new search queries and angles in your settings for one-click approval. A Claude-powered quality gate rejects anything scoring below 70 before it sends, so you never get spam-grade messages while the strategy is still tuning. If something looks off, pause in one click, or chat with your engine inside the dashboard to reconfigure on the fly.

Both. Email support reaches a human on a best-effort basis, usually within a business day. The in-dashboard chat is your engine itself: ask it to add a city, switch a channel, change strategy, or explain why it skipped a phase, and it makes the change as a config mutation. For deliverability or DNS edge cases, we bring a human in directly.

Managed plans (Launch, Growth, Scale) get a 72-hour trial at full features, capped at 20 emails and 30 social drafts a day — enough to see the engine work end-to-end without opening the door to abuse. Agency Unlimited (BYOK) gets 7 days at full capacity, with a 48-hour grace window to upload your Gemini and OpenRouter keys. A card is required upfront on both, and there are no surprise charges: when the trial ends you carry on with the plan you picked, or you cancel and we stop.

Yes. One click pauses; one click resumes. Pipeline data, prospect history, and conversation threads all stay put — and because you send through your own inbox, your deliverability and sender reputation were always yours and are never affected by a pause. If the engine stops for any other reason, a health alert tells you. Billing keeps running while paused unless you cancel or schedule deletion.

Cancellation runs through the self-serve Danger Zone: type your brand name, schedule deletion, and a 7-day grace starts so you can roll it back. After grace, a daily cron cascades the delete across all engine tables, and your Stripe subscription cancels at period end (no mid-cycle refund, no extra charge). Your sending was always yours — it's your own Google, Outlook, or SMTP inbox, so cancelling SignalEngine never touches it; you simply disconnect the engine and keep your tools. For a clean exit, export your prospects and conversation history as CSV before the grace expires.