Our mission is to radically accelerate the pace of software development for every company in the world.

Why we care about this mission:

• The world is increasingly built on software. The faster we can move the pace of software development, the faster we can accelerate growth & technological development, and help solve the biggest problems ahead of us.

Value: Focus

Explanation: We relentlessly focus on the #1 highest impact task to drive our business forward. We push ourselves to think strategically about what truly matters: it’s too easy to fall into doing work because it feels **like the “right” way to build something, or it’s the ‘obvious’ next thing, without thinking from first principles on what actually moves Meticulous closer to achieving our mission, or helps us discover the path to do so.

In addition we want to solve a few problems extremely well. It’s dangerously easy to fall into the trap of trying to solve everything for everyone.

Value: Collaborate closely & enjoy the journey together!

Explanation: We always try to help each other, before we're asked to do so. We teach with compassion, which means sharing our knowledge and realising the leverage of empowering our teammates. We provide continuous feedback to each other, support our teammates, win as a team and regularly celebrate this. Such tight collaboration on problems as challenging and groundbreaking as those at Meticulous can be a lot of fun. We lean into that, and try every day to make each others’ experience as fun as possible.

Examples:

• Working and brainstorming together in person, rather than remote or async communication
• When we hit a milestone, ship a large feature or win a significant customer we take the time to celebrate together.

Value: Find the truth

Explanation: Know what your underlying assumptions are and test them. Strategically identify implicit assumptions in high-investment decisions and systematically validate or invalidate each one. Work to disconfirm your beliefs.

Examples:

• When making a major multi-month product decision, work out the assumptions behind that product being highly profitable & successful in the market, and how to test those assumptions.
• Don’t spend long making a non-impactful decision, such as code style.