To those who found Eyes. Why we built this tool.

This page is written for those who found Eyes through Product Hunt and other channels. I'm Ryohei Kameyama, representative of covelline, LLC.

Hello, I'm Kameyama, the creator of Eyes

Thank you for taking interest in Eyes.

Our landing page and press releases are packed with "service correctness," but on this page, I'd like to write more casually about what I'm thinking as I build Eyes. Rather than listing features in bullet points, I hope you'll read this as a story.

From feather to Eyes

I've been developing continuously with a classmate from Oyama National College of Technology, where we spent 5 years in the same classroom. One of our flagship creations was the Twitter client app "feather for Twitter".

feather was an app that allowed quite free customization of timeline layouts. You could finely adjust button positions and displayed information, creating a sense of growing your own "personal Twitter client." What we valued most there was "being able to use it without stress." We kept thinking about how to reduce unnecessary friction and create a state where you could focus only on what you wanted to do.

The gap between "what we want to do" and "what we end up doing"

Through developing feather, I became deeply interested in this theme: "How can we reduce the gap between what users want to do and what they actually end up doing?"

For example, when using analytics tools, what you really want to know might be "What should I do to increase conversions?" But what you actually end up doing is "staring at numbers in dashboards," "making graphs in Excel," "trying to find patterns..." and before you know it, hours have passed without getting any actionable insights.

This gap exists everywhere. We want to "understand our users," but we end up "drowning in data." We want to "make improvements," but we end up "endlessly analyzing."

Eyes: A tool to eliminate this gap

Eyes was born from the desire to eliminate this gap.

Instead of showing you more data, Eyes directly tells you "what you should do." Instead of making you think about what the numbers mean, it presents concrete action plans.

For instance, if there's an issue with your signup form, instead of just showing "conversion rate has dropped," Eyes says "Reduce the 12 required fields" or "Try implementing social login."

We're not trying to make "yet another analytics tool." We're trying to make "a tool that eliminates the gap between analysis and action."

What we're aiming for

Our goal is to create a world where "anyone can make their website better."

Currently, improving websites requires specialized knowledge, time, and experience. You need to understand analytics tools, know how to interpret data, and figure out what actions to take. This is too difficult for most people.

But it doesn't have to be this way. AI can handle the complex parts. What humans should focus on is understanding their users and making decisions.

Eyes handles the "analysis and insight generation" part, while humans focus on the "decision-making and implementation" part. This division of roles allows for much better results than either could achieve alone.

Our commitment

We will never stop asking ourselves: "Is this really making users' work easier?"

Features that look cool but don't solve real problems, interfaces that seem sophisticated but are hard to understand, data that appears useful but doesn't lead to action—we won't build any of these.

Instead, we'll continue building a tool that truly makes your work easier, just as we did with feather.

A word about pricing

Our pricing structure is designed around "try it free first," as detailed on our landing page.

Our free plan is sufficient for trying out the main features with one site. If you think "this fits our team's workflow," then you can consider upgrading to a paid plan that includes unlimited chat analysis, shared links, and automatic report delivery.

For detailed pricing and plan information, please see:

Learn more about Eyes

If you'd like to try it right away, you can sign up directly here:

What I personally want to achieve with Eyes

Beyond the product goals, I have my own small ambitions as CEO/Product Manager.

One is to help more "people who aren't good with analysis but want to grow their business" become friends with data. Instead of only data-savvy people having the right tools, I want to give proper tools to those who aren't naturally inclined toward numbers.

Another is to reduce the gap between "people who read numbers" and "people who actually take action." When report writers and the people who run ads or create content are separate, communication costs inevitably arise. Eyes wants to be a bridge between them.

We want to enable small teams to properly run hypothesis-testing cycles. To achieve this, we want our tool to handle the necessary "groundwork" and "ease of sharing."

Final thoughts

By reading this far, you're likely either in a position where you look at numbers, or you're in a position where you're overwhelmed by numbers. Regardless of which position you're in, I'd be happy if Eyes could help you "decide on your next move."

Please give it a try. If there's anything that doesn't feel right, please let us know why—it would be very helpful. Both as a product and as a team, we're still very much in the growth phase.

Try Eyes for free

Ryohei Kameyama
CEO, covelline, LLC.