Skip to content
Language: English

Business analysis and product consulting

Know what to build, why, and in what order, before coding starts

For organizations that know they need a system for the way they work but have not yet decided what to build first, and for teams that want to turn a product idea or an existing system into requirements that can be implemented.

01

Problems we solve

  • We know our business needs a system, but we do not know where to start or what to build first.

  • Some employees know the business rules, but they are not written down anywhere.

  • We received differing proposals from development firms and cannot compare them, because what we need is not clear in the first place.

  • We started a project once before, and it stopped because the requirements changed halfway through.

02

What the service includes

  • F.01

    Analyzing processes as they actually run

    We sit with the people who do the work and map the current processes, with their steps, their exceptions, and the documents that pass through them.

  • F.02

    Documenting business rules

    In language your team can review, we write down the rules that govern the work: permissions, approvals, calculations, and exceptions.

  • F.03

    Requirements and backlog

    We turn what we have documented into requirements and user stories, ordered in a backlog by impact and priority.

  • F.04

    Defining the product and its stages

    We set the scope of the first release and what is deferred to later stages, so development starts at a size that can be delivered.

  • F.05

    The proposed solution path

    We explain the most suitable option: building a custom system, improving an existing one, or starting with a smaller step, with the reasons for each.

  • F.06

    A clear handover to development

    The development team receives one clear file: the processes, the rules, the requirements, and the prioritized backlog.

03

How it runs

  1. We listen and observe

    We meet with management and with the people who do the work, follow the processes as they actually run, and collect the forms and spreadsheets.

  2. We analyze and document

    We map the processes, write down the business rules, and review them with your team until they match reality.

  3. We prioritize and set the scope

    We turn the analysis into requirements and a prioritized backlog, and agree with you on the scope of the first release.

  4. We hand over to development

    We hand over the complete analysis file, present it to the development team, and answer its questions before work starts.

04

What it looks like in practice

Illustrative example

A distribution company wants an order management system and has received three proposals that cannot be compared, because each one understood what was needed in a different way. We start by documenting the order cycle, from receiving the order to collecting payment, along with the discount and approval rules, then organize the requirements into a backlog and set the scope of the first release. The company compares the proposals on one clear basis, and development starts from agreed requirements.

05

What we need from you to start

  • Someone from management with the authority to decide priorities
  • Time with the people who do the work in the departments involved
  • The forms, spreadsheets, and reports you work with today

06

Follow-up after the analysis is handed over

Our work does not end when we hand over the analysis file: we answer the development team’s questions and update the documents if the requirements change.

  • Answering the development team’s questions after the analysis file is handed over.
  • Updating the analysis documents if the requirements change.

07

Common questions

Technologies we work with

  • BPMN
  • User stories
  • Product backlog
  • Wireframes
  • Do we need the analysis if we already know what we want?

    Often, yes, but on a smaller scale. We review what you have and document the rules and exceptions that a general description doesn’t show, because they’re what changes the size of the development work later.

  • Can we do the development with another provider after the analysis?

    Yes. We write the analysis file for any development team to use, whether it’s ours or someone else’s.

  • How is this service different from digital transformation?

    This service ends with a clear plan and requirements you can build on. Digital transformation includes building the system and moving the work onto it in stages, and it may start with this analysis.

  • We have an existing system that does not suit us. Is that where we start?

    Yes. We analyze how the system is actually used and where it differs from the way you work, then make clear whether it’s better to improve it, replace it, or connect it to other systems.

Let’s start with how you work

Describe your processes and the problem you want to solve, and we will define a clear first step with you.