Builder Assessment: How to determine if your CTO/CPO is right for your company – Paul Müller, Adjust & EWOR Partner

About this episode

Who you choose as a builder for your startup largely determines success or failure. But how do you know if your choice is right and has what it takes for a long-term, successful collaboration?

Paul Müller, co-founder of Adjust and newly appointed partner at EWOR, shares his valuable experiences as a builder of a unicorn in this episode. His practical insights and perspective as an angel investor are invaluable for any founder facing this critical decision.

Why business understanding is crucial for builders

A common mistake: Many founders search for the most technically brilliant builder but overlook a crucial element – business understanding. Paul emphasizes that successful builders must not only be able to write code or develop products, but understand how their work contributes to company success.

The builder must understand the connection between technical decisions and business outcomes. Only then can they set priorities correctly and deploy resources optimally.

Green flags: How to recognize a good builder

Over the years, Paul has identified clear patterns that distinguish successful builders:

• –Business orientation: The builder understands company goals and can align technical decisions accordingly
• –Pragmatic approach: Focus on solutions that advance the business, rather than technical perfection for its own sake
• –Communication skills: Can explain complex technical matters in an understandable way for the entire team
• –Adaptability: Willing to reconsider processes and decisions as the business evolves

Red flags: Warning signs you should take seriously

Just as important as green flags are the warning signs Paul has identified in his time as founder and investor:

• –Technology for technology's sake: Builders who always want to use the latest tech without questioning business value
• –Poor communication: When the builder cannot explain why certain technical decisions were made
• –Inflexibility: Stubbornness about process adjustments or resistance to business-driven priority shifts
• –Isolated working: Builders who isolate themselves from the rest of the team and live in their own world

MVP vs. long-term architecture: What can you change later?

One of the most difficult decisions for founders: What needs to be done right from the start and what can be adjusted later? Paul makes a clear distinction:

Changeable later:

• –Many technical implementation details
• –Development processes and workflows
• –Team structures and responsibilities

Hard to change:

• –Fundamental architecture decisions
• –Data models and structures
• –Security concepts

The key is to make pragmatic decisions for the MVP that advance the business while keeping long-term implications in mind.

When your builder choice is suboptimal

Paul provides practical advice for when you realize your builder choice wasn't optimal:

1. –Honest assessment: Concretely identify where the problems lie
2. –Clear communication: Address issues directly
3. –Development opportunities: Offer coaching and continuing education
4. –Set timeframes: Define clear improvement goals and timelines
5. –Develop Plan B: Prepare for the case where no improvement occurs

Co-founder vs. employee: Does it make a difference?

An important aspect Paul addresses: Does it make a difference whether the builder is a co-founder or early employee? His experience shows clear differences:

Builder as co-founder:

• –Higher emotional connection to the company
• –Greater willingness to go through tough times
• –Harder to replace if it doesn't work out

Builder as early employee:

• –Clearer role distribution and responsibilities
• –Easier to adjust or replace
• –Requires stronger financial incentivization

How to optimally support your builder

As CEO, you bear responsibility for your builder's success. Paul recommends:

• –Communicate clear goals: The builder must understand what business outcomes are expected
• –Provide resources: Ensure the necessary tools and right team are available
• –Regular feedback: Establish continuous dialogue about performance and expectations
• –Shield from distractions: Help maintain focus on the most important priorities

The builder checklist

In conclusion, Paul provides a compact checklist for builder evaluation:

• –Does the builder understand our business goals?
• –Can they justify technical decisions in business-oriented terms?
• –Do they communicate clearly and understandably with the entire team?
• –Do they show flexibility when requirements change?
• –Have they successfully mastered similar challenges before?

Choosing the right builder is one of the most critical decisions for any founder. With Paul's experience and this structured approach, you significantly increase your chances of finding the right builder for your startup and achieving long-term success.