Can you take over our existing Iterable instance?
Most of our Iterable work is takeover. The first two weeks are a full audit — Workflow Studio review, deliverability, Snippet hygiene, Command Center reporting tied back to revenue. You get a gap list ranked by what hurts the most, and we start operating from week three. No kickoff theater.
How fast does a new Workflow ship?
Five to ten business days for a standard lifecycle or transactional Workflow — copy, Handlebars build, QA, deliverability check. Cross-channel Workflows with Data Feeds and Catalog dependencies usually run two to three weeks. We respect your release cadence.
Are you handling deliverability and Snippet hygiene?
Yes — neither is a separate engagement. New dedicated IPs, warming schedules, Postmaster + SNDS monitoring, complaint-rate triage, and Snippet inventory cleanup are baseline operating work on every Iterable instance we run.
We're considering migrating to Iterable. What does that look like?
Discord migrated onto Iterable + Hightouch with our team running the cutover — Snowflake reverse-ETL feeding traits and segments, event taxonomy mapped, Workflows rebuilt in Handlebars, deliverability preserved end-to-end. We've also pulled brands off SFMC, Braze, Mailchimp, Klaviyo, Customer.io, Marketo, HubSpot, Responsys, and in-house systems.
Who builds the templates and Snippets?
We do. Design, Handlebars build, Snippets, Catalog configuration, Data Feeds endpoints, QA — all in-house. Strategy without execution is a deck, not a program.