Marketing Automation Requirements Checklist (2026)
A marketing automation requirements checklist keeps the buying process focused on workflows, data, and sales handoff instead of demo polish. Most platforms can show an impressive journey builder. Fewer can support your actual lifecycle rules, CRM sync, scoring model, consent data, reporting, and day-to-day ownership.
The practical question is not "which automation tool has the most features?" It is "which tool can run the workflows we can define, maintain, and measure?" Use this checklist before shortlisting HubSpot, Marketo, ActiveCampaign, Brevo, or another automation platform.
If the category choice is still unclear, start with email marketing vs marketing automation. If the automation decision is part of a larger CRM purchase, use the CRM requirements checklist first, then come back here for the marketing automation layer.
Marketing automation requirements checklist: quick version
Use this short marketing automation requirements checklist before booking demos:
- Define the business outcome the automation platform must improve.
- Map the lifecycle stages the tool will support.
- List the workflows you need in the first 90 days.
- Decide which triggers, conditions, delays, branches, and goals each workflow needs.
- Define audience segments by data fields, behavior, consent, and lifecycle stage.
- Write lead scoring rules before asking vendors about scoring features.
- Define the sales handoff: threshold, owner, SLA, task, alert, and fallback.
- Document CRM sync rules for contacts, companies, deals, activities, and campaign data.
- List required reporting: workflow performance, source, lifecycle conversion, pipeline, and revenue influence.
- Check data, consent, unsubscribe, suppression, and audit requirements.
- Define implementation ownership and weekly maintenance responsibilities.
- Score vendors against must-have workflows, not feature volume.
TechTarget's marketing automation checklist makes a useful point for small teams: automation requirements should cover goals, customer journey, segmentation, what to automate, CRM fit, lead scoring, and APIs before a platform is selected. That framing matters because most failed automation projects are not caused by a missing button. They are caused by unclear rules.
Marketing automation requirements checklist before demos
Most teams start too late. They watch three demos, fall in love with one interface, then try to force their workflows into the product after purchase.
Start with the operating model instead.
Define the outcome
Pick one main outcome for the first purchase decision:
- Convert more demo requests into sales conversations.
- Nurture early-stage leads until they are ready for sales.
- Reduce manual follow-up after webinars, downloads, trials, or pricing visits.
- Connect campaigns to pipeline and revenue reporting.
- Replace disconnected email, forms, CRM tasks, and spreadsheets.
- Support ecommerce or subscription lifecycle messaging.
- Give marketing and sales one shared view of lead readiness.
The outcome becomes the tie-breaker. ActiveCampaign may be the better fit if the outcome is lifecycle automation depth at a lower platform cost. HubSpot may be the better fit if CRM, sales, forms, and reporting should live together. Marketo may be the better fit if the team has enterprise B2B campaign operations, scoring, Salesforce alignment, and governance needs.
For those trade-offs, compare ActiveCampaign vs HubSpot, HubSpot vs Marketo, and HubSpot vs Brevo before treating all automation platforms as interchangeable.
Map the lifecycle stages
Marketing automation needs a lifecycle model. Otherwise workflows become a pile of one-off campaigns.
Define the stages you will use, such as:
- subscriber
- lead
- marketing qualified lead
- sales qualified lead
- opportunity
- customer
- expansion or renewal candidate
- inactive or disqualified
HubSpot's lifecycle stage documentation describes lifecycle stages as a way to categorize contacts and companies by where they are in marketing and sales processes. That is the right level of thinking. The exact labels can change, but the team needs shared stage definitions before automation starts moving people.
For each stage, write:
- entry criteria
- exit criteria
- owner
- allowed campaigns
- sales visibility
- suppression rules
- reports that depend on the stage
This keeps marketing from pushing leads to sales too early and keeps sales from ignoring leads that met a real threshold.
List the first 90-day workflows
Do not buy around every future idea. Write the workflows needed in the first 90 days.
Common B2B examples:
- demo request routing
- content download nurture
- webinar registration and follow-up
- pricing-page sales alert
- abandoned demo booking follow-up
- trial activation or onboarding
- lead score threshold alert
- stale lead recycle workflow
- customer onboarding education
- renewal or expansion signal workflow
Common ecommerce examples:
- welcome sequence
- abandoned cart
- browse abandonment
- post-purchase education
- review request
- replenishment reminder
- win-back campaign
- VIP or loyalty segment campaign
If most of your needs are simple campaigns and short sequences, you may not need a full automation platform yet. Read signs you've outgrown your email marketing tool before replacing a simple tool with a more expensive one.
Marketing automation requirements by workflow
Write requirements as workflows, not feature names.
"Has automation" is not a requirement. "When a demo request is submitted from an account with more than 100 employees, create a sales task, notify the account owner, assign lifecycle stage SQL, and exclude the person from general nurture" is a requirement.
Trigger requirements
List the events that should start or update a workflow:
- form submission
- list membership
- email click
- page visit
- pricing-page view
- webinar registration
- event attendance
- demo request
- trial signup
- product usage event
- purchase
- support issue
- lifecycle stage change
- CRM deal created
- renewal date approaching
The key requirement is not just whether the trigger exists. It is whether the trigger can use the right data at the right time. A pricing-page visit is only useful if the platform can connect it to a known contact, account, source, consent status, and sales owner.
Logic requirements
Document the workflow logic you need:
- if and then branches
- wait steps
- goal steps
- split tests
- score changes
- field updates
- task creation
- owner assignment
- internal notifications
- suppression checks
- re-entry rules
- exit rules
This is where lower-cost tools and deeper automation platforms separate. Brevo may be enough for practical email, SMS, WhatsApp, and lightweight CRM workflows. ActiveCampaign is stronger when branching logic, scoring, CRM actions, and lifecycle journeys are the center of the purchase. Compare ActiveCampaign vs Brevo if that is the shortlist.
Channel requirements
Automation is often email-led, but requirements should cover every channel the workflow touches:
- SMS
- in-app or product messages
- ads and retargeting audiences
- sales tasks
- sales sequences
- direct mail or event follow-up
- support or success notifications
The more channels a workflow touches, the more important suppression and ownership become. A customer should not receive a generic lead nurture email while support is handling a serious issue or while sales is negotiating a renewal.
Marketing automation requirements for CRM handoff
CRM handoff is the part of marketing automation that most often breaks. The automation tool can send emails, but sales still needs a clean record, a reason to act, and a clear next step.
CRM sync requirements
Write what must sync, in which direction, and how often:
| Data | Requirement to define |
|---|---|
| Contacts | Which fields sync, which system wins conflicts, and how duplicates are handled |
| Companies or accounts | How contacts attach to accounts and how account-level fields update |
| Deals or opportunities | Whether automation can read or create deal data |
| Activities | Which email, form, page, and campaign actions are visible to sales |
| Lifecycle stage | Which system updates the stage and whether backward movement is allowed |
| Consent and subscription status | Which system owns opt-out, suppression, and subscription data |
| Source and campaign data | How UTM, ad, form, and content data survive the handoff |
If the CRM is the center of the decision, compare HubSpot vs Salesforce, Pipedrive vs HubSpot, and Zoho CRM vs HubSpot. If the team wants CRM and automation in one system, read best CRMs with email marketing and CRM email marketing software.
Lead scoring requirements
Lead scoring should not start with arbitrary points. Start with the sales definition of readiness.
Define:
- fit signals, such as industry, company size, region, role, tech stack, or plan
- intent signals, such as pricing visits, demo requests, product usage, webinar attendance, and high-value page views
- engagement signals, such as recent email clicks, content downloads, repeat visits, and event participation
- negative signals, such as student emails, competitor domains, unsubscribes, bounced emails, low-fit regions, and inactivity
- decay rules, because old engagement should lose value over time
- thresholds for MQL, SQL, sales alert, nurture recycle, and disqualification
Adobe's Marketo Engage scoring guidance frames scoring as a way to measure qualification and set sales-ready criteria. That is the standard to use in demos: can the platform show why someone became sales-ready, not just assign a number?
Sales handoff requirements
For every sales handoff, document:
- what creates the handoff
- who receives it
- what task is created
- how fast sales should act
- what sales sees on the record
- what happens if sales rejects or ignores the lead
- how the lead returns to nurture
- how conversion is reported
This is where a workflow becomes a revenue process. Without handoff rules, automation only creates more alerts and noisier CRM records.
Reporting and attribution requirements
Reporting requirements should come before the demo. Otherwise every vendor dashboard looks good because it is built on clean sample data.
Useful reporting requirements include:
- campaign performance by audience and lifecycle stage
- workflow conversion by step
- form conversion by source
- MQL to SQL conversion
- SQL to opportunity conversion
- sales response time after automation alerts
- meetings booked from automation
- pipeline influenced by campaign
- revenue influenced by campaign
- unsubscribe and complaint trends by workflow
- stale workflow membership
- contacts stuck in lifecycle stages
- duplicate and missing field reports
Current marketing tools put more weight on AI, data, and personalization every year. The useful takeaway for buyers is simple: automation is only valuable when the data behind it is clean enough to personalize and report on.
If your team cannot answer which campaign created pipeline, whether MQLs are accepted by sales, or where leads stall, the platform has not met the reporting requirement.
For B2B SaaS teams, pair this with the SaaS marketing stack and B2B tech stack guides. Automation reporting depends on analytics, forms, CRM, sales, support, and customer-data handoffs outside the workflow builder.
Data, consent, and implementation requirements
Marketing automation touches sensitive data: email consent, subscription status, sales activity, customer history, product usage, and sometimes billing or support context.
Define requirements for:
- opt-in source
- unsubscribe handling
- global suppression lists
- regional consent rules
- double opt-in if needed
- marketing contact status
- bounced and invalid email handling
- deleted or archived contacts
- audit history
- field permissions
- export permissions
- data retention
- test environments or sandbox access
Contact pricing also belongs in the requirements document. HubSpot, ActiveCampaign, Brevo, Mailchimp, Klaviyo, and other tools do not count contacts the same way. Before importing old records into an automation platform, read email marketing contact billing and clean the list with the email list cleaning checklist.
Implementation requirements should cover ownership too:
- who owns lifecycle stage definitions
- who owns workflow creation
- who approves new fields
- who reviews scoring rules
- who monitors failed automations
- who maintains CRM sync
- who reviews reports with sales
- who documents changes
If the vendor is already chosen and the project is moving into setup, use the CRM implementation checklist and email marketing migration checklist before importing contacts or rebuilding workflows.
Marketing automation RFP and vendor demo scorecard
This checklist can also become a lightweight marketing automation RFP. Keep it practical: ask vendors to prove the workflows, data rules, CRM handoff, scoring model, reporting, suppression logic, and implementation support your team actually needs. Do not send a bloated questionnaire that nobody scores consistently.
Ask each vendor to demo your requirements with realistic sample data. Do not accept a generic product tour.
| Requirement | Priority | Vendor A | Vendor B | Notes |
|---|---|---|---|---|
| Demo request routes to the right owner with source data intact | Must | Test with two regions and two owners | ||
| Lead score combines fit, behavior, recency, and negative signals | Must | Ask how the score is explained to sales | ||
| Workflow can suppress customers, open opportunities, and unsubscribed contacts | Must | Check all suppression sources | ||
| CRM record shows campaign, web, email, and lifecycle history | Must | Sales should not need a marketing login | ||
| Reports show MQL to SQL to opportunity conversion | Should | Ask for stage conversion and time-in-stage | ||
| Admin can audit workflow changes and failed syncs | Should | Important for growing teams |
Use a five-point scale:
- Does not meet the requirement.
- Meets it only with awkward workarounds.
- Meets it with setup, add-ons, or custom integration.
- Meets it clearly.
- Meets it clearly and is easy for weekly users to maintain.
The winner is not the tool with the longest feature list. The winner is the tool that meets must-have workflows with the least hidden operational cost.
For category-level research, use best marketing automation software. If the shortlist is still broad, compare ActiveCampaign vs HubSpot, HubSpot vs Marketo, HubSpot vs Brevo, and ActiveCampaign vs Brevo.
Common marketing automation requirements mistakes
Buying automation before defining the lifecycle
The workflow builder cannot fix unclear lifecycle stages. Define the stages first, then automate movement between them.
Confusing campaign sending with automation
If the team only sends newsletters and promotions, a standard email marketing platform may be enough. A marketing automation platform is justified when behavior, scoring, CRM actions, routing, and reporting matter.
Ignoring sales adoption
Marketing can create alerts, tasks, and scores, but sales needs to trust them. Include sales reps and managers in the handoff requirements before launch.
Treating scoring as a one-time setup
Scores drift. Review scoring after enough leads move through the funnel. Remove signals sales ignores, add signals that correlate with good opportunities, and use decay rules so old behavior does not create false urgency.
Forgetting suppression rules
Bad suppression logic can create embarrassing customer experiences. Exclude customers, open opportunities, active support escalations, unsubscribed contacts, bounced addresses, and disqualified leads from the wrong workflows.
Underestimating admin work
Automation needs maintenance. Someone must own field changes, sync errors, workflow testing, scoring updates, report review, consent rules, and documentation.
Actionable takeaways
- Write marketing automation requirements before demos, not after.
- Start with lifecycle stages, workflows, data, scoring, sales handoff, and reporting.
- Compare vendors by whether they can run your first 90-day workflows.
- Keep scoring explainable to sales.
- Treat CRM sync and consent data as must-have requirements.
- Build reports before launch so the team can see where leads move, stall, and convert.
- Choose a platform your team can maintain, not just one that looks powerful in a demo.
Frequently Asked Questions
What is a marketing automation requirements checklist?
A marketing automation requirements checklist is a structured list of workflows, data rules, CRM handoffs, scoring rules, reporting needs, consent rules, integrations, and ownership requirements a team defines before choosing or implementing automation software.
What should marketing automation requirements include?
They should include lifecycle stages, workflow triggers, branching logic, segmentation, lead scoring, CRM sync, sales alerts, source tracking, campaign reporting, consent handling, suppression lists, security, implementation ownership, and vendor scorecard criteria.
How is this different from a CRM requirements checklist?
A CRM requirements checklist defines the system of record for contacts, companies, deals, owners, pipeline, activities, permissions, and reports. A marketing automation requirements checklist defines what should happen around those records: nurture, scoring, routing, segmentation, campaign triggers, suppression, and lifecycle updates.
Do small businesses need marketing automation?
Only if behavior-based workflows, lead nurturing, CRM handoff, or multi-channel messaging are real needs. If the business mainly sends newsletters, promotions, and simple welcome emails, standard email marketing software may be cheaper and easier.
Which teams should help write marketing automation requirements?
Include marketing, sales, operations, CRM admin, customer success or support if post-sale workflows matter, and leadership if reporting or pipeline influence is part of the purchase. Do not let marketing write the handoff rules without sales input.
How many workflows should we define before buying?
Define the first 5 to 10 workflows in enough detail to test vendors. You do not need every future journey mapped, but you do need enough real workflows to reveal whether the platform can support your lifecycle, CRM handoff, reporting, and data rules.
Next steps
Use the checklist to write your must-have workflows before you compare platforms.
If the decision is automation-first, compare ActiveCampaign vs HubSpot, ActiveCampaign vs Brevo, and ActiveCampaign vs Mailchimp. If the decision is CRM-led or enterprise B2B, compare HubSpot vs Marketo, HubSpot vs Salesforce, and HubSpot vs Brevo.
For broader planning, read email marketing vs marketing automation, B2B tech stack, and CRM requirements checklist. Then use best marketing automation software when you are ready for a ranked shortlist.
