About

You are buying judgement, so it matters whose

Amir Habib founded Kendoo and leads it as CTO. The work pairs that perspective with senior engineers, so decisions and delivery sit in the same team.

Amir Habib, founder of Kendoo
Amir Habib, Founder & CTO

Inside Kendoo

Built close to the work

Kendoo's work is deliberately hands-on: in the room with the people making decisions and the teams carrying them through. This quiet office moment belongs here because it is real, not staged.

Installing the Kendoo identity at the office

Relevance

What the experience is actually for

A chronological CV answers the wrong question.

What matters when someone enters an existing organisation is whether they have handled complex systems they did not build, stakeholders who disagree, delivery that has already slowed, modernization under commercial pressure, and change that has to survive after they leave.

The relevant part of twenty-five years is not its length. It is having seen enough failure modes to recognise one early, and having been accountable for the consequences of the calls rather than only advising on them.

The consulting years matter for a different reason: entering an organisation you do not know, forming a view quickly on incomplete information, and being willing to say the unwelcome thing while there is still time to act on it.

Working principles

How the work is done

  1. Evidence before opinion

    Most stuck technical arguments are stuck because nobody has the data, not because the question is hard. Instrumentation and baselines come before recommendations.

  2. Decisions, recorded

    Architectural choices are written down with their reasoning, so they can be revisited when the facts change rather than reopened whenever someone new objects.

  3. Accountability, not advice

    Decision rights are agreed in writing at the start. Advice without accountability rarely survives contact with delivery pressure.

  4. Progress you can check

    A monthly written report against a baseline agreed in the first month, including what did not move. Evidence rather than assurance.

  5. Capability left behind

    Coaching your leads is part of the engagement, not a bonus. If the organisation is no more capable at the end, the retainer did not work.

  6. Saying no

    Engagements that do not fit are declined on the call, with the reason. That protects your time and the results of the work that is taken on.

How Kendoo works

A CTO's perspective, with senior engineers

Strategy that never meets the code drifts, and engineering without a technical owner repeats itself. Kendoo puts both in the same team.

The leadership side

  • Technical direction and the architecture decisions behind it
  • Decision rights agreed in writing at the start
  • A weekly leadership cadence and a monthly written report
  • Coaching for your leads, so capability stays in the organisation
  • Amir accountable for the direction throughout

The engineering side

  • Senior engineers who read the code and the incidents
  • Design review, standards and delivery practices, applied in practice
  • Architectural disputes settled on evidence rather than seniority
  • Work done alongside your team rather than handed over as a report
  • Progress you can see in the system, not only in a document

That pairing is how the technology work runs. The brand, experience and team dynamics lines are run the same way. Where a company needs large build capacity instead, that is worth establishing on the call rather than three months in.

Expert network

Specialists who join an engagement when it calls for them

Independent professionals Kendoo works with, each brought in where the work needs a discipline of its own rather than a generalist opinion.

  • Shay Ben Barak

    Product, UX & HCI expert

    Product and experience strategy, user research, interaction design and usability for complex systems. Shay holds an M.Sc. in cognitive science from the Technion, lectures at the University of Haifa and mentors startups through Google for Startups.

    User Experience Strategy

  • Yana Levin

    Product Lead

    Product leadership: what to build, for whom and in what order. Yana works with Kendoo where a product needs clear priorities and a team aligned on them.

    User Experience Strategy

  • Noa Boker

    Strategic Storyteller & Human Dynamics Lead

    Psychodramatist, group facilitator and strategic storyteller with twenty years of experience across the public and business sectors. Noa brings depth in human dynamics to organisational work and facilitates the Team Dynamics workshops.

    Team Dynamics workshops

  • Noam Eshed Zvida

    People & HR Consultant

    Fifteen years in HR, working directly with leadership, managers and employees in changing organisations. Noam diagnoses the people and management picture, coaches managers through hard decisions and conversations, and acts as an external HR / People partner where a company has no HR function of its own.

    People & HR Advisory

Independent practitioners with practices of their own, whom Kendoo brings into an engagement when the work calls for their discipline.

What to expect

Working with Kendoo

If you are an executive

Direct answers, including about the things that are not going well.

A written monthly account you can check, rather than a verbal reassurance that everything is on track.

The trade-offs behind a recommendation, so the decision stays yours to make.

If you lead the engineering team

Someone who will look at the process and the system around the team, not only at the code.

Architectural disputes settled on evidence rather than seniority.

Someone who is not there to conclude that the team is the problem.

If you lead product, design or the people side

Work that treats brand, experience and team dynamics as their own disciplines, not as decoration on an engineering plan.

Sessions run with the group that actually has the problem, whatever function it sits in.

Both should expect the first month to be slower than they would like. Observation and baselining come before intervention, because acting in week one is how you fix the wrong thing confidently.

Company

Experience
Twenty-five years in software, eight of them consulting.
Registered
Kendoo Tech Consulting LTD, Israel. Offices in Haifa and Tel Aviv.
Professional history
On LinkedIn, linked in the footer.

Talk to the person who would do the work

Thirty minutes with Amir directly. There is no account manager in between.