The idea means different things to different people
Founders, sales and operations each picture a different product. We get those versions into one flow before anyone writes a backlog.
Explore
Consultancy · Discovery workshop
Discovery that ends in a working prototype, not a PDF
Our business analysts run discovery together with product designers from Widelab, our design brand, and the engineers who will build the product. We work through your users, workflows and data with the people who decide, in clear stages. AI helps at every step, and people make every call. You leave with a clickable prototype built in real code, plus requirements, decisions and user flows that stay your living project docs. When you build, that prototype becomes your production frontend.
- 130+People, remote across Poland
- 12 questionsIn our public AI readiness scorecard
- 5.0Clutch rating, 11 reviews
This is for you if you need a shared picture of the product
You want to see it before you fund it
A slide deck won't tell you if the flow works. A clickable prototype your users can try will. And if buying a ready tool makes more sense, we say so.
You don't want to pay for discovery twice
Workshop notes that end up in a drawer get redone later. Here the requirements, flows and prototype carry straight into the build.
You need a price with the assumptions written down
A price range with every assumption spelled out, so the budget talk is about choices, not guesses.
What you get. Docs and code your team keeps using
A clickable prototype in real code
Built by our designers and engineers in React and Next.js, sometimes started in Lovable. It isn't a throwaway mockup. It grows into your production frontend.
User flows and UX from Widelab
Widelab is our product design brand, same company. Its designers map how each role moves through the product and shape the screens your users test.
Requirements that stay current
Users, roles, data and business rules written as living project docs in Notion or Confluence. They get updated as the build moves, so they never go stale in a PDF.
A decision log
What was decided, why, and who decided it. Six months in, nobody has to guess why a flow works the way it does.
A prioritized backlog
What goes into the first version and what waits, already in Linear or Jira and ready for a team to pick up.
Risks, a price range and a straight answer
Build, buy or wait. The risks and dependencies we found, and an indicative budget with the scope assumptions behind it.
Tech stack. From whiteboard to working frontend
Analysts, designers and engineers work in the same tools, so what comes out of discovery goes into the build without being rewritten.
Tech stack
- Figma
- Lovable
- Claude
- Claude Code
- v0
- FigJam
- Miro
- React
- Next.js
- TypeScript
- Tailwind CSS
- Storybook
- Supabase
- Notion
- Confluence
- Linear
- Jira
- Google Meet
- Fireflies
How we work
Five stages, with your decision-makers in each one
Business analysts lead discovery, with Widelab designers and our engineers in the room from day one. AI does a lot of the work between sessions: it transcribes, drafts flows and requirements, and spins up first screens. People review every output and make every decision. A dedicated business analyst is the reason this works: on a US campaign-finance platform, the team says the MVP would not have shipped on time without one.
When you propose something to them, they don't simply say yes. They come back with a pro and con.
How it works. From competing ideas to a working frontend
Gather what already exists
Sketches, research, the spreadsheet the process runs on today. AI sorts and summarizes it, and the business analyst turns it into the questions the workshop has to answer.
Map users, roles and workflows
Who logs in as which role, what they need to get done, which data moves where and what must not change. Sessions are recorded and transcribed, so nothing said in the room gets lost.
Design the flows and screens
Widelab designers turn the workflows into user flows and UX in Figma. AI drafts options fast. Designers choose, fix and own what goes forward.
Build the clickable prototype in code
Engineers build it in React and Next.js, with tools like Lovable and Claude Code to move fast. Your users click through it, and we change it based on what they do.
Write the scope, decisions and price
Requirements, the decision log, the backlog, risks and a price range with its assumptions, walked through with your stakeholders. Build, buy or wait: if a ready tool fits, we say so.
Proof, not promises
EdTech · AI
AI-powered medical tutoring for Elite Medical Prep
PropTech · Platform
Rescuing a construction management platform after a failed first build
Questions before a discovery workshop
- No. We work in your repository, your cloud and the tools your team already uses. If one of them gets in the way of the work, we tell you what and why, and you decide.
- With a 30-minute scoping call. We look at what you have and what you need, then propose a first step with its scope and price before any work starts.
- The people who can explain the user problem and make product decisions, plus whoever owns the data and systems it touches. From our side, a business analyst who leads it, a product designer from Widelab and a senior engineer or architect.
- No. Existing sketches, research or notes help us prepare, but the workshop is intended to turn incomplete input into a clearer scope.
- For a new product it usually takes one to two weeks, depending on how many teams and systems are involved. We agree the scope and schedule first, and you get a price before we start. The output gives you a price range for the build, not a fixed-price contract. That needs agreement on the remaining assumptions and commercial terms. Development is a separate decision.
- No. We build it in real code (React and Next.js), not as a picture of an app. When you move to development, the prototype is the starting point of your production frontend. We add the backend, permissions, edge cases and tests around it instead of starting over.
- Yes. If a ready product fits your process, we say so and stop there. We would rather tell you an idea doesn't hold up than quietly build the wrong spec.
- Requirements, user flows, the decision log, the backlog and the prototype code. They live in your tools (Notion or Confluence, Linear or Jira, Figma, your Git repo) and stay the project docs during the build, not a PDF. Yes, another team can pick them up and build from them.
- You can stop with the docs and the prototype, take them to another team, or keep going with us. In that case the prototype grows into your product's frontend and the docs keep getting updated as we build.
- It depends on the project. Typically FigJam or Miro for mapping, Figma for UX, and Lovable, v0, Claude and Claude Code to get a working prototype fast. The code is React, Next.js and Tailwind, with Storybook for components. Docs and backlog go into Notion or Confluence and Linear or Jira, or whatever you already use.
- AI is in every stage. It transcribes sessions, summarizes research, drafts requirements and flows, and generates first screens and code. People do the rest. The business analyst checks every requirement, designers decide on UX, engineers review the code, and you make the product decisions.
How we think about this, in our own words
Interactive briefs and articles by our team, picked for this service
The new Pareto: 95/5
Why the 5% of effort that makes a convincing prototype hides the edge cases and permissions your scope has to price.
Read the briefBuild an MVP that works: Key steps to launch fast without burning cash
How to decide what the first version needs, test it with real users and launch small before funding the full build.
Read the articleBuild vs Buy in FinTech: When Custom Software Makes Business Sense
When building custom software makes business sense and when buying is the better call, shown on financial products.
Read the articleTurn the open questions into a product brief
Tell us the business problem, the people involved and the decision you need the workshop to support.
Direct contact
Mike KacprowiczBook a callChief Growth Officer