A 35-person AI agency in San Diego had a troubling pattern. Sales would close a $200,000 deal, delivery would estimate it needed $180,000 in resources to complete, and finance would discover at project close that actual costs were $220,000. The project that looked like a win in the pipeline became a loss on the books. This happened on roughly one in three projects. Sales blamed delivery for scope creep. Delivery blamed sales for underscoping. Finance blamed both for not tracking costs. Nobody owned the revenue lifecycle end-to-end, so nobody could fix it.
Revenue operations — RevOps — is the operational discipline of aligning sales, delivery, and finance around the full revenue lifecycle. It ensures that deals are scoped accurately, priced profitably, delivered efficiently, billed promptly, and collected completely. In an AI agency, where the gap between sold work and delivered work creates most of the margin erosion, RevOps is the function that closes that gap.
The Revenue Lifecycle
Revenue in an AI agency follows a lifecycle with distinct phases, each owned by a different function but connected to all the others.
Phase 1: Pipeline (Sales)
A potential project enters your pipeline. Sales qualifies the opportunity, develops the relationship, and works toward a commitment.
RevOps involvement:
- Pipeline data quality: Every opportunity has complete, accurate information (client, project type, estimated value, probability, expected close date)
- Pipeline coverage: Total weighted pipeline should be 3-4x your revenue target for the period
- Stage definitions: Clear criteria for each pipeline stage so that "proposal sent" means the same thing to everyone
- Win rate tracking: Historical win rates by stage, deal size, service type, and salesperson
Phase 2: Scoping and Pricing (Sales + Delivery)
The deal is being shaped — scope is defined, approach is determined, and pricing is set. This is where most revenue leakage begins.
RevOps involvement:
- Scoping accuracy: Delivery team reviews and validates all scopes before pricing. No deal is priced without delivery input.
- Pricing discipline: Every engagement is priced using standard rate cards and loaded cost calculations. No ad hoc discounting without leadership approval.
- Margin validation: Every deal is reviewed for minimum margin requirements (typically 40%+ gross margin) before approval to proceed.
- Terms review: Payment terms, milestones, and billing structure are validated by finance before contract execution.
The scoping-pricing handoff:
This is the most critical handoff in the revenue lifecycle. Problems here cascade through everything downstream.
Best practice: Sales develops the business case and client relationship. Delivery develops the scope, estimate, and approach. They collaborate on the proposal, with sales owning the client relationship and delivery owning the technical content. Finance validates pricing and terms. A formal "deal review" meeting brings all three together before any proposal over a defined threshold (typically $50,000+) is sent.
Phase 3: Contracting (Sales + Legal + Finance)
The deal is agreed in principle and needs to be formalized.
RevOps involvement:
- Contract terms: Standard terms for payment, scope, change control, and IP are used consistently
- Revenue recognition: Finance confirms how revenue will be recognized (percentage of completion, milestone, monthly)
- Billing setup: Payment terms, milestones, billing contacts, and PO requirements are captured
- CRM update: Opportunity is updated to "closed won" with accurate contract value and timeline
Phase 4: Delivery (Delivery + Finance)
Work begins and revenue is earned through execution.
RevOps involvement:
- Project setup: Project is created in project management and time tracking tools with budget, timeline, and resource allocation matching the contract
- Revenue tracking: Revenue is recognized in the accounting system as work is completed
- Cost tracking: Hours and expenses are tracked against the project budget in real time
- Margin monitoring: Actual margin is compared to planned margin weekly for large projects, biweekly for smaller ones
- Change control: Any scope changes go through a formal process that updates both the project plan and the financial model
Phase 5: Billing and Collection (Finance)
Invoices are generated, sent, and collected.
RevOps involvement:
- Invoice accuracy: Invoices match contract terms and are generated promptly
- Collections cadence: Systematic follow-up on overdue invoices
- Cash application: Payments are matched to invoices and recognized in the accounting system
- Revenue reconciliation: Billed and collected amounts are reconciled to contracted amounts
Phase 6: Renewal and Expansion (Sales + Delivery + Client Success)
The current engagement winds down and the opportunity for continued or expanded work arises.
RevOps involvement:
- Renewal tracking: Upcoming contract expirations are flagged 90 days in advance
- Expansion opportunity identification: Delivery and client success identify opportunities for additional work during active engagements
- Account health: Client satisfaction, delivery performance, and relationship health are monitored as leading indicators of renewal likelihood
- Lifetime value tracking: Revenue, margin, and cost-to-serve are tracked at the account level over time
Building the RevOps Function
RevOps Roles
At small agencies (under 20 people): RevOps is a shared responsibility. The founder or COO serves as the revenue operations coordinator, ensuring alignment across sales, delivery, and finance. No dedicated hire needed, but the function needs an explicit owner.
At mid-size agencies (20-50 people): A dedicated RevOps manager or director. This person:
- Owns the CRM and pipeline management process
- Manages the scoping-pricing handoff
- Monitors deal profitability and margin tracking
- Produces revenue reporting and analysis
- Coordinates between sales, delivery, and finance on revenue matters
At larger agencies (50+ people): A RevOps team including:
- Revenue operations director
- Sales operations analyst (CRM, pipeline, forecasting)
- Delivery finance analyst (project profitability, utilization)
- Business intelligence (dashboards, reporting, analysis)
RevOps Technology Stack
CRM: HubSpot, Salesforce, or Pipedrive — the single source of truth for pipeline and client data
Project management: Linear, Asana, or Jira — integrated with CRM so deal progression flows to project setup
Time tracking: Harvest or Toggl — integrated with project management for real-time utilization and cost tracking
Accounting: QuickBooks Online or Xero — integrated with CRM and time tracking for billing and revenue recognition
Reporting: A BI tool (Metabase, Looker, or Tableau) or spreadsheet dashboards that pull data from all sources into unified views
The integration imperative: RevOps depends on data flowing between systems. If your CRM does not talk to your project management tool, which does not talk to your accounting system, you are managing revenue with blind spots. Invest in integrations — native, via Zapier/Make, or custom — to create a connected data flow.
RevOps Metrics and Reporting
The Revenue Dashboard
Build a dashboard that provides real-time visibility into the revenue lifecycle:
Pipeline metrics:
- Total pipeline value (weighted and unweighted)
- Pipeline coverage ratio (weighted pipeline / revenue target)
- Stage conversion rates
- Average deal size
- Average sales cycle length
- Win rate by deal size, service type, and salesperson
Revenue metrics:
- Monthly and quarterly revenue (actual versus plan)
- Revenue by service type and client
- Recurring revenue percentage
- New versus expansion versus renewal revenue
Profitability metrics:
- Gross margin by project, client, and service line
- Margin variance (actual versus planned at project level)
- Utilization rate
- Revenue per employee
- Effective billing rate (actual revenue per billable hour)
Cash metrics:
- Billings (invoiced but not necessarily collected)
- Collections (cash actually received)
- DSO (days sales outstanding)
- AR aging
Monthly RevOps Review
Conduct a monthly RevOps review with sales, delivery, and finance leaders:
Agenda:
- Revenue performance versus plan (10 minutes)
- Pipeline review — health, coverage, and forecast (15 minutes)
- Delivery profitability — active project margins and at-risk projects (15 minutes)
- Collections and cash flow (10 minutes)
- Issues and actions (10 minutes)
This meeting ensures that all three functions are aligned on revenue reality and working together on problems.
Common Revenue Leakage Points
Leakage Point 1: Underscoping
Deals are scoped too optimistically, leading to cost overruns during delivery.
Fix: Require delivery team review of all scopes. Use historical data from similar projects to validate estimates. Add contingency buffers (15-25% for AI projects).
Leakage Point 2: Scope Creep Without Billing
Additional work is absorbed without corresponding billing.
Fix: Enforce change control. Every scope change has a documented impact on timeline and budget. Additional work requires a change order before execution.
Leakage Point 3: Unbilled Time
Team members spend time on client work that is not tracked or billed.
Fix: Track all time, not just some. Review time entries weekly. Flag projects where tracked time is below expected levels — this often indicates unbilled effort.
Leakage Point 4: Rate Erosion
Deals are discounted excessively, or billing rates do not keep pace with cost increases.
Fix: Maintain standard rate cards. Require approval for discounts above a threshold (typically 10%). Review effective billing rates quarterly and adjust rates annually.
Leakage Point 5: Collection Failure
Revenue is earned and billed but not collected, or collected very late.
Fix: Systematic collections process with defined cadence and escalation. Track DSO monthly. Establish AR management as a leadership priority.
Leakage Point 6: Client Concentration
Over-dependence on a few large clients creates revenue risk if any client churns.
Fix: Track client concentration monthly. No single client should exceed 25% of revenue. Actively diversify through business development.
Revenue Forecasting
Forecasting Methodology
Bottom-up forecast (most accurate for short-term):
- Start with contracted revenue (existing retainers, signed projects with defined billing schedules)
- Add weighted pipeline (deal value x probability for each pipeline opportunity)
- Adjust for historical accuracy (if your pipeline consistently over-predicts by 20%, adjust accordingly)
Top-down forecast (useful for annual planning):
- Revenue target based on growth goals and capacity
- Required win rate, deal size, and pipeline volume to achieve target
- Reality check against historical performance
Forecast accuracy: Track forecast accuracy monthly. Calculate the variance between forecasted and actual revenue. Aim for less than 10% variance on a quarterly basis. Investigate and address systematic biases (consistently over-forecasting or under-forecasting).
Your Next Step
This week:
- Map your current revenue lifecycle. Where are the handoffs between sales, delivery, and finance? Where are the gaps?
- Review your last 5 completed projects. Compare original scope and pricing to actual costs and revenue. Where did leakage occur?
- Check your pipeline hygiene — is every opportunity in your CRM current, accurately staged, and with a realistic close date?
This month:
- Implement a deal review process for proposals above your threshold.
- Set up margin tracking for all active projects using loaded cost rates.
- Build or refine your revenue dashboard with the metrics listed above.
This quarter:
- Conduct a monthly RevOps review meeting with sales, delivery, and finance leaders.
- Identify and address your top 3 revenue leakage points.
- Implement integrations between your CRM, project management, and accounting systems.
- Build a forecasting model and begin tracking forecast accuracy.
Revenue operations is the connective tissue between the functions that drive your agency's financial health. Without it, sales, delivery, and finance operate in silos, each optimizing for their own metrics while the overall revenue engine sputters. With it, you build a machine that consistently converts pipeline into profitable, collected revenue.