About
Software built by a method you can verify
Silesian Solutions designs and builds software for B2B companies: panels, integrations, B2B shops and process automation. Quality is guarded by CI gates that stop a release when a requirement is no longer met.
- Operating since
- 2015
- Engagement model
- Fixed price for a defined scope, or a rate for ongoing work
- What stays with the client
- Code, tests, documentation
- Quality
- Verified by a CI gate
The scope of our work
Application security reviews
System boundaries and data flow, checked where something could actually be exploited.
Compliance built into CI
GDPR, WCAG and other requirements turn into a test that stops the release.
A direction for an existing system
Whether it pays to rewrite it, or rather keep developing it further.
Integrations and cloud sized to scale
Connections between systems with a rule for failure, infrastructure described as code.
Diagnosis before automation
How often a task repeats and how long it takes, before any tool gets picked.
Agents and model integrations
A narrow scope of action and a gate that stops work on an unexpected result.
Panels and web applications
Roles, statuses and a change history available from the browser, with no install.
B2B shops and data-fed catalogues
Prices that depend on the customer, data fed from external sources.
Where scope and price come from
Scope follows from what the system has to do, not from a ready-made price list. The first conversation settles which parts are necessary and which can wait for a later stage.
A fixed price covers work that can be described upfront: a known scope, known inputs, a clear end result. A time-based rate applies where the scope shifts during the work, for example when a system keeps developing after launch.
The estimate carries nothing nobody can justify: an oversized document, a meeting with no agenda, hours booked in as a buffer.
Who we build for
Deployments cover small and medium companies in B2B services and trade.
Scope and technologies used are described on the case studies page.
Three checkpoints in every project
Each of these checkpoints has its own condition: either it is met, or the work stops.
- Before the start
- Scope, stages and cost in one proposal
- During the work
- Every stage ends with a version that can be run
- At release
- A gate in CI stops the build when a requirement is not met
A proposal with scope, stages and cost is written before the first line of code, so billing is never a surprise. Every stage after that ends with a version that can be run and clicked. At release a condition decides, not an opinion: a requirement that a machine can check is either met, or the build stops.
From the technical proposal
What the scope excludes. It is the part of a proposal that gets read least often, and the part that settles an argument after a month instead of after a year. It is written with the same care as the list of what will be built.
What you get once the project is finished
- The code, the tests and the documentation stay with the client.
- The system can keep being developed further without the same vendor as a bottleneck.
- Requirements checked by machine work as a gate in CI, not as a one-off audit.
- Every stage ends with a version that can be run and checked.
Industries we work in
- Claims handling works against statutory deadlines, and every decision has to be reconstructible years later. Accountability matters here, not speed on its own.
- B2B wholesale runs on terms negotiated with each customer separately. The same item carries a different price for two buyers, and an error costs a trading relationship.
- Cybersecurity demands order in data that goes stale faster than in other industries. The credibility of a source weighs more here than its volume.
Questions that come up most often
Who is behind Silesian Solutions and what does the company do?
Silesian Solutions designs and builds software for B2B companies: panels for handling business processes, B2B shops, system-to-system integrations and automation for work still done by hand. Every deployment ends with code, tests and documentation on the client's side.
What does the first contact look like, and what does a client get before the project starts?
The first conversation ends with a technical proposal: what gets built, in what stages, what it costs and what falls outside the scope. Every stage ends with a version that can be run and looked at, not with a progress update.
How does Silesian Solutions guard software quality?
A requirement that can be checked by machine, such as accessibility, structured data or link correctness, turns into an assertion in the CI pipeline. The assertion passes or it stops the release.
Does Silesian Solutions have references, can I see how this works in practice?
Deployed systems are described in the case studies, together with their scope and the technologies used. Cyber Katalog is a service about the cybersecurity market, built with the same method.
What stays with the client once a deployment is finished?
Code, tests and documentation, not only access to a finished panel. The system can keep being developed further without the same vendor as a bottleneck.
What industries and company sizes does Silesian Solutions have experience with?
Small and medium companies in B2B services and trade. The systems described here run in claims handling, in an industrial goods wholesaler and in a service about the cybersecurity market.
Four pillars of the offer
Cybersecurity and compliance
Application security and compliance: code and architecture review, threat modelling, dependency hygiene, protective headers, GDPR and WCAG as automated CI/CD gates.
IT architecture and modernisation
IT architecture, system integrations, cloud infrastructure and CI/CD pipelines built for a company's actual scale. Technical advisory and modernisation of existing systems.
AI and process automation
Automation of repetitive processes, integrations with language models, agent tooling built on the Model Context Protocol, and data collection for reporting.
Custom software
Building systems to order: web applications and PWAs, admin panels, B2B shops, portals and searchable catalogues. Maintenance and development after launch.