-
Notifications
You must be signed in to change notification settings - Fork 1
Roadmap
The purpose of this document is to lay out a plan for our initial MVP of Mailbadger. Here we will establish different topics that we want to work on. Keep in mind that this is a living document, as we execute the plans, we may drop or add certain topics and features.
The MVP version of the product will contain all of the fundamentals needed for a viable e-mail marketing tool, and we aim to publish it in early July 2021.
- ✅ The core feature of mailbadger is sending a campaign, which basically translates to sending a large batch of e-mails to subscribers at once. This means that this part of the application is the most important, so for the MVP it must be thoroughly tested and proven to handle a large volume of messages.
- ✅ Ability to unsubscribe from list.
- ✅ Templated emails, ability to customize templates with fields e.g.
{{name}}
. - ✅ Monitor email sending using Amazon SES event publishing - track opens, clicked links, sends, deliveries and failures.
- ✅ Service limits (boundaries) on a per user basis depending on the tier.
- ✅ Search functionality for each resource.
- 🏃♂️ Per campaign analytics and global analytics based on events.
- ✅ Schedule campaigns.
- 🏃♂️ Ability to delete the account and all associated data.
- ⛅ API keys management.
- ✅ Role-based access control (RBAC).
-
New users should be greeted with a short walkthrough on how to use the application and should have a smooth experience with sending their first campaign.
- The steps of creating the resources is important:
- Add SES keys
- Import subscribers
- Create a template
- Create groups (segments)
- Create & send a campaign
The path to sending that first campaign should be clear to the user.
- The steps of creating the resources is important:
-
Work on responsive design (especially pages that include analytics and reports).
-
🏃♂️ Work on wireframes, animations, and overall UX for every screen and workflow.
- Provide the users an easy way to install and run the application.
- Write a comprehensive guide on how to install the application.
- Create simple monthly plans for users, which will involve three tiers:
- FOSS (self-hosted)
- Free
- Paid
- Premium
The Paid and Premium tiers will be a pay as you go type, based on the number of subscribers, and will be calculated at the end of the billing cycle and included in the costs for the upcoming month.
Tiers matrix
Self-hosted | Free | Paid | Enterprise | |
---|---|---|---|---|
# of subscribers | / | 3000 | 5000 & up | 500k & up |
# of campaigns | / | 5 per month | Unlimited | Unlimited |
Stats retention | / | 30 days | Unlimited | Unlimited |
Scheduling campaigns | ✔️ | ❌ | ✔️ | ✔️ |
Organization & team members | ✔️ | ❌ | ✔️ | ✔️ |
SAML | ✔️ | ❌ | ❌ | ✔️ |
Support | Github issues | Github issues | Email Chat | Priority support |
- Setup docs repository.
- Host documentation on netlify.
- API reference using openapi v3.
- ✅ Logo, colors & tagline.
- Setup site repository.
- Host site on netlify.
- Show pricing options.
- Mailbadger vs. alternatives page.
- Features page.
- Terms of use.