Purpose of Discovery phase
The first step is a domain workshop, where the Client describes his needs, pains, and existing status quo by sharing how he achieves goals today.
The second step is to list and validate possible technical, legal, and business model related show-stoppers by making a set of experimental proofs-of-concept.
List all dependencies
Research on listed and prioritized vendors and dependencies of a product allows to provide a precise project estimate instead of abstract placeholders.
Once the technical set of tools is clear, it is possible to make calculations for different system workloads - downtime, minimum profitable, target, and exponential growth.
Discovery phase artefacts for different project size
Feature Breakdown list
Software architecture document (SAD)
User Journey Map
Software requirements specification (SRS)
Project Goals and Scope
Feature Breakdown list
User Journey Map
List of User stories
Statement of Work
Risks Register and Mitigation Plan
Quality attribute scenarios
6 cases for whom the Discovery phase is obligatory
We work hard every day to help our Client's Products success
Non-technical entrepreneurs who plan to outsource all the tech tasks
For founders who are new to the business domain
For existing software updates with complex interdependencies and multiple vendor changes
For those who introduce a new business model or service to a market
For entrepreneurs who have too many ideas or prioritization issues
For any fixed-price project with a budget of more than 50 000 USD
How do we engage with Clients during Discovery phase
Internal Kick-off meetings, team composition or hiring activities, reading 5 times for each document provided by a Client, setting up a place in infrastructure, and a lot of silent work by a Project Manager. At this stage, a Client just provides the documentation and contacts of project stakeholders.
Interviews, workshops and brainstorms with Business analyst
We appreciate when Client's team members are engaged in conversations and openly share the business context. Be ready to spend 5-8 hours on calls with us weekly.
Experiments with focus groups
When a Proof of Concept is ready - it's time to model an experiment on a focus group. Here we have a set of tools from Product management to facilitate and receive valid data sets and decrease UX uncertainty.
Interdependencies check between Tech, Marketing and Management teams
Before we proceed to the execution, we collide all groups of interest within the project to make a last check of business logic and exclude future frustration. Once everybody agrees on a sense level, we document and visualize the system.
Core Discovery phase team
Optional Discovery phase team
Got more specific questions and ready to talk?
A clear representation of business data and smooth interactions with customers, working with analytics regardless of the screen size or browser used.
Websites, Admin dashboards and PWA
Our Clients testimonials
The app met the expectations of the internal team, increasing customer loyalty and attracting new customers. RedCat establishes a smooth workflow through effective communication. The team is professional, hard-working, and easy to work with. For sure I would strongly recommend them
CTO at BioNexus
The company appreciates the RedCat team’s transparency and predictability level. The team is good at providing explanations for each of the decisions they propose to the company. Our partnership is 100% business-concentrated. Each thought and word is aimed at finding a wise and sagacious solution.
CEO at Excedo Ventures
RedCat’s efforts were met with positive acclaim by internal and external stakeholders. Their work has attracted new customers and met all their clients’ expectations. Helpful and coordinated, customers can expect an efficient team that delivers quality work at a reasonable price point
Founder of Renthopper
Thanks to RedCat’s contributions, the client was able to execute a successful provider transition 500% faster than the average speed. The team showcased their diligence in all engineering projects and adapted seamlessly to the client’s internal project management. They were great to work with.
CEO at Raxel Telematics
Questions You may have
The overall idea of this phase is to reveal and fill in the critical gaps before investing in the most costly part, e.g., development. The more clarity, documents, design, etc the Client has in the beginning – the less work needs to be done during the discovery phase. But the official position of RedCat for a fixed price, sometimes dedicated team contracts, and projects delivered by milestone is the same: without a critical obligatory minimum of documentation, development start is senseless. A predictable budget is possible only if you have etalon documentation to refer to.