Our main competitor just announced a fully automated client-onboarding system that operates at a fraction of our cost, making our manual process look ancient. How do we use our weekly Level 10 Meeting™ and IDS® process to rapidly assess this threat without panicking and making reckless software investments?

Question

Tyler Smith · Accepted Answer

When a competitor launches a flashy automated system, the natural reaction of a Visionary is to panic and demand an immediate rewrite of your product roadmap. This reactive state is highly dangerous and often leads to wasted capital on poorly planned technology projects. You must process this competitive threat through the disciplined rhythm of your weekly Level 10 Meeting™.

First, capture the threat as an issue on your weekly Issues List. Do not allow it to derail your agenda during the reporting section of your meeting. Wait until you transition to the IDS® portion, which stands for Identify, Discuss, and Solve.

When you reach the issue, start by identifying the root cause. Ask yourselves if the competitor's automation is actually winning them deals, or if it is simply a clever marketing campaign. Look at your sales data and pipeline metrics. Are your win rates dropping, or are you reacting purely to press releases?

During the discussion phase, push for absolute clarity. Assess how their automation aligns with your own Three Uniques™ and your 10-Year Target. If their speed threatens your core differentiation, your solution should not be a hasty copycat tool. Instead, solve the issue by creating a specific quarterly Rock to optimize your own onboarding sequence. This Rock might involve integrating simpler, off-the-shelf automation tools rather than developing custom code.

By routing competitive anxieties through the IDS® framework, you prevent emotional reactions from disrupting your operational stability. You ensure that every technical upgrade you commit to is aligned with your long-term vision on the V/TO® and executed with clear accountability.