Most remote companies are remote by accident. They hired someone in a different city, then another, and suddenly they're "distributed."
We're remote by design. Not because it's a perk. Because it's the only way to build what we're building.
Here's something most companies miss: you can't actually build a diverse team without being remote-first.
If you're hiring in San Francisco, your talent pool is San Francisco. That's 1 timezone, 1 dominant culture, 1 cost of living, 1 set of perspectives.
We operate across 12+ timezones. North and South America. Europe. Asia. Different cultures, different languages, different lived experiences.
This isn't about checking diversity boxes. It's about accessing perspectives we'd never find in a single geography.
When someone from Eastern Europe suggests a GTM tactic that worked in their market, it's often invisible to someone who's only worked in the US. When someone from South America points out a cultural nuance in messaging, it changes how we communicate globally.
Remote-first doesn't guarantee diversity. But diversity is impossible without it.
The trade-off? Coordination gets harder. You can't just walk to someone's desk. You can't do daily standups when half the team is asleep.
So we built systems that work async. Not as a compromise - as the default.
We structure work around small teams - 2 to 4 people maximum.
It starts with 2. One person working alone hits walls. Two people solve problems faster, catch each other's mistakes, compound learning.
As work scales, the team grows to 3, sometimes 4. The moment you add that third person, something shifts - a leader emerges. Not because we assigned the role, but because 3 people need coordination that 2 don't.
We don't force leadership. We watch who steps up.
These small teams own outcomes, not products. We have 1 product - Unstuck Engine. But we have multiple outcomes: outbound campaigns that convert, demos that educate, onboarding that activates, content that teaches.
Each small team owns 1 outcome fully. They decide what to build, how to build it, when to ship it. No approvals needed beyond the team itself.
Why small teams?
Speed. A 2-person team ships faster than a 10-person team because there's no coordination overhead. No alignment meetings. No waiting for consensus. Just build and ship.