Business analysis and application MVP scope

You do not need to arrive with a technical specification. We need to understand how the company works today, where the problem occurs and what should change after implementation.

When is this workshop useful?

The workshop is the right step when a company understands the problem but cannot yet define the delivery scope responsibly. This is common when:

• several people have different ideas about the future way of working
• the process involves multiple roles, decisions and exceptions
• data is spread across several applications, spreadsheets or files
• the new application must work with other systems
• the feature list keeps growing, but nobody knows what the first release truly needs
• pricing depends on information that cannot be established during a short call.

A phrase such as "order management" does not define a project. We still need to know who may change an order, what happens when data is missing, which system holds the stock level and how the company will decide that the stage is complete. These decisions affect scope far more than the feature name itself.

When may a simpler brief be enough?

Paid analysis is not necessary for every task. If a change is small, has a clear outcome and does not involve many roles, data migration or uncertain integrations, a description of the problem and the available materials may be enough for pricing.

You can begin with our free project brief builder. It helps organise information, but it does not replace specialist work, meetings, process mapping or dependency assessment.

How do we work?

1. We briefly qualify the need

A free call of up to 20 minutes helps establish the problem, the goal and the materials needed for the next step. It is not a diagnosis, an analysis or a free report.

2. We agree the workshop scope and price

Before work begins, you receive an individual proposal. It records the scope, meeting dates, expected outcome, completion rules for the stage and price.

3. You prepare the materials you already have

They do not need to form complete documentation. Useful materials include a description of the current process, applications and files in use, example data categories, user roles, known exceptions and organisational or technical constraints.

Do not submit passwords, API keys, database copies or real customer data through the ordinary contact form. If any such material is required, we will agree a separate and secure transfer method.

4. We hold two remote sessions

The standard scope includes two sessions of up to 90 minutes each. In the first, we organise the problem, the process and user needs. Between the sessions, we analyse the information collected. The second session resolves gaps, dependencies, exceptions and the boundaries of the first stage.

We normally schedule both sessions within one week. Exact dates are confirmed in the proposal. An on-site meeting and travel require separate arrangements and pricing.

5. We deliver the agreed summary

We deliver the summary within 5 business days after the final session. Its format and the completion rules for the stage are agreed before work begins.

What do you receive after the workshop?

The precise contents follow the proposal, but the standard outcome includes:

• a description of the problem, goal and users of the future solution
• a simplified map of the current process and the proposed way of working
• a division into the MVP, later stages and items outside the scope
• a list of required data, integrations and important dependencies
• assumptions, constraints and risks that affect delivery
• acceptance criteria for the first stage
• a proposed order for further work
• an initial estimate when the collected information is sufficient to prepare one responsibly.

The summary has value on its own. You may use it in further work with Domin Software or give it to another supplier of your choice. The materials remain confidential and are not intended for public distribution.

How do we define the MVP scope?

An MVP is the smallest version of the solution that performs a specific job and can be verified in the real process. It is not an arbitrarily reduced or unfinished application.

When dividing the scope, we examine:

• which problem must be solved first
• who will use the first version and what decisions they make
• which data is essential and which can be added later
• which integrations are required from the beginning
• which exceptions block work and which can wait
• how the client will accept the stage and confirm that it works as agreed.

We do not assume that an MVP is always the best option. If dividing the project would create an inconsistent process, duplicate work or risks to data, that must be considered before a decision is made.

What is not included in the standard scope?

Unless the individual proposal says otherwise, the workshop does not include:

• a complete technical specification for the entire system
• tender documentation
• interface design
• a clickable prototype
• final architecture for every module
• a guaranteed final estimate for the entire application
• an unlimited number of sessions or scope revisions
• application implementation or development work.

If a prototype, additional data analysis, an on-site consultation or separate integration discovery is needed for a sound decision, we propose another stage instead of hiding it inside a general promise.

Price, payment and further delivery

We price each workshop individually. The price depends on process complexity, the number of roles, available materials, integrations and the expected detail of the summary.

Payment is normally due after the agreed stage is complete. For a larger scope, we may agree an advance payment.

If Domin Software later delivers the project described during the workshop, the paid analysis cost is credited towards the total project cost. You are not required to commission the next stage from us. You may also use the materials with another supplier.

Frequently asked questions

Do I need a complete specification before the workshop?

No. A description of the current situation, the problem, the people involved, the applications in use and the expected change is enough. Existing files and earlier decisions may also help.

Is the first call free?

Yes. The short qualification call lasts up to 20 minutes and helps determine whether the workshop is the right step. It does not include a diagnosis, analysis or report.

What does the standard workshop include?

It includes two remote sessions of up to 90 minutes, analysis of the supplied materials and the agreed summary. The precise scope, outcome and completion rules are recorded in the proposal.

Will I receive an exact price for the whole application?

Not always. We prepare an initial estimate when the information collected allows us to define the scope responsibly. If integrations, data or dependencies remain unclear, we explain what must be resolved before pricing.

Does the workshop include interface design or a clickable prototype?

Not in the standard scope. If such an asset is needed to test the idea or make a decision, we can price it as a separate stage.

When will I receive the summary?

Within 5 business days after the final session. We confirm the exact date and delivery format in the proposal.

Is the workshop cost credited towards later development?

Yes, if Domin Software delivers the later project. The paid analysis cost is then credited towards the total project cost.

May I give the materials to another supplier?

Yes. You may use them with a supplier of your choice, while keeping them confidential and not publishing them.

Can the sessions take place at our office?

The standard option is remote. An on-site session and travel require separate arrangements and pricing.

What should you send first?

In your first message, describe:

• the problem the application should solve
• the people or roles involved in the process
• the applications, spreadsheets and files used today
• the data that must be migrated or exchanged
• known integrations and constraints
• the expected project start date.

We do not need a technical specification at this stage. From a short description, we can assess whether an ordinary estimate is enough or whether the workshop should come first.

CTA: Define the workshop scope

If you prefer to organise the information first, use the free project brief builder.

Related services

Once the direction is clear, you can move on to application delivery, review the scope of a custom CRM or ERP system, or discuss integrations and data exchange.