The Two-Year Commuter Marriage That Nearly Broke Us: A Cautionary Tale for GTM Teams and Remote Work Advocates

I’ve spent the last decade building go-to-market strategies for high-growth SaaS companies. But the toughest organizational structure I ever tried to design? A dual-state marriage.

When my husband accepted a VP-level role in Spartanburg, South Carolina, and I stayed behind in Washington, DC, with our six rescue pets, I thought we had a perfect GTM plan: temporary separation, clear milestones, and a remote work escape hatch. Two years later, I can tell you it was the worst decision we ever made—and it’s a lesson every revenue leader should internalize before greenlighting distributed team models or forcing a “hybrid later” promise.

Here’s what happened, why it failed, and the hard data-backed playbook for avoiding the same collapse in your personal life or your pipeline.

The Initial Pitch: Why We Convinced Ourselves It Would Work

After months of job hunting, my husband finally landed a role that checked every box: higher salary, better title, and a company he genuinely admired. The only catch? The office was in Spartanburg, South Carolina—a seven-hour drive from our home in DC.

We never considered relocating together. I’d lived in DC since grad school, and our “nontraditional family” (six rescue pets, including cats and dogs) had roots in the city. He needed work, and nothing viable had appeared locally for months. So we crafted what felt like a rational plan: he’d move to South Carolina; I’d stay in DC. We called it temporary.

Here’s where the GTM thinking crept in. We convinced ourselves that:

• Remote work flexibility was inbound. Once he “proved himself,” his company would allow a hybrid arrangement.
• Absence would strengthen our connection. I’m independent and outgoing. I figured space would make us miss each other in a healthy way.
• The cost-benefit math worked. We bought a single-story fixer-upper in SC with a mortgage cheaper than local rentals. I could bring the dogs, hire a cat sitter for DC visits.

I was wrong. Spectacularly wrong.

The Pipeline Collapse: What Actually Happened After He Moved

The Remote Work Promise Died Immediately

His new company was vehemently opposed to any remote or hybrid arrangement. The flexibility we assumed would materialize never did. He was expected in-office every day, so our plan to see each other midweek evaporated. We were limited to weekends and holidays.

The Logistics Became a Drag

Because he had taken our shared vehicle, visits required a 14-hour round trip drive every weekend. I couldn’t easily bring the dogs on every trip. The cat sitter logistics became a part-time job. The “cheap” fixer-upper turned into a money pit of repairs we couldn’t supervise together.

The “Fun” Factor Never Arrived

I had envisioned solo city adventures and rekindled romance. Instead, I spent weeknights managing the pets alone, handling the DC home solo, and feeling our marriage degrade into logistical updates. We stopped growing together. We stopped building together.

The Data That My Heart Already Knew

Our two-year experiment cost us more than time. It cost us momentum.

In GTM terms, we violated three core principles that every revenue team should know:

1. Temporary Arrangements Almost Always Become Permanent

We said “two years max.” We meant it. Yet we spent those two years surviving, not thriving. The temporary structure became our permanent operating model. In sales, this is the equivalent of launching a pilot with no end date. You never optimize. You never commit.

2. Remote Work Flexibility Is Not a Given

We assumed his office-based role would evolve. It didn’t. Many companies still view remote work as a privilege, not a tool. If your GTM plan depends on future flexibility that you don’t have in your contract today, you are building on sand.

3. Relationships and Revenue Require Proximity

Whether you’re managing a pipeline or a partnership, proximity matters. Weekly phone calls and weekend visits didn’t replace daily alignment. We lost the small moments—the hallway conversations, the shared dinners, the collaborative problem-solving. My husband and I became a weekly sync call, not a life team.

The Recovery: How We Eventually Rebuilt

After two brutal years, he landed a role back in DC and moved home. The reunion wasn’t instant magic. It took months to rebuild trust, routines, and the muscle memory of living together.

Here’s what I’d do differently—and what I now recommend to any revenue team considering a split arrangement:

Establish Hard Boundaries on Duration

If you must separate, set a firm end date. No “we’ll reassess in 6 months.” No “once he proves himself.” Lock in a 3-, 6-, or 12-month maximum with a documented exit plan.

Codify Communication Cadence

We didn’t schedule real conversations. We relied on catch-up calls. Now I know: daily 15-minute alignment is non-negotiable. Weekly deep dives. Monthly in-person resets. Treat your relationship like your most important account.

Build a Buffer for Reality

We underestimated costs, driving fatigue, and emotional drain. Add 30% to your time and budget estimates for any separation arrangement.

The GTM Lesson for Tech Leaders

This story isn’t just about marriage. It’s about the assumptions we make when we design distributed teams, hybrid work models, or cross-location sales territories.

Your remote strategy is only as strong as your worst-case scenario.

When you promise “remote later,” or “flexibility after ramp,” you’re betting on culture change that may never come. When you split core team members across different time zones, you’re betting on communication tools to replace presence. When you ask sales reps to manage accounts from seven hours away, you’re betting on their resilience to outlast the friction.

Sometimes those bets pay off. Sometimes they don’t. In my case, the cost was two years of a marriage that never fully recovered.

If you’re a founder, VP of Sales, or RevOps leader reading this, ask yourself:

• Are we designing for the reality of today or the flexibility we hope tomorrow brings?
• Are we measuring cost savings or cost impact?
• Are we optimizing for short-term wins or long-term alignment?

Two years apart taught me this: Proximity is a feature, not a bug. Don’t sacrifice it because the short-term math looks good.

If you want to build something that lasts—whether it’s a partnership or a pipeline—keep your team close. Your bottom line will thank you.

And your heart will, too.