Internal tools, forms, integrations and web applications that solve a specific operational task. From data and interface design to secure deployment, monitoring and backups. I work remotely with clients across the Czech Republic.
A description of the process, data, integrations and error states.
Back-end and user interface development, input validation, automated tests and documentation of key decisions.
Containerisation, Ansible, CI/CD, reverse proxy, TLS, database, logging, monitoring and backups as part of the application, not as an add-on after launch.
I clarify the inputs, users, permissions and expected output. This makes it possible to separate the essential functionality from ideas that would only make the solution more expensive or harder to maintain.
Custom development makes sense when a recurring process cannot reasonably be covered by an available product, or when re-keying data by hand causes errors and regularly takes up people’s time.
Three typical situations in which custom software makes sense. These are illustrative examples, not references from specific clients.
Custom software pays off when a recurring business process cannot reasonably be handled by an off-the-shelf tool, or when re-keying data by hand causes errors and delays. The first step is not programming, but describing the users, inputs, decision rules, outputs and exceptions. From that comes a verifiable scope for the first version, a data model and an integration design. Development includes tests, version control, secure handling of credentials, automated deployment and operational documentation. For a web application, monitoring, backups and a way to roll back a failed change are addressed at the same time. A good solution removes a specific bottleneck and can be developed step by step; it is not a large project built on untested assumptions.
I don’t design an open-ended system. The first version covers one complete process from input to output, so that real users can work with it.
Further roles, reports and integrations are added once the first version has been proven, as separately agreed extensions.
Operation after launch – hosting, monitoring and maintenance – is agreed separately and has its own ongoing costs.
Two completed projects from my references. They show data integration, forms and operation; they are not large internal information systems.
I confirm the price of the first version before work starts. It depends on the roles, data, integrations, data migration and availability requirements.
We go through the situation and I tell you whether a custom solution makes sense and in which direction. It is not a detailed specification or a finished design.
With a clear brief, it is enough to refine the scope. With an unclear one, we start with a paid analysis or a small prototype, the price of which I confirm in advance.
You receive the price and scope of the first version. Extensions and operation after launch are agreed separately.
The amount for an e-shop or web application is not a minimum for every integration. I price smaller integrations or changes to an existing system according to the defined scope. I am not registered for VAT.
The best starting point is not a long list of features, but one specific work scenario from input to result. Prepare a sample of your current spreadsheets or forms, user roles, decision rules, required outputs and the systems the data should be exchanged with. Mark any sensitive data and the change history you need to keep. An estimate of how often the process runs and how much time it takes today is also useful. Based on this information, the first usable version can be separated from features better suited to later stages.
How to prepare a brief for an application or integrationBefore commissioning custom development, it is worth comparing configuring an existing service, simple automation and a full application. An off-the-shelf product is usually cheaper if it supports most of the process and does not require risky workarounds. Custom development makes more sense for unique know-how, specific integrations or repetitive work with measurable savings. The first version might, for example, cover one continuous flow, from receiving a form through checking the data to passing it into an internal record system; further roles and reports are added only once it has proved itself in practice. Before work starts, ownership of the source code, dependency licences, the repository location, access to infrastructure and the scope of documentation are agreed in writing, so that the handover does not depend on a vague verbal agreement. The price depends on roles, data, integrations, migration and availability requirements, which is why it is useful to start with a paid analysis or a small prototype.
The handover includes the source code, the production configuration and a description of the deployment, according to the agreed scope. The aim is a solution with no hidden manual steps and no dependence on a single undocumented environment.
Ownership of the source code, the licence, where the repository is hosted and access to the infrastructure are agreed in writing before work starts. I can take over further operation and development myself, or someone else can continue from the documentation.
Not every project needs every layer. The architecture is chosen according to the data, integrations, number of users and how the application will be run.
A description of the process, data, integrations and error states. A design for the first usable version that can be tested with real users.
Back-end and user interface development, input validation, automated tests and documentation of key decisions.
Containerisation, Ansible, CI/CD, reverse proxy, TLS, database, logging, monitoring and backups as part of the application, not as an add-on after launch.
Custom software development starts with a description of the business process, users, data and integrations. This is followed by the design of the first usable version, implementation, testing, secure deployment and, as agreed, monitoring, backups and further development.
First we describe the workflow, users, inputs, permissions, integrations and expected output. From that comes the scope of a first usable version that can be tested with real users.
Yes. Custom development can include integrating external services and APIs, data validation, handling of error states and monitoring whether the data exchange works.
Yes, depending on the agreed scope. I can deliver containerisation, CI/CD, a reverse proxy, TLS, a database, logging, monitoring, backups and deployment documentation together with the application.
A few sentences about what is not working or what you need are enough. I will reply with a suggested first step and an estimate of the scope.
Prices of the core services are listed in the indicative pricing.