Implementation BlueprintExecution layer

Broadcast Client Email Infrastructure Setup (7-10 days)

Deploy Broadcast on a client-dedicated Ubuntu server, wire it to Amazon SES or Postmark, and hand over a branded email platform the client owns outright for a one-time license instead of a monthly SaaS bill. Time: 7-10 days.

By InnovaAI ResearchPublished

Email Marketing

How do you implement it?

Blueprint

Broadcast Client Email Infrastructure Setup (7-10 days)

Deploy Broadcast on a client-dedicated Ubuntu server, wire it to Amazon SES or Postmark, and hand over a branded email platform the client owns outright for a one-time license instead of a monthly SaaS bill.

Prerequisites
  • Ubuntu server provisioned for the client (or a VPS the agency controls) with root access and a static IP
  • Broadcast Extended License ($1000 one-time) purchased, since client installations are only permitted under that tier
  • Sending domain ready with DNS access to publish SPF, DKIM, and DMARC records
  • An email sending account with Amazon SES, Mailgun, Postmark, or SendGrid, plus SMTP credentials
  • Client brand assets: logo, color values, and the customer lifecycle stages the automation sequences must cover
Execution Timeline
  • 1.Provision the Ubuntu server and confirm outbound port 25 or the provider API path is open
  • 2.Install Broadcast and complete the admin account and database setup
  • 3.Record the server baseline (PHP version, cron jobs, disk layout) in the client runbook
  • 1.Publish SPF, DKIM, and DMARC records for the client sending domain
  • 2.Verify the domain inside Broadcast and confirm authentication passes
  • 3.Run a seed-list test send to check inbox placement before any client list is loaded
  • 1.Connect Broadcast to Amazon SES, Mailgun, Postmark, or SendGrid using the client's own sending account
  • 2.Set sending limits and bounce thresholds so a bad list cannot burn the client's sender reputation
  • 3.Test both bulk campaign sends and transactional sends through the RESTful API
  • 1.Build the client's branded email template in the drag-and-drop editor
  • 2.Create a second template for transactional mail (receipts, password resets) via the API
  • 3.Save both as reusable templates so the client's team does not rebuild them each campaign
  • 1.Import the client's opted-in subscriber list and map custom fields
  • 2.Configure GDPR consent fields and the unsubscribe handling on the list
  • 3.Segment the list by the lifecycle stages agreed in the onboarding brief
  • 1.Build the first automation sequence (welcome or onboarding) in Broadcast's automation builder
  • 2.Build the second sequence (re-engagement or post-purchase) with its trigger conditions
  • 3.Send each sequence to an internal test address and fix timing or branch errors
  • 1.Confirm open, click, and bounce tracking is recording correctly against a live test campaign
  • 2.Set up the client's separate channel or brand inside Broadcast if they run more than one audience
  • 3.Document the admin login, sending provider console, and DNS registrar in the handover pack
  • 1.Run a 60-minute training session with the client's team on campaign creation and list hygiene
  • 2.Hand over the runbook covering server updates, backups, and what to do when deliverability dips
  • 3.Agree the retainer scope: monitoring, template work, and sequence iteration at 4 hours per month
$1000 one-time for the Broadcast Extended License, plus $640/mo for the Starter Email Setup retainer (12h setup + 4h/mo), plus the client's own server and sending provider costs7-10 days
ROI Logic

The Extended License is a single $1000 payment that covers installation on up to 25 servers, so an agency running ten client deployments carries roughly $100 of license cost per client against a $640/mo retainer. That retainer is billed monthly while the license is paid once, which means the margin on each client improves every month the relationship holds. Compare that to per-subscriber SaaS pricing, where the client's growing list raises the agency's own cost base instead of the agency's margin.

Deliverables
  • Client-dedicated Broadcast instance on Ubuntu with SPF, DKIM, and DMARC verified
  • Sending provider integration (Amazon SES, Mailgun, Postmark, or SendGrid) with bounce thresholds configured
  • Two branded templates: one campaign template and one transactional template
  • Two live automation sequences with tested triggers and branch logic
  • Handover runbook covering admin access, DNS records, backup schedule, and the 4h/mo retainer scope
Definition of Done

The client can log into their own Broadcast admin, send a campaign to their full list, and see opens, clicks, and bounces recorded, with no agency involvement required for a routine send.

Open the Broadcast courseBroadcast decision recordBrowse the Academy

More on Broadcast

More for Email Marketing