Why I built Easy Team Subs

A lot of kids sport coaching happens in small windows of attention.

You are watching the play, listening to a child on the bench, keeping an eye on the clock, and trying to remember whether someone has already had a longer run than everyone else.

That is where Easy Team Subs came from.

It was not built because the world needed another complicated coaching platform. It was built because fair playing time is easy to care about and surprisingly hard to manage in the middle of a real game.

The real problem was not planning before the game

Before kickoff, everything feels manageable.

You know the squad. You know roughly how often you want to rotate. You may even have a rough idea of who should start.

Then the game begins.

One child is tired earlier than expected. Another arrives late. Somebody needs to sit out for a while and then come back. The score changes the rhythm. The sideline gets noisy. A parent asks whether a player has had enough time. Your nice tidy plan turns into a memory test.

The hard part is not building a perfect schedule before the game. The hard part is keeping the next decision fair when the context changes every few minutes.

I wanted something calmer than paper, memory, or panic

Most people solving this problem are not full-time coaches with an analyst next to them.

They are volunteer coaches, parents helping on the sideline, assistant coaches, or managers trying to do the right thing for a group of kids.

That is why I wanted the tool to feel calm instead of clever.

The job was simple:

• keep the next change obvious
• show enough context to make the call feel fair
• avoid account setup, heavy admin, or a pile of screens
• stay useful even when the game stops following the original plan

That is still the core idea behind the app.

Fairness is emotional as well as practical

Playing time is not just a numbers problem.

It shapes whether children feel noticed. It affects how families judge whether the game felt fair. It changes whether a coach feels in control or always half a step behind.

That is why I cared about the app being easy to read under pressure.

If the tool is too dense, it fails. If it hides the next decision behind too many taps, it fails. If it expects the adult on the sideline to read long explanations while the match continues, it fails.

The right tool should reduce mental load, not add another layer of it.

Why local-first mattered

I did not want the app to depend on creating accounts, joining workspaces, or hoping signal was good enough on the field.

For this product slice, the job is mostly personal and local.

A coach needs to open the app, see the team, start the game, follow the live flow, and keep enough history to be more consistent over time.

That is why the product leans local-first. It should feel quick to open, quick to trust, and simple to use again next weekend.

Why the blog exists too

The app solves one very specific problem, but the blog supports the bigger conversation around it.

There are parents and coaches searching for things like:

• how to make substitutions feel fairer
• what to do when a player arrives late
• how to handle a player sitting out and coming back later
• whether an app is actually better than paper notes on match day

Those are real questions, and the site should answer them in plain language.

The product goal stayed intentionally small

Easy Team Subs is not trying to be a giant coaching suite.

It is trying to make one difficult moment easier: the next substitution decision when fairness still matters and the game keeps moving.

That is why I built it, and that is still the standard I use when deciding what belongs in the product.