I Stopped Calling It My Business and Asked Whose Life It Was Actually Costing

# I Stopped Calling It My Business and Asked Whose Life It Was Actually Costing

There was a dinner. Hollie across the table. Food I don’t remember. Phone face-down but still warm in my mind — the last email half-written, the follow-up I hadn’t sent, the thing that wasn’t done yet.

She wasn’t angry. That’s the part that stayed with me.

She’d just adjusted. Somewhere along the way, without a conversation, without a negotiation, Hollie had recalibrated her expectations around my absence. Not the physical absence — I was sitting right there. The other kind. The kind where someone is present in body and somewhere else entirely in everything that matters.

I didn’t recognize it in the moment. I filed it under *this is what building something costs* and moved on.

That’s the story I want to unpack. Not because it ends well and I want credit for figuring it out. Because I think a lot of operators are sitting at that same table right now and calling it something other than what it is.

—

## The Frame I Was Living Inside

The logic felt airtight from the inside.

I was building something. Everything it cost was evidence it mattered. Late hours weren’t a problem — they were proof. Missed evenings weren’t a failure — they were the price of the thing I was doing *for my family.* The sacrifice wasn’t the story. The sacrifice was the point.

I believed this. That’s worth saying plainly, because it’s easy to look back and perform clarity you didn’t have at the time.

The equation was: *sacrifice equals commitment equals meaning.* The more it extracted, the more real it must be. If it hurt enough, it must be worthy. That’s not logic — it’s a thing that got wired in early, when the emergency was real and the only way through was to keep moving. When there’s no money and the power is at risk and dinner isn’t guaranteed, you push harder because you have to. That’s not a character flaw. That’s survival.

The problem is the emergency passes. The wiring doesn’t update automatically.

So you keep paying. And you keep calling it commitment.

—

## Who Was Actually Running the Tab

At some point I started tracing where the cost was landing.

Not on me.

On Hollie, who learned to navigate around the work calendar. Who stopped asking if I’d be done soon. Who adjusted dinner timing, adjusted conversation expectations, adjusted what she planned to share with me versus what she’d just handle herself.

On Alan and Kenneth, who watched what *important* looked like every day and drew their own quiet conclusions about where they fit in the ranking. Kids don’t need a speech. They watch. They learn what wins. They remember.

**A lot of operators aren’t running a business. They’re running a transfer of cost.**

The business doesn’t absorb the extraction. The people around the owner do. And they never agreed to be part of the tab.

It doesn’t happen in one dramatic moment. It happens in fragments. Repeatedly. Quietly. Missed dinners. Half-attention that the other person can feel even when you think you’re hiding it. A household that never fully powers down because the operator is still the switchboard and everyone in the house knows it. Kids learning that work always wins the interruption contest. A spouse silently adapting, over and over, until the adaptation becomes the baseline and neither of you can remember when it changed.

These aren’t crimes. They’re the bill being paid in installments nobody sees.

—

## The Question That Changed Everything

I stopped asking *how much can I endure* and started asking *who else is carrying the load I’m calling ambition.*

That question does something the first one doesn’t. It removes the heroic frame. It makes the cost visible. It makes the people visible.

There was a week — not that long ago — where I didn’t open my laptop for three days. Not a planned break. Just a stretch where I stepped back and let the systems run.

Nothing broke. The pipeline scored leads. Content published. Follow-ups went out. Nothing waited for me.

What surfaced wasn’t relief. It was a question I hadn’t been ready to ask before: *What was all the previous cost actually for?*

If the business could run without me for three days and nobody noticed, then a significant portion of what I’d been spending — attention, presence, evenings, the particular kind of aliveness you bring to a table when you’re actually there — none of that was required by the business. It was a habit. A habit that had outlived the emergency that created it.

And the people it was costing hadn’t been consulted about whether the emergency was still real.

—

## What Systems Actually Do and Don’t Do

The operators who find their way to the work I do now aren’t lazy. They’re not avoiding automation because they don’t understand it.

A lot of them are avoiding it because setting it up means facing something uncomfortable: the business has been running on a tax they were levying on everyone around them. Building the system makes that visible. That’s harder than staying busy.

I want to be direct about what automation actually does and doesn’t fix.

It doesn’t settle the relational debt. If Hollie spent three years recalibrating around my absence, a workflow doesn’t erase that. That’s a different conversation — one that systems create the space for but can’t have on your behalf.

What systems do is remove the ambush points. The 11pm text that pulls you back in. The Sunday morning “catch-up” that eats three hours. The dinner that gets interrupted because a lead came in and you’re still the only one who can respond. The way the household holds its breath because everyone knows you’re almost done and almost done keeps extending.

Removing those points frees you *for* something — not just *from* tasks. Presence. Actual attention at an actual table. The capacity to hear what Hollie is saying instead of processing it in parallel with everything else still open in the background. That’s what the systems are for. That’s what they can do.

They don’t do the work of accountability. They create the conditions where accountability becomes possible. The difference matters.

—

## Where I Actually Am

I’m not writing this from a mountain.

I’m still at Walmart. Hollie’s still waiting on the other side of a plan that isn’t complete yet. The question changed before the circumstances did — and that’s not a small thing, but it’s also not a resolution.

What changed is I can no longer not see it.

I can’t look at a 10pm work session and call it sacrifice without asking who the sacrifice is actually serving. I can’t call missed presence an investment without asking what the return looks like and who cashed out at a loss to fund it.

The question isn’t comfortable. I don’t think it’s supposed to be.

*Whose life is your business actually costing?*

Not as an accusation. As the real version of the question most operators never get around to asking because they’re too busy proving the thing is real by paying for it.

Trace the cost. Actually trace it. See where it lands. See whose account it’s coming from.

That question is worth more than any system I’ve ever built. The system just creates the space to ask it without the business ambushing you mid-thought.

That space is what I’m trying to build. For myself first. And for anyone else sitting at a table where the food has gone cold and they can’t quite explain why.

—

*Jeff Halligan is a licensed real estate agent in North Idaho with Epique Realty and the founder of FlowState Ops — AI and automation systems for operators who are ready to stop being the switchboard. He lives in Kootenai with his wife Hollie.*