Discovery & Consulting
Analysis of your needs and a clear product strategy
What it is
A short, focused engagement that turns a vague idea or a stalled project into something you can actually cost and schedule. We run workshops with your stakeholders, map users and constraints, and pressure-test the assumptions the plan rests on. You leave with a written scope, a prioritised roadmap, and an estimate, documents you own outright. Whether we build it is a separate conversation, and a genuinely open one.
How it works
Align
A kickoff workshop to surface goals, users, constraints, and success measures.
Investigate
We review existing systems, data, and research; we interview the people who will use it.
Shape
Scope, architecture options, and risks written down, with the trade-offs made explicit.
Hand over
A roadmap and estimate you own. Take it to us, to your team, or to another vendor.
When to choose it
- /The idea is real but the scope is not yet clear
- /Stakeholders disagree on what is being built
- /A previous attempt stalled and you need a diagnosis
- /You need a defensible number for a budget conversation
What you get
- /A written scope and prioritised roadmap
- /An estimate with the assumptions shown
- /Architecture options and a risk register
- /Full ownership of every deliverable
- /A recommendation on which model fits next
This is usually the first step, not the whole journey.
Most discovery engagements end with a recommendation for one of the other models, commonly Fixed Scope & Price once the scope is nailed down, or Dedicated Agile Teams if the roadmap will keep evolving. You are under no obligation to take it.
Common questions
What is included in a discovery and consulting engagement?+
We typically run stakeholder workshops, review existing systems and constraints, map users and requirements, assess technical options, identify risks, and shape the scope into something that can be estimated and scheduled.
How long does discovery usually take?+
Most discovery engagements take around two to four weeks, depending on the complexity of the product, number of stakeholders, and how much existing material needs to be reviewed.
What do we receive at the end?+
You receive a written scope, prioritised roadmap, estimate with assumptions, architecture options, and identified risks. All deliverables belong to you.
Do we have to continue development with higroup afterwards?+
No. There is no lock-in. You can continue with us, take the deliverables to your internal team, or use them with another development partner.
When should we choose discovery instead of going straight into development?+
Discovery is the better starting point when the idea is clear but the scope is not, stakeholders are not aligned, technical risks are still unknown, or you need a defensible budget before committing to a build.
What usually happens after discovery?+
We recommend the cooperation model that best fits what we learned. A settled scope often moves into Fixed Scope & Price, while an evolving roadmap is usually better suited to a Dedicated Agile Team.