01 · Foundation
Mission & Vision
Mission
What we do, today
We build human-centred products that create genuine value at scale.
Vision
The world we are working toward
Products that leave people more capable, more hopeful, and more free.
These two statements anchor every product decision we make. When we are unsure whether to build something, take a direction, or walk away from an idea — we return here first.
The distinction matters. Our mission is operational — it describes who we are right now. Our vision is directional — it describes the impact we are working toward. Both are necessary. Neither is decoration.
The founding premise
Real, lasting revenue only comes from creating real, lasting value. From building things people genuinely need — that work better than anything before them.
02 · Foundation
What We Believe
Five principles. Each one is meant to be tested against real decisions — not recited. If a principle doesn't hold when something is at stake, it isn't a principle.
01
Value before everything.
Mission and money are not in conflict. Revenue is the outcome of doing the job well — not a goal to chase independently. When we feel the pull toward profit before purpose, we stop and ask: who are we actually serving here, and how?
02
Non-extractive by design.
We do not manufacture need, exploit attention, or engineer dependency. Every product we ship gives more than it takes. This is not a constraint on our ambition — it is the foundation of it. The most durable companies are the ones users trust completely.
03
Pivot as a discipline.
We are not our ideas. Killing what isn't working is a competency, not a failure. The teams we most admire are not the ones who held on longest — they are the ones who read the evidence clearly and moved. Sunk cost is not a reason to continue.
04
Build as if it scales.
We make decisions as if millions of people will use what we build — even when we have none. The quality of our thinking does not depend on the size of our current audience. Small decisions compound. We treat them accordingly.
05
Co-elevation is the operating model.
No one's growth here comes at another's cost. Credit, decisions, and risk are shared equally across the founding team. Generosity in how we work together is not a cultural nice-to-have — it is a structural commitment we make on day one.
03 · Operations
How We Work
We operate in a repeating cycle. Not linear — we move between stages as the work demands. The discipline is this: we do not scale what we have not proven, and we do not grow what we have not earned.
01Create
Build the thing. A working version in the world is worth more than a perfect version in a document.
02Prove
Test whether it works and whether it matters. Real signal only — not internal enthusiasm reflected back.
03Improve
Iterate with intention, informed by what users actually do — not what we assumed they would.
04Process
Build systems and documentation that allow the work to scale beyond any one person.
05Remove
Cut what is not earning its place. We hold nothing sacred except the mission and the beliefs.
06Grow
Scale what is proven. Investing in growth before proof is expensive noise.
The product filter — before anything enters the cycle
Every product we consider building gets asked three questions first. All three must have a clear yes before we proceed.
01
Does this create genuine value — or does it manufacture a need that didn't exist?
02
Will the person using it leave more capable and more free — or more dependent?
03
Can it scale without compromising either of the above?
04 · Thinking
Borrowing from the Giants
Good thinking belongs to everyone who uses it. These principles come from people and companies we admire — we name the source, take what's useful, and make it our own.
G
From Google
Platform over product, by default.
Before committing to a product, ask: could this be infrastructure? Could this enable others to build, create, or transact on top of it? Platforms compound in value the more people use them. Products don't. When both are possible, build the platform.
10x, not 10%.
If the idea is only incrementally better than what already exists, it is not worth our time. We look for ideas that are an order of magnitude better — or categorically different. Marginal improvements serve incumbents. We are not incumbents.
N
From Netflix
Context, not control.
The leader's job is to set clear context — the goals, the reasoning, the constraints — and then trust people to make good decisions within it. Micromanagement is a symptom of unclear context, not of unreliable people. We build decision-making capacity at every level, not just the top.
People over process.
Brilliant processes don't build great products — brilliant people do. We hire for judgment, not compliance. When a company starts adding rules to compensate for weak people, it drives out the strong ones. We keep the team right and trust them to figure out the rest.
P
From Patagonia — Yvon Chouinard
Stand behind everything you make.
Patagonia ran a full-page ad on Black Friday that said: "Don't Buy This Jacket." Not as a stunt — as a belief. If you wouldn't tell a customer the truth about your product's costs and limits, you don't fully believe in it. We only build what we can stand behind completely.
Profit and purpose are not in conflict.
Chouinard built a billion-dollar company while treating ethics as non-negotiable — not as a brand strategy, but as a way of operating. The companies that claim they can't afford to do the right thing are the ones that haven't yet understood that the right thing is the business model.
Px
From Pixar — Ed Catmull
Story is king.
Pixar's founding principle: nothing — not technology, not marketing, not deadlines — gets in the way of the story. For us: nothing gets in the way of the core human value a product delivers. Features, aesthetics, and business models are all in service of that. If you can't say clearly what story you're telling, you're not ready to build.
Get the team right before you get the idea right.
"Give a good idea to a mediocre team and they will screw it up. Give a mediocre idea to a great team and they will fix it or find something better." — Ed Catmull. The idea is never the most important thing in the room. The people are.
Ab
From Airbnb — Brian Chesky
Design the company, not just the product.
Chesky treats company-building as a design problem — the culture, the structure, the rituals are all designed with the same intentionality as the product itself. "It doesn't matter how great your original idea is if you can't build a great company — the product will not endure." We design how we work with the same care we bring to what we build.
It's better to have 100 people love you than a million people like you.
Go deep before you go wide. Build something that moves a small number of people completely — that intensity is the signal that tells you whether to scale. Products that try to please everyone at launch end up mattering to no one.
Sp
From Spotify
Autonomy with alignment.
Autonomous teams move faster, own their work more deeply, and innovate more freely — but only when the mission and goals are genuinely clear. Autonomy without alignment produces chaos. Alignment without autonomy produces bureaucracy. We find the balance by being explicit about the what and the why, and trusting people with the how.
Bc
From Basecamp — Jason Fried & DHH
Do less, but do it well.
The answer to better work is not more hours — it's fewer things. Say no more often. Build the epicentre first — the one thing a user must be able to do — and postpone everything else. Constraints sharpen decisions. A calm company is not a slow company; it is a focused one.
Opinionated products attract the right people.
Products that try to be everything to everyone end up mattering to no one. Having a clear point of view — and being willing to say who this is not for — is what creates loyalty. We build products with a perspective, not products that hedge.
D
From Design Thinking — IDEO
Problem before solution.
Define the problem with the same rigour as the solution. A well-defined problem is half solved — and most teams skip this step entirely. We don't move to ideation until we can articulate the problem clearly enough that someone who has never heard of it understands why it matters.
Desirable, feasible, viable — in that order.
Does a real person genuinely want this? Can we actually build it? Will it sustain a business? Checking viability before desirability is how hollow products get made. We start with human need and work outward — not the other way around.
Fail early to succeed sooner.
The cost of preventing errors is almost always greater than the cost of fixing them. We prototype to think, not to prove. A rough version that reveals the wrong assumption in week one is more valuable than a polished version that reveals it in month six.
Jb
From Jeff Bezos — Shareholder Letters
Invent for empowerment.
The most transformative inventions are those that empower others to create and pursue their own ambitions. AWS didn't just serve Amazon — it gave thousands of companies the infrastructure to exist at all. When we ideate, we ask: does this make other people more powerful?
Plant many seeds.
"We need to plant many seeds because we don't know which one will grow into a mighty oak." Ideation is a volume game first, a quality filter second. We generate broadly before we commit narrowly. No attachment to any single idea is useful — only attachment to the mission.
Mi
From Hayao Miyazaki — Studio Ghibli
Make it honest, or don't make it.
Miyazaki has said he would rather stop making films than produce something dishonest. He duked it out with American studios to protect the authenticity of his work — and won. The work is the thing. Not the deal, not the distribution, not the market size. If the work isn't honest, nothing else matters.
Easy-to-understand is not the same as good.
"Easy-to-understand movies are boring. Logical storylines sacrifice creativity." We do not simplify to the point of dishonesty. We make things as simple as they need to be — and no simpler. Complexity in service of truth is not a problem to fix.
05 · Culture
Who We Are
This is a living document. It will be revised as we grow, as the company learns, and as our understanding of what we're building deepens. The version you are reading is a starting point — not a final answer.