Skip to content
Asterion Softwares.r.o. · Praha

Approach

How we would tackle four common situations

Four problems our services are built for, each with the method we would apply, the technologies we would reach for, and how the work would normally be contracted.

Read this before the rest of the page

These are illustrative examples of our approach — not case studies. They do not describe past client projects. No client is identified, no logo is reproduced, no project is claimed, and no figure on this page is presented as an achieved or promised result. They exist so you can see how we think about a problem before you spend an hour on a call.

Manufacturing & logistics

Replacing a spreadsheet-run operations process

The situation this applies to

Order intake, scheduling and dispatch coordinated across a shared spreadsheet, an email inbox and one person who knows the exceptions.

How we would approach it

  1. 01Model the real process, including the exceptions, before designing screens
  2. 02Build the transactional core first; reporting second
  3. 03Run the new system in parallel with the spreadsheet for one full cycle
  4. 04Migrate historical data with a reconciliation report both sides sign off

Technologies we would reach for

  • PHP 8.3
  • React
  • MySQL
  • Docker

Contract shape

Would normally be contracted as fixed-scope delivery

An illustration of our method, not a record of a project. Any duration for real work is agreed in the written quote after discovery.

Professional services

Moving a self-hosted application to managed cloud infrastructure

The situation this applies to

A working application on ageing hardware, with deployments performed by hand and no tested restore procedure.

How we would approach it

  1. 01Inventory every environment dependency, including the undocumented ones
  2. 02Define infrastructure as code and stand up a parallel environment
  3. 03Cut over with a rehearsed rollback and a restore drill run beforehand
  4. 04Hand over the pipeline so the client deploys without us

Technologies we would reach for

  • Terraform
  • AWS
  • Docker
  • GitHub Actions

Contract shape

Would normally be contracted as consultancy plus implementation

An illustration of our method, not a record of a project. Any duration for real work is agreed in the written quote after discovery.

Retail & e-commerce

Connecting an ERP, a storefront and a logistics provider

The situation this applies to

Three systems exchanging data through nightly CSV files, with mismatches discovered at month end.

How we would approach it

  1. 01Define the contract between systems before touching either side
  2. 02Make every message idempotent, then add retries and a dead-letter queue
  3. 03Publish a daily reconciliation report so a mismatch surfaces the same day
  4. 04Retire the CSV job only after a full period of clean parallel running

Technologies we would reach for

  • REST
  • OpenAPI
  • RabbitMQ
  • PostgreSQL

Contract shape

Would normally be contracted as fixed-scope delivery

An illustration of our method, not a record of a project. Any duration for real work is agreed in the written quote after discovery.

Software product companies

Extending an in-house product team

The situation this applies to

A product roadmap that has outgrown the internal team, with hiring lead times measured in quarters.

How we would approach it

  1. 01Introduce named engineers and let the client interview them
  2. 02Work inside the client repository, board and review process from day one
  3. 03Report weekly in writing: shipped, in progress, blocked
  4. 04Document everything so the engagement can end without a knowledge cliff

Technologies we would reach for

  • React
  • TypeScript
  • Node.js
  • CI/CD

Contract shape

Would normally be contracted as a dedicated team, monthly rolling

An illustration of our method, not a record of a project. Any duration for real work is agreed in the written quote after discovery.

What you can check instead

A case study written by the supplier proves nothing about the supplier. These do, and you can check every one of them without taking our word for anything:

  • Our entry in the Czech Commercial Register (Obchodní rejstřík) under IČO 10736697 — open it in ARES.
  • Our VAT registration CZ10736697 in the European Commission VIES system.
  • A technical conversation with the engineer who would lead the work, before any contract is signed. You will learn more in thirty minutes of that than from any page on this site.
  • Ask us directly what we can share about comparable work. We will tell you what we are permitted to disclose and what we are not, rather than publishing something neither of us can stand behind.

Start with a scoped conversation

The estimator turns five answers into delivery phases, a duration band and a team shape. It takes about two minutes, and it gets you a far more specific first reply than a blank contact form.

Request software estimateOr just email us