The 0-to-1 Product Problem Founders Often Mistake for a Marketing Mishap

At an early-stage company, a product problem and a marketing problem can look remarkably similar. The technology works, but prospective users do not understand why it matters. The team responds with a sharper pitch, a longer demo, or another landing page, and the value still does not land.

Often, the problem isn’t that the market needs more convincing. The product itself hasn’t made the value clear enough yet. When users have to work out for themselves why a technical capability should matter to them, the product has handed off one of the founder’s most important jobs. Before a startup can persuade a market, its product should be legible on its own.

Vaishnavi Varma says her work as an artificial intelligence (AI) product designer focuses on this 0-to-1 interval, where early-stage founders have to turn technical ideas into products people can understand and use without stripping away their complexity. She says her approach brings together user journeys, visual craft, and security considerations, particularly as AI tools make it easier to build software quickly.

That combination matters more now because speed has changed what it means to have a product. A functioning prototype can arrive well before a coherent experience. The interface may exist before the team has settled what it should ask of a user and what it should explain along the way.

For Varma, design is where those decisions become visible to the user, which makes it part of the product from the start.

Why a working product can still confuse people

Varma’s approach is less about simplifying technology than making its complexity understandable. In written remarks, she said she has spent five years designing across cybersecurity, fintech, health tech, and consumer technology, and that her earlier work included working as an Application Control Specialist at Bank of America. Working in vulnerability management taught Varma how difficult it can be to turn invisible technical complexity into something a person can understand and act on. That lesson has carried into her work designing AI products.

The confusion problem is sharpest at the beginning of a company, when product assumptions are still hardening into systems. A founder may know every edge case and dependency because they have lived with the idea for months or years. A founder may know exactly why a feature exists, what data powers it and what should happen next. A new user sees only a button. What feels obvious inside the company can feel like unexplained labor outside it.

The 0-to-1 designer’s task is to decide what the user needs to understand now, what can wait, which actions should feel consequential and where trust could break. In an AI product, that often means showing what the system is doing and being clear about its limits, so that convenience never quietly overrides security or user control.

Varma describes the company goal in direct terms. For her, the goal isn’t simply to make technology easier to use. She wants to build “tech products that feel like art” where visual expression and interaction create an emotional connection alongside utility. She argues that authentic visual expression can create an emotional connection even when no person is present to guide the user.

Software communicates before anyone reads the onboarding copy. Rhythm, hierarchy, friction, feedback, and visual tone all tell users what kind of experience they have entered. Founders who treat those elements as finishing touches may be postponing part of the product strategy itself.

AI raises the stakes of the design decision

The spread of AI-assisted development has helped shorten the distance between an idea and a buildable interface. The harder problem is no longer always whether something can be built. It is deciding what should be built, what it should communicate, and what the user should be asked to trust.

Varma says part of her work with early-stage founders is helping them use AI tools while keeping design systems rooted in security and human judgment, a perspective she connects to her background in vulnerability management and data intelligence. In written remarks, she described her motto as “build technology to aid you, not replace you.”

That distinction has practical consequences. AI can generate components, flows and content, but the founder still has to decide what the product should optimize for. A tool can propose a user journey without knowing which moment calls for reassurance, and it can remove friction without knowing whether that friction was doing useful work.

Art and security sit far apart on most product roadmaps, yet both depend on paying attention to things a user cannot immediately see. Art concerns what the experience communicates beyond its utility. Security concerns what the experience permits beyond its intended path. Good 0-to-1 design weighs both before patterns become expensive to undo.

Varma says she often hand-designs and draws while working through UI and UX for founders. The principle behind the method is that the speed of the available tool should not dictate the depth of the thinking. A startup can use AI to accelerate execution without delegating its point of view.

Building her own case study with khaa-lo

khaa-lo has become a real-world test of this philosophy. As the founder of the platform, Varma is applying the same principles she uses with other early-stage companies to a product she has to understand from both sides: as a designer and as a founder. The company is aiming to expand from AI visibility tooling for emerging consumer brands into a platform intended to help brands understand consumer intent, search behavior and market trends while connecting shoppers with relevant emerging labels.

According to the company, its broader product vision is to help both consumers and brands understand what is actually being consumed.

Few founders will build an AI search platform, but any founder can use their own product as a proving ground for the principles they sell to others. In Varma’s case, khaa-lo asks whether a complicated information layer can become a warmer consumer experience without treating people as data points or independent brands as optimization targets.

The product also reflects how Varma approaches 0-to-1 design more broadly: product decisions are shaped by understanding what people actually need, not simply by what a company wants to communicate. Varma said in written remarks that she spent more than two years talking to consumers and founders of emerging CPG brands (via hosting events and networking) understanding the pain points on each side. Her thesis is that many tools begin with the brand’s desire to appear in an answer, while khaa-lo begins with what the consumer is actually asking.

Varma said khaa-lo recently moved its Discover feature ahead of the conventional homepage, so the first thing a visitor encounters is the search itself rather than an explanation of it. This interface change helped triple brand searches. The company further reported that users who had previously entered a single prompt and left now average three prompts per session, following up on their own results. Varma reads this as the product finally making its exchange clear without having to argue for it.

What founders should resolve before they scale

One of the most useful parts of Varma’s philosophy is her insistence that founders answer a few questions before growth makes the answers harder to change.

The first concerns comprehension. Not every technical fact belongs in the interface, but the central exchange should be unmistakable: what the user contributes, what the system does and what they get back. More acquisition on top of a confusing exchange usually produces more confusion.

The second concerns trust. AI products frequently handle decisions, recommendations or personal information in ways users cannot fully inspect. Product design should surface that uncertainty instead of hiding it behind fluency, so people know when to rely on the system, when to review it and what control they retain.

The third concerns feeling. A useful product can still feel generic and disposable. This is where Varma’s “feel like art” idea becomes commercially relevant, because a product that expresses a coherent point of view through the experience itself gives users something more specific to connect with than a feature list.

The last concerns provenance. Early software can accumulate accidental decisions quickly, and founders should be careful not to let an AI-generated default or a rushed workflow harden into the permanent logic of the company. Some early choices are strategic. Others are just artifacts of the tools that built the first version, and the team needs to know which is which.

The strongest 0-to-1 work can help make a company’s judgment easier to see. Users can feel what the product values, and the team has a clearer foundation for what to build next. For Varma, that is the point at which a prototype that demonstrates capability starts to become a product people can connect with.

Entrepreneur Media was not involved in the creation of this content.