Understand the problem and see the system designed before spending on code
Discovery is the stage where we listen to the people who use the process, decide what to build first and show you the screens. You reach development knowing what you will get.
Signs you need this
- You know something is stuck, but cannot say what to build.
- Everyone in the company describes the process differently.
- You have received a quote that did not explain what was included.
- You want to compare vendors on something concrete.
What comes out of discovery
- A map of the current process, with the points where it gets stuck.
- A prioritized list of what to build first and what can wait.
- Designs of the main screens, so you can see and comment before any code exists.
- A written estimate, with what is in and what is out.
- An honest recommendation, including when the answer is "use a ready-made tool" or "do not build this now".
Step by step
- We talk to the people who use the process, not only to those who decide.
- We follow the real work, with the data and spreadsheets that exist today.
- We design the screens and flow, and review them with you.
- We close the estimate and what goes into the first build stage.
When it is not needed
If the problem is small and clear, like a simple automation, we go straight to building. Discovery exists to lower risk when there is doubt.
Frequently asked questions
Do I need a finished scope to start?
No. Helping define the scope is exactly the job of this stage.
Why not just build right away?
Because fixing a designed screen costs far less than fixing a finished system. Discovery asks the hard questions while they are still cheap.
What happens afterwards?
You decide. You can continue with Wyber to build, hire elsewhere or wait. The written recommendation is yours.
See also
Want to start with a conversation?
Tell us the problem, even if it is still fuzzy.
We reply within 1 business day.