Product
Why we split "assistant" and "coach" into two apps
The moment an app tries to both finish your emails and question your five-year plan, it gets worse at both. Here's the reasoning behind keeping them apart.
Read the note →Battlewits
We build AI assistants that get things done, and AI coaches that push back — two different jobs, done well, instead of one blurry chatbot that half-does both.
Two products, two jobs
Most AI products blur the two together and end up mediocre at both. We keep them separate on purpose.
Assistants
Built for speed and follow-through: drafting, scheduling, research, the parts of your day that don't need a debate — just a result you can trust.
Coaches
Built to disagree productively: it asks the question you skipped, names the weak point in your plan, and won't let a bad idea coast on confidence.
Our approach
"A good opponent makes you better. We think an AI worth using should occasionally disagree with you — and always tell you exactly why."— The Battlewits design principle, applied to every assistant and coach we ship
From the journal
Short field notes from building assistants and coaches — what worked, what we scrapped, and why.
Product
The moment an app tries to both finish your emails and question your five-year plan, it gets worse at both. Here's the reasoning behind keeping them apart.
Read the note →Design
Disagreement that lands feels earned, not scripted. Notes on pacing challenge against support so the coach stays useful, not exhausting.
Read the note →Behind the scenes
An assistant that quietly fails is worse than one that's slow. How we designed status updates that tell you the truth, including when it's stuck.
Read the note →Battlewits assistants and coaches are launching on iOS and Android. Get notified the day we open the gates.