Question 1

Do we have to throw away a system that has run for years?

Accepted Answer

Not where we start. Here the goal was **refreshing the technical layer** and closing known problems — with a process teams already know. A big bang replacing everything is a different conversation and budget.

Question 2

Will modernisation stop operations?

Accepted Answer

We work **in stages**: agreed priorities, regression on real scenarios, deployments without a “month-long off switch”. Sensible legacy modernisation assumes the organisation keeps working throughout.

Question 3

Why Symfony and API Platform?

Accepted Answer

Because a **maintainable backend** was needed for a complex operational domain and a **clear API** for front-end and integrations (including finance and KSeF). The point is structure that lasts — not a trendy stack.

Question 4

Does KSeF require a new system?

Accepted Answer

Not by definition. Here the goal was **invoicing and KSeF from the same case record** — not as a separate entity beside operations. Modernisation tied that into one flow.

Question 5

Does this reveal industry or client?

Accepted Answer

No. We describe the **problem and solution pattern** without company name, industry detail or specifics that could identify the organisation.

Question 6

How to start with 8mb?

Accepted Answer

Write: how long the system has been in use, what hurts, what you defer and where information is lost. We reply with a **first, small step** — or say honestly we are not a good fit.

The system had run for two decades — it needed a refresh, not a replacement