Solar Outbound Built Around Incentive Deadlines
Solar outbound has a rhythm no other industry shares: it spikes. A state announces a new incentive program, a utility files a rate change, a federal credit gets a step-down date — and suddenly there's a 60- or 90-day window where every qualifying facility owner in a territory is worth contacting at once. The developer who reaches them first books the assessments; everyone else inherits a picked-over list. Steady drip prospecting doesn't win those windows. Sprints do.
This guide covers how solar teams build a sprint-ready stack with Instantly and ColdRelay: Instantly as the campaign layer — templates, A/Z variant testing, the Unibox — and ColdRelay as the infrastructure underneath, the secondary domains, mailboxes, and dedicated IPs that Instantly sends from. The goal is simple: when an incentive drops, you're sending qualified outreach within a day, not standing up infrastructure for two weeks while a competitor works your list.
Why Run Instantly on ColdRelay Infrastructure
Instantly was built for exactly this kind of burst-and-scale motion. Paid plans allow unlimited email accounts, bulk SMTP/IMAP import takes a CSV of credentials, and the campaign builder is fast enough to clone and relaunch a campaign in minutes. What Instantly doesn't do is mint the mailboxes themselves — it sends from whatever accounts you connect, and the deliverability of those accounts is the infrastructure layer's problem.
That's where ColdRelay fits. When an incentive announcement creates a window, you order mailboxes on isolated Azure tenants with dedicated IPs — SPF, DKIM, and DMARC pre-configured, ready in about an hour, with no warmup waiting period before sending. Warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), so a mailbox provisioned Monday morning is sending real outreach Monday afternoon.
The two layers are complementary, not competing: ColdRelay is the infrastructure, Instantly is the sending and sequencing engine on top. Instantly's unlimited-accounts model means there's no per-seat penalty for connecting a large ColdRelay pool — which is precisely what a deadline sprint demands. With 95%+ inbox placement underneath, the race to reach every qualifying facility owner before the window closes is actually winnable.
Visit Instantly →Connecting ColdRelay Mailboxes to Instantly
Provision a sprint-sized pool on ColdRelay
Size the pool to the window, not to a steady-state budget. If a program covers roughly 3,000 qualifying facilities and you have 90 days, you need about 35 sends/day just for first touches — call it 60-80 mailboxes once follow-ups are in the mix, at 2 outbound sends/day each (4/day total with warmup). ColdRelay supports 100-150 mailboxes per domain, so one or two secondary domains covers most state-level programs. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour.
Bulk-import the pool into Instantly via CSV
Export your mailbox credentials from the ColdRelay dashboard, then in Instantly go to Email Accounts → Add New → Connect Existing Accounts and choose the bulk SMTP/IMAP CSV import. The whole pool connects in one upload — no per-account OAuth dance — and Instantly's unlimited email accounts on paid plans means a 60-mailbox sprint pool costs the same to connect as six.
Set daily limits and skip Instantly's warmup
Set each account's daily campaign limit in Instantly to 2 emails per day, matching ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. Leave Instantly's own warmup toggled off for these accounts: ColdRelay handles warmup continuously on its side, and double-warming just burns budget.
Build the sprint campaign from your incentive template
In Instantly's campaign builder, start from the pre-written template that matches the incentive type (more on the template library below), merge in the program name, qualification criteria, and the actual deadline date, and attach the full account pool. Instantly rotates sends across every connected mailbox automatically.
Launch with A/Z variants and triage in Unibox
Before launching, load two framings as A/Z test variants — one leading with savings math, one leading with the deadline (see the playbook). Then work replies out of Unibox, Instantly's unified inbox, so one BD rep can triage responses across all 60-80 sending accounts from a single screen during the surge.
The Solar Incentive-Sprint Playbook for Instantly
Build a template library per incentive type, before you need it
Incentive announcements repeat in shape even when the programs are new: a state rebate with a funding cap, a utility rate change with an effective date, a federal credit step-down, a net-metering tariff revision. Write one Instantly campaign template per shape now — subject lines, sequence steps, and merge fields for program name, dollar amount, and deadline — and save them in your workspace. When an announcement drops, the campaign is a clone-and-fill job measured in minutes, and your first sends go out while competitors are still drafting.
Scale the mailbox pool to the window, then wind it down
A 90-day funding window with 3,000 qualifying facilities is an arithmetic problem: at 2 outbound sends/day per mailbox, your pool size determines whether you cover the list once or three times before the deadline. Because ColdRelay provisions in about an hour with no warmup waiting period, and Instantly imports the new accounts in one CSV upload, you can double capacity mid-sprint if reply volume justifies it — then retire the surge pool when the window closes instead of paying for idle steady-state capacity.
A/Z test savings math against deadline urgency — per program
Every incentive email has two honest framings: "this program is worth roughly $X/year for a facility your size" and "applications close on [date] and funding is first-come, first-served." Which one wins varies by program and audience — CFOs tend to engage with the math, owner-operators with the date. Run both as Instantly A/Z variants from day one of each sprint, check campaign analytics after the first few hundred sends, and shift the remaining volume to the winner. Over a few sprints you'll know which framing to lead with for each incentive type before you even test.
Treat reply speed as part of the offer
During a deadline window, your prospect is probably hearing from three other developers the same week — the first substantive human response usually gets the site visit. Staff Unibox like a queue, not a mailbox: same-day responses during a sprint, with the program's qualification checklist ready to paste so an interested reply becomes a scheduled assessment in one exchange. Instantly's campaign analytics tell you when reply volume is peaking; that's when triage discipline pays for the whole sprint.
Typical Solar Sprint Benchmarks (Instantly + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate during deadline windows | 3-7% | Above steady-state solar prospecting; a real program deadline outperforms any manufactured urgency |
| Announcement to first send | Under 24 hours | ~60 minutes to provision on ColdRelay, one CSV import into Instantly, clone the matching template |
| Mid-sprint capacity scale-up | Same day | New mailboxes send immediately — no warmup waiting period before the first outbound |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
What It Costs: Instantly + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — which matters for sprint economics, since a surge pool gets cheaper per mailbox as it grows.
Instantly is billed separately on its own subscription for campaigns, A/Z testing, Unibox, and analytics — with unlimited email accounts on paid plans, so connecting a large sprint pool doesn't change the software bill.
Infrastructure cost scales with mailbox count and flexes with each window; Instantly's cost stays flat regardless of how many accounts you connect. That asymmetry is what makes deadline sprints affordable — you pay for capacity only while the incentive window is open.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Instantly handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Instantly?
No — they're complementary layers. Instantly handles campaigns, A/Z variant testing, account rotation, and reply management in Unibox. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Instantly sends from. You connect ColdRelay mailboxes to Instantly via bulk SMTP/IMAP import and run both together.
An incentive was just announced — how fast can we be sending?
Under a day, realistically. ColdRelay mailboxes provision in about an hour on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, and there's no warmup waiting period — warmup runs continuously as part of each mailbox's 4/day budget (2 outbound + 2 warmup). Bulk-import the credentials into Instantly via CSV, clone your template for that incentive type, and first sends go out the same afternoon.
How many mailboxes does a deadline sprint need?
Work backward from the list and the window. At 2 outbound sends/day per mailbox, covering 3,000 qualifying facilities with a three-step sequence inside 90 days takes roughly 100 outbound sends/day — about 50 mailboxes, comfortably more with headroom. ColdRelay supports 100-150 mailboxes per domain, so most state-level sprints fit on one or two secondary domains, and you can add capacity mid-sprint the same day if replies justify it.
Should we use Instantly's built-in warmup with ColdRelay mailboxes?
No — leave it off for ColdRelay accounts. Each ColdRelay mailbox already runs continuous warmup as 2 of its 4 sends/day (the other 2 are your outbound). Running Instantly's warmup on top would double-warm the accounts and eat into a fixed budget. Point Instantly at outbound sending only and let ColdRelay handle reputation maintenance.