Architecture help before the decision gets expensive
I work with companies that are about to commit budget to a product, a platform or a vendor, and want an architect's view of what to build and what it will cost to change later.
- For CTOs, founders and boards
- Remote from Białystok, in Polish or English
- Contracted through Arpeggia Studio
- Starts with a free 30-minute call
Situations I am brought in for
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.
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.
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.
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.
Three ways to work together
Each one can be a single engagement or the first step of a longer one. If your team needs to build the skill itself, there is also the Architectural Kata workshop.
Product discovery
- When
- Before a build, when the goal is clear and the product is not.
- What we look at
- Business goals, constraints, decision risks, scope, priorities and the architecture that follows from them.
- You leave with
- Options with their impact on cost, risk and time, a risk map and an action plan your team or vendor can execute.
Technology risk review
- When
- A vendor proposal, a troubled project, a legacy system or a new digital product.
- What we look at
- An independent look at the architecture, the assumptions and the risks, by someone who has delivered systems like it.
- You leave with
- A clear view of what can go wrong, what it would cost, and what to do first.
Architecture for a new platform
- When
- When the product is decided and needs a design a team can build and run.
- What we look at
- Requirements, the qualities that matter, trade-offs, C4 diagrams, fitness functions and team boundaries: the six steps.
- You leave with
- A buildable design. Current examples: a verifiable credentials platform and a game-show engine.
From first call to agreed scope
A 30-minute call
You describe the decision in front of you. No preparation needed, a short description is enough.
A proposal
I suggest the form of work that fits, or tell you honestly if someone else would serve you better.
A contract with Arpeggia Studio
Commercial work runs through the company I co-founded. I stay your architect throughout.
Work and words from the client side
Contract Lifecycle Management for INNIO
A platform that configures the contracts INNIO signs and simulates their costs before signing, so contracting follows one controlled process.
My roleEngineering Team Lead & Lead Architect
Read the case studyA B2C platform for DPD in 14 countries
Three portals that gave a B2B parcel carrier a direct relationship with recipients in 14 countries and 13 business units, each with its own rules.
My roleJava Architect & Team Lead
Read the case studyPiotr doesn't just build, he optimises. He is a ‘safe pair of hands’ for any product team.
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.
Why the contract is with Arpeggia
I co-founded Arpeggia Studio with Sebastian Dąbkowski and Wojciech Kasa, and all my commercial work runs through it. For you that means a contract with a company rather than a freelancer, and co-founders who can join when the work needs more than one architect. When you book a call, you will land on the Arpeggia calendar; the call is with me.
Tell me what you are deciding
A free 30-minute call, booked through the Arpeggia Studio calendar. Or write to me directly if you prefer.