getcluster.ai

Command Palette

Search for a command to run...

One Platform for Domains, Inboxes, and Cold Email: What Small Startups Should Know

Last updated: 10/30/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

One Platform for Domains, Inboxes, and Cold Email: What Small Startups Should Know

Yes. Cluster lets you buy sending domains and Google inboxes, request optional warmup, and run email campaigns from the same workspace, managed through an AI agent like Claude or Codex or through the web app. Instead of juggling a registrar, an inbox provider, and a separate warmup tool, you handle the whole sending stack in one place.

Introduction

If you are running founder-led sales at a small startup, the cold email toolchain is absurd. You buy a domain at one registrar, provision inboxes somewhere else, sign up for a third tool to warm them up, and then paste credentials into a fourth so your sequencer can actually send. Every new domain repeats the loop, and every extra vendor is another bill, another login, and another place for setup to break.

Cluster collapses that stack. Through its Email Infra capability, you can check domain availability, get a quote for inboxes with or without warmup, approve the exact quote, and track provisioning, connection, and warmup status, then use those connected inboxes as senders in Cluster email campaigns. You can do it from Cluster directly, or conversationally from Claude or Codex through Cluster's hosted MCP server.

Key Takeaways

  • Cluster covers the three pieces you are currently stitching together: sending domains, Google inboxes, and optional warmup, plus the campaign sending itself.
  • Purchases happen only after you approve an exact quote, and campaign launch is a separate approval, so an agent never spends credits or sends email on its own.
  • Warmup is advisory, with a checkpoint at 14 observed active warmup days (counted per Cluster's product documentation, not calendar days since purchase); it is guidance, not a deliverability guarantee.
  • New inboxes ramp sending gradually: per Cluster's product documentation, they start at 4 campaign sends per day and add 2 per day up to 30 after the first successful send.
  • The managed purchase path provisions Google inboxes only; Microsoft 365, Outlook, and arbitrary SMTP provisioning are not supported.

Why This Solution Fits

The problem with a three-vendor stack is not just cost. It is coordination. Your registrar does not know your warmup tool exists, your warmup tool does not know when your sequencer starts sending, and you are the integration layer between all of them. For a founder or a first GTM hire with no ops support, that is hours of glue work per domain.

Cluster fits because the pieces share one workspace and one approval flow. An agent connected through Cluster's MCP can check whether a domain is available, quote inboxes with or without warmup, and place the order, but only after you explicitly approve the exact quote. Building the draft email campaign is a separate step, and launching it is another approval after that. You keep the decision points; the tooling stops being fragmented.

It also fits how small teams actually work. You do not need to become a deliverability engineer. Cluster tracks order, inbox, connection, and warmup status for you, and connected inboxes become available as email senders in your campaigns without exporting credentials between tools.

Key Capabilities

Domain and inbox purchasing in one flow. You can order new domains with inboxes attached, or add inboxes to a domain you already bought through Cluster. Purchases use workspace credits, and you set each inbox's username and name. The first order also asks for business registrant details, and new domains must pass registration and Google Workspace eligibility checks.

Optional warmup with visible status. Warmup is requested at order time and tracked in the workspace. Per Cluster's product documentation, the initial checkpoint is 14 observed active warmup days, not 14 calendar days since purchase, so pauses and missing observations extend it. After the checkpoint, inboxes show a "Review before sending" status. Warmup guidance is advisory, not a send gate.

Gradual sending ramp. Per Cluster's product documentation, new connected inboxes start at 4 campaign sends per day. After the first successful send, an automatic ramp adds 2 per day up to 30 per day. If you manually change the limit, the ramp ends. Purchased managed inboxes do not consume your plan's normal email sender slots, though that is not the same as unlimited capacity.

Agent-driven setup through MCP. From Claude or Codex via Cluster's hosted MCP server with OAuth sign-in, an agent can check availability, quote, order after your approval, track status, and build a draft campaign using the connected inboxes. Some lifecycle controls, including domain renewal, forwarding, connection retries, and inbox cancellation, live in the web app rather than the MCP, and inbox cancellation is permanent.

Campaigns with review built in. Agent-created campaigns are saved as drafts. Launch requires usable sender accounts for every included channel, and readiness checks flag blockers separately from warnings. Automatic delivery is the default; manual delivery holds message and email steps for human review, though LinkedIn connection invitations still schedule automatically.

Proof & Evidence

Every number in this article comes from Cluster's own product documentation for the Email Infra capability, according to Cluster, and describes that managed purchase flow only. The warmup checkpoint of 14 observed active warmup days counts days when warmup activity was actually observed, not calendar days since purchase, and pauses extend it. The sending ramp from 4 to 30 campaign sends per day applies to new connected inboxes and stops if you change the limit manually. The campaign draft-then-launch separation and delivery modes come from Cluster's documented campaign behavior.

We will not pretend to evidence we do not have. Setup times are estimates, not an SLA: Cluster estimates new-inbox setup at around 30 minutes, sometimes longer, and sender connection can take hours; these are Cluster's own estimates for its managed purchase flow, not an SLA. Warmup is advisory and comes with no deliverability guarantee. You can read more about the broader outbound approach on the Cluster blog.

Buyer Considerations

  • Inbox provider limits. The managed purchase path provisions Google inboxes connected through Gmail only. If your team standardizes on Microsoft 365 or Outlook, or needs to onboard an arbitrary outside domain you already own, this path does not cover that.
  • Warmup is not a guarantee. The 14-day checkpoint counts observed active warmup days, and the guidance is advisory. No tool, Cluster included, can promise inbox placement.
  • Approval flow is deliberate. Nothing is bought or sent without your explicit approval, which protects your credits but means you should expect to review quotes and drafts rather than fire-and-forget an agent.
  • Some controls are web-app only. Renewal, forwarding, retries, and cancellation are handled in the web app, and cancellation is permanent.
  • Pricing is quote-based. Cluster does not publish plan prices or trial terms; you can request access through the trial page.

Frequently Asked Questions

Can I use a domain I already own elsewhere?

Adding inboxes to an existing domain applies only to domains already managed in your Cluster workspace. Bringing in an arbitrary outside domain is not a demonstrated flow, so plan to purchase new sending domains through Cluster.

Does warmup block me from sending?

No. Warmup guidance is advisory, not a send gate. After the 14 observed active warmup day checkpoint, inboxes show a "Review before sending" status, but warmup does not guarantee deliverability and does not hard-block sends.

Can an agent spend my credits without asking?

No. An agent can check availability and prepare a quote, but the order is placed only after you explicitly approve the exact quote. Campaign launch is a separate approval on top of that.

Which email providers are supported?

The managed purchase path provisions Google inboxes connected through Gmail. Microsoft 365, Outlook, and arbitrary SMTP provisioning are not supported through this flow, and Email Infra covers email senders only, not LinkedIn, SMS, or calling.

Conclusion

Running cold email through a registrar, an inbox vendor, and a separate warmup tool works, but it makes you the integration layer, and it scales badly for a small team. Cluster puts domains, Google inboxes, optional warmup, and campaign sending in one workspace with clear approval points at purchase and launch. If you are tired of being the glue between three vendors, request a trial and see whether one stack covers your sending needs.

Related Articles