Copilot vs Autopilot: Remember the Role of Cracking the Egg

When developing a product, startups that use AI must choose whether to go for a fully autonomous product, aka Autopilot, or an assistant that facilitates and accelerates current processes, known as Copilot.

Here are some definitions and tips that I hope will help you think and make product decisions:

Autopilot:

Trusting an autopilot means fully delegating responsibility, which requires absolute confidence in the technology. Beyond the fact that the technology is not mature enough, user trust and the technology adoption process are also not fully developed.

While technological development is not complete yet, we are very close to seeing this technology effectively in action. To prepare users for this moment, we can work on developing the necessary trust in them.

The Role of the Copilot:

The co-pilot, on the other hand, focuses on reducing time and delegating the final decision to the user. It simplifies tasks by gathering data, preparing responses, and proposing solutions, but always leaving the decision to proceed in the user's hands. This allows for edits, adding stakeholders, and maintaining control of the process, making us more professional, efficient, and productive. By giving control to the user, we are building trust and delegating the responsibility for each action to them.

The true customer here is the user (operator, sales rep, manager, etc.), not the company.

Our goal is to serve the user, improve their productivity, save time, and help them shine in front of their peers and superiors.

The Importance of Interface and Engagement:

Like the example of cake mixes that didn't sell well until the step of cracking an egg was added, a good copilot must allow for that interaction that generates ownership. Finding daily or frequent-use functions is key to generating loyalty and adoption, even if the primary use case is low frequency.

Tangible Value Creation:

Measuring and clearly communicating the value and results is essential. Providing metrics on interactions made and time saved, for example, helps the user perceive the value added.

Capturing the Created Value:

The biggest challenge is capturing the created value. Starting with a low price or a trial helps overcome initial barriers. Once implemented and fine-tuned, the benefits become evident. At this stage, proactivity and communication are crucial to reinforce the user's confidence and highlight their role in the process.

When the product becomes critical, the usage-based pricing model may increase the monthly cost. It's vital to clearly communicate the savings and perceived value to avoid cuts in service. Raising the price when the client depends on the product is a strategy, but reaching this point is complex and time-consuming. Improvements in this area directly impact the startup's bottom line.