Business and solution architect

I turn how a business actually decides into a model your team can own.

Decisions, rules and their owners written down and agreed, and a system design that follows from them, so the next change can be planned and delivered without surprises.

For founders, CEOs and CTOs of growing companies, and for delivery teams preparing a bid.

  • 9+ yearsin architecture design, development and audit
  • 100+presales and projects, from banking and government to healthcare and aviation
  • Millions of citizensuse a government digital services platform I designed as solution architect
  • Experience at Andersen, Ericsson and EPAM. Client work under NDA.

Industries

Typical situations in the industries I have worked in.

Finance and banking

Products, limits and pricing rules spread across core systems and spreadsheets. Changing one rule safely means knowing every place it is applied.

e‑Health

Several organisations and systems share patient data under one standard. The hard part is agreeing who owns each record and each change to it.

Government information systems

Services built over years by different vendors, each holding part of the same case. Consolidation needs clear boundaries and an order of migration that keeps public services running.

Legal tech

Large volumes of documents and rules that change often. Value comes from structured content and a clear model of how it is acquired, enriched and published.

Aviation and travel tech

Operations that run around the clock on systems that grew as one large application. Change has to happen in phases, without stopping operations.

Media and software vendors

A product has to keep serving its customers while it is rebuilt. Customers move across one at a time, without losing service or history.

Where the problem usually sits

A growing company seldom stalls on technology first. It slows down where nobody can say who decides, which rule applies or which system holds the right number. Those answers live with a few people and in code nobody wants to touch, so every change costs more than it should.

My work sits between the business and the engineering team. I make these answers explicit, agree them with the people responsible, and then design the operating model and the architecture that follow from them. The team gets a structure it can build on and change.

Skip the illustration

BeforeAfter

  • Rules live in people's headsEvery rule has an owner
  • Two systems disagreeOne source of truth for each thing
  • Every change breaks somethingChanges land where they are expected

How I can help

People usually get in touch when one of these is true.

  • The same decision is argued again at every planning meeting.
  • Only two or three people know why the system behaves the way it does.
  • Two systems report different numbers for the same thing, and nobody owns the difference.
  • Estimates keep slipping because every change touches more than expected.
  • Manual work grows with every new client, partner or market.
  • A migration or modernisation is planned and the order of steps is unclear.
  • A bid or a proposal needs an architecture behind it, and the deadline is fixed.

Founders and CEOs

A clear picture of how the business makes decisions today and what has to change for it to grow, in terms you can take to partners, investors and the team. The decision stays with you. I make the options and their consequences visible.

CTOs and CIOs

A second, experienced view on a decision, a migration plan or a vendor proposal before it is committed. Business rules and ownership are settled before the architecture, so your team builds on agreed ground.

Delivery organisations and bid teams

The architecture and the decisions behind it for a proposal, a bid or the start of a programme, delivered as documents your team can estimate and build from. I don't supply people or run delivery.

Services

  • End-to-end system design

    A new product or platform, from how the business works to a design a team can estimate and build. I design, your team or vendor builds.

    Discuss this
  • Decision and architecture review

    A decision, a migration or a vendor proposal needs a view from outside the team before it is committed.

    Discuss this
  • Technical audit

    A running system slows the business down, or an investment needs an outside assessment first.

    Discuss this
  • AI adoption

    AI added to a process that was never written down produces answers nobody can check. The decisions it supports, their owners and their limits come first.

    Discuss this
  • Architecture support during delivery

    A design exists and the team builds it. Reviews and decisions as the system grows, with the design kept in step with the code.

    Discuss this

Selected client work

What the client needed, what I delivered and in which role.

  • Government digital servicesRegion: Gulf regionScope: Rebuild of a citizen and business services platform and migration off a legacy portalDelivered: Decision records, service designs, data migration plan, API contracts, backend codeRole: Delivery architect
  • Retail bankRegion: Central AsiaScope: New version of the mobile banking app on event-driven servicesDelivered: Target architecture in C4, notification design, API contracts, schema migrationsRole: Architect and engineer
  • European media groupRegion: EuropeScope: AI-assisted schedule planning for streaming channelsDelivered: Architecture vision, decision records, AI architectureRole: Author of the architecture vision

See all 10 engagements

One system I can show end to end MAXBRIX, a price catalogue I designed, built and run. See the decisions behind it

How we work together

  1. A first conversation

    You describe the situation. I ask the questions I start every engagement with. You leave with a clearer view of where the problem sits, whether or not we continue.

  2. A proposal for your case

    Scope, stages, timing and cost, written for your business after the conversation. Nothing is taken from a fixed package.

  3. Work in stages

    Each stage has its own scope, an upper bound on hours and an acceptance criterion agreed before it starts. You can stop after any stage and keep the documents it produced.

The stages a full engagement can run through. Each case uses the ones it needs, and the deliverables are chosen per case.

Discovery

Stages 1-2

Fix the business goals and the current state before design begins.

Design

Stages 3-4

Decide how the solution is built and how to get there in stages.

Detailed design and oversight

Stages 5-7

Take the solution to a level fit for estimation and development.

Stage 1 of 7  ·  Discovery

01

Discovery and business architecture

Work

  • Interviews with key stakeholders
  • Goal workshop: turning goals into measurable targets
  • Review of product economics and margin structure
  • Inventory of decisions and their owners
  • Identification of constraints, assumptions and risks

Deliverables

  • Vision and Scope: a shared understanding of goals, boundaries and expectations
  • Business context and stakeholder map
  • Business capability map
  • Domain glossary
  • Decision inventory with owners
  • Measurable business goals and KPIs
  • Risk and assumption register

Stage 2 of 7  ·  Discovery

02

Current state

Work

  • Walkthrough of processes on real transactions
  • Mapping of data flows and sources of truth
  • Review of the current decision logic
  • Review of the current architecture and integrations
  • Reconciliation of the description with actual system behaviour
  • Analysis of bottlenecks and their causes

Deliverables

  • Current process model: the factual picture of how the work runs today
  • Current decision model
  • Data flow and source of truth map
  • Systems and integrations map
  • Inventory of manual operations and their cost
  • Bottleneck and technical debt analysis

Stage 3 of 7  ·  Design

03

Target operating model

Work

  • Design of the target processes
  • Separation of decisions between the system and the operator
  • Definition of rule owners and the change procedure
  • Design of the KPI framework and its link to decisions
  • Sign-off of the target model with the client

Deliverables

  • Target operating model and responsibility split: who decides what once the change lands
  • Target process model
  • Automation strategy
  • Business rule governance procedure
  • KPI framework and its link to decisions

Stage 4 of 7  ·  Design

04

Solution architecture

Work

  • Identification of architectural drivers: business goals, major features, constraints
  • Definition of quality attributes and their targets
  • Identification of contexts and the boundaries between them
  • Design of integrations and exchange contracts
  • Assessment of headroom for load and data growth
  • Key architecture decisions with rationale
  • Planning the staged transition to the target state

Deliverables

  • Architecture Vision: the target shape of the solution and the key rationale
  • Architectural drivers and design constraints
  • Quality attributes with targets
  • Context and boundary map
  • Architecture in the C4 model: context and containers
  • Deployment view
  • Integration and exchange contract diagram
  • Architecture decision log
  • Staged transition plan

Stage 5 of 7  ·  Detailed design and oversight

05

Detailed business design

Work

  • Domain decomposition and object lifecycles
  • Formalisation of rules as inputs, conditions and outcome
  • Compilation of the business rules and invariants catalogue
  • Description of events and their link to the KPIs
  • Validation of the rules against real data
  • Preparation of acceptance scenarios

Deliverables

  • Domain model: formalisation of the key business entities and their relationships
  • Detailed process diagrams
  • Decision tables
  • Business rules catalogue
  • Object lifecycles
  • Business event catalogue
  • Business invariants
  • Acceptance scenarios

Stage 6 of 7  ·  Detailed design and oversight

06

Detailed technical design

Work

  • Decomposition into components and definition of their responsibilities
  • Description of interface and event contracts
  • Design of the data model and data ownership
  • Description of key operational workflows, failure paths included
  • Agreement of integration contracts with external systems

Deliverables

  • Component descriptions and responsibilities: the basis for estimation and development planning
  • Interface contracts (API)
  • Data model and entity diagram
  • Technical event catalogue
  • Key operational workflows
  • UML diagrams: sequence, state, activity
  • Integration contracts

Stage 7 of 7  ·  Detailed design and oversight

07

Architecture oversight

Work

  • Regular architecture oversight
  • Review of team technical decisions against the target architecture
  • Resolution of contested decisions and alternatives
  • Analysis of deviations from agreed decisions and their consequences
  • Analysis of change impact on the architecture and the KPIs
  • Architecture input into release planning
  • Keeping the decision log and documentation current

Deliverables

  • Architecture oversight notes: traceability of decisions through implementation
  • Review findings on technical decisions
  • Register of deviations from the target architecture with a closure plan
  • Change impact analysis
  • Architecture section of the release plan
  • Current decision log and documentation
  • Scope and an upper bound on hours are fixed before each stage starts.
  • A stage closes when the documents are handed over and the agreed criterion is met.
  • Rights to the documents pass to you once the stage is paid, and confidential information stays confidential.
Dzmitry Pintusau

About me

Architect of enterprise solutions and digital products. I take a product from business goals to a working implementation.

Up to 30
people in the teams I have led as architect
4 regions
Europe, the Gulf, Asia and North America
More about me

Building solutions together

Discuss your case or request a proposal

Tell me what is happening and what prompted you to write now. We start with a conversation, and a proposal follows if it makes sense for both of us.

Dzmitry PintusauBusiness and solution architect

Enter your name.

Enter an email address I can reply to.

The situation, what you expect from me, and any deadline. A few lines are enough.

Tell me briefly what you need.

What would help most

Your message comes to me directly and is kept for up to 24 months. Privacy notice