# Launch console for cold email domains and mailboxes

> Pick a client, get ranked domain suggestions with live prices, and buy domains and mailboxes in one confirmed step instead of juggling tabs and a spreadsheet.

- Workflow type: app
- Services: InfraForge, Smartlead, Slack Bot, General Input Database
- Categories: Sales, Operations
- Published: 2026-08-31

## What it does

- Enter a client name, their real brand domain, a budget, and how many mailboxes you want per domain, then let a background agent brainstorm brandable lookalike domains and check which ones are actually available.
- Review a ranked grid of candidates with availability badges and prices, tick the ones you want, and watch a running total build against the client's budget and your remaining balance.
- Confirm once, then the app buys the domains, creates the mailboxes using your naming pattern, and hands them straight to your sending platform, with a CSV download as a backup.
- A launch history tab keeps every past run with the domains bought, the mailbox count, and what it cost, and your team gets a Slack message when a launch finishes.

## What you'll need

- An InfraForge account with credit on the balance, since domain and mailbox purchases are charged the moment you confirm
- A Smartlead login if you want new mailboxes added to your sending tool automatically
- A Slack workspace and the channel where your team wants launch announcements posted
- The client's real brand domain, so the agent has something to build lookalike variants from

## Prompt

Build me an internal app my team uses to stand up cold email infrastructure for a new client, or add sending capacity to an existing one, so we stop piecing it together across the InfraForge UI and a spreadsheet. It has two tabs: New launch and Launch history.

Across the top of both tabs, always show the current InfraForge credit balance using Get Credit Balance Settings, with the auto-topup setting next to it. Amounts are whole US dollars, not cents, so format them as dollars with no decimals. This balance is load bearing: purchases charge it immediately with no checkout step, and an overspend fails with an insufficient balance error partway through a launch, so nobody should be able to start a launch without seeing what they have.

The New launch tab is a form with these fields: client name, the client's real brand domain, a budget in whole dollars, how many mailboxes per domain, the mailbox naming pattern, and the sending platform. For the destination workspace, let the user either pick an existing client workspace from List Workspaces, or type a new workspace name and have the app create it with Create Workspace when the launch runs. The sending platform picker drives the CSV format later and should offer the supported export formats, which include Salesforge, Smartlead, Instantly, First Quadrant, Luna, Reply.io, Mailivery, Woodpecker, SuperAGI, Pipelime and MasterInbox.

A Suggest domains button kicks off a background agent. The agent takes the client's real brand domain and brainstorms a long list of brandable lookalike variants, the kind of shadow domains agencies buy so the primary domain never carries cold volume: prefixes and suffixes like try, get, go, hq, mail and team, plausible word swaps, and alternate endings like .com, .co, .net and .io. It should generate well beyond the number needed so there is room to rank. It then checks them with Bulk Check Domain Availability, which accepts at most 100 domains per call, so the agent must chunk its candidate list into batches of 100 or fewer and merge the results. It writes a ranked candidate grid back into the app where the user can see it: one row per domain with an availability badge, the price, a brandability score, and a one line reason it was suggested. Rank available and on budget candidates first, and keep unavailable ones visible but clearly marked so nobody re-suggests them next time.

The user ticks the candidates they want. As they tick, show a running total that adds up the selected domain prices plus the mailbox cost, which is the number of selected domains multiplied by the mailboxes per domain. Compare that total against two things at once: the budget entered on the form, and the live credit balance. Show it clearly when the selection goes over budget, and block or hard warn when the total exceeds the available balance, because that is the launch that dies partway through.

Provision sits behind a confirmation step. The confirm dialog spells out exactly what is about to happen and what it costs: the domains being bought and their prices, the mailbox count and cost, the total charge, the balance before and after, and the destination workspace. Only after the user confirms does anything get purchased.

On confirm, run the launch in this order. First, buy the selected domains into the client's workspace with Buy Domains. Second, create the mailboxes on those domains with Buy Mailboxes, applying the naming pattern the user picked, or use Generate Mailboxes when the pattern maps cleanly onto its naming strategy. Third, read the mailboxes back with List Mailboxes passing with_credentials set to true, because passwords and the IMAP and SMTP settings only come back on that call and they are what makes the handoff possible. Fourth, create a sending account in Smartlead for each mailbox with Create Email Account, feeding in the address, password and IMAP and SMTP host and port from the previous step. Fifth, generate a CSV with Export Mailboxes in the client's chosen platform format and offer it as a download, so there is always a manual fallback if the Smartlead handoff fails or the client uses a different tool.

Persist a launch record for every run: client name, workspace, date, who ran it, the list of domains actually bought, the mailbox count, the total credit cost, the sending platform, and the per step status. Write this progressively as the steps complete rather than only at the end, so that a launch that fails partway leaves an accurate record of what was already bought and charged. Show the failure state in the app with a clear note about which step broke and what was already paid for.

The Launch history tab lists every past provisioning run, newest first, with client, date, domain count, mailbox count, credit cost and status. Clicking a row opens the detail: the exact domains bought, the mailboxes created, whether each one made it into Smartlead, and a button to re-download that launch's CSV. Let the user filter history by client so they can answer how much infrastructure a given client already has.

When a launch finishes, post a message to the team channel with Slack Bot Send a Message: the client name, how many domains and mailboxes were created, the total credit cost, the remaining balance, and whether the sending tool handoff succeeded. Post on partial failure too, since that is exactly when the team needs to know.

## How to customize

- Change the mailbox naming pattern per client, such as first name only, first.last, or role addresses like hello@ and sales@.
- Set house rules for domain suggestions: preferred endings, words to avoid, or a maximum price per domain.
- Point the finished launch at a different sending platform, or skip the automatic handoff and just take the CSV.
- Choose which Slack channel gets the launch announcement, or turn the announcement off entirely.

## FAQ

### Will this spend money without asking me?

No. Nothing is bought until you tick the candidates you want and click through a confirmation step that shows the exact total. Because purchases are charged to your InfraForge credit balance immediately with no separate checkout, the app keeps your current balance and the running total visible the whole time.

### What happens if my balance runs out partway through a launch?

The app compares your running total against your balance before you confirm and warns you when a launch would cost more than you have available. If a purchase still fails, the launch history records what was actually bought and charged, so you can top up and finish the rest without double buying anything.

### Can I use this with a sending tool other than Smartlead?

Yes. The automatic handoff is built for Smartlead, but every launch also produces a CSV in your client's platform format, and there are ready made formats for tools like Instantly, Reply.io, Woodpecker and several others.

### How many domains can it check at once?

As many as you like. The agent brainstorms a long list of variants and checks them in batches behind the scenes, so you get one ranked grid back instead of checking names one at a time.

### Does this work for existing clients, or only new ones?

Both. You can point a launch at an existing client workspace when you want to add sending capacity, or have the app create a fresh workspace when you are standing up a brand new client.

Use this prompt in General Input: https://www.generalinput.com/prompts/launch-console-for-cold-email-domains-and-mailboxes