Lifecycle marketing that stays managed

We look for gaps between joining the list, making a first purchase, returning and participating in loyalty. A useful journey might introduce your dispensary to a new subscriber, follow up on an expressed category interest or reintroduce your store to an eligible customer who has become less active.

We begin with the current account rather than assuming every idea can be supported. Required events, permissions, message channels and integration behavior must be available before the dependent work can proceed.

• Program review: an inventory of agreed flows, their purpose, owners and known issues.
• Journey planning: welcome, post-purchase, repeat-visit or reactivation messages, with relevant entry conditions and a clear reason for each step.
• Message production: copy and branded creative using accurate, approved source material.
• Build and testing: the scoped configuration and checks supported by the account.
• Maintenance: scheduled reviews and permitted updates within the agreed allowance.
• Reporting: an understandable view of available activity and unresolved questions.

First, we agree what each journey is meant to do and which team owns its inputs. We document the dependencies, prepare the work and review it with the authorized approver before launch.

Once a flow is active, maintenance has a defined cadence. We look for outdated content, missing information and changes that need a new decision. When a dependency breaks or a message is no longer appropriate, we bring the issue to the responsible owner rather than silently changing the purpose of the program.

The published AIQ packages define a simple flow as one trigger, up to three email or SMS messages in total and at most one conditional branch, using existing data and native integrations. The number of initial builds, review cadence and maintenance time vary by package.

New or substantially rebuilt journeys, additional accounts, migrations and custom integrations need separate agreement. Other platforms receive their own scope; AIQ allowances do not automatically carry across.

Can you take over existing flows?

Yes, subject to an account and scope review. We first establish what is running, what the team has approved and which dependencies or unknowns need attention.

Are new flows included every month?

Not by default. The agreement distinguishes initial builds, ongoing maintenance and new project work so the workload and cost stay clear.

How is lifecycle performance reviewed?

We use the reporting available in the account and explain its limits. Activity and attributed outcomes are useful evidence, but they do not establish that the program caused a specific revenue change.