I'm afraid of spending months and budget on something nobody wants
Before any development we build a clickable prototype (a mockup that behaves like the real app) and test it with 5–6 people from your target audience.
Test your idea with real users before you pay for development
We review your product idea, build a clickable prototype and test scenarios with people from the intended audience. You receive observations, open questions and a proposed first development scope. Research format and schedule are agreed after your brief.
Quote and schedule after your brief
Who it's for
- Founders with a product or app idea and no code yet
- Business owners moving a manual process into a web service or client portal
- Teams that disagree on priorities and lack data
- Startups that need a prototype for an investor or a first pilot
Problems we solve
Everyone on the team pictures a different product
In the first workshop we agree on the goal, users and main scenario. It all goes into one document you can hand to developers.
I don't know which features belong in version one
We rank ideas by value and effort and define a minimum viable product (MVP). Everything else goes on a later list.
I can't tell what development will cost
After testing we give you a list of screens and features. A development estimate is built from it, as a range rather than a guess.
What's included
- Workshop on goals, audience and project risks
- Review of 3–5 competitors or analogues: what works, what frustrates
- 5–6 user interviews or test conversations
- User journey map (the steps from need to outcome)
- Wireframes of the main scenarios
- Clickable prototype in Figma
- Usability test with 5 people, recorded, with findings
- Prioritised MVP feature list
- Report: what held up, what didn't, what to change
- Rough development estimate based on sprint results
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Express
A simple idea with one core scenario
- Workshop and competitor review
- Wireframes for one scenario
- Clickable Figma prototype
- Test with 3–4 people
02
Standard
A service or portal with several roles and scenarios
- Workshop, competitor review, journey map
- 5–6 user interviews
- Prototype of the main scenarios
- Test with 5 people and a report
- MVP feature list
03
Discovery + design
A complex product that needs ready-to-build design after the sprint
- Everything in Standard
- Two rounds of testing
- Visual design of key screens
- Basic design system in Figma
- Handoff to developers
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Workshop
Together we define the goal, users, risks and key hypotheses. We agree on what we are testing and what result counts as a pass.
Prototype
We draw wireframes and build a clickable Figma prototype. AI tools speed up the drafts; designers make the decisions.
User testing
We show the prototype to 5–6 people from your audience, record the sessions and look for where they get stuck.
Report and decision
You receive the report, the designs and a development estimate. All files and access are yours under the agreed terms.
Scope and limits
- We don't promise the idea will be confirmed: sometimes a sprint shows it's better not to build it, and that is a valid result
- We don't promise statistical certainty: 5–6 tests reveal problems but don't replace large-scale research
- We don't find test participants without your help: we usually use your customer contacts, and recruiting from scratch costs extra
FAQ
How is a design sprint different from regular design?
Regular design draws what has already been decided. A sprint first checks whether the decision is right. You pay for an answer and a plan, not a finished interface.
What do I need to prepare?
A description of your idea, even one page, and access to 5–6 people from your target audience. We also need a decision-maker who can join the workshop.
Can I do this with a prototype only, no code?
Yes, that is the point. A Figma prototype looks and clicks like an app but has no complex logic behind it. You can show it to users and investors.
What happens after the sprint?
You can hand the designs to any development team, including ours. We can also propose a pilot with a measurable KPI to test the idea in a real launch.
How does payment work?
Payment terms are agreed with the quote before work starts. For a staged project, we describe the result and acceptance criteria for each stage. Support and third-party services are listed separately.
Who owns the materials?
We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.