Managed lifecycle email
ContextPilot turns first-party product behaviour into lifecycle email a person can review and send. It is a managed service for small SaaS and marketplace teams: setup, then monthly running and tuning.
What exists now is that reviewed path. A pilot is how the work is scoped. Scheduling, automated experiments, and a self-serve product are not built.
02
A saved item in the product becomes a reviewed email. The pilot measures whether the person comes back to that item.
01
02
Illustrative draft
To Sam Example
The shortlist you saved is still there
You saved “Q3 supplier shortlist” on 28 October and have not opened it since.
Three suppliers on that list updated availability this week. The shortlist is otherwise unchanged.
Link in the draft: Open the shortlist
You would receive this because of your own activity in Example Co. Opt out in one step. A person reviews the draft before it is sent. This specimen is not a link.
03
Agreed action: opened that saved shortlist within 7 days.
The action is in the product, not an email open rate.
Where volume permits, a holdout group is not sent the message, so the groups can be compared.
No outcome is shown. A pilot would measure the action. It would not promise a change.
03
The working prototype is a reviewed draft, not a platform you log into. A person stays in the path from the first step to the send.
Choose the context
A person selects the in-product fact the message is allowed to use.
Write the brief
A model prepares a brief from that context.
Propose angles
A few ways to say it, still tied to the same fact.
Draft the email
A draft with one next step back into the product.
Edit and send
A person edits the draft and sends it through the mail system the team already uses.
There is no date on this list. It is a boundary, not a roadmap.
04
Each pilot starts with one of these. Upgrade is in scope only when a paid offer already exists and you have approved it.
Someone who has used the product and then gone quiet. The message cites a real earlier action and offers a single way back.
Someone who started and has not reached the first useful action. The message names that step, which is already visible in the product.
A saved, drafted, or unfinished item that is still there. The message refers to that item. It does not guess at the person’s life outside the product.
Only where a paid plan exists and the offer is one you have approved. The message may refer to a limit they have actually met. It is not the default brief.
The first experiment is internal, on Domodex, which has no paid tier. It is there to learn whether a message grounded in product behaviour leads to meaningful engagement. Domodex is not a customer, and this is not a result.
05
The same letter goes to a list because the calendar says it is time. It is not written from something a particular person did.
A model can write fluent email. Without a duty to a fact in the product, the draft is only tone. If a draft cannot point at that person’s own in-product behaviour, it does not send.
One use case. A fact from that person’s use of the product. A draft a human can edit. Sending through mail you already operate. An agreed action to measure afterwards.
06
We set the pilot up and then run it with you. One product, one narrow data connection, one use case. Drafts stay reviewed.
The action is agreed up front: a return, a first useful step, a saved item opened, or an upgrade only where a paid offer exists. A holdout is used where the volume can support one.
There is a setup, then a monthly service. Scope is agreed before work starts. Prices are not published.
Answer from what is true of the product. The reading stays in this browser. Nothing is stored or sent.
Reading in progress. Answered 0 of 7. Met 0. Limits 0. Blocks 0.
Answered 0 of 7. Met 0. Limits 0. Blocks 0. Reading in progress. Nothing is stored or sent.
07
A pilot uses first-party behaviour from the product: events, saved or unfinished items, and CRM or billing where those records are already part of serving that account. The connection is narrow and agreed before setup. It is limited to what the one use case needs.
No. Not external profiles, not bought data, and not inferred facts about a person’s life outside the product. The fact in the draft has to be something they did in the product.
A person does. In the prototype, someone chooses the context, works through a brief, angles, and a draft, then edits it and sends it with the mail system you already use. The pilot keeps that review. Unattended sending is not on offer.
No. Upgrade is one use case, and only when a paid offer already exists and you have approved it. A product with no paid tier can still run a pilot on reactivation, activation, or saved work. The Domodex experiment is that kind of brief: there is no paid tier, and the measure is meaningful engagement.
Messages go to people you already have a basis to contact, and each message needs a working opt-out. The pilot minimises data to the agreed use case. It does not add a tracking programme of its own. This site does not claim GDPR compliance or any certification. The legal basis for contact stays with you to confirm.
No. Domodex is an internal experiment, and the first place this is being tried. It is not a customer, not a testimonial, and not evidence of results.
Scheduling, automated experiments, automated holdouts, and a multi-tenant self-serve product are not built. This website has no login and no dashboard. The working piece is the reviewed path from a chosen context to a draft sent through existing mail.
There is a setup, then a monthly service to run and tune the pilot. Product, data connection, use case, review, and the action to measure are agreed before work starts. Prices are not published.
The pilot agrees an action in the product before it starts, such as opening the saved item. Where volume permits, a holdout group receives no message, so the action can be compared. There is no promised lift.
No. The fit questions run in the browser and are not sent. A verified enquiry address has not been connected. There is no form, and nothing here can take your email address.