Personably is in the build phase. This page separates what we are designing, what we will measure in a pilot, and what remains a later roadmap item. It is shared in the open so teams can judge the work without a feature-inventory sales pitch.
We are defining the product artifact before treating generation as the product: eligible facts, exclusions, offer boundaries, message plan, customer-safe explanation, reviewer action, and the final outcome. A message should never be the only record of a decision.
The first design-partner work will use one jointly selected Shopify and Klaviyo lifecycle moment. Where volume supports it, a randomized holdout will distinguish an incremental business outcome from a polished but unproven demo.
A real customer-memory system needs source, timestamp, consent scope, retention rule, and explicit ownership for every fact. Schema consistency, route authorization, and reviewable identity resolution are prerequisites for a credible pilot.
Personably begins beside the delivery system a team already trusts. The first proof uses Klaviyo for dispatch while Personably makes the decision, its constraints, and its measurement visible. A native sender is a later operating obligation, not a shortcut.
Broader customer profiles, loyalty context, additional lifecycle jobs, controlled autonomy, and multi-channel work remain deliberate roadmap items. They are not being sold as a present platform until the first controlled decision loop is safe and repeatable.
These are early research notes, not product claims.
Every merchant-facing number will be backed by holdout measurement before it ships. That is the standard.