Bestemail should present what is live now, what is still beta, and what is coming later without mixing them together. That keeps the product credible and easier to sell.
Live now
These are the areas you can safely present as current product capability today.
Create campaigns with subject lines, content, and a usable drafting flow for real sending.
Use reusable email templates to speed up common campaign creation work.
Manage contacts, import audiences, and prepare lists before sending campaigns.
Create practical audience groupings around current contact and campaign workflows.
Use a real delivery workflow without exposing the infrastructure details in public-facing product copy.
Review simple campaign counts and early reporting without overselling analytics depth.
Create forms and connect them to core lead collection and contact flows.
Beta / partial
These can be shown, but they should stay clearly labeled as beta, early, or partial.
Automation screens and product direction exist, but the backend should still be treated as partial.
AI-assisted content support can be positioned as an early helper, not a fully proven conversion engine.
Builder and design guidance can be discussed carefully if the real workflow is still evolving.
This should stay under beta until there is a full end-to-end testing and result workflow in place.
Basic merge and audience targeting can be referenced, but advanced personalization should not be oversold.
Only present these as early or partial unless the exact connected workflow is already live and tested.
Coming soon
These should never be shown as if they are already available today.
Do not claim extra communication tooling until the real integration, sync logic, and workflow are implemented.
Delivery expansion should stay in roadmap territory until there is real implementation behind it.
CRM syncing should remain a roadmap item until there is working setup, authentication, and field mapping.
Avoid claims like 70+ criteria unless that exact targeting depth is already present in the product.
Keep API claims conservative unless a real stable API product and documentation are already live.
Practical rule: if a workflow is not live and testable today, it should stay in beta or coming soon.