Enterprise trade accounts with complex, multi-stakeholder buying processes involving 3-5+ decision makers. High account volume where manual orchestration doesn't scale.
Smaller trade accounts where a single contact typically makes the purchasing decision. Lower account volume where manual segmentation is manageable.
Use Meridian Journey B2B for your highest-value enterprise trade accounts where buying groups are complex and multi-stakeholder. Use standard Meridian Journey for smaller trade accounts where a single contact makes the decision.
Define a threshold — accounts above $X annual revenue or with 3+ known contacts get Meridian Journey B2B treatment. Everyone else gets standard Meridian Journey journeys. This maximizes ROI on the Meridian Journey B2B investment while keeping the simpler accounts simple.
How many stakeholders in a typical Cordova trade purchase? If usually 1 person → Meridian Journey B2B is overkill. If 3-5 decision makers → it adds real value.
Is buying group management overhead justified by account count? B2B Edition shines at scale with hundreds of accounts.
Does sales need in-CRM visibility into buying group status? B2B Edition provides Salesforce/Dynamics 365 integration for this.
Does the client already have Convoy Engine?? If not, adding it solely for B2B Edition significantly increases scope.
1. Model 3-5 representative Cordova accounts with realistic buying groups
2. Build a simple account journey through awareness → evaluation → purchase
3. Test role-based email orchestration (different content per role)
4. Review reporting dashboards for engagement visibility
5. Document findings in a recommendation memo scoring all three options
Your architecture recommendation memo becomes a key input for the client discussion. Score each option against the four criteria, include what you learned from sandbox testing, and make a clear recommendation with rationale.