From a business problem to an architecture your teams can build.

I design systems where business goals, software structure and team organisation have to fit together: logistics, the public sector, insurance, telco and manufacturing, across 22 years. I started out writing the code, so my designs come with the trade-offs, the team boundaries and the cost of change already worked out.

  • Founder at Arpeggia Studio
  • First place, O’Reilly Architectural Katas, Winter 2024
  • Co-author of Responsible Software Architecture
Portrait of Piotr Filipowicz
Piotr FilipowiczBiałystok, PL · Remote

What companies bring me in for

Most work starts with a decision that is expensive to get wrong. These are the ones I see most often.

  • A new product with an unclear shape

    You know the business goal but not yet what to build. I turn it into requirements, the qualities that matter and an architecture a team can start on.

    How I work
  • A legacy system or a troubled project

    Replace, rescue or rebuild: the options compared on cost, risk and time, so the decision is made while it is still cheap to change.

    Work with me
  • A vendor proposal on the table

    An independent view of the architecture and the risks before you sign, from someone who has delivered systems like it.

    Work with me
  • One platform for many markets or units

    Shared foundations with local rules, as in the DPD platform for 14 countries and the portal for every labour office in Poland.

    DPD case study

What clients say

From written recommendations by people who worked with me on the client side of these projects.

Piotr doesn't just build, he optimises. He is a ‘safe pair of hands’ for any product team.

Janos VerProduct Management Consultant, INNIO

Able to create a big picture design and also to go top-down even in very complicated environments. He still has his hands deep on technology.

Wojciech RudzińskiHead of Development, DPDgroup IT Solutions

He was able to fully understand where all of us were coming from, and at the same time offer new, futuristic, way-ahead-of-us kind of solutions.

Vlatka BencinaProject Manager, DPDgroup CSEE

How I approach architecture

Responsible Software Architecture says what a good design has to take care of. The six-step process is how I get there on a real project. Architectural Kata 2.0 is where people practise it.

  1. Responsible Software ArchitectureFour pillars a design has to answer to
  2. Six-step design processFrom requirements to team boundaries
  3. Architectural Kata 2.0A workshop to rehearse the process

The concept and the six steps in detail

Workshops: practise the decisions

Architectural Kata 2.0 is a one-day workshop where teams take a realistic business problem through the six steps and defend the result in front of a demanding client.

  • From business goals to architecture requirements
  • Finding system boundaries
  • Comparing options and justifying trade-offs
  • Communicating architecture
  • Testing assumptions
  • Using AI in architecture work

Who it is for and how it works

Architect, engineer by origin

I started in 2004 writing code, then led teams and designed platforms for logistics, the public sector, insurance and telco. Today I am a Solution Architect and a co-founder of Arpeggia Studio, where I design architecture with clients and run the Architectural Kata workshops.

Facing a decision that’s expensive to undo?

piotr.filipowicz@arpeggia.studio

  • Architecture for a project

    A new product, a troubled delivery, a legacy system or a vendor proposal. You work directly with me; contracts and booking run through Arpeggia Studio, the company I co-founded.

    Book a call at Arpeggia Studio ↗
  • A workshop for your team

    Architectural Kata 2.0, run in-house for your architects and senior engineers.

    Workshop details ↗
  • A talk, podcast or event

    Conference talks, meetups and guest episodes, in Polish or English.

    Send an invitation