PHI

Tag: Attribution

  • RevOps for Startups: What to Build in Your First 90 Days

    RevOps for Startups: What to Build in Your First 90 Days

    Most early stage tech startups hit $1M ARR with a CRM that looks like a crime scene. Deals in the wrong stage. No close dates. Three different definitions of “qualified” depending on which rep you ask. Marketing has no idea which campaigns actually produced revenue. The CEO is still building pipeline reports by hand in a spreadsheet every Sunday night.

    That’s not a people problem. It’s an infrastructure problem. And it’s exactly what a RevOps engagement is supposed to fix.

    Here’s what revops for startups actually looks like, week by week, tied to specific deliverables that show up in the pipeline report. Not theory. Not a roadmap slide. The actual work.

    Weeks 1-2: The Audit You Don’t Want to Do

    The first two weeks of any early stage revops engagement are uncomfortable. You’re not building anything yet. You’re finding out how bad the existing system actually is.

    The deliverable is a CRM audit. Every deal stage, every field, every automation (or lack of one) gets documented. What you’re looking for: where deals stall, what data is missing, and whether your pipeline report is measuring what you think it’s measuring.

    In almost every startup we’ve worked with, the audit surfaces the same three problems. Deal stages are based on rep behavior, not buyer behavior. Lead source attribution is either missing or wrong. And there’s no consistent definition of what “qualified” means, so your ARR forecast is built on guesswork.

    You can’t fix the system until you know what’s actually broken. The audit is the foundation everything else gets built on.

    Weeks 3-6: Definitions, Deal Stages, and Attribution

    This is the longest phase, and the most important. You’re setting the rules the entire revenue team will operate by.

    The work breaks into three tracks running in parallel.

    1. Deal stage redefinition. Each stage gets a buyer-behavior exit criteria. A deal doesn’t move to “Proposal” because the rep sent one. It moves when the prospect acknowledged receiving it and confirmed a next step. Small distinction. Massive impact on forecast accuracy.
    2. Lead scoring and routing. What makes a lead qualified? You’re building the scoring model now, not later. This is where ICP tightens from “companies with 50+ employees” to something you can actually enrich against in a tool like Apollo.
    3. Attribution modeling. First touch, last touch, or multi-touch? The answer depends on your sales cycle length. For most tech startups with a 30-60 day cycle, a simple first-touch-plus-last-touch model is enough to start. You’re not building a perfect attribution system. You’re building one that’s better than nothing, which is where most startups are right now.

    By the end of week six, your pipeline report should look different. Deal stages reflect reality. Lead routing is automated. And for the first time, you can trace a closed deal back to its source. Startup RevOps is not about picking the perfect stack. It is about picking the minimum stack that can run for the next 12 months without a rebuild.

    If your sales team is running outbound alongside this work, make sure the sequencing infrastructure is connected to the CRM from day one. The outbound pod and the RevOps layer have to talk to each other, or you’re building two separate systems that don’t compound.

    PhiOperators, not advisorsWe’ll show you exactly what to build firstIn the first conversation, we map your current RevOps gaps and tell you which ones are costing you pipeline right now.Book an intro

    Weeks 7-10: Automation That Actually Saves Time

    By week seven, you have clean deal stages and a working attribution model. Now you automate the work that was happening manually, or not at all.

    The highest-value automations at this stage are not complicated. They’re the ones that eliminate the five-minute tasks reps do thirty times a week.

    AutomationWhat it replacesPipeline impact
    Auto-create contact on form fillManual data entry by SDR or AEFaster lead response, no dropped leads
    Deal stage change triggers task creationRep manually setting follow-up remindersConsistent follow-up, fewer deals going cold
    Sequence enrollment from CRM propertyRep manually adding contacts to sequencesHigher outbound volume without more headcount
    Win/loss notification to SlackWeekly deal review in a meetingReal-time feedback loop for the whole team
    Renewal date triggers CS outreachCS manager manually tracking spreadsheetExpansion and retention caught before churn

    None of these automations require a custom build. They’re native workflows in most CRMs. The reason most startups don’t have them is not complexity. It’s that nobody ever sat down and designed the system.

    For more on what automation looks like inside a RevOps pod, including how workflow automation connects to your CRM layer, the patterns we see across early stage tech companies are worth reading.

    Weeks 11-13: Closed-Loop Reporting

    The final phase is the one most startups skip because they think they’re not ready for it. They are.

    Closed-loop reporting connects marketing spend to closed revenue. Not leads. Not MQLs. Closed revenue. You’re building two reports: a pipeline report that shows where deals come from and where they stall, and a revenue attribution report that shows which channels produced actual ACV.

    When both reports are running, you can answer the question every founder is actually asking: “Which thing we’re spending money on is producing customers?”

    This is also when the RevOps layer connects to the CS function. Onboarding workflows, health scoring, expansion triggers. The revenue system doesn’t stop at closed-won. For a look at what that connection looks like in practice, the AtoB CX engagement shows how a retention system gets built on top of a sales infrastructure.

    What 90 Days Looks Like With Proof

    Datatruck came to Phi with no revenue system. Founder-led sales, no CRM discipline, no attribution. In 90 days, the RevOps infrastructure was running. Pipeline was visible. Marketing spend was connected to revenue. The outbound and RevOps layers were operating as one system.

    Case StudyDatatruck: $0 to $2.5M ARR, 97% drop in CACPhi built Datatruck’s RevOps and GTM system from scratch in 90 days, taking them from founder-led sales to a repeatable revenue engine that raised a $12M Series A.Read the story

    The result was $2.5M ARR, a $12M Series A, and a 97% drop in CAC. Not because of better salespeople. Because the system was finally designed to produce pipeline instead of just track it.

    Revops for tech startups is not a long-term strategy project. It’s a 90-day build. The question is whether you start now or wait until the mess is expensive enough to force the issue.

    If you want to see what the first 90 days would look like for your specific stack and stage, there’s more on how we approach RevOps best practices that move pipeline, or you can talk to someone who’s built this system before.

  • RevOps Consulting That Ships Infrastructure in 30 Days

    RevOps Consulting That Ships Infrastructure in 30 Days

    Most pre-Series-A founders who come to us have the same setup: a CRM someone configured in an afternoon, a spreadsheet that one salesperson owns, and no idea which channel is actually generating pipeline. They’ve often already paid for RevOps consulting once before. What they got was a slide deck titled “Revenue Operations Roadmap” and a Notion doc nobody opened after week three.

    That’s not a vendor problem. It’s a model problem. Most revenue operations consulting engagements are designed around advice, not execution. The consultant leaves. Nothing runs.

    Here’s what a 30-day engagement should actually produce.

    What You’re Actually Buying (and What You Aren’t)

    When a pre-Series-A company hires a revops consultancy, the goal isn’t a framework. The goal is a working system that your team can operate without the consultant on a Slack call every morning.

    That means five specific artifacts. Not recommendations about them. The actual built things.

    1. CRM stage architecture. Named stages that map to real buyer behavior, not the default HubSpot template. Entry and exit criteria written in plain language. Every open deal re-staged against the new model before the engagement closes.
    2. Attribution model. First-touch, last-touch, or multi-touch, depending on your sales cycle length. The model is wired into your CRM, not living in a spreadsheet. When a deal closes, you know which channel sourced it.
    3. Sequence infrastructure. At least two active outbound sequences connected to your CRM. Replies, bounces, and meeting books all flow back into contact records automatically. Your outbound pod or your first SDR plugs into this on day one.
    4. Lead routing logic. Rules for how inbound leads get assigned. No more “whoever saw the notification first” routing. Criteria-based, logged, auditable.
    5. Weekly revenue report. A single dashboard your CEO and head of sales can read in under four minutes. Pipeline by stage, new meetings booked, deals moved, deals stalled. Numbers, not narrative.

    If a revops consulting services engagement doesn’t ship all five of these, it isn’t RevOps. It’s research.

    The 30-Day Cadence, Week by Week

    The reason most engagements fail isn’t bad strategy. It’s sequencing. Consultants spend too long on discovery and run out of time to build.

    Here’s the cadence that actually works.

    DaysWorkOutput
    1-10CRM audit, ICP validation, stage mapping, attribution scopingArchitecture doc, signed off by founder before day 11
    11-20CRM build, stage migration, sequence infra wired up, routing rules liveWorking CRM, first sequences sending, lead routing active
    21-25Attribution model connected, reporting dashboard built, data QADashboard your team can read without explanation
    26-30Handoff, documentation, 30-day usage walkthrough with your ops leadSOPs, video walkthroughs, your team owns the system

    Days 1-10 are the only phase where the word “strategy” belongs. After day 10, everything is build or QA. If your revenue operations consulting partner is still running workshops in week three, something is wrong.

    Why the 90-Day Strategy Deck Doesn’t Work for Pre-Series-A

    Larger RevOps firms default to 90-day engagements because that’s how they staff for utilization. A senior consultant does discovery. A junior analyst does the build. A project manager coordinates. By month three, you have a thorough document and a Loom video. Your CRM looks the same as it did on day one.

    Pre-Series-A companies can’t absorb that model. You have 12 to 18 months of runway. Every week without a working pipeline system is a week of compounding cost. Hiring an AE into a broken CRM is expensive. Hiring two into a broken CRM is a crisis.

    The founders who get this right treat RevOps the same way they treat product: ship something that works, get feedback, iterate. They don’t wait for the perfect system. They build the right system for where they are today and wire in feedback loops so it gets better as the team grows.

    PhiOperators, not advisorsWe build your revenue system in 30 daysFirst call is a working session: we map your current CRM state and tell you exactly what gets built in the first 30 days.Book an intro

    The Infrastructure That Connects Everything

    RevOps isn’t a standalone function. It’s the connective tissue between your outbound motion, your ARR reporting, and your sales team’s daily workflow.

    When the CRM stage architecture is right, your outbound sequences tie directly to pipeline stages. A prospect who books a meeting through your outbound pod lands in the CRM at the right stage, gets the right follow-up sequence, and shows up in the right pipeline report. Nothing manual. Nothing falling through a gap between tools.

    When attribution is wired in, you stop guessing which campaigns are working. You can tell your board exactly what channel sourced your last ten closed deals. That matters for Series A conversations more than founders expect.

    When lead routing logic exists, your inbound leads don’t get cold. Speed-to-contact is one of the highest-use variables in early-stage sales. An inbound lead that waits 90 minutes for a response is often already talking to a competitor.

    The companies that scale past $2M ARR without a RevOps hire burning them aren’t lucky. They built the infrastructure before they needed it. Datatruck did exactly this: by the time they were generating meaningful inbound, the system was already tracking it. They went from $0 to $2.5M ARR and raised a $12M Series A, with CAC dropping 97% along the way.

    Case StudyDatatruck: $0 to $2.5M ARR, 97% drop in CACHow building revenue infrastructure before scaling headcount kept acquisition costs from spiraling as pipeline grew.Read the story

    The One Test That Tells You If It Worked

    After 30 days, there’s one question worth asking. Can your head of sales pull a pipeline report, by stage and by source, without asking anyone for help?

    If the answer is yes, the engagement worked. The system is real. It’s theirs.

    If the answer is no, you don’t have RevOps infrastructure. You have a consultant’s CRM that nobody on your team fully understands. That system will decay inside 60 days, and you’ll be back to the spreadsheet.

    Good revenue operations consulting doesn’t make itself indispensable. It builds something your team can own, operate, and improve without the consultant in the room. Anything that doesn’t meet that standard is a service, not infrastructure.

    The difference between a founder who closes their Series A with clean pipeline data and one who walks into that meeting with a spreadsheet usually comes down to whether they treated RevOps as a one-time project or as the operating layer their revenue team runs on. Build the layer. Everything else gets easier.

  • Where Your Pipeline Actually Leaks (It’s Not Your Sales Team)

    Where Your Pipeline Actually Leaks (It’s Not Your Sales Team)

    Most founders, when pipeline stalls, look at their reps. Are they sending enough emails? Are the call numbers up? Is the close rate acceptable? Then they hire a sales coach or fire the SDR lead and reset the clock.

    The pipeline problem is almost never the people. It’s the system they’re plugged into.

    A real revenue audit doesn’t start with rep activity. It starts with the infrastructure underneath the reps: data quality, CRM architecture, handoff protocols, attribution logic, and the visibility layer that tells you what’s actually working. When those break, every rep in the org is flying blind and you’re diagnosing the wrong patient.

    Here are the six places pipeline leaks before it ever reaches a conversation. Walk through these in order before you touch headcount.

    1. Lead Data Quality: The Leak Nobody Measures

    Your sequences aren’t underperforming because the copy is bad. In most cases, they’re underperforming because 30 to 40 percent of the contact data feeding them is stale, incomplete, or miscategorized.

    Check your bounce rate on outbound email. Anything above 5 percent is a signal your data layer has a problem. Check how many records in your CRM are missing firmographic fields, like employee count, revenue range, or tech stack. If your outbound pod is running sequences without enriched ICP data, they’re generating noise, not pipeline.

    The diagnostic question: can your team pull a clean list of 500 ICP accounts with verified contacts, job titles, and technographic fit in under an hour? If the answer is no, your revops strategy has a data problem, not a messaging problem.

    Apollo in the Phi stackOur outbound pods use Apollo to pull verified contacts and layer in firmographic data before any sequence touches a prospect.See how we use it

    2. CRM Architecture: Are You Tracking Deals or Creating the Illusion of Tracking?

    Open your CRM right now and answer three questions. What percentage of open opportunities have a defined next step with a date attached? What percentage of closed-lost deals have a documented reason? And how many deals in your pipeline haven’t been touched in more than 14 days?

    If you can’t answer all three in under two minutes, your CRM is a contact database, not a revenue operating system.

    Bad CRM architecture creates three specific failure modes: reps work the deals they’re comfortable with instead of the ones that need action, managers run forecasts based on gut feel instead of stage data, and nobody can trace why a deal went cold because the history isn’t there. The RevOps pod exists specifically to fix this, building stage definitions, field requirements, and automation workflows that enforce the discipline the CRM was supposed to create.

    3. MQL-to-SQL Handoff: The Dead Zone Where Leads Go to Die

    Marketing sends a list. Sales ignores half of it. Marketing blames sales for not following up. Sales blames marketing for sending garbage leads. This conversation happens every week at companies of every size and it never gets resolved because nobody has defined what a qualified handoff actually looks like.

    The specific things to check here:

    1. Is there a documented SLA for how fast sales must contact a marketing-sourced lead? (The industry benchmark is under five minutes for inbound. Most teams are at 24-plus hours.)
    2. Do MQLs have a minimum data threshold before they route to sales? (Job title, company size, and intent signal at minimum.)
    3. Is there a feedback loop from sales back to marketing on lead quality? Or does that feedback happen in quarterly reviews and get ignored?
    4. What happens to an MQL that sales doesn’t contact within the SLA window? Does it route to a nurture sequence or fall into a void?

    If you don’t have written answers to all four, you have a handoff problem. Your marketing operations and your sales ops need to be one connected system, not two teams with adjacent spreadsheets.

    4. Attribution: You’re Measuring the Last Click, Not the System

    Most B2B companies attribute closed deals to the last marketing touchpoint or the SDR who sent the final email. This tells you almost nothing useful.

    A deal that closed from an outbound sequence touched the prospect through LinkedIn content first, a cold email second, a case study third, and a referral fourth. If your revops roadmap only credits the email that got the reply, you’ll defund LinkedIn, deprioritize content, and cut the referral program. Then you’ll wonder why outbound starts underperforming six months later.

    The fix isn’t a fancier attribution tool. It’s first-touch, multi-touch, and pipeline-influenced attribution running simultaneously, with someone accountable for interpreting the data and translating it into channel decisions. That’s a RevOps function, and most early-stage companies don’t have it.

    PhiOperators, not advisorsRun the revenue audit with operators who fix it afterIn the first conversation, we map your specific leak points and tell you which ones are costing you the most pipeline right now.Book an intro

    5. Handoff from Sales to Customer Success: Where Expansion Revenue Disappears

    The handoff from a closed deal to your CS team is one of the most ignored leak points in B2B revenue. The AE closes, throws the account into an onboarding queue, and moves on. CS inherits a customer they know nothing about, with no context on what was promised during the sale, no visibility into the technical environment, and no playbook for the first 30 days.

    The result: slower time-to-value, lower CSAT scores, and reduced expansion potential. The customer that was supposed to grow into a $200K account renews flat because nobody was tracking health signals in the first 90 days.

    This is precisely what the CS pod fixed at AtoB. Retention systems, onboarding workflows, and health scoring built across thousands of fleets. The outcome was a 40% CSAT improvement.

    Case StudyAtoB: 40% CSAT improvement across thousands of fleetsPhi built AtoB’s retention engine from scratch, connecting onboarding workflows to health scoring so no account went dark in the critical first 90 days.Read the story

    6. Reporting and Visibility: The Audit Nobody Wants to Run

    The final leak point is the one that makes all the others invisible: you don’t have a reporting layer that shows you where pipeline is dying in real time.

    Pull your pipeline velocity report. If you don’t have one, that’s the answer. Pull your stage conversion rates for the last 90 days. If they aren’t tracked by rep, by segment, and by source, you can’t diagnose anything. Pull your average time-in-stage. If deals are sitting in “Proposal Sent” for 30-plus days with no activity logged, something upstream is broken and nobody knows it yet.

    A working revops strategy gives leadership one dashboard that answers four questions: how much pipeline do we have, where is it stalling, what’s the source quality, and what does the next 90 days look like? If your current setup can’t answer those four questions in a single view, you’re making revenue decisions without data. You’re not operating a system. You’re running on feel.

    The companies we work with don’t hire us to diagnose their revenue system and hand them a deck. They bring in the RevOps pod to build the reporting infrastructure, fix the CRM architecture, close the handoff gaps, and run the operation going forward. That’s different from revops consulting or revenue operations consulting services that map the problem and leave. We’re in the system with you.

    If you’re reading this checklist and recognizing your own pipeline, the useful next question isn’t “which of these do we have?” It’s “which one is costing us the most right now?” That’s where the audit starts.