Hard Work, Wrong Things
You can feel when a post-sales team is grinding.
Calendars are stacked. Slack never quiets. The QBR deck looks fine. Your reps are putting in the hours. And yet the metric you actually own — NRR, GRR, expansion, retention, whatever your North Star happens to be — isn't moving the way it should.
Renewals you thought were safe wobble. Expansion plays you bet on stall. The CSM who seemed slammed turns in a quarter that doesn't match the workload they described. The team is working hard. The number isn't catching up.
If you've felt that gap, you're not imagining it. And it's not a motivation problem, or a talent problem, or — usually — a customer problem.
It's an alignment problem.
The work is happening. The work just isn't pointed at the thing you're trying to drive.
This essay is about that gap — what causes it, why it's gotten harder to see, and what you can do about it without buying anything from anyone, including us. There's a self-assessment toward the end. The pieces that follow it are not Lumopath's framework so much as observations from the hundreds of post-sales orgs we've talked to: the patterns that keep showing up, and the moves that work when leaders decide to fix the problem instead of work around it.
If you take only one thing away: most teams don't lose the number because they're slacking. They lose it because their hard work is going to the wrong things, and nothing in their stack is set up to tell them where the misalignment lives.
Why this got harder, and why it's finally fixable
A decade ago, this was a smaller problem. Customer-facing work happened in two places: email and the phone. You could roughly see where the hours went.
Today the same work is scattered across Slack, Zoom, Salesforce, Gong, Zendesk, Notion, Linear, Gmail, Calendar, your CSP, your product analytics tool, and a half-dozen internal channels.
We try to make sense of our work via the old tools:
Headcount-to-ARR ratios that assume every account is the same.
Spreadsheets stitched together by RevOps from six tools.
Quarterly time studies that are obsolete the moment they're finished.
Gut reads — "I think Clark is overloaded" — which carries less weight in the an ELT meeting
These are real disciplines. The leaders practicing them are doing real work. They're just bad versions of a better discipline that has only recently become possible.
What changed: passive activity capture finally works across modern tool stacks. AI can interpret that activity at the scale of an entire org without anyone logging anything. The question "where is my team's time actually going, and is it going to the right places?" now has an answer that isn't a guess or a tax on the team.
We call this discipline revenue alignment: the continuous practice of matching your team's time, attention, and effort to the customers, tasks, and outcomes that drive your number. The name matters less than recognizing that it's a real discipline, distinct from the things you already track, and that most leaders are practicing it badly because that's the only option they've had.
Five places where alignment breaks down
Misalignment is rarely one big thing. It's a series of small disconnects between where your team's effort goes and where revenue actually comes from. We've found those disconnects cluster into five layers — five places where alignment most commonly breaks.
Read these as a diagnostic lens, not a doctrine. Most teams are strong in some and weak in others. The point is to see clearly where you are, not to score yourself on a leaderboard.
1. Metric instrumentation
Are you actually tracking the things that drive your number?
You probably know your North Star. NRR, maybe. Or expansion ARR, gross retention, time to value — whatever your business model implies. The harder question is whether you can name the three to five input metrics that move it, and whether any of them are tracked in a way that updates faster than a quarterly review.
A few honest checks:
Can you name your North Star and three to five input metrics that drive it without checking a doc?
Do those input metrics update at least weekly, or are you reading numbers that are 60 to 90 days old?
Is "engagement" or "coverage" defined the same way across your team, or does each manager calculate it differently?
If your North Star moved five points last quarter, could you point to which input metrics drove the change?
If the answers wobble, you're not alone — but it's worth noticing. Output metrics like NRR are lagging by design. By the time they move, the work that produced them already happened. Without leading indicators, you're driving by looking in the rearview mirror.
2. IC frontline clarity
Do your individual contributors know which accounts and activities to prioritize today?
Pick a CSM on your team. Ask them: what are your top three priorities today, and why? Now ask whether their answer ties back to the North Star.
This is where alignment lives or dies. Your input metrics can be perfect. Your dashboards can be beautiful. If the person actually doing the work is assembling their day from inbox triage, recent calls, and whichever customer was loudest yesterday — none of it matters.
A few honest checks:
Do ICs have a prioritized list each day based on revenue impact, or do they assemble their own from emails and Slack?
Can a CSM see, per account, the upside or risk if they move it forward?
Do high performers and average performers prioritize the same way, or do high performers rely on instinct that hasn't been systematized?
Could a new hire become productive on prioritization in week one, or is the prioritization logic tribal knowledge?
The cost of weak frontline clarity isn't visible until you compare two reps with similar books. One hits goal, one doesn't, and no one can quite explain why. The answer is almost always: their hours went to different places.
3. Manager insight
Do your managers walk into 1:1s with data, or with anecdote?
Ask one of your managers to explain why one of their reps is hitting goal and another isn't. If the answer is "Carol works harder" or "Daniel's book is easier," that's a signal. Both might be true. Neither is actionable.
Good managers eventually figure out the answers. They do it through conversation and observation and time. The problem is that good managers leave, and bad managers don't figure it out at all, and even great managers can't compare two reps' books on coverage, engagement consistency, and time allocation in any rigorous way.
A few honest checks:
Going into a 1:1, does your manager arrive with effort data and behavioral observations, or with the rep's self-report?
Can managers spot drift in input metrics before it shows up in lagging output?
When a manager rebalances a book, is it backed by workload data or by gut?
If a manager left tomorrow, would the replacement inherit a system, or rebuild from scratch?
The hardest version of this question: are your 1:1s data-driven coaching sessions, or status updates dressed up as coaching? Most leaders, in private, will tell you the latter.
4. Executive visibility
Do you, the leader, see how team effort is distributed across customers and activities?
You see the output. You see NRR move. You see churn spikes. You see expansion deals close. The question is whether you see the effort — the hours, the coverage, the proportion of your team's time going to each segment, each tier, each kind of work.
Most exec visibility is built around outputs because outputs are easy to measure. The trouble is that outputs are lagging, and by the time a strategic account churns, you can't reconstruct the 90 days of coverage and effort and risk-response that preceded it.
A few honest checks:
When you make a headcount call, do you have data on actual workload by segment, or just account count and ARR?
Could you identify, right now, the five accounts getting disproportionate attention this quarter without asking a manager?
When NRR moves, can you tell the effort story behind it — not just the headline?
Are staffing investments justified with effort data, or with logos and finger-in-the-air?
Executive visibility isn't a dashboard problem. It's a decision-quality problem. Decisions made without effort data are defensible until they aren't, and then they're very expensive.
5. Operational visibility
Does Ops have a clear view of the internal drag getting in the way of the work?
Even when your North Star is clear, your input metrics are tracked, your ICs know their priorities, your managers coach with data, and your execs have visibility — your team can still be misaligned if the system around them is leaking time.
Internal drag is real, and it's almost always under-counted. Cross-functional handoffs that take a week. Deal desk requests that bounce. Security reviews that stall. Recurring internal meetings nobody would notice if they disappeared. Tooling that requires three logins to do one thing. None of this shows up in coverage reports. All of it eats into customer-facing hours.
A few honest checks:
Can you quantify how much of your team's time goes to internal work versus customer-facing work?
Do you know which other functions (Product, Support, Legal, RevOps) generate the most drag on your team?
When a recurring internal workflow consumes capacity, can you measure its cost, or does it surface only in skip-levels and Slack venting?
Do you set capacity plans assuming real productive hours, or 100% productive time?
The thing about internal drag is that fixing it is often the highest-leverage move available. Every hour you reclaim from it is an hour that goes back to revenue-driving work. But you can't fix what you can't see.
A 10-minute self-assessment
You can do a real version of this on your own, right now, with no tooling.
For each of the five layers above, rate your organization on a scale of 1 to 5:
Never — we don't do this systematically.
Rarely — we have it in pockets, not consistently.
Sometimes — we do it, but with gaps.
Usually — it's the default, with exceptions.
Always — it's instrumented, consistent, and drives our decisions.
Your scores tell you the shape of your alignment, not the size of your problem.
A team scoring high on metric instrumentation and low on IC frontline clarity has a translation problem — good data, bad use. A team scoring high on IC clarity and low on executive visibility has a reporting problem — the work is right, but leadership can't see it. A team scoring low everywhere has a foundation problem, and that's actually the easiest place to start, because every move is high-leverage.
We've built a more structured version of this assessment — it maps your scores against revenue model and North Star, surfaces the input metrics most likely to be moving (or not moving) your number, and translates the gap into an estimated revenue impact. It takes about ten minutes. You can take it [here].
But you don't need our tool to do the work. The assessment matters more than the tool. If you do nothing else after reading this, run those five questions past three of your managers and compare answers. Variance is the diagnosis. If you all see the same gaps, you have a clarity problem. If you each see different gaps, you have an alignment problem about alignment itself, and that's the deeper one.
What you can do this quarter, without buying anything
Each of the five layers has at least one move you can make in the next 30 days that doesn't require new software, a budget cycle, or a board approval.
For metric instrumentation — adopt the rule of three. Pick three input metrics you genuinely believe correlate with your North Star. Assign one owner per metric. Build one dashboard where they all live. That's it. The discipline of picking three is harder than it sounds, and most teams fail at it because everyone wants to track everything. Three is enough. You can add later. Most teams over-instrument and under-act; three is the version that gets used.
For IC frontline clarity — write a one-page priority playbook. Not a long doc. One page. It should answer: if a CSM has 60 minutes of free time today, which account should they touch and why? Tie it to your three input metrics. Distribute it. Have managers reinforce it in 1:1s for two weeks. You'll be surprised how much drift this fixes — not because the playbook is brilliant, but because the act of writing it forces the alignment conversation at the top of the org.
For manager insight — change one ritual. Pick your weekly manager meeting and require every manager to bring one data point that explains a performance gap on their team. Not anecdote. A number. They'll resist this for two weeks. By week four it'll be the most useful meeting on your calendar, because the question "what's the data?" is the question that converts coaching from gut to evidence.
For executive visibility — start tracking effort distribution in one segment. Pick your most important customer segment (top quartile by revenue, or strategic accounts, or whatever your equivalent is). For 30 days, do a structured effort review: how many hours did your team put into these customers, on what activities, and what was the result? Don't extrapolate. Don't generalize. Just do that one segment, and use it to start a conversation about whether your assumed coverage matches reality. It almost never does.
For operational visibility — run a drag audit. Block 60 minutes with three of your strongest ICs. Ask them: what's the most useless internal thing you do every week? Write it down. Don't defend any of it. Take the top three answers and kill, automate, or move them. You'll recover hours. More importantly, you'll signal that internal drag is a real cost — which changes how every other function in the company treats it.
None of this requires us. None of it requires anyone. It just requires you to decide that alignment is a discipline you're going to practice, not a vague aspiration you're going to wait on.
What we built, and why we mention it at all
We built Lumopath because we believe revenue alignment is the discipline that defines the next decade of post-sales leadership, and we couldn't find anyone doing it well. So we built the tool we wished existed when we were running these orgs ourselves: passive capture across your team's full tool stack, AI interpretation that turns the activity into answers, and a workflow built specifically for these five layers.
But the discipline matters more than the tool. The companies that figure this out first will be the ones who decided alignment was real, named the gaps, and started fixing them. Some will use spreadsheets. Some will build internally. Some will use us.
If you take the self-assessment and your weak spots are concentrated in places you can fix yourself with the moves above, fix them yourself. If your weak spots are concentrated in places that genuinely require continuous, automated visibility into thousands of activities across dozens of people and a dozen tools — that's the conversation we want to have.
What we don't want is for another quarter to go by where your team is working hard, the number isn't moving, and no one can explain the gap.
Mikey Renan is the co-founder and CEO of Lumopath. The five-pillar framework draws on conversations with dozens of post-sales leaders and on patterns we've seen running these teams ourselves. If you want to take the structured 5-minute assessment, it lives [here]. If any of the five layers above hit a nerve, I'd genuinely like to hear which one and why — that's how this framework keeps getting sharper.
