Your CFO can tell you where every dollar went last month, down to the software subscription nobody uses. Ask your sales team what percentage of last week actually went to selling, and you'll get guesses and maybe a little defensiveness. Meanwhile, payroll sits at ten times the size of your next biggest expense on the books, and nobody has ever audited an hour of it.
There's no Jay this week, just me. I'm Sarah Shepard, COO at StringCan Interactive, where I run operations and the financials, and this episode is my case for the least glamorous revenue topic there is: time tracking. You'll come away with a reason to bring hour data into your revenue conversations, a two-week snapshot your team won't mutiny over, and the story of how our timesheet-averse CEO ended up logging time more accurately than the rest of us.
This post is based on Episode 75 of Revenue Rewired | The Real Cost of Ignoring Time Tracking in Your Revenue Team.
If you'd rather listen than read, find the full episode on Apple Podcasts, YouTube, Spotify, or Amazon. It's worth your time.
Credit for the soapbox goes to Drew at AMI, who's spent years pushing me on this. Money has a paper trail, so dollars get reconciled by software almost effortlessly and your expense report stays accurate to the penny. Time never gets that audit, even though the hours behind payroll are the raw material for every dollar the company earns.
There's a political layer underneath it, too. Look too busy, and people stop handing you new projects. Seem too idle, and you start worrying about your job, an anxiety AI has only made sharper. People fudge their hours for reasons exactly like these, so meet it with some grace and admit that your company culture probably helped write those rules.
Revenue doesn't only break in obvious places. It can leak 15 minutes at a time, hidden inside a calendar nobody's tracking, and scope creep, rework, and unclear ownership all land in the hours bucket long before they surface in your margins.
No one's proposing a permanent timesheet. If time feels like one giant gray bucket and you know revenue's leaking somewhere, take a snapshot instead: two weeks, maybe once a quarter, tracked at the team level, not by individual. You'll hit weird weeks and outliers, and that's fine, because you're hunting for patterns, not perfection.
Keep the reporting stupid simple. For a sales team, a few buckets cover it: core selling work, internal meetings, admin time, rework, and requests that come in from other departments. Self-reporting takes about two minutes when it happens daily, and daily is the hinge, because four days out no one remembers where Tuesday went, the same way you blank when someone brings up a breakfast you shared last week.
How you share the results decides whether this builds trust or resentment. Tell the team you're doing it together to find gaps and inefficiencies, then mean it when you say it. Anyone who runs a snapshot like this and turns around to cut people because AI can absorb the low-hanging work has poisoned the well for every future attempt at getting real data.
Picture a proposal with a line item that reads five hours. Ask where the number came from, and you'll hear that Bob over in IT figured it was about what it would take. Then it turns out Bob misunderstood the request, the work runs three times as long, it needs a tool no one budgeted for, and your delivery team quietly eats the difference on a scope sales signed with full confidence.
I've met plenty of peers on the service side who describe their job as reverse engineering: sales sold the thing, now figure out how to deliver it inside whatever hours were promised. That pigeonholes talented people into budgets that were never real, keeps them from doing their best work, and eventually the client feels the friction. Retention gets much easier when your service team walks into an engagement with numbers built from actual data instead of somebody's gut.
Agencies get forced into this discipline because proposals allocate hours from day one, the way a law firm's retainer is simply hours wearing a suit. You don't need to become an agency to borrow the instrument. When an engagement starts going sideways, the timesheet knows about two weeks before the status meeting does, and that head start is the whole reason to bother.
Jay Feitlinger, our CEO and my co-host, is what I affectionately call a squirrely visionary, and he runs his whole life by his calendar. His first reaction to time tracking was the one every founder has: isn't avoiding this exact chore why I started a business? Even last week, he told me his time felt scattered, and the logging felt like extra work, then admitted in the same breath that he knows how much it matters.
So we automated around him. Our ClickUp process works with Claude to read his calendar, match each meeting to the right task, log the time, and close the task out in the project management system. Anything ambiguous goes to his virtual assistant as a short checklist to verify, and for a stretch Jay had the sharpest time data in the entire building, cleaner than mine.
We run our own deep version quarterly, tracking daily for two straight weeks, and something useful falls out every single time. One round restructured our internal meeting cadence, another stripped granularity from a process that had stopped needing it, and the retros keep getting sharper, since a past project's budget sheet, which is really just time and dollars, becomes the evidence for scoping the next one.
Q: Won't time tracking feel like surveillance to my team?
A: It will if you run it like surveillance, which is why the snapshot works as a team exercise instead of an individual scorecard. Present the findings as a group effort to spot inefficiencies, follow through on what you find, and the resentment loses its oxygen pretty fast.
Q: How long should a pilot run before the data means anything?
A: Two weeks is enough to see real patterns, even with an anomaly or two in the mix. We repeat ours quarterly at StringCan, and each round surfaces something new about our meetings or our capacity.
Q: What buckets should my sales team actually track?
A: A handful is plenty, something like selling, meetings, admin, and rework. The aim is a two-minute daily self-report, not a forensic log, because recall dies fast once the day is gone.
Q: My CEO refuses to log hours. What are my options?
A: Automate around them instead of arguing with them. Jay's setup matches calendar events to tasks in ClickUp and logs hours with zero manual entry, and that calendar-driven approach fits any leader or seller who already lives inside their schedule.
Q: Do we need special software to start?
A: No, a shared doc with a few daily buckets gets a pilot off the ground. We happen to run projects and hours through ClickUp with some Claude automation layered on top, but the tool matters far less than the habit of writing it down the same day.
StringCan Interactive helps mid-market companies wire marketing and sales into one revenue system, and hour data turns out to be a bigger part of that wiring than anyone expects. If your proposals run on gut feel or your capacity picture has gone foggy, we've lived that exact problem and built our way out of it.
Episode 75 covers all of this in under 17 minutes, in my voice, right here. And when you've run a snapshot of your own, email us at podcast@stringcaninteractive.com, because I'd love to hear what your team's hours were hiding.