Hypothesis & Features

This part of the process is the foundation that lays the groundwork for everything that follows. A startup idea is a hypothesis, our goal is to help you validate it. In this part of the process, you'll work with our team to refine your idea and match it to the right market opportunity. We'll do that by looking at potential solutions, competitors, and your business goals.

What problem are you solving and how?

By clearly articulating the idea and the potential solution we understand better what you're trying to build. Then we think about how can we apply technology to solve this problem and what type of solution should we implement.

Is someone already doing it?

According to Peter Theil (founder of PayPal) -Competition is for losers. By looking at other competitors on the market, we can narrow down the scope of your digital product and find its niche. Looking at the competitors provides insights into their business model, solutions, and the pain points of the users.

Who will be using it?

User personasare the foundation on top of which you build software products. Before thinking about the details of the product, you need to determine who your target audience is, and who are you building a product for. Remember, if you're building a product for everyone, you're not building it for anyone.

What is your business model?

The goal of every startup and business is to make money. Considering user personas and the hypothesis we examine different revenue sources. Afterward, we decide together which one best fits your product and goals.

What is the easiest way to test the hypothesis?

In this stage, we identify the minimum viable feature set for testing the hypothesis. This will help you get feedback on the right and truly important things. Founders usually focus too much on nice-to-have features and lose focus on finding the product fit.

How can we improve the user's experience even more?

It's not enough to solve a problem, most of the time, it has to be done in a way that is attractive and enjoyable to the user. By identifying things that would make the experience better, we can create products that solve problems and delight the users.

Feasibility & Tech

Not all problems have a solution. Our technical team will assess the feasibility (security, performance, regulations) of the hypothesis. Different technological approaches and alternatives are being analyzed and estimated.

On top of that, an architectural diagram of the system is being built for a visual overview of the solution. This will help you understand different technological approaches and their advantages and disadvantages.

Are all the features feasible?

Not everything is technologically feasible. When building a digital product, there are a lot of constraints (technology, legal, etc). Our experts, we'll analyze all the potential problems and highlight ways to overcome them. Sometimes that means taking a new approach from a feature set perspective.

How can we implement it, what are the alternatives?

If the feature set is feasible, you need to decide what technologies to use to implement this. Our team will explain all the alternatives and possibilities. This will help you make an informed decision on what's best for your product and roadmap.

How much is going to cost and how long it will take to build it?

That's one of the primary questions asked by both founders and investors. For every approach, our team will give you a detailed breakdown of the time (and cost) needed to implement each feature. This will help you refine even more the feature set and give you a real quote on what would it take to build your MVP.

What would make the product better technology-wise?

Sometimes as a founder, you're not aware of the latest technology features and trends. Our team will brainstorm ideas and try to find new technologies that could improve your product (3rd party services, new cutting edge SDKs, AI, ML).

What's the cheapest and fastest way we can build this?

Our goal is to help you test your hypothesis with the least resources. Sometimes, a simpler and cheaper approach can give you the same insights as an over-featured product. With the hypothesis in mind, we will assess the feature set, reduce it and find cheaper alternatives for implementing it.

User Experience

In this section, we're going to express the agreed feature set in a cohesive narrative that is easy for the customer to follow and understand. After the narrative is set, we'll build the user experience, branding guidelines, and user interface.

Collecting feedback as early as possible is mandatory. The simplest and most powerful way for collecting it is through clickable prototypes. They visually express your hypothesis and are a great tool for getting feedback or communicating your idea to investors or users.

What is the narrative we tell?

As humans, we are attracted to good stories, those that follow a well-defined narrative and structure. Building the correct chronology will help us create user experiences that delight the users. This will also help us reveal obvious problems within that specific experience.

How is the user going to complete the tasks?

By combining the user personas with the feature set and the narrative we'll define all the user journeys in your product. Journey maps help us to find gaps in customer experiences and explore potential solutions.

What makes a great user experience for your product?

Based on the user journeys, we'll define and agree on the components and the information that will be presented to the users of your product. This will help us structure the information architecture and build the wireframes.

What's important for the visual identity of your brand?

In this part of the process, we'll determine the aesthetic of the product. Starting by selecting colors, typography, and interactions and aligning those with the vision of the product and its brand.