What Running Four Departments Actually Looks Like

7:30am: Marketing review. 10am: Finance committee. 2pm: Tech sprint. 4pm: HR sync. 9pm: Slack. All of them.

That's my Tuesday at GAIN, a $100M SaaS company where I run Finance, Marketing, Technology, and HR. Not a brag. Just context for what follows.

When most people talk about cross-functional alignment, they're theorizing. I'm living it. Every day. Often imperfectly. Here's what it actually looks like on the ground.

7:30am: Marketing Review

Pipeline meeting. How many MQLs last week? What's converting? What's stuck?

The question I always ask: "What's the warmth distribution?" Not how many leads. How many are genuinely engaging across channels.

Marketing wants volume. Finance wants quality. My job is making sure both sides understand the trade-off before we commit budget.

Today's tension: Marketing wants to increase ad spend by 20%. CAC is already creeping up. I push back. "Show me the warmth data first. Are we getting more leads or better leads?"

They don't know yet. Meeting deferred to Thursday.

Time in meeting: 45 minutes. Actual decisions made: zero.

10:00am: Finance Committee

Monthly close review. Where are we vs. plan? What's driving variance?

The usual suspects: revenue came in 3% under, expenses came in 5% under. Net result is fine. But the composition matters.

I spend 30 minutes explaining why the revenue miss is a timing issue (two deals slipped to next month) while the expense underrun is real savings. These are very different situations, and the board narrative has to reflect that.

Board-facing version: "Revenue timing shift, expense discipline intact."

Honest version: We got lucky that expenses were down, or this month would look worse.

Time in meeting: 90 minutes. Actual decisions made: one (adjust forecast methodology).

2:00pm: Tech Sprint Review

Biweekly sprint retrospective. What shipped? What's blocked?

The question I ask: "What's the cost-per-feature this sprint?"

Tech hates this question. They want to talk about velocity, story points, technical debt. All valid. But I need to connect their work to budget. If we shipped 8 features and spent $200K on engineering this sprint, our cost-per-feature is $25K. Is that improving or declining over time?

Today's tension: Tech wants to hire two more engineers. Finance sees burn increasing. The middle ground is hiring one now and deferring one to Q2 based on revenue targets.

Time in meeting: 60 minutes. Actual decisions made: one (hire one, defer one).

4:00pm: HR Sync

Weekly check-in on open roles, retention, and compliance.

The question I always ask: "What's time-to-productivity on recent hires?"

We've grown 20% this year. If new hires take 90 days to contribute at full capacity, we're carrying significant cost longer than the model assumes. If they ramp in 60 days, the economics change meaningfully.

Today's tension: HR wants to slow hiring to focus on retention. Finance sees the pipeline and wants to accelerate. The answer is not either/or. It's "hire for the roles that drive revenue directly, pause on the ones that don't."

Time in meeting: 30 minutes. Actual decisions made: one (prioritize 2 roles, pause 3).

9:00pm: Slack. All of Them.

Finance channel: Revenue recognition question from accounting.

Marketing channel: Someone wants to launch a campaign tomorrow with no budget approval.

Tech channel: Production issue. Not critical but needs acknowledgment.

HR channel: Offer letter needs sign-off.

This is the job. The connective tissue nobody talks about in the job description. Not the meetings. The after-hours layer that holds the meetings together.

Time on Slack: 45 minutes. Decisions made: four (yes, no, acknowledged, signed).

The Messy Truth About Running Multiple Departments

Three things nobody tells you before you end up here.

You stop being an expert in anything. I know enough about marketing to ask good questions. Not enough to run a campaign. Same with tech. Same with HR. My value is not expertise in any single domain. It's pattern recognition across all of them.

Every department thinks they're underfunded. Marketing wants more budget. Tech wants more headcount. HR wants better tools. Finance is usually trying to cut everyone else. Your job is holding that tension while the budget doesn't math. There is no version of this job where everyone gets what they want.

Competing priorities are a feature, not a problem. Marketing wants leads. Finance wants clean data. Tech wants speed. HR wants compliance. If they all agreed on everything, you wouldn't need someone sitting across all four functions. The conflict is where the value lives.

The Ratio That Actually Matters

Map your last week. How much time did you spend in meetings per department? How many actual decisions came from those meetings? Where did the real work happen, in the meeting or after?

My Tuesday: 3.5 hours in meetings. Four actual decisions made. At least 45 minutes of real decision-making happening in Slack after 9pm.

The ratio of time spent to decisions made is your operating efficiency signal. A meeting that ends with no decision is just a conversation with a calendar invite. Not all of those are bad, but you should know which ones you're running.

When you see the ratio clearly, you start seeing where the bottlenecks actually are. And you start making different choices about which meetings need to exist at all.

That's the discipline that matters most when you're covering this much ground. Not the ability to switch between domains. The ability to see across them clearly enough to know where your time is actually going and where decisions are getting stuck.

Because at the end of the day, the job isn't being an expert in four things. It's making sure four things move in the same direction.

That's harder than it sounds. And most days, it's exactly what I'm still figuring out.