Thank you for your inquiry, we will contact you as soon as possible.

Please wait. Your request is being processed.

Sorry! Check your network connection and try again.

Contact Us

Discovery Phase

Define the product-market fit and accelerate product launch time and budget with Kindgeek's expert discovery approach. It has been proven: mitigating risks in the early stages of development pays off in the long haul.

Get in touch

Looking to launch a new business vertical or product or want to iterate your custom fintech solution?

The Discovery Phase is the first step before the first line of code is written. It helps you to find the most efficient and cost-effective solution to your business needs and to come up with the full system design architecture, interfaces, and data to meet specific requirements.

Here’s what it’s about:

Reduce uncertainty

Analyze your ideas and vision beforehand and get confident regarding scope, timelines, team composition, and functionality to a level enough to begin implementation.

Optimise development timeline

Start seamlessly, move confidently, and optimize the implementation scope and roadmap matched to the budget.

Do competitors benchmarking

Identify opportunities for differentiation, understand market trends, refine your product strategy and perform end-user needs assessment.

Select tools & technologies

Ensure to launch with the right technology and tools, and maximize the potential of getting off to a flying start.

Assess 3-party solutions

Choose the most suitable third-party solutions to align with your requirements, saving time and resources in development.

Accomplish gap analysis

Identify and assess gaps between the current state of a product or project and its target state.

Stay in line with compliance and regulations

We’ve worked with fintech & financial enterprises from all over the world – diving deep into legacy systems and regulatory compliance doesn't challenge us.

Optimise development budget

It's an upfront investment that will lead to significant savings by mitigating scope creep risks in the early stages of development.

Build trust with your IT vendor

By regularly communicating and engaging in in-depth discussions with the team, you can ease your mind and establish a two-way trust for further development.

Who is a discovery phase for?

For those who look to form and validate product vision.

For those pursuing guidance on creating a seamless user experience.

For those who need to elaborate NFR in detail.

For those needing advice on selecting third-party partners for their fintech product

For those wanting to set up a development plan with clear requirements and development tasks.

For those looking to reduce financial loss by covering the current user flows.

We offer

Product Audit

For businesses willing to do a comprehensive assessment of the building blocks of existing product. Product Audit seeks to enhance the product with deep tech expertise. It includes third-party benchmarking, feature analysis, and comparisons to identify improvement areas. The package provides actionable insights and a cost-benefit analysis for selecting third parties while optimizing the product's performance, user experience, and business value.

Product Discovery

For businesses willing to refine a product idea to make informed decisions about further development. Product Discovery aims to test the business idea's problem-solution and product-market fit. The Product Discovery model includes ideation, prototyping, and testing to ensure the product is actually solving the existing problem and meets the business objectives. Product discovery includes creating effective development strategies, designing a well-thought-out product architecture, and optimizing resources for maximum efficiency within specific timeframes.

Our product discovery & design foundation approach

Approach scheme

Discovery Phase flow

Discovery phase tiger team composition

During the discovery phase, team composition is crucial for a successful outcome. The team collaborates closely with the Product Owner or visioner, ensuring alignment with the overall product vision and goals. Depending on the specific requirements of the project, the discovery phase team can be extended to include additional experts such as DevOps specialists, Mobile leads, or other domain-specific professionals.

Around 3-4 weeks

Role Resposibility
Product owner Business advocate
Project manager Process advocate
Business analyst Product advocate
UX User advocate
Architect Technology advocate

You will receive

During the discovery stage, the business analyst takes the lead, supported by team leads, software developers, and the tiger team who assist with the clearly prioritized scope on the level of detailing enough to provide an estimate and implementation roadmap.

The outputs produced during the discovery phase are crucial considering the time and budget invested.

Once this stage is complete, you will receive:

Ui proto

Click-through UI prototype

Dev ready kit

Development-ready mockups and UI kit

Arch vision

Architecture vision


Technology, tools & frameworks

3rd party

3-party solution assessment


Infrastructure vision


Implementation efforts estimate

Team composition

Development team composition


Implementation budget and roadmap

Ensure your product achieves market fit and acquire a specific strategy for developing fintech solutions that meet your customer's needs.

Contact us for the next steps

Selected clients

Frequently asked questions

What is your approach to the product discovery phase? How do you ensure a comprehensive understanding of our business goals and requirements?

At Kindgeek, our product discovery phase is divided into two stages. In the problem identification stage, we focus on understanding your business pains, stakeholder and user needs, and product expectations to elicitate requirements. In the problem-solving stage, we delve into architecture design, and create user flows and UI/UX designs that align with your goals. We utilize high-fidelity prototypes to provide a realistic solution representation, allowing for valuable feedback and validation.

What methodologies, techniques, and tools do you use during the product discovery phase? How do you ensure effective communication and collaboration between your team and ours?

At Kindgeek, we leverage the combined power of Customer-centric design and the Lean Startup methodology throughout the product discovery phase. This helps us define clear problem statements and identify the right questions to ask. We embrace the Lean Startup approach in the solution phase to test and iterate potential solutions rapidly. 


To gather insights, we employ the following techniques:


Analysis techniques:

  • Competitive benchmarking

  • Process analysis

  • Root cause analysis

Visualization techniques:

  • Mind mapping

  • Sequence diagrams

Requirements techniques:

  • Functional decomposition

  • Non-Functional Requirements (NFR) analysis

  • User story workshops

Design techniques:

  • Prototyping

Management techniques:

  • Backlog management


Effective communication and collaboration are vital to our process. We maintain regular meetings, progress updates, and interactive sessions to align priorities. Leveraging project management software, issue-tracking systems, and collaborative document sharing, we ensure seamless coordination and transparency.

How do you determine the scope and duration of the product discovery phase? What factors and methodologies do you use to estimate timelines and resources required?

Agile approach: We follow an agile approach to project management, which involves breaking the work into smaller, manageable iterations called sprints. During weekly sprint planning, we collaborate with you to prioritize goals and deliverables based on their highest priority and value.


Iterative planning: By focusing on delivering tangible outcomes at the end of each sprint, we use these results as a starting point for planning subsequent sprints. This iterative process allows us to adapt and refine the scope and duration of the product discovery phase based on evolving priorities and requirements.


Resource allocation: We carefully assess the resources required for each sprint, including the expertise, skills, and capacity needed to meet the defined goals. Our team works collaboratively to allocate the necessary resources to ensure efficient execution and timely completion of the product discovery phase.


By adopting weekly sprint planning and focusing on delivering high-priority deliverables, we ensure that the product discovery phase progresses in a structured and goal-oriented manner. This iterative approach allows us to adjust the scope and duration based on evolving needs and priorities, ensuring optimal resource utilization and timely completion of the discovery phase.

How do you involve stakeholders and end-users during the product discovery phase? What methods do you use to gather their feedback and insights?

We actively involve stakeholders and, if needed, end-users during the product discovery phase. We conduct stakeholder workshops, interviews, and requirements elicitation sessions to gather their feedback and insights. We also employ various end-user research methods, such as in-depth interviews and analysis, to gain insights into their preferences, pain points, and behaviors. Additionally, we conduct design testing to gather prototype feedback and ensure a user-centric approach.

What deliverables can we expect at the end of the product discovery phase? What level of detail and documentation will be provided to guide the subsequent implementation phase?

At the end of the product discovery phase, you can expect several important deliverables that guide the subsequent implementation phase. These deliverables will vary based on the project scope and requirements but typically include the following:

  • Click-through UI prototype

  • Development-ready mockups and UI kit

  • Architecture vision

  • Technology, frameworks  & tools

  • 3-party solution assessment

  • Infrastructure vision 

  • Implementation efforts estimate

  • Development team composition

  • Implementation budget

  • Implementation roadmap

Our iterative approach and weekly sprint planning allow us to adapt the scope based on your evolving requirements and budget constraints, remove low-priority deliverables, and ensure effective budget utilization.

How do you handle potential risks and challenges during the product discovery phase?

At Kindgeek, we proactively handle potential risks and challenges that may arise during the product discovery phase. Here's an overview of our approach:


  • Risk Identification and Assessment: Our project manager creates a risk register, systematically identifying and assessing potential risks and challenges that could impact the project. This includes considering technological uncertainties, resource constraints, and changing requirements.


  • Risk Management Strategies: Once risks are identified, we develop appropriate risk management strategies. This involves defining mitigation plans, contingency measures, and alternative approaches to address potential issues. We prioritize risks based on their potential impact and likelihood of occurrence.


  • Communication and Collaboration: We maintain open and transparent communication with our clients throughout the discovery phase. We involve you, as the client, in the risk management process, seeking your input and suggestions for mitigation strategies. We ensure that you have the authority to approve and implement any necessary risk mitigation actions.


  • Risk Response and Monitoring: If a risk event occurs, we promptly communicate it to you, providing all relevant details. We discuss the potential impact on timelines, scope, vision, and deliverables. We collaborate to adjust plans and mitigate the risk effectively.


  • Out-of-Scope Management: We work closely with you to clearly define the project's boundaries and establish what is within the scope of the product discovery phase. If any requirements or features fall outside this defined scope, we identify them as out-of-scope items. 


Our goal is to ensure that any potential risks are addressed promptly and efficiently, enabling the smooth progression of the project and the achievement of your business goals.

How do you ensure the product discovery phase aligns with our budgetary constraints? Are there any additional costs we should know beyond the implementation phase?

We are committed to maintaining transparency and open communication regarding budget control and any potential additional costs. Here's how we ensure budget control and address any additional costs:


  • Budget Burndown: We closely monitor and track the budget throughout the product discovery phase. By regularly reviewing the actual expenditure against the planned budget, we maintain transparency and provide visibility into how the budget is being utilized. This helps us identify any deviations and take corrective actions, if necessary, to stay within the agreed budget.


  • Monthly Budget Predictions: We provide monthly budget predictions outlining the expected expenses for each phase of the product discovery process. This lets you understand the projected costs and make informed decisions based on your budget constraints.


Following the Scrum methodology ensures you receive actionable deliverables regardless of your budget after each sprint. Our iterative approach allows us to provide value consistently throughout the product discovery phase.


Regarding additional costs, we may request a license or other resources if your project scope includes third-party testing and investigation. Any such potential costs will be communicated to you in advance. We will provide detailed information about the nature of these costs, allowing you to decide whether to proceed with them or explore alternative solutions.

What are your criteria for transitioning from the product discovery phase to the implementation phase?

Our criteria for transitioning from the product discovery phase to the implementation phase are as follows:


  • High-Level Vision, Design, and MVP Scope: We consider completing the high-level vision, design, and solutions for the Minimum Viable Product (MVP) scope an essential criterion for transitioning. This ensures a clear direction and understanding of the product's goals and features.


  • Detailed Vision for Future Sprints: We require a clear vision for the upcoming sprints, including specific features, functionalities, and priorities to be implemented. This enables a smooth progression and incremental development of the product.


To ensure a seamless transition and continuity, we follow these practices:


  • Gradual Onboarding: If additional team members are required for the implementation phase, we gradually onboard them. This approach allows for effective knowledge transfer and ensures the new team members are familiar with the project and its objectives.


  • Option for Internal Team: If you prefer to proceed with your internal team for the implementation, we provide all the actionable deliverables from each sprint. These deliverables guide your team, outlining the user stories, feature specifications, and other necessary documentation.


By meeting these criteria and facilitating a smooth transition, we aim to ensure that the product discovery phase seamlessly integrates with the implementation phase. This approach promotes effective collaboration, knowledge transfer, and successful execution of your project.