Skip to main content

Cadence

Purpose​

The Revenue Operating Cadence defines how MetaCTO runs the Revenue Context System week to week.

Its job is to make sure revenue context does not become a pile of docs. The system should actively support:

  • founder-led sales
  • SDR / BDR execution
  • demand generation
  • partner development
  • proof capture
  • market learning
  • buyer understanding
  • offer refinement
  • revenue agents
  • fast follow-up and proposal response

This cadence connects the revenue team, the context docs, and the agents into one operating system.

The goal is not more meetings. The goal is faster response, sharper decisions, stronger pipeline, better proof, and compounding GTM learning.

Core Operating Model​

Operating principle​

The Revenue Context System only matters if it improves revenue execution.

Each week, MetaCTO should use the system to:

  • respond quickly to live opportunities
  • choose the right revenue priorities
  • generate qualified demand
  • move accounts and opportunities forward
  • support founder-led selling
  • help the SDR / BDR act with better context
  • manage strategic partner relationships
  • capture proof
  • improve offer and message clarity
  • sharpen market point of view
  • improve revenue agents
  • update the revenue wiki / KB
  • log decisions
  • reduce repeated founder thinking

The operating rhythm​

Respond daily. Test weekly. Decide monthly. Recalibrate quarterly. Respond daily

Sales response, follow-up, proposal prep, marketing execution, partner touchpoints, proof capture, and agent runs happen every day based on live events.

Test weekly​

Demand gen, messaging, channels, outbound angles, proof assets, and agent outputs are reviewed weekly.

Decide monthly​

Monthly review is where MetaCTO decides what to scale, change, stop, or systematize.

Recalibrate quarterly​

Quarterly review is for strategy: positioning, ICP, offer architecture, proof maturity, market shifts, channel strategy, partner strategy, and agent permissions.

Always-On Revenue Loops​

MetaCTO should not organize all revenue work by day of the week. A small revenue team needs speed. Agents can run continuously. Inbound leads, sales replies, proposal requests, partner intros, and campaign signals do not wait for a scheduled block.

The weekly cadence exists to review and improve the system, not to delay execution.

Sales Response Loop​

Purpose​

Respond quickly to live sales signals and keep opportunities moving.

Speed is a competitive advantage. Inbound response, follow-up, proposal prep, and next-step clarity should happen as close to the event as possible.

Triggers​

  • new inbound lead
  • prospect reply
  • completed discovery call
  • proposal request
  • referral
  • partner intro
  • stalled opportunity
  • pricing or scope question
  • new stakeholder added
  • prospect opens or engages with key content

Standard​

For every meaningful sales event:

understand the account context​

identify buyer role and pain​

determine fit​

draft next step​

update CRM​

capture objection or proof signal​

assign owner​

set follow-up​

Human owners Founder owns:

  • high-value opportunities
  • strategic accounts
  • partner-led deals
  • final commercial judgment

SDR / BDR owns:

  • triage
  • account research
  • follow-up execution
  • outbound
  • CRM hygiene
  • account progression

Agent support​

Sales Ops Agent should run around every meaningful sales event.

It can prepare:

  • account brief
  • discovery summary
  • follow-up draft
  • CRM update draft
  • fit score
  • missing context list
  • next-step recommendation
  • relevant proof suggestions
  • proposal input pack

Output​

  • fast response
  • clear next step
  • updated CRM
  • captured buyer language
  • proof or objection logged
  • follow-up queue maintained

Follow-Up and Proposal Loop​

Purpose​

Make follow-up and proposals faster, sharper, and more consistent.

Follow-up cannot wait for a weekly sales day. It should happen daily and event-driven.

Triggers​

  • discovery call completed
  • buyer asks for proposal
  • buyer asks for pricing
  • internal scope decision made
  • new stakeholder joins
  • prospect goes quiet
  • proposal needs revision
  • signed deal needs handoff

Standard​

For each call or proposal event:

summarize the buyer’s situation​

identify the pain and desired outcome​

map to the right offer​

list open questions​

draft follow-up​

draft proposal input pack​

select proof assets​

identify scope assumptions​

assign next action​

Agent support​

Sales Ops Agent drafts:

  • call summary
  • follow-up email
  • CRM note
  • proposal input pack
  • proof recommendations
  • scope assumptions
  • next-step checklist

Strategy Agent supports strategic or high-value deals by drafting:

  • positioning angle
  • tradeoff memo
  • offer-fit recommendation
  • risk / opportunity summary

Marketing Agent supports with:

  • proof snippets
  • case-study excerpts
  • buyer-specific language
  • proposal copy blocks

Output​

  • same-day follow-up where possible
  • faster proposal turnaround
  • stronger proof alignment
  • fewer dropped next steps
  • cleaner handoff to delivery

Marketing Execution Loop​

Purpose​

Make marketing a daily revenue function, not a weekly event.

The Marketing Manager should create, refine, publish, test, package, and support GTM assets throughout the week.

Triggers​

  • active campaign
  • new proof
  • new objection
  • new market signal
  • founder idea
  • sales asset need
  • landing page need
  • content deadline
  • paid test update
  • SEO opportunity
  • partner asset request
  • webinar / podcast / event opportunity

Standard​

Marketing work should support one or more of:

  • qualified pipeline
  • stronger positioning
  • proof activation
  • better sales conversations
  • clearer offer education
  • audience learning
  • channel testing
  • partner enablement

Human owner​

Marketing Manager owns daily marketing execution.

Agent support​

Marketing Agent supports:

  • content drafts
  • page outlines
  • ad variants
  • founder posts
  • SEO briefs
  • webinar outlines
  • podcast prep
  • proof packaging
  • email copy
  • language system checks
  • repurposing sales insights into content

Output​

  • shipped assets
  • active tests
  • proof-backed content
  • better sales support
  • clearer market learning

Demand Gen Planning and Testing Loop​

Purpose​

Turn demand channels into measured experiments that create qualified pipeline and market learning.

Demand gen execution is daily. Planning, test design, review, and decisions happen on cadence.

Channels in scope​

  • SEO
  • blogs
  • podcast guesting
  • LinkedIn / social posts
  • webinars
  • written guides
  • video content
  • Google paid search
  • Meta paid
  • LinkedIn paid
  • Clutch / referral surfaces
  • conferences and events
  • new channel tests

Daily execution​

Marketing Manager executes and monitors channels daily.

Daily work may include:

  • writing content
  • publishing posts
  • editing landing pages
  • setting up campaigns
  • checking paid search
  • reviewing ad performance
  • repurposing sales calls
  • supporting founder thought leadership
  • preparing webinar or podcast assets
  • coordinating with SDR / BDR
  • creating sales enablement assets Weekly planning

Every Monday, define active demand gen tests.

Test Chan Audie Offer Messa Asset Succe Owne Decisi nel nce ge ss r on Signal Date

Weekly review​

Every Friday, review active tests.

Test What Signal Learning Decision Next Step Happened

Keep / Change / Stop

Monthly channel review​

Once per month, review by channel.

Chann Spend / Leads SQLs Pipelin Closed Learnin Decisio el Effort e Revenu g n e

SEO Blog / content

Podcast guestin g

LinkedI n organic

Webina rs

Google Ads

Meta Ads

LinkedI n Ads

Events / confere nces

For organic channels, “spend” may mean time and effort instead of dollars.

What to measure At minimum:

  • traffic
  • leads
  • MQLs
  • SQLs
  • meetings booked
  • proposal requests
  • pipeline created
  • closed revenue
  • cost per SQL
  • pipeline per dollar
  • conversion rate by source
  • lead quality
  • sales cycle quality
  • message learning
  • offer fit

For content channels, also measure:

  • target-account engagement
  • comments and replies
  • saves and shares
  • referral conversations
  • inbound mentions
  • assisted pipeline
  • sales usefulness
  • objection coverage

Monthly decisions​

At monthly review, decide whether to:

  • scale the test
  • refine the angle
  • change the audience
  • change the offer
  • create better proof
  • pause the channel
  • increase or reduce spend
  • turn into a campaign
  • retire the idea
  • explore a new channel

Partner Development Loop​

Purpose​

Build and manage strategic partner relationships that can create qualified mid-market opportunities, especially where trust, expertise, and warm access matter.

Partner work is primarily Founder / Strategy owned, with support from Marketing, Sales Ops, and thought leadership.

It should not be buried under general marketing.

Partner types​

  • PE operating partners
  • diligence firms
  • RevOps / growth agencies
  • executive networks
  • operator advisors
  • industry consultants
  • technology ecosystem partners
  • existing client/referral partners
  • construction / field services advisors for Spreadsheet to App
  • agencies or consultants serving growing companies

Human owners​

Founder owns:

  • strategic relationships
  • partner selection
  • high-value outreach
  • executive conversations
  • warm intros
  • partner narrative
  • deal strategy
  • deciding who is worth investing in

Marketing Manager supports:

  • partner one-pagers
  • thought leadership
  • webinar assets
  • co-marketing content
  • proof packs
  • email copy
  • landing pages
  • partner-specific collateral

SDR / BDR supports:

  • CRM tracking
  • planned touchpoints
  • follow-up reminders
  • contact enrichment
  • intro notes
  • partner-sourced opportunity tracking
  • next-step hygiene

Agent support​

Strategy Agent supports:

  • partner prioritization
  • relationship maps
  • partner-specific angle
  • follow-up recommendations
  • opportunity analysis
  • “why this partner / why now” briefs

Marketing Agent supports:

  • co-marketing ideas
  • partner content drafts
  • webinar outlines
  • one-pagers
  • proof packs

Sales Ops Agent supports:

  • partner CRM hygiene
  • next-touch reminders
  • intro summaries
  • partner-sourced pipeline tracking

Daily / event-driven execution​

  • respond to intros
  • send follow-ups
  • schedule partner calls
  • prepare partner-specific notes
  • update CRM
  • log relationship context
  • capture partner signals
  • send relevant thought leadership or proof
  • make clear asks

Weekly partner review​

Partner Owner Relation Last Next Opportu Needed ship Touch Touch nity Asset Stage

Monthly partner review​

Partner Active Intros Meetin Pipelin Closed Learnin Decisio Type Partner gs e Revenu g n s e

PE / operatin g partner s

RevOps / agencie s

Executi ve network s Industry consult ants

Tech partner s

Partner touchpoint plan​

Each important partner should have:

  • owner
  • relationship stage
  • target cadence
  • next planned touch
  • relevant offer angle
  • relevant proof
  • content to send
  • open asks
  • potential accounts
  • CRM link

Proof Capture Loop​

Purpose​

Capture evidence as revenue work happens.

If proof is not captured in the moment, it will usually be lost.

Triggers​

  • client result
  • prospect objection
  • buyer quote
  • internal time saved
  • agent output accepted
  • proposal sent faster
  • workflow improved
  • campaign creates qualified conversation
  • partner validates a pain point
  • team creates reusable asset
  • client gives praise
  • internal dogfooding creates measurable gain

Standard​

Every week should create at least one of:

  • proof item
  • quote
  • metric
  • screenshot
  • before/after note
  • case-study seed
  • proof gap

Human owner​

Marketing Manager owns the Proof Library.

Founder approves public claims.

Sales Ops / SDR and agents help capture proof signals.

Agent support​

Sales Ops Agent​

  • captures objections, buyer language, follow-up speed, proposal prep time, and sales proof signals

Marketing Agent​

  • packages proof into usable assets

Strategy Agent​

  • identifies which proof supports or challenges the current positioning

Weekly proof questions​

Ask every Friday:

  • What claim did we make this week that needs evidence?
  • What result did we create that should become proof?
  • What internal output could become a case-study seed?
  • What client/prospect quote should be saved?
  • What before/after story is emerging?
  • What metric should we start tracking now?

Market Signal Capture Loop​

Purpose​

Capture outside-world learning continuously and synthesize it on cadence.

Market research belongs in the cadence, but the actual research lives in Doc 9: Market Context.

Signals to capture​

  • AI adoption trends
  • production AI language
  • mid-market AI ROI concerns
  • buyer objections
  • competitor messaging
  • category terms
  • LinkedIn / founder conversations
  • analyst reports
  • search trends
  • partner/channel feedback
  • industry-specific pain
  • engineering AI performance signals for AEMI
  • spreadsheet pain signals for Spreadsheet to App

Daily / event-driven capture​

Anyone can capture:

  • buyer phrase
  • objection
  • competitor claim
  • market stat
  • interesting article
  • podcast insight
  • keyword trend
  • channel signal

Weekly synthesis​

Marketing Manager owns a light weekly scan.

Output:

  • 3 market signals
  • 3 buyer phrases
  • 3 content ideas
  • 1 implication for messaging
  • 1 implication for sales

Monthly synthesis​

Marketing Manager produces a 1–2 page Market Context Update:

  • what changed
  • what buyers are saying
  • what terms are gaining traction
  • what competitors are emphasizing
  • what we should test
  • what we should ignore
  • what should update in Language System or Offer Context

Revenue Context Maintenance Loop​

Purpose​

Keep the Revenue Context System current, useful, and authoritative.

The docs are not archival. They are operating assets.

Core revenue context docs​

Company Truth​

ICPs​

Offer Context​

Other Offers / Sub-SKUs​

Language System​

Proof Library​

Revenue Agent Constitution​

Revenue Operating Cadence​

Market Context​

10.Buyer Context 11.Partner Context 12.Channel and Campaign Context 13.Source-of-Truth Map 14.Decision Log

Triggers for context updates​

  • decision made
  • proof captured
  • language changed
  • offer definition changed
  • ICP insight learned
  • market signal repeats
  • agent repeatedly fails because context is missing
  • source-of-truth conflict appears
  • buyer language changes
  • offer gets traction or fails to get traction
  • channel test produces signal
  • partner relationship creates learning

Weekly updates​

Owner: Marketing Manager Reviewer: Founder for strategic changes

Update weekly:

  • Proof Library
  • Decision Log
  • market notes
  • buyer language
  • agent improvement notes
  • channel test notes
  • partner notes
  • open questions

Update only when needed:

  • Company Truth
  • ICPs
  • Offer Context
  • Language System
  • Revenue Agent Constitution

These should not change casually.

Update rules​

Minor updates​

Can be made by owner.

Examples:

  • add proof item
  • add market note
  • tag objection
  • add quote
  • add campaign result
  • add partner touchpoint
  • correct typo
  • add source link

Major updates​

Require founder review.

Examples:

  • change ICP definition
  • change flagship offer positioning
  • change approved language
  • change offer hierarchy
  • retire a SKU
  • approve public proof claim
  • change agent permission level
  • change channel strategy
  • change partner strategy

Stale content rule​

If a doc section has not been used, reviewed, or validated in 90 days, mark it:

  • current
  • needs review
  • outdated
  • archived

Agents should not treat outdated content as current truth.

Revenue Agent Improvement Loop​

Purpose​

Improve revenue agents as part of operations, not as a side project.

Agents can run 24/7 and respond to incoming events, but humans must review patterns, failures, and permission levels on cadence.

Triggers​

  • bad output
  • great output
  • repeated correction
  • missing source
  • new template needed
  • permission issue
  • new automation opportunity
  • agent creates noise
  • agent saves meaningful time
  • human repeats the same correction

Weekly agent review​

Owner: relevant human owner Support: agent itself

Review:

  • top outputs created
  • accepted / edited / rejected outputs
  • recurring mistakes
  • missing context
  • source issues
  • time saved
  • next improvements

Output:

  • agent scorecard
  • prompt updates
  • template updates
  • source access requests
  • permission recommendations

Monthly agent scorecard​

Score each agent on:

  • accuracy
  • usefulness
  • alignment
  • completeness
  • efficiency

Agent Accurac Usefulne Alignme Complet Efficienc Notes y ss nt eness y

Strategy Agent

Marketin g Agent

Sales Ops Agent

Quarterly permission review​

Founder decides:

  • what agents can read

  • what agents can draft

  • what agents can recommend

  • what agents can update with approval

  • what agents can execute within bounds Do not expand permissions unless:

  • outputs are consistently useful

  • review effort is falling

  • source quality is stable

  • humans trust the output

  • metrics show value

Monday Focus and Planning​

Monday is the revenue alignment reset.

It does not mean planning only happens Monday. It means the team starts the week with clear outcomes, active tests, top accounts, partner priorities, proof targets, and agent tasks.

Monday output​

A one-page weekly revenue plan.

Weekly Revenue Planning Template​

Week of: [Date]

Top 3 revenue outcomes​

Founder priorities​

  • ●
  • ●
  • ●

Sales priorities​

Account / Owner Next Step Risk Needed Opportunity Support

Follow-up / proposal priorities​

Opportunity Trigger Owner Needed Deadline Output

Demand gen tests this week​

Test Chan Audie Offer Messa Asset Succe Owne Decisi nel nce ge ss r on Signal Date

Marketing priorities​

Asset / Owner Status Needed Proof Deadline Campaign

Partner priorities​

Partner Owner Relationship Next Touch Needed Asset Stage / Ask

Proof opportunities​

Source Proof Type Owner Capture Needed

Market / buyer learning focus​

This week we are listening for:

  • ●
  • ●
  • ●

Revenue agent tasks​

Agent Task Owner / Reviewer Due

Strategy Agent​

Marketing Agent​

Sales Ops Agent​

Decisions needed​

Decision Owner Needed By Context Needed

Daily Revenue Execution Standards​

Daily execution is event-driven.

These standards apply every workday.

Sales​

  • respond to inbound quickly
  • draft follow-ups same day when possible
  • keep next steps explicit
  • update CRM
  • flag stuck deals
  • prepare for calls with account context
  • move proposals forward

Marketing​

  • execute active campaigns
  • publish or draft priority content
  • support sales with assets
  • package proof
  • monitor channel performance
  • capture buyer language
  • support founder thought leadership

Demand Gen​

  • monitor active tests
  • check channel performance
  • adjust copy or creative when needed
  • capture signal from paid, organic, social, SEO, podcast, webinar, and referral sources
  • coordinate with SDR / BDR on campaign follow-up

Partners​

  • respond to intros
  • send planned touchpoints
  • log relationship context
  • prepare partner-specific assets
  • keep next asks clear

Agents​

  • run on incoming events
  • draft outputs for review
  • flag missing context
  • capture proof and buyer language
  • log errors and feedback opportunities

Revenue Context​

  • capture decisions as they happen
  • capture proof as it appears
  • capture market and buyer signals
  • avoid waiting until Friday to save important context

Friday Revenue Review and Learning​

Friday is where the Revenue Context System compounds.

The goal is not to relive the week. The goal is to decide what we learned, what to update, what to improve, and what carries forward.

Friday Review Template​

Week of: [Date]

What moved?​

  • sales:
  • demand gen:
  • marketing:
  • partners:
  • proof:
  • revenue systems:
  • agents:

What did not move?​

  • ●
  • ●

What broke or created drag?​

  • ●
  • ●

Sales review​

Opportunity Status Next Step Risk Owner Change

Follow-up / proposal review​

Opportunity Follow-Up Proposal Turnaround Issue / Next Sent? Status Time Step

Demand gen review​

Test What Signal Learning Decision Next Step Happened

Keep / Change / Stop

Partner review​

Partner Last Touch Signal Next Touch Needed Asset / Ask

What did we learn from the market?​

  • buyer language:
  • objections:
  • category signals:
  • competitor / alternative signals:
  • content ideas:

What proof did we capture?​

Proof Item Type Source Public / Next Step Internal

What did revenue agents get right?​

  • Strategy Agent:
  • Marketing Agent:
  • Sales Ops Agent:

What did revenue agents get wrong?​

  • Strategy Agent:
  • Marketing Agent:
  • Sales Ops Agent:

What context needs updating?​

Doc Update Needed Owner Priority

Company Truth​

ICPs​

Offer Context Language System

Proof Library​

Revenue Agent Constitution

Market Context​

Buyer Context​

Partner Context​

Channel and Campaign Context

Decision Log​

What decisions were made?​

Decision Owner Why What Would Change It

What carries into next week?​

  • ●
  • ●
  • ●

Monthly Revenue Operating Review​

Once per month, run a deeper revenue operating review.

This is where weekly execution turns into decisions.

Monthly agenda

What moved pipeline?​

What created qualified demand?​

What proof did we create?​

What market signals matter?​

What language is working?​

What offers are gaining traction?​

What partners are producing signal?​

What revenue agents are creating leverage?​

What revenue context docs are stale?​

10.What should we stop doing? 11.What should we double down on? 12.What should change next month?

Monthly demand gen decisions​

Review by channel.

Chann Spend / Leads SQLs Pipelin Closed Learnin Decisio el Effort e Revenu g n e

SEO Blog / content

Podcast​

guestin g

LinkedI​

n organic

Webina​

rs

Google​

Ads​

Meta​

Ads​

LinkedI​

n Ads

Events /​

confere nces New channel tests

Decision options:

  • scale
  • refine
  • pause
  • stop
  • change audience
  • change offer
  • change message
  • increase spend
  • reduce spend
  • build better proof
  • move to nurture
  • revisit next quarter

Monthly partner decisions​

Partner Active Intros Meetin Pipelin Closed Learnin Decisio Type Partner gs e Revenu g n s e

PE / operatin g partner s

RevOps / agencie s

Executi ve network s

Industry consult ants

Tech partner s

Decision options:

  • invest more
  • nurture
  • ask for intros
  • create partner asset
  • co-host webinar
  • pause
  • remove from priority list

Monthly proof review​

Proof Area New Proof Gaps Next Asset​

ECE AEMI

Spreadsheet to App​

Agent Development​

Continuous AI Ops​

Product Development

Lightning Pods​

Monthly revenue agent scorecard​

Agent Useful Accepted Rejected Main Next Outputs With Light Failure Improveme Edits Mode nt

Strategy Agent

Marketing Agent Sales Ops Agent

Monthly outputs​

  • next month’s GTM focus
  • channel decisions
  • partner decisions
  • proof library refresh
  • revenue agent scorecard
  • market context update
  • revenue context cleanup
  • website / GTM backlog update

Quarterly Revenue Strategy Review​

Once per quarter, review strategic alignment.

Agenda

Is Company Truth still accurate for GTM?​

Is ECE still clearly the flagship?​

Are ICPs self-selecting correctly?​

Are offers creating a coherent path?​

Which demand channels are worth scaling?​

Which partner types are worth more founder time?​

What proof has improved?​

What proof is still missing?​

What market language is changing?​

10.Are revenue agents reducing work or creating work? 11.Are we drifting toward startup, enterprise, or generic AI language? 12.What should be locked, changed, or retired?

Quarterly outputs​

  • Revenue Context System update
  • proof maturity assessment
  • offer portfolio cleanup
  • ICP validation
  • channel strategy update
  • partner strategy update
  • revenue agent permission review
  • GTM focus for next quarter

Role Ownership​

Founder​

Owns:

  • revenue priorities
  • strategic decisions
  • final positioning
  • offer hierarchy
  • high-value sales conversations
  • major partnerships
  • partner strategy
  • final approval on public claims
  • revenue agent permission expansion

Weekly responsibilities:

  • set top 3 revenue outcomes
  • review pipeline and priorities
  • approve strategic revenue context updates
  • review decision log
  • provide feedback on agent outputs
  • lead high-value partner touches

Marketing Manager​

Owns:

  • demand gen planning and execution
  • channel testing and measurement
  • content calendar
  • website / landing page copy
  • Language System upkeep
  • Proof Library
  • market scan
  • founder amplification
  • campaign messaging
  • case-study packaging
  • partner marketing assets
  • Marketing Agent review

Weekly responsibilities:

  • execute active campaigns daily
  • package proof
  • update market and buyer notes
  • draft or refine assets
  • run copy through Language System
  • identify proof gaps
  • maintain GTM asset backlog
  • review channel performance

SDR / BDR​

Owns:

  • account research
  • outbound execution
  • inbound follow-up
  • prospect objections
  • CRM hygiene
  • account progression notes
  • sales signal capture
  • partner CRM support
  • Sales Ops Agent feedback

Weekly responsibilities:

  • respond quickly to inbound and replies
  • progress target accounts
  • update CRM
  • tag objections
  • report buyer language
  • review Sales Ops Agent outputs
  • capture proof and pain signals from conversations
  • support partner touchpoint tracking

Strategy Agent​

Owns:

  • weekly strategic synthesis
  • drift detection
  • decision brief drafts
  • market implication notes
  • context contradiction flags
  • partner prioritization support

Marketing Agent​

Owns:

  • copy drafts
  • page outlines
  • content briefs
  • proof packaging drafts
  • language system checks
  • market scan synthesis
  • demand gen test briefs
  • partner asset drafts

Sales Ops Agent​

Owns:

  • account briefs
  • call summaries
  • follow-up drafts
  • CRM update drafts
  • proposal input packs
  • stalled-deal flags
  • sales proof capture
  • partner next-touch reminders

Metrics​

Track only what helps revenue decisions.

Sales execution metrics​

  • qualified opportunities created
  • pipeline value
  • meetings booked
  • proposals sent
  • proposal turnaround time
  • follow-up turnaround time
  • close rate
  • time to first response
  • account progression
  • stalled opportunity count

Demand gen metrics​

  • traffic
  • leads
  • MQLs
  • SQLs
  • meetings booked
  • proposal requests
  • pipeline created
  • closed revenue
  • cost per SQL
  • pipeline per dollar
  • conversion rate by source
  • lead quality
  • assisted pipeline
  • channel learning Marketing execution metrics
  • page updates shipped
  • content published
  • proof assets created
  • campaign tests launched
  • webinars planned / hosted
  • podcast appearances booked
  • founder posts published
  • paid tests launched
  • SEO pages shipped

Partner metrics​

  • active partners
  • touchpoints completed
  • intros received
  • partner-sourced meetings
  • partner-sourced pipeline
  • partner-sourced closed revenue
  • co-marketing assets created
  • partner responsiveness
  • next-touch completion

Proof metrics​

  • proof items captured
  • public proof items approved
  • case-study drafts created
  • verified stats
  • quotes approved
  • before/after examples documented
  • internal dogfooding metrics captured

Revenue agent metrics​

  • outputs generated
  • accepted as-is
  • accepted with edits
  • rejected
  • time saved
  • review effort
  • recurring failure modes
  • permission level

Revenue context metrics​

  • docs updated
  • stale sections flagged
  • decisions logged
  • source gaps resolved
  • agent prompt updates made
  • market notes added
  • buyer language captured
  • channel learnings added
  • partner notes updated

Revenue Context Update Rules​

Update immediately​

Capture these as they happen:

  • major revenue decision
  • new proof
  • approved claim
  • strong buyer phrase
  • strong objection
  • offer change
  • partner commitment
  • major source conflict
  • agent failure pattern
  • demand gen signal
  • channel learning

Review weekly​

Review these on Friday:

  • proof additions
  • agent feedback
  • buyer language
  • market signals
  • demand gen learnings
  • partner progress
  • decision log updates

Synthesize monthly​

Synthesize these monthly:

  • market context
  • buyer context
  • channel performance
  • offer traction
  • proof maturity
  • partner strategy
  • revenue agent performance

Recalibrate quarterly​

Review quarterly:

  • Company Truth
  • ICPs
  • Offer Context
  • Language System
  • Revenue Agent Constitution
  • Source-of-Truth Map
  • Revenue Operating Cadence

First 30-Day Rollout​

Week 1: Start simple Implement:

  • Monday weekly revenue plan
  • Friday revenue review
  • Sales Response Loop
  • Follow-Up and Proposal Loop
  • Proof Library updates
  • Decision Log
  • Sales Ops Agent review

Do not try to run the full system perfectly.

Week 2: Add demand gen tests Implement:

  • Demand Gen Planning and Testing Loop
  • weekly channel/test table
  • simple channel metrics
  • Marketing Agent support
  • first monthly-style channel notes

Week 3: Add partner tracking and market learning Implement:

  • Partner Development Loop
  • partner touchpoint table
  • weekly market scan
  • buyer language notes
  • content ideas from market signals

Week 4: Run first monthly review Output:

  • what worked
  • what was too heavy
  • what should be simplified
  • what context needs cleanup
  • what agents should do next
  • what proof assets are ready to activate
  • what channel tests continue, change, or stop
  • what partners deserve more attention

Minimum Viable Revenue Cadence​

If the team is overloaded, use this lighter version.

Daily​

Respond to live events:

  • inbound
  • replies
  • follow-ups
  • proposals
  • partner intros
  • campaign signals
  • proof moments
  • agent outputs

Monday, 30 minutes Answer:

What are the 3 revenue outcomes this week?​

What sales opportunities matter most?​

What follow-ups or proposals need speed?​

What demand gen tests are active?​

What partner touches matter?​

What proof do we need to capture?​

What should agents prepare?​

Friday, 30 minutes Answer:

What moved?​

What broke?​

What did we learn?​

What proof did we capture?​

What demand gen tests should we keep, change, or stop?​

What partner relationships advanced?​

What should update in the Revenue Context System?​

What should agents do better next week?​

Monthly, 60 minutes Answer:

Which channels created qualified demand?​

Which messages landed?​

Which offers had pull?​

Which partners produced signal?​

Which proof gaps matter most?​

Which agents are useful?​

What should we stop, scale, or change?​

Final Standard​

The Revenue Operating Cadence exists to make the Revenue Context System useful every week.

The standard is:

Respond daily. Test weekly. Decide monthly. Recalibrate quarterly. The cadence should help MetaCTO:

  • move faster
  • respond sooner
  • create qualified pipeline
  • support partner relationships
  • capture proof
  • keep revenue context fresh
  • improve revenue agents
  • make clearer revenue decisions

If the cadence creates drag, simplify it.

The cadence is not the work.

It is the loop that makes revenue work compound.

Market​