Tomasz Kłoś · Business-system analysis and solution design

I design the system before anyone writes code.

Business-system analysis, scoping and RFPs, solution design. Nine years across automotive, aerospace, insurance, telecom and healthcare for clients in the UK, the US and Germany.

Let's talk · 30 min See the packages →

C4 · Level 2 · Containers example / hld.md

Which of these is you?

You are commissioning a system

You know the problem you want solved, but there is no scope, RFP or design yet. You get a document a software house can answer with a concrete proposal.

Packages C and E →

You have a proposal to check

A vendor sent a quote, or you drafted an RFP, and you want a second pair of eyes before you sign. In two or three days you get the gaps, risks and questions.

Package A →

You are building with a team

You have the team, but nobody to own the backlog, roadmap and documentation where business meets engineering. I join for months, not weeks.

Package F →

How I work

Three steps, from problem to design

1 / 3 · Context

Understand

Workshops, process maps, goals and metrics. Before anyone says “system”, we know which problem we are solving and what it is worth.

2 / 3 · Containers

Define

Scope in / out, requirements, risks, estimate. A document a vendor can answer with a proposal and a board with a budget.

3 / 3 · Components

Design

C4, services, domain and data model, integration contracts. A technology-independent design the team starts coding from, not guessing from.

Packages

Four ways to work with me

Prices after a 30-minute call: they depend on scope and market. Every package ends with a document you can hand to a vendor or a team.

A 2–3 days

Second opinion

Holding a vendor proposal or a drafted RFP? Before you sign, I review the scope, assumptions and risks through the eyes of someone who has built such systems.

What you get

report on scope gaps and unclear assumptions
question list for the vendor before you negotiate
technical and schedule risk assessment
recommendation: sign, clarify, or redesign

“His understanding of technical issues combined with his meticulous analysis of business aspects made his work exceptionally detailed.” Michał Czerwonka, .NET Software Engineer

C 3–5 weeks

Scoping and turnkey RFP

From the first workshop to vendor selection. You get a document a software house can answer with a concrete proposal, and a way to compare those proposals.

What you get

stakeholder workshops, process maps (BPMN)
goals, metrics, in / out of scope, high-level requirements
RFP document and bid evaluation criteria
vendor Q&A support, bid comparison, recommendation

Variant B: discovery and scope only. 2–3 weeks, without the RFP document and bid evaluation. Ends with a scope statement, a seed backlog and a risk register.

“A great help in a pre-sale process. His analytical skills, deep knowledge of the IT topic, smart questions and attention to detail consistently ensured that our projects were well-defined.” Margarita Golubeva, Design and everything around IT

E 3–6 weeks

System design (HLD)

You have a scope but no team yet, or the team is waiting for a design. You get technology-independent documentation you can start development with or price with a vendor.

What you get

C4 diagrams: context and containers
service decomposition, domain model (DDD), data model
integration contracts, non-functional requirements
release plan and first-phase backlog
add-on: documentation prepared for AI coding agents

Variant D: estimation and feasibility. 1–2 weeks. Independent three-point estimate, assumptions, dependencies, risks, budget and timeline range for a team.

“He is able to architect very complex systems with technical team to a granular detail, uncovering scenarios and mitigations that would otherwise be missed.” Syed Ammar Ahmad, Product Growth Specialist

F 2–5 days a week

Technical Product Owner, embedded

I join your team for months, not weeks. Backlog, roadmap, refinement, documentation and the technical decisions where business meets engineering. Experience with microservices, TM Forum standards and healthcare platforms.

What you get

analysis of the business problem and its decomposition into requirements the team can implement
owning the product backlog and roadmap
stakeholder workshops and refinement with the team
technical documentation and release materials
risk management and cross-team dependencies

“Tomasz is an exceptional Product Manager. He's thorough and imaginative, and above all else, customer focussed.” Paul Charlesworth, Head of SDN & Customer-Facing Innovation, SYNLAB International

9 recommendations on LinkedIn

“He has a remarkable talent for bridging the gap between technical teams and business stakeholders. He's able to clearly articulate complex technical concepts to non-technical audiences while ensuring that the technical implementation aligns perfectly with the business requirements.”
Tomasz JanczewskiSenior Software Developer, NG Logic Read all on LinkedIn →

Why me

Most analysts stop at the requirements list. I go further: I decompose the system into services, model the domain and the data, and specify integration contracts. What I hand over is ready for a development team, for a vendor answering an RFP, and for the AI agents that now write part of the code.

Have a project, or a proposal to check?

Thirty minutes is enough for me to tell you which package makes sense and how long it takes. No commitment.

Let's talk · 30 min