Product Consultation Before Software Development
Good decisions at the start matter and help prevent expensive mistakes later.
How can I help?
Are you planning a new product, app, internal tool or automation? We review target users, competitors, available alternatives and the first version, so it becomes clear what is worth building and where unnecessary costs may appear.
User and market research
We find out what people need, how they solve the problem today and what competitors or alternatives already exist.
First usable version scope
We choose features that validate the main product value and postpone ideas that increase cost without a clear benefit.
Consultation output
The output depends on the goal. It may include a recommended first-version scope, risks, open questions or a recommendation on whether to continue with a brief, prototype, MVP or another solution.
Who this consultation is for
- Companies with a digital product ideaYou want an app, internal system or online service and need to validate the direction before development starts.
- Founders and small teamsYou have a product or MVP idea and need to turn it into a clear scope, priorities and a next step.
- Companies with an unclear processYou are solving an operational problem and are not sure whether it needs an app, automation, internal tool or process change.
- Review of an idea, brief or planYou want someone to review the product idea, brief, roadmap or first-version scope before development.
When it makes sense to discuss the product with me
I have experience with my own apps, client Android projects, web applications, internal tools and automations. That helps me connect product thinking with what can be built, operated and developed further in a reasonable way.
- Less handoverYou discuss the work directly with me.
- Lower overheadYou don't pay for team coordination or an expensive agency.
- Faster decisionsChanges can be discussed and included without long approval chains.
How the consultation works
- 01Goal and expectationsWe discuss why you need the consultation, what stage the product is in and what output you need.
- 02Users, market and alternativesWe look at target users, competitors, available solutions and how people solve the problem today.
- 03First version and risksWe choose what belongs in the first version, what can wait and where technical, product or budget risks may appear.
- 04Recommended next stepI summarize the recommended scope, open questions and whether to continue with a brief, prototype, MVP, development or another solution.
My experience
Product and software work examples
All projects →
DashCam TravelMy own Android product available on Google Play for over 10 years. It includes app design, long-term maintenance, updates and work with user feedback.View case study →
Video RecapAn Android app for creating short recaps from long videos, where the product flow from video input to finished output matters.View case study →
AI invoice and receipt recognitionA local web tool showing how a vague need for document processing can become a concrete workflow with output review.View case study →
TradingView Balance Daily StatsA custom TradingView tool that turns a concrete trading need into an overview of daily P&L, win rate and trade count directly in the chart.View case study →FAQ
What is product consultation before software development?
It is a joint clarification of the product before you start paying for development. We discuss the target user, problem, first version, risks, technical options and the next step.
Do I need to have a finished brief?
No. It is enough to describe the idea, problem or process you want to solve. The consultation can help turn the intention into a more concrete brief.
Can you help decide whether we need an app, automation or internal tool?
Yes. At the start, this is often the main question. Sometimes a mobile app makes sense, sometimes a web application, internal tool, automation or a smaller process change.
What belongs in the first product version?
The first version should include the features that validate the main value for users. Other ideas are better postponed, so the first step does not become unnecessarily expensive.
Will I get a development cost estimate after the consultation?
If the scope is clear enough, I can prepare an indicative estimate for further work. For unclear ideas, I first recommend what to add or validate before estimating.
Is consultation useful before contacting an agency or another developer?
Yes. The output can help clarify the brief, name priorities and avoid a situation where different suppliers estimate different things.
Can we continue directly with development after the consultation?
Yes, if the project fits my capacity and technologies. If another approach or a wider team makes more sense, I will say so directly.
Let's review your product idea.
Tell me what you want to build, who it is for and what stage it is at. I will suggest a sensible first step.
Ask in chat