Our mission and values
This page explains what a company is trying to do, why, and how it intends to get there. The values described here are aspirations rather than a scorecard: they are meant to guide decisions and behavior, and the company acknowledges it will not always meet them.
The mission
> Help developers make more money.
Four core values
The company organizes its working principles around four core values: Customer Obsession, Always Be Shipping, Own It, and Balance. Each value carries a set of supporting practices that describe how it shows up in daily work.
Customer Obsession
When a decision is genuinely difficult, a useful test is to ask what would make the customer's life easier. That answer is not always the convenient one: it can mean extra work for a team, or reversing a decision already made. Over time, acting in the customer's interest is treated as a reliable guiding principle.
Customer Empathy
Every customer interaction should be considered from the customer's point of view. Would a given email campaign annoy them? Is a message too terse? A single negative experience can turn an enthusiastic user into a detractor.
Customer First
A customer's positive outcome and experience is treated as more important than several things the company controls. The list below captures those trade-offs.
Customers are the only reason we exist
The company warns against becoming obsessed with itself rather than its customers. Every activity is meant to serve customers and the mission.
Always Be Shipping
Long-term progress is treated as the accumulation of small daily progress. Minimizing time-to-value and shipping frequently is expected to compound over time.
Iterate Quickly
Fast iteration matters. The Pareto principle is treated as real: find the 20% of work that produces 80% of the outcome and do that first. Deciding and acting quickly also allows faster course correction, since plans rarely survive first contact with reality. The sooner something ships, the sooner it can be adjusted and shipped again.
Default to Action
Doing is preferred to merely talking. As a company gains momentum, it can be tempted into analysis paralysis and the innovator's dilemma. Progress is attributed to hard work, risk-taking, and action. Shipping means delivering things that deliver value, not just discussing them.
Be Efficient
Time and capital should be used efficiently. Long meetings, over-engineered solutions, and costly rewrites are to be minimized. Minimizing time-to-value is inherently efficient. Toilsome work should be automated, simple solutions that are cheap to discard are preferred, and the big picture should be kept in view.
Communicate Well
As a distributed company, written communication carries much of the load. Writing should be clear and provide enough context for the reader to understand what matters. Over-communicating is discouraged; simple, direct, easy-to-consume writing is preferred.
Own It
If someone has a bad experience with your work, that should matter to you. Own what you build. Avoiding mistakes is admirable, but being available to help when mistakes happen matters more.
Attention to Detail
A great product is a collection of thousands of tiny details. Attention to detail does not mean getting every detail right or spending hours polishing pointlessly. It means noticing the details, focusing on the right ones, and shipping.
See something, do something
If something looks off or strange, if there is a bad experience, or if a ball is about to be dropped, act. Do not assume someone else is handling it. Ask a manager, a manager's manager, or in the questions channel. If no one owns the issue, it becomes your issue: own it if it needs owning.
One Company
Many teams exist, but everyone is part of one team with a shared mission. Problems should not be thrown over fences, and blame games should be avoided.
Kaizen
Kaizen is a term for continuous improvement. When something goes wrong, such as a bug or a bad customer experience, the team runs a quick retrospective and makes changes to do a little better next time.
Personal Growth
Kaizen also applies to personal knowledge, skills, role, and responsibilities. Each day, look for small ways to improve what you do and how you do it. Investing in yourself is treated as a compounding advantage for both the individual and the company.
Appreciate Feedback
Constructive feedback between colleagues is essential to continuous personal improvement. Good feedback is a gift, and the best feedback can be the hardest to hear. Listen to feedback, consider it, and question your own self-perceptions; that is how improvement happens.
Balance
The journey is described as very long and very difficult. To go the distance, a balanced approach is required, both in the intensity of work and in how people make decisions, communicate, and relate to each other.
Maintain a Controlled Burn
Ambitious goals require hard work. Working at the company will stretch people, but it should not break them. Balance means maintaining a controlled burn: everyone experiences stress, and the key is keeping it manageable.
Work is not your life
Work matters and is important, but it is not the whole story. A job should not replace friends and family. As a remote company, deep social connection with teammates can be harder than in an office, and that is acceptable because it leaves time for other things. The point is to actually make time for those things.
Keep boundaries and respect boundaries
Balance includes a right to disconnect. Without an office, response-time expectations can be unclear, and anyone can be texted, emailed, or messaged at any time. Keep your own boundaries and have methods for emergency contact, but do not feel obliged to be instantly responsive on every channel. When seeking responses, be mindful of true urgency and avoid urgency theater in the name of shipping.
Be Kind
Building a startup is hard enough. Be good to each other every day. Default to nice.
Praise Publicly
When someone does something great, tell them and share it with the team. A dedicated good-feels channel is suggested as a good place for this.
Give Negative Feedback Privately
Critical feedback should be shared often, but sharing it in public does not help anyone. Share critical feedback in the smallest possible setting, ideally one on one.
Believe
Most startups fail, and the company expects to miss many goals. The key is to keep believing in the mission and in eventual success, while recognizing that success has not yet arrived.
A decision checklist drawn from these values
Use these prompts to test a decision against the stated values:
- Customer test: does this make the customer's life easier, even if it costs the team more work?
- Empathy test: would the customer find this interaction annoying or confusing?
- Shipping test: is this the smallest slice that delivers value and can be adjusted later?
- Ownership test: if this goes wrong, who is on the hook to make it better?
- Balance test: is the urgency real, or is it urgency theater?
- Feedback test: is praise public and is critical feedback private and specific?
- Improvement test: what small change will make the next attempt better?
Worked example: applying Customer First
Suppose a customer reports that a feature is hard to implement even though the internal team assumed it would be simple. The Customer First list says the customer's experience outranks the company's plans and assumptions. So the team would not defend the original plan; it would investigate why many customers struggle and adjust. At the same time, the list says the customer's stated request is not automatically the answer: the team should listen to the underlying pain and design a solution that actually solves it. Finally, even if the difficulty stems from something outside the company's control, the company is still on the hook to make the experience better.
Aspiration versus guarantee
These values are explicitly described as aspirations. The company states that it does not and will not always live up to them. They function as a framework for guiding work, not as a promise of perfect behavior or a measurable standard. Readers should treat them as stated intentions rather than verified outcomes.
| Item | What it means |
|---|---|
| Company plans | The product vision should not be placed above what customers need; customers may know better. |
| Company assumptions | If many customers struggle to implement something that was assumed to be easy, the assumption should be dropped. |
| What a customer says they want | Listen to the pain and solve the underlying problem rather than simply doing what is requested. |
| What the company controls | If a customer has a negative experience related to the product, the company is still responsible for improving it, whether or not the cause is under its control. |
This table reflects the stated values as written; it is not a measured performance record.
Frequently asked questions
Are these values a guarantee of how the company behaves?
No. The company describes them as aspirations and acknowledges it does not and will not always live up to them. They serve as a framework for guiding work.
Does Customer First mean always doing exactly what a customer asks for?
No. The stated approach is to listen to the customer's pain and solve the underlying problem, rather than simply implementing a requested feature. The company believes it often knows the product and its capabilities better than the customer.
How does the company reconcile shipping fast with work-life balance?
The values warn against urgency theater. People are encouraged to keep boundaries and not feel obliged to be instantly responsive on every channel, while still having methods for genuine emergency contact.
Where should praise and criticism be shared?
Praise should be shared publicly with the team, for example in a good-feels channel. Critical feedback should be shared in the smallest possible setting, ideally one on one.