Balance reads your git history and shows how your hours really split between building and selling. Then it tells you the one marketing move to make next. A free skill for Claude Code.
With an agent, the next feature is an hour away and it always works by evening. Telling people about it is slow, awkward and gets no green checkmark. So the ratio drifts, one reasonable day at a time.
An AI agent makes every feature feel almost free. Nothing on your screen says stop.
A product nobody knows about doesn't sell, however good this week's commits are.
Your calendar doesn't show it and your git graph looks great. Balance puts the number in front of you.
It runs on your machine, reads commit times and file paths, and nothing else.
Your commits are grouped into work sessions. A commit that only touches your blog, landing page or README counts as marketing, not building.
If you schedule posts in Wingspan, every published post and draft is added to the marketing side, per product.
Not a dashboard to admire. One marketing action for your most over-built product, tied to what you just shipped.
This is the author's own output, last 14 days, five products. It is why Balance exists.
| Project | Build h | Market h | Build % | |
|---|---|---|---|---|
| cerver | 27.6 | 7.4 | 79% | over-building → market |
| kompany | 22.7 | 0.0 | 100% | over-building → market |
| wingspan | 1.0 | 0.0 | 100% | over-building → market |
| All products | 51.3 | 7.4 | 87% | target 20% |
| Side projects | 32.1 | — | — | off-product time |
Side projects took 32 hours, more than half of what went into the products. That one line was worth the install.
Balance also runs quietly inside Claude Code. When you ask for another feature on a product that's already far over, you hear about it once, with a better move. Then it does what you decide.
curl -fsSL https://work-work-balance.autobirds.com/install | sh in your terminal./balance. With no setup it reads every repo in ~/Code, one row each.~/.claude/skills/balance/config.json.It's what an established company spends on R&D. Early on you may want 40%. Set your own target; the point is to choose it, not drift into it.
No. Only commit times and changed file paths, from your local git. Nothing is sent anywhere.
Commits that only touch blog posts, landing pages, READMEs and images, plus posts you publish through Wingspan. You can edit the list.
Not counted yet. Hours are an estimate from commit sessions: good enough to see the split, not to bill by.
The script runs on its own with Python 3: python3 balance.py. Claude Code adds the next-move advice and the nudge.
Nothing. It's a script and a skill file. Read both before you run them; they're short.