Discovery Phase
Many companies are eager to launch their new software without delay to see results faster however 90% of startup companies fail because of a lack of market need, so if we go to work without a discovery step, we are doing our customers a disservice.
It helps us shape the product’s vision, unite all the participants around a common idea, plan the project budget more accurately, etc.
Clients can skip the product discovery process and move to the project realization only if they are confident in their idea and set clear data-driven requirements. Otherwise, they risk investing money into a product that nobody needs.
Discovery phase benefits
- Reduces risks
- Ensures your product will fit the market
- Gives understanding of product value
- Sets roadmap (clearly defined milestones, deliverables, and deadlines)
- Increases chances to attract investors
- Minimizes costs
Discovery pricing
Basic
from $3600
This is a preliminary phase where the team will gather information about the project requirements, constraints, and stakeholders. It typically involves conducting stakeholder interviews, reviewing project documentation, and creating a high-level project plan. This phase typically takes 40-80 hours, depending on the complexity of the project.
- Collecting of business requirements
- Analyzing technical stack
- Possible options for implementation
- Project roadmap
- Technical analisys
- User flows
In-Depth
from $7000
This phase is a more comprehensive analysis of the project requirements and constraints, including technical and functional analysis, process mapping, and detailed planning. This phase usually takes 80-160 hours, depending on the size and complexity of the project.
Basic - Design wireframes
- Technical documentation
- Product development consultation
- Rough estimate
Extended
from $15000
This is a comprehensive analysis of the project, including the development of prototypes, user testing, and a thorough review of all project requirements and constraints. This phase typically takes 160-300 hours, depending on the size and complexity of the project.
In-Depth - Detailed estimate
- Visual consept (UI kit, logo, colours, styles, fonts)
- Design mockup 2-3 pages
- Acceptance criteria
- Market research
1 plan. Marketing research & structure plan/project strategy
*Startup full discovery bridge the gap between a business idea and
a targeted IT solution
- Investigating technical specification
- Defining killer feature
- Architecture and technical requirements (technologies and server environment recommendation)
- Scope decomposition into the small tasks and estimation with priority
- Defining timelines (will be presented as planed iterations)
- Presentation with all scope
- Creating User Flow (3-4 main user flows)
- Creating User description flow (3-4 schemas of relations between pages/screens)
- Creating 2 mockups (designed) or 5-6 wireframes (monochrome)
*This type of discovery is relevant at the stage of idea, where we are responsible for deep analysis, making a discovery, giving recommendations, looking for approaches. answers the question: Do people want your solution?
2 plan. Project plan + mockups
*Startup full discovery bridge the gap between a business idea and
a targeted IT solution
- Defining killer feature
- Architecture and technical requirements (technologies and server environment recommendation)
- Scope decomposition into the small tasks and estimation with priority
- Defining timelines (will be presented as planed iterations)
- Presentation with all scope
- Creating User Flow (3-4 main user flows)
- Creating User description flow (3-4 schemas of relations between pages/screens)
- Creating 2 mockups (designed) or 5-6 wireframes (monochrome)
*This type of discovery is relevant at the stage of idea, where we are responsible for deep analysis, making a discovery, giving recommendations, looking for approaches. answers the question: Do people want your solution?
3 plan. Mockups + Project plan + Technical Documentation
*Discovery Phase. The main goal of the Discovery Phase is to define an optimal system with its architecture and UX design which will satisfy stakeholders’ requirements, and to estimate accurately costs for Project development.
- Collecting of business requirements
- Analyzing technical stack
- Possible options for implementation
- Detailed estimate
- Design mockup
- User flows
- Communication and discussions
- Acceptance criteria
- Delivery plan
- Industry standards set up
*This type of discovery is relevant at the stage of idea, where we are responsible for deep analysis, making a discovery, giving recommendations, looking for approaches. answers the question: Do people want your solution?
to find a perfect solution
Before rushing into the product, we should know
what client pains they want to satisfy and how.