About
About the company
What we do
Silesian Solutions builds the systems a company uses every day: a panel for handling claims, a B2B shop with orders, an application that runs in the browser without installation, a catalogue with search. Alongside them, integrations between the systems a company already runs, and automation of work still done by hand. The code, the tests and the documentation stay with the client.
Who it is for
The deployments were built for small and mid-sized companies, for a non-governmental organisation and as in-house products. The industries these systems run in: claims handling, B2B wholesale ordering, cybersecurity and digital education. Every deployment is described in the case studies, together with its scope and the technologies used.
How the work runs
The first conversation ends with a technical proposal: what gets built, in which stages, what it costs and what the scope excludes. Every stage ends with a version that can be run and looked at. Requirements a machine can check - accessibility, page weight, structured-data correctness - become tests in the CI pipeline and stop a release before the change reaches production. This site is built exactly that way. Billing is a fixed price for a defined scope, or a time rate for continuous work.
What we do not do
No round-the-clock on-call and no monitoring with a guaranteed response time. No penetration testing and no compliance certificates - that is the work of an accredited auditor. No training of proprietary models and no maintenance of Kubernetes clusters. A boundary stated at the start is cheaper than a surprise mid-project.
Services
Three service pillars
Quality and compliance in the pipeline
Legal, SEO, accessibility and security requirements become automatic gates in CI/CD that fail the build instead of ageing quietly in a document.
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 agent systems
Language model integrations, agent tooling (MCP), process automation and data analysis. A scope sized to what a small team can actually maintain.
FAQ
- What business goals should the IT project achieve?
- Early conversations focus on understanding the client's strategic business goals. Process optimisation, wider service availability, automation or expansion into new markets - the technology gets matched to the actual need. That gives the project technological value plus a real effect on growth and competitiveness.
- What functionality should the system include?
- Settling the key functionality is one of the first steps of project analysis. Early discussion identifies the features that answer end-user needs, support internal processes and deliver real value. Advice covers which components are worth building first and which can wait for a later stage of the system's development.
- Are there specific technology preferences to account for?
- An initial meeting is a chance to note the technologies or platforms already in use. The stack stays flexible: React, Next.js, TypeScript, Node.js and PostgreSQL are all in active use, alongside containerisation and cloud technologies. Advice on the best stack accounts for future scalability, security and maintenance cost.
- Is the project a new system or a modernisation of an existing one?
- Distinguishing a greenfield project (built from scratch) from a brownfield one (modernising or integrating existing solutions) matters from the first conversation. It shapes the scope, the potential risks and the cost. Either way, a full analysis and a transparent approach point to the most cost-effective path.
- How large will the system be and how many users will it have?
- The discovery stage settles the expected scale of the project: the number of users, the volume of data processed, the required availability, responsiveness and resilience. That analysis is what a suitable architecture, an infrastructure plan (on-premises or cloud) and a cost estimate for maintenance and further development get built on.
- What cooperation model fits the project?
- The possible cooperation models come up in the first conversations. A fixed-price model fits a closed, defined scope; time and materials fits ongoing work. The choice depends on the project's pace, the scope of responsibility and the client's own availability.
- How are project stages and the schedule planned?
- Transparency and predictability matter most here. The schedule is worked out together with the client, covering project stages, milestones and the time needed for testing and deployment. Project management tools such as Jira, Asana or ClickUp keep progress visible and make it possible to react to changes quickly.
- Will the project need to integrate with other systems?
- Early conversations cover the existing systems the project should integrate with - ERP, CRM, payment systems, message queues, external APIs or other cloud services. Identifying integration requirements early cuts the risk of incompatibility and limits later deployment costs.
- What are the data security and regulatory compliance requirements?
- Security comes up from the first stages of a project. The required level of data protection, GDPR compliance, WCAG requirements and other industry standards get settled early. Systems are designed secure by design - data encryption, multi-level authorisation, backup policies and regular security testing. External auditors and cybersecurity specialists get brought in where the project calls for it.