Questions, answered honestly

No forced ESP cutover is required in Connect mode. The first supported pilot is designed to keep Klaviyo as the delivery system while the agreed history is imported and reconciled. Move mode is a separate, guided migration with a dual-run, cutover, and rollback plan.

A data and eligibility audit, one jointly selected lifecycle workflow, a reviewed message plan, explicit policy boundaries, a holdout design where volume permits, and a final decision report. It does not include a full platform migration or native sending.

That is the point of the pilot. The operating contract requires the team to inspect the customer facts, eligibility, excluded actions, message plan, and reason before delivery. A human approval point remains part of the founding-beta model.

The source manifest names every object family and date range before access is authorized. The data contract requires consent, suppression, source identifiers, and lineage to be preserved. Conflicting consent resolves to the most restrictive applicable state until reviewed. Personably is not a substitute for a brand's privacy, preference, or legal obligations.

Brand Studio is being built for customer-facing outputs: logo, color, typography, buttons, spacing, product cards, images, footer and legal content, voice, offers, and reusable blocks. The release design includes preview, version, approval, publish, and rollback controls. It does not reskin the Personably operator interface.

The best first partners are US DTC brands with roughly $10M to $200M GMV, Shopify and Klaviyo already in the stack, a named lifecycle owner, and enough volume to keep a control group. Very small or email-only teams are usually better served by Shopify Email or Klaviyo.

The pilot is designed to answer that question with evidence. Where traffic allows, a holdout remains on the current flow and the decision report includes the outcome, review quality, guardrail signals, and what should happen next. A modeled number is never treated as a promise.