Understand the problem first. Then make changes.

Complex e-commerce leaves no room for arbitrary decisions.

Before development starts, we establish what actually needs to be solved, what the dependencies are and where the greatest risks lie.

We then work in short stages, verify the result regularly and do not leave testing until the final days before launch.

Our process can be divided into four stages.

The process

Four stages for running a project

  1. 01

    Understanding and discovery

  2. 02

    Design and delivery

  3. 03

    QA and launch

  4. 04

    Stabilisation and ongoing development

Understanding and discovery

The scope of the first stage depends on the project.

For a new implementation, it may include workshops on business processes, architecture and integrations.

For a migration, we review the current platform’s features, data and the processes that need to be retained or changed.

When taking over an existing Magento platform, we also analyse its code, configuration, database, integrations and infrastructure.

Above all, we want to answer several questions:

  • what business problem are we solving,
  • which features are genuinely needed,
  • which systems are connected,
  • where each type of data originates,
  • what can be achieved with standard platform features,
  • where customisation is justified,
  • what the most important risks are.

For larger projects, discovery results in an agreed scope and functional and technical documentation on which development can be based.

When we take over an existing platform

We do not assume that the old system needs to be rewritten.

We assess each element using four possible decisions:

Keep

It works and there is no reason to change it.

Rebuild

It has value, but needs to be brought under control.

Replace

Continuing to develop the current solution no longer makes sense.

Remove

It increases complexity or cost without providing sufficient value.

The goal is to solve the problem, not to create the largest possible scope of work.

Design and delivery

Once the direction is agreed, we divide the larger scope into smaller parts.

We usually work in cycles of one to two weeks. In larger projects, backend, frontend and integrations can be developed in parallel.

A PM manages the project day to day.

They are responsible for work organisation, status, priorities and communication. When an architectural, integration or technical decision is needed, the people responsible for that area join the discussion.

The client has visibility into progress, current priorities and decisions that affect the project scope.

If requirements change, we want to know before work begins on that element, not after it has been implemented.

QA and launch

Testing is part of the process, not the last task before production. On our side, we verify delivered features and critical paths in the sales process.

Depending on the project, this includes:

  • functional testing,
  • integration testing,
  • regression testing of key processes,
  • performance verification,
  • verification in a pre-production environment.

For processes that require specialist business knowledge or significant new features, the client also carries out their own UAT.

Changes first go to staging or a pre-production environment. We deploy them to production only after verification.

For larger updates, we prepare the deployment in a way that limits the risk of interruptions to sales and, where necessary, allows the change to be rolled back quickly.

Stabilisation and ongoing development

A launch does not mean the project disappears from our radar.

After major changes, we monitor the system under real traffic and with real data. Problems that only appear in production are addressed during stabilisation.

The relationship can then move into ongoing platform maintenance and development.

This may include:

  • incident handling,
  • Magento updates,
  • security,
  • development of new features,
  • performance,
  • further integrations,
  • B2B development,
  • expansion into new markets.

This keeps the knowledge gained during the project within the team that later takes responsibility for its continued development.

Technical support and maintenance

How we can start working together

Diagnosis

When the source of the problem and the priorities need to be established first.

Project

When the scope includes an implementation, migration, project rescue, integration or major rebuild.

Support for an existing team

When a company has its own team but needs additional Magento, Hyvä, integration or infrastructure expertise.

Ongoing care and development

When the platform is important to the business and needs continuous maintenance and further change.

Communication

We use Freshdesk, Microsoft Teams and/or Slack, as well as email, in our day-to-day work. We can also work in the client’s tools if that is how their organisation operates.

The tool is secondary.

What matters is that everyone knows what we are doing, what comes next, who is responsible and where a risk has emerged.