InboxSire AI-First

1 · Where we are

Live site, clean base, no customers yet. That is the best possible starting point.

Everything below is in place today. The legacy servers are still running only as a backup until the new sending setup is ready.

Done

inboxsire.com is live on new infrastructure since August 11, with a fixed address, valid certificates and health monitoring.
Brand applied. SendIt is now InboxSire across the product, system emails and domains.
Clean base. The app was rebuilt away from the compromised legacy server. All legacy data was exported and stored off-box (August 10 and August 27).
Inherited engine intact: sequences, mailbox warmup, open and click tracking, reply detection, Stripe billing and a public API.
Greenfield by choice. The acquisition came with almost no active customers, so nothing needs to be migrated.

Not yet

Sending infrastructure (mailboxes and sending servers) is still on the legacy hosts. Not trusted for real volume.
Real-time engagement signals (opened, clicked, replied) are tracked inside the product but not yet pushed out to other tools.
Campaign and lead operations are not exposed in the public API yet. This is the piece an AI assistant needs.
Legal pages and cookie notice still carry old wording.
Logo and site feedback from Rob are pending.
Hosting home. The app runs on Google Cloud under David's account. Decision D3 moves everything to a SouthDesk-owned Hetzner account.

What this means: from here on we spend time on product, not on firefighting. The question is no longer "can we run it" but "what do we build first".

2 · The thesis

Cold email is about to be operated by AI assistants, not by dashboards.

Smartlead, Instantly and Email Bison are built for a person clicking through a UI. The next wave of buyers will ask an assistant to run outreach for them. InboxSire can be the first cold email platform built for that from day one.

MCP

In one sentence: a standard plug that lets any AI assistant use InboxSire the way a person would, with permissions and an audit trail. Claude, ChatGPT, Grok, Cursor or SouthDesk's own bots connect once and can find leads, write sequences, send and read results.

Different, not cheaper

We do not win a feature race against Smartlead. We win by being the platform agents reach for first, which no incumbent is today.

SouthDesk eats first

Our own outreach moves off Smartlead as soon as the comparison holds up. That gives us a real customer, real volume and a done-for-you offer for clients.

Compounding

Every capability we add becomes a tool an assistant can call. Onboarding, list building and copywriting all ride on the same plug.

3 · The path, three moves

Agent-ready core first, then the "wow" onboarding, then the platform story.

Each move has one outcome we can show. Dates assume the decisions below land this week.

MOVE 1 · SEP 3 TO SEP 16

Agent-ready core

InboxSire MCP: create campaigns, add leads, write and schedule sequences, read replies and stats from any assistant.
Complete the public API with campaign and lead operations.
Push engagement signals (opened, clicked, replied) to any tool in real time.
Rob's test: the same outreach through GrokBot plus InboxSire versus Smartlead.
Infrastructure move to Hetzner runs alongside, invisible to users.

Outcome: an assistant runs a full campaign end to end, and we have our first head-to-head numbers.

MOVE 2 · SEP 17 TO OCT 14

The "wow" onboarding

Paste your domain. The assistant drafts your ideal customer profile, you adjust, it builds the lead list from company databases, writes the sequence and sends.
Mailboxes and domains in three clicks, backed by Rob's reseller setup for Google and Microsoft.
Clean sending infrastructure on fresh addresses, warmed properly before any volume.

Outcome: first campaign in minutes, not days. Demo-ready for early customers.

MOVE 3 · FROM OCT 15

Platform and go-to-market

InboxSire as the first tool of a modular platform, with the same plug reused for every next product.
Done-for-you outreach for SouthDesk clients on top of the product.
Pricing that survives a lifetime-deal launch (AppSumo) once cost per lead closes.
SouthDesk fully off Smartlead.

Outcome: revenue from two motions (self-serve and done-for-you) and a product story worth telling.

4 · A day with InboxSire

What "agent-first" looks like from the user's chair

No dashboard tour. The user talks to the assistant they already use, and InboxSire does the work behind it.

You

Start a 200-lead campaign for dental clinics in Miami. Three-step sequence, casual tone, send from the sales mailboxes.

InboxSire

Done. 212 leads pulled from your company database, three-step sequence drafted in your voice, two warmed domains ready. First batch goes out tomorrow at 8 AM ET. Want to review the copy first?campaign created · 212 leads · 2 sending domains · scheduled

You

Show me replies every morning and pause anyone who says no.

InboxSire

Set. Interested replies land in your CRM as hot leads with the thread attached. Opt-outs pause instantly, and you get a morning digest at 8 AM.rule: reply → classify → pause or hand off · digest: daily 08:00 ET

Every line above maps to a capability we already have, or will have by the end of Move 1. The assistant can be Claude, ChatGPT, Grok or a SouthDesk bot. InboxSire is the engine underneath.

5 · Decisions we need from Rob

Four decisions. Tap an option on each, or tell us yours.

Recommended options are marked. Picks are saved on this device only, and the button at the bottom copies a summary you can paste back to David.

D1

What comes first?

Move 1 makes InboxSire usable by assistants and gives us the Smartlead comparison. Move 2 is the demo that sells. We can do one properly, or both slower.

D2

How do we judge InboxSire against Smartlead?

The test only means something if we agree on the scoreboard before it starts.

D3

Where does InboxSire live, and who owns the bill?

Today the app runs on Google Cloud under David's account. Two facts settle this one: Google Cloud blocks outbound mail (port 25) with no exception process, so our own mail and sending servers can never fully live there, and the same servers cost about four times more. Proposal: a new Hetzner account owned by SouthDesk, on Rob's card, with three clean servers (app, mail, sending). Google Cloud keeps only SouthDesk's serverless pieces.

Hetzner: 3 servers, IPs and backupsabout $45 / month

Google Cloud: app + mail only, no sending server possible$140 to $170 / month

Google Cloud today: app onlyabout $61 / month

A new Hetzner account unlocks outbound mail ports after about a month and the first paid invoice. Cold email goes through Google and Microsoft mailboxes anyway (see D4), so this does not hold up Move 1 or Move 2.

D4

Sending path: reseller mailboxes first, or own IPs from day one?

In 2026 cold email lands best when it goes out through real Google Workspace and Microsoft 365 mailboxes: roughly 92 to 96% inbox placement, against 60 to 75% from custom SMTP on dedicated IPs. Rob's reseller setup covers exactly that. Our own sending server and IPs still matter for system mail and later volume, but they are not the first lane.

6 · Next two weeks

Who does what, starting now

Owners and outcomes, not a task list. Anything blocked on a decision above is marked.

Owner	This week (Sep 2 to 8)	Next week (Sep 9 to 16)
David	MCP prototype connected to the live product. Campaign and lead operations in the public API. Hetzner migration plan: three clean servers (app, mail, sending), nothing copied from the compromised legacy hosts (needs D3).	Engagement signals pushed out in real time. Comparison test running with Rob. Migration started: app first, then mail; sending server when the mail ports unlock.
Rob	Logo and site feedback. Decisions D1 to D4. Comparison scenario: list, offer and mailboxes to use with GrokBot.	Run the comparison and score it. Open the SouthDesk Hetzner account and add David (needs D3). First batch of Microsoft 365 or Google Workspace mailboxes through the reseller, for the comparison test.

7 · Landing page, a small shift in words

Today the site sells an "email operating system". The AI-first story deserves the headline.

Same page, same design. We swap the words so the site tells the story we are actually building. About two hours of work once we agree on the direction.

Today

Headline: The email operating system. Replace your entire email stack.
Subheadline: Transactional, marketing, and outbound email unified in one API, one dashboard, and one automation layer.
Call to action: Book a walkthrough
How it works: Five steps, from connecting a domain to operating a dashboard.

Proposed

Headline: Cold email your AI assistant can run.
Subheadline: InboxSire is the outreach platform built for agents. Connect Claude, ChatGPT, Grok or your own bot, and it finds leads, writes sequences and sends from warmed mailboxes.
Call to action: Connect your assistant. Keep "Book a walkthrough" as the second button.
How it works: Three steps: connect your domain and mailboxes, plug in your assistant, say what you want sent.