Pick Your Battles

Running a business is basically playing chess with landmines.

You’ve got big-picture strategy on the one hand - growth, hiring, partnerships, vision.
And then you’ve got the daily debris: last-minute change requests, “quick” favours that turn into full-blown projects, and invoice disputes that drag out longer than your average Marvel movie.

Let’s talk about one of those.

‍

The $0 Dispute That Cost Me 5 Hours

A while back, we had a minor scuffle with one of our partner teams. Not over strategy. Not over outcomes. Over nine hours logged for a UI design deliverable. Their product owner decided they only wanted to pay for half.

The reason?
Apparently, the work “wasn’t quite what was briefed.”
Never mind that the brief was vague to begin with.
Never mind that the project got paused halfway through to refocus on a different deliverable.
And definitely never mind that we built a scalable, structured Figma component library that could be restyled in under five minutes.

They didn’t see the value… at least, not all of it.

And so, a mountain was built out of a molehill.
Back-and-forths. Emails. Voice notes. Passive-aggressive calendar nudges. You know the dance.

By the end of it, I’d spent more time justifying the invoice than the actual hours in question.

Let that sink in.

‍

When the Battle Isn’t About the Outcome

In that moment, I realised something that’s become a bit of a mantra for me since:
Just because you're right doesn't mean it's worth it.

This wasn’t about the invoice anymore. It was about principle.
But principle is expensive when it costs you sleep, attention, and momentum.

And that’s the paradox of leadership no one really talks about:
You don’t just manage people.
You manage your focus.

Focus is finite. It’s your real currency. And if you waste it fighting over breadcrumbs, you won’t have anything left when it’s time to hunt the bigger game.

‍

The Real Problem Wasn’t the Invoice

Let’s zoom out.

What actually went wrong?

Simple: misalignment and lack of context.

The brief we got was standard-issue vague: “Refine the icon library. Ensure consistency.”
That’s like being asked to “clean the house” without knowing if the guest bathroom is a crime scene or if the kitchen’s been converted into a meth lab.

So we did what we always do at Nexubis:
→ Validate what’s still in use
→ Remove the clutter
→ Add use-case context
→ Rebuild it as a proper, swappable component library in Figma

Because that’s not just the right way to do it - that’s the only way to do it if you want a scalable product.

But here’s the kicker: people don’t value what they don’t understand.
We tried explaining it, but the damage was already done. And when understanding is low, perception becomes truth.

As we wrote in Your Perception Is Your Reality:

“You can’t build successful products or websites on a shaky foundation of insufficient context. You need to understand the goal and your client better than they understand it themselves.”

Spot on. And yet, here we were.

‍

The Real Fix? Sharpen the Process, Not the Pitchfork

After licking our wounds (and rechecking the invoice for the hundredth time), we didn’t just moan about it. We looked at the battlefield.

Where did the system break?

The answer was obvious: no post-brief alignment.

We didn’t have a follow-up to clarify use cases, scope creep, or the long-term design implications. That’s on us.

So now, every client brief gets a quick sync… even if it feels redundant. Because redundancy is better than refunding hours because someone “just didn’t get it.”

We also added internal QA checkpoints, more visual aids to explain component logic, and started tagging potential misunderstanding areas before they escalate.

Again, as we wrote in Resentment Is a Symptom of Poor Process:

“Most ‘performance issues’ are really just process issues in disguise.”

The same applies here… just swap ‘performance’ for ‘client trust’.

‍

Know When to Let Go (and When to Double Down)

Every founder has these moments - where you know you're right, but pushing harder will cost more than it saves.

So you ask yourself:
→ Will this move the business forward?
→ Will this protect the team?
→ Will this prevent the same issue from happening again?

If the answer’s no… walk away.
But if it’s yes? Push. Gently. Strategically. Like a velvet sledgehammer.

Just don’t waste a 10X founder brain on 1X problems.

‍

TL;DR – What to Take With You

• Not all battles are worth fighting, but all are worth learning from.
  
• Clarify briefs. Then clarify again.
  
• Value needs context. If clients don’t get it, that’s on you.
  
• Your time is currency. Spend it like it matters.

And maybe most importantly:

Don’t lose a client over 4.5 hours, but don’t lose your standards either.

Pick your battles. But always bring a bigger strategy than just your ego.