
Survey Questions & Answer Choices
State of the GTM Pro 2026 — 12 sections, 60 questions. Use Print to export as PDF.
About you and your role
Six quick questions about what you do today.
- Marketing Operations
- Revenue Operations
- Sales Operations
- GTM Engineering
- GTM Architecture
- Data & Analytics
- Enablement
- Customer Success Operations
- Marketing generalist with ops responsibilities
- Consultant or agency serving ops
- Other
- Marketing Operations
- Revenue Operations
- Sales Operations
- GTM Engineering
- GTM Architecture
- Data & Analytics
- Enablement
- Customer Success Operations
- Marketing generalist with ops responsibilities
- Consultant or agency serving ops
- Other
- I was not working in ops 12 months ago
- I was not working
- Owner / Founder / CEO
- Chief Operating Officer
- Chief Financial Officer
- Chief Marketing Officer
- Chief Revenue Officer
- Chief Technology Officer
- Other C-suite
- Senior Vice President
- Vice President
- Senior Director
- Director
- Senior Manager
- Manager
- Individual Contributor / Staff
- Contractor / Consultant
- Other
- 0–1 years
- 2–5 years
- 6–9 years
- 10–14 years
- 15+ years
- 0–1 years
- 2–5 years
- 6–9 years
- 10–14 years
- 15+ years
- Yes, closely
- Roughly, but it understates the scope
- No — my title describes a narrower job than I do
- No — my title describes a broader job than I do
Your company
Three questions so we can compare you with companies like yours.
- 1 (self-employed)
- 2–10
- 11–50
- 51–100
- 101–500
- 501–1,000
- 1,001–5,000
- 5,001–10,000
- 10,001+
- Technology
- SaaS
- Healthcare
- Financial services
- E-commerce
- Manufacturing
- Education
- Media & entertainment
- Professional services
- Real estate
- Retail
- Telecommunications
- Transportation
- Energy
- Other
- Sales-led
- Product-led
- Hybrid
- Channel or partner-led
- Self-serve / e-commerce
Where ops sits
How your team is set up and who it reports to.
- Marketing
- Revenue Operations
- Sales
- Finance
- Product
- IT / Engineering
- C-suite directly
- Other
- Chief Marketing Officer
- VP of Marketing
- Director of Marketing
- Chief Revenue Officer
- Chief Operating Officer
- Chief Executive Officer
- Chief Financial Officer
- Chief Technology Officer
- VP of Sales
- VP of RevOps
- Head of Revenue Operations
- Head of Sales Operations
- Head of Marketing Operations
- IT / Engineering leadership
- Not sure
- Marketing Operations
- Revenue Operations
- Sales Operations
- GTM Architecture
- GTM Engineering
- Data & Analytics
- Enablement
- Customer Success Operations
- Yes
- No
- Not sure
- Sales
- Sales Operations
- Revenue Operations
- Demand Generation
- C-suite / leadership
- IT
- Customer Success
- Support
- Product
- Finance
- Partnerships
- None
Team and resources
Headcount and budget authority.
- Just me
- 2–3
- 4–7
- 8–12
- 13+
- We don't have a full-time ops resource
- Grew
- Stayed flat
- Shrank
- We tried and failed to get a role approved
- Work was absorbed by automation or AI instead of a hire
- Work simply didn't get done
- Work was outsourced to an agency or contractor
- None of these
- Under $25K
- $25K–$100K
- $100K–$500K
- $500K–$1M
- More than $1M
- Not sure
- None — I can't approve spend alone
- Under $25K
- $25K–$100K
- $100K–$500K
- $500K–$1M
- More than $1M
- Not sure
- Yes
- No
- Often
- Sometimes
- Never
Scope and ownership
What you own. This is the heart of the survey, so thanks for taking your time here.
- Marketing automation ownership
- CRM ownership
- Integration management
- Data governance
- Database management
- Attribution & reporting
- Lead routing
- Lead scoring
- Lifecycle / nurture strategy
- AI automation
- Website / landing page management
- Campaign operations
- Vendor management
- Revenue operations
- Annual GTM planning
- Project management
- Own
- Co-own
- Support
- Not involved
- Yes — it's me
- Yes — someone else
- I could name several people, but no single owner
- No — I couldn't name anyone
- Not sure
- 90% execution / 10% strategy
- 70% execution / 30% strategy
- 50 / 50
- 30% execution / 70% strategy
- Mostly strategic (80%+)
- 90% execution / 10% strategy
- 70% execution / 30% strategy
- 50 / 50
- 30% execution / 70% strategy
- Mostly strategic (80%+)
- I lead this planning
- I contribute regularly
- I am occasionally involved
- I am not involved
- Marketing
- Sales
- Customer Success
- Partner / Channel
- Finance
- Product
- None of these
- Other
- Marketing → Sales
- Sales → Customer Success
- Data → Reporting
- Planning → Execution
- Vendor → Internal team
- None of these
- Other
Skills and barriers
What it takes to succeed, and what's in the way.
- Cross-functional collaboration and communication
- Strategic thinking, planning and roadmap development
- Technical proficiency with MarTech and SalesTech
- Data analysis, interpretation and storytelling
- Data modeling and architecture
- AI and automation expertise
- Project and process management
- Data governance and compliance
- Product management thinking (intake, roadmap, prioritization)
- Coding or development skills
- Critical
- Lacking
- Both
- Neither
- Organizational silos and limited collaboration
- Poor data quality and systems integration
- Leadership misunderstanding or misalignment
- Insufficient budget / resources
- Lack of skilled personnel
- Lack of needed tools / martech
- Too much execution work to make room for strategy
Your tech stack
The platforms you run and what you can do with them.
- Marketo
- HubSpot
- Pardot / Account Engagement
- Salesforce Marketing Cloud
- Eloqua
- Braze
- Iterable
- Klaviyo
- Conversion
- Inflection
- Pamings
- Phave
- We don't have a MAP
- Other
- Salesforce
- HubSpot CRM
- Microsoft Dynamics
- Pipedrive
- Zoho
- No CRM in use
- Other
- Marketing automation platform
- CRM
- Project / task management
- Analytics / BI
- Data warehouse or lakehouse
- Reverse ETL / data activation
- Data management or enrichment
- Tagging or tracking
- Email or landing page builders
- AI-powered tools
- Integration / iPaaS
- Direct query access to the warehouse
- Can write SQL against production data
- Own or co-own the semantic / metrics layer
- Build or maintain reverse-ETL syncs
- Depend on a data team for every request
- No warehouse exists
- Write and debug SQL
- Write Python or a scripting language
- Build or consume an API integration
- Configure webhooks
- Build a data model or schema
- Use AI to write code I could not write myself
- None of these
- Ability to integrate with existing tools
- Cost and licensing model
- Flexibility and customization
- Reporting and analytics capabilities
- Ease of use for ops teams
- Scalability across regions or business units
- Vendor support and onboarding
- Compliance and data governance
Data and measurement
How you measure success and where the data is heading.
- Strategic project completion and outcomes
- Operational efficiency metrics
- Pipeline velocity and conversion rates
- ROI of campaigns and initiatives
- Lead conversion rates
- Customer journey optimization and experience
- Data quality scores
- We don't have a primary KPI
- Not sure
- AI or ML-based tools
- Marketing attribution or reporting
- Workflow and process automation
- Customer data platforms or data warehouses
- Lead scoring or routing automation
- System integration platforms
- Campaign execution / content tools
- Project or resource management
- We are not planning to invest
- Implement a strategy for data quality and integrity
- Enrich data to support GTM initiatives
- Assess and understand our data health
- Develop a formal data strategy
- Make our data usable by AI tools and models
- Consolidate data into a warehouse
- Build or improve the metrics layer
- Other
- We have no formal data priorities
- No
- Partially
- Thoroughly
- Not at all
- Partially
- Fully
- Ops
- Marketing
- No one
- Unclear
- Other
- Weekly
- Monthly
- Quarterly
- Yearly
- Never
AI in practice
How AI is actually showing up in your work.
- Yes, extensively across many workflows
- Yes, in a few workflows
- Yes, we're beginning to test or experiment with it
- Not yet, but we're exploring it
- No, and we have no plans to do so
- Daily
- Several times a week
- Weekly
- Monthly
- Never
- Writing copy or content
- Building workflows or automation
- Cleaning or enriching data
- Reporting and analysis
- Writing code, SQL or formulas
- Research
- Documentation
- QA and testing
- None yet
- Always
- Usually
- Sometimes
- Never
- Live connected systems
- Context I paste in
- A mix of both
- Not sure
- AI absorbed work we would otherwise have hired for
- AI made a case for adding headcount
- AI has not changed our staffing either way
- Too early to say
GTM Architecture and GTM Engineering
Two role titles everyone is talking about. We want your honest read.
- GTM Engineer
- GTM Architect
- Very familiar
- Somewhat familiar
- Aware but unsure
- Unfamiliar
- They are the same role with different names
- Architecture is the senior, strategic layer above Engineering
- Engineering is the broader role; Architecture is a specialization within it
- They are two distinct roles with different skill sets
- I'm not familiar enough with the terms to say
- GTM Architect
- GTM Engineer
- Both equally
- Neither
- I'm not familiar enough with the terms to say
- Completely new skill sets
- Mostly new with some overlap
- Mostly traditional skills with new terminology
- Simply rebranding of traditional Marketing Ops roles
- I'm unsure
- Yes
- No
- Not sure
- Data modeling and architecture expertise
- Advanced technical proficiency (MarTech / SalesTech)
- Strategic planning and product management mindset
- Cross-functional alignment and communication
- Deep understanding of AI and automation
- Systems design and integration architecture
- Commercial and revenue fluency
- Coding or development skills
- Other
- Lack of clear role definition and understanding
- Organization structure constraints
- Misalignment with current ops responsibilities
- Insufficient leadership buy-in or support
- Limited training and resources
- No budget for a new senior role
- Leadership prefers the GTM Engineer title
- GTM Engineer
- GTM Architect
- Posted a role
- Hired externally
- Retitled someone internally
- No
- Don't know
- Maintain a roadmap for the GTM tech stack
- Run an intake and prioritization process
- Own build-versus-buy decisions
- Design system architecture across more than one GTM function
- Write requirements or specs for other teams
- Set data standards or governance policy others must follow
- Run a formal release or change-management process
- None of these
- More reliance on predictive analytics and advanced reporting
- Greater emphasis on GTM strategy and planning
- Increased cross-functional integration (RevOps model)
- Real-time data integration and automation
- Enhanced data privacy regulations
- Emergence of GTM Architecture roles
- Emergence of GTM Engineering roles
- Consolidation of the GTM tech stack
- Ops moving out from under marketing
Career and outlook
Where you're headed and how it feels to do this work.
- Clearly defined and available
- Limited but improving
- Limited with little improvement
- No clear pathway or opportunities
- Misalignment with organizational leadership expectations
- Lack of recognition within the organization
- Limited growth opportunities
- Insufficient training or skill development
- Compensation
- Workload or burnout
- Other
- On-the-job training and experience
- Mentorship and peer collaboration
- Support from leadership
- Networking opportunities
- Certifications or formal education
- Other
- Strongly agree
- Agree
- Neutral
- Disagree
- Strongly disagree
- Highly strategic (ops seen as a key business driver)
- Supportive but tactical
- Administrative and reactive
- Underappreciated and misunderstood
- Very satisfied
- Somewhat satisfied
- Neutral
- Somewhat dissatisfied
- Very dissatisfied
- Go into management / build a team that reports to me
- Stay in ops as a technologist
- Move into RevOps / GTM Ops
- Move into GTM Engineering / GTM Architecture
- Move into SalesOps
- Move into data or analytics
- Become an independent consultant
- Work for a consultancy or agency
- Move into another area of marketing
- Shift to a totally different job function
- None of these
- Very likely
- Somewhat likely
- Unsure
- Somewhat unlikely
- Very unlikely
- Compensation
- No career path
- Leadership
- Burnout
- Scope of the role
- Relocation
- Yes
- No
- Depends
- None
- 1–2 hours
- 3–5 hours
- 6–10 hours
- 11 hours or more
- Yes, extensively
- Yes, somewhat
- No, but we are planning to
- No, not currently under consideration
A few last details
Three quick ones. Compensation is used only to compare groups and is never reported individually.
- Under $100K
- $100K–$150K
- $150K–$250K
- More than $250K
- Prefer not to say
- 18–22
- 23–25
- 26–30
- 31–35
- 36–40
- 41–45
- 46–50
- 51–60
- 60–65
- 65+
- Prefer not to say