Mida
Day 10 after signup
A Mida Use Case: The crux of buying fruit trees that will actually fruit
Why it works
- Open with a specific use case so readers immediately know what the issue is about.
- Explain the customer problem before introducing the proposed experience, making the solution easy to follow.
- Use one clear primary call to action, then keep any closing reminder focused on the same resource.
How it is built
- Weekly topic intro
- Shopping problem overview
- Planner concept explanation
- Use case call to action
- Library reminder
Email copy
This week: An orchard planner for Trees.com's fruit tree page Hey [First name] [First name], This week, we take a look at Trees.com, where the four checks that decide whether a fruit tree fruits (zone, state shipping, pollination partner, harvest season) are spread across the page, and Honeycrisp, Rainier, Bing and Fuji never say in the buy box that they need a second variety. The cost shows up in reviews: "half died or never bloomed." We looked at what happens when a one-step planner builds a complete orchard instead. Shoppers pick a fruit and a tree count, and every tree is matched to their zone and state, with a pollination partner added where needed and one click to add it all to the cart. Head to our Test Ideas page for the full breakdown, demo video, and the experiment we built in MidaGX. Read the Full Use Case P.S. Our library of use cases are live on our Test Ideas page — Every breakdown, demo video, and experiment we've built is there whenever you need inspiration for your next test. The email was sent to you@example.com. To no longer receive these emails, unsubscribe here.