Custom web applications

Web application and internal portal development

Database applications, internal portals, admin interfaces, APIs and integrations that solve a specific business process. The design includes permissions, validation, testing and secure operation.

Let’s talk Indicative pricing

Internal applications and portalsAppUI · API · Ops

Internal portals

Records, approvals, bookings, document management and other processes with a change history and permissions based on user roles.

APIs and integrations

Connecting existing systems, secure data exchange, input validation, retrying failed requests and monitoring of the integration.

Deployment and operation

Databases, containers, CI/CD, TLS, logging, monitoring and backups.

What each plane carries

Portals with change history and permissions

Secure data exchange and validation

Database, containers, CI/CD and backups

An app is defined as much by what it connects to as by its own screens. The interface people use, the data plane with APIs and integrations, and the running platform - database, containers, CI/CD, TLS, logging, monitoring and backups. The operating solution grows together with the development, not after it.

A web application must match the real work of its users.

First we describe the roles, data, decision points and exceptions together. I limit the first version to a coherent workflow that can be deployed and validated, instead of long development of features without feedback.

When a web application is better than another spreadsheet

A custom application makes sense when data is used by several roles, history needs to be kept, validation is required or automated follow-up steps are needed, and ordinary office tools are already leading to more errors.

Several people edit the same data with no clear history
The process requires approvals, permissions or automatic notifications
Information is copied by hand from forms into internal records
The company needs a single interface on top of several existing systems

How does custom web application development work?

In practice

Web application development starts with a description of the work process and the roles involved, not a list of screens. Together we establish who enters and changes data, which rules are checked, which outputs are important and which systems the application connects to. The first version covers the most valuable end-to-end scenario and makes it possible to validate real use before the full scope is built out. The technical solution includes the data model, authorisation, input validation, an audit trail of important changes, automated tests and versioned deployment. Before launch, monitoring, database backups, recovery and secrets management are put in place. The result should be a maintainable tool with documented operation, not just working forms with nobody responsible for the data and future updates.

What to consider when deciding

An internal portal or integration pays off when it connects a recurring process, eliminates duplicate record-keeping or gives specific roles access to the right data. For an infrequent task, adjusting an existing system may be enough; for a unique process, a custom application is clearer in the long run than a chain of spreadsheets and manual exports. The price depends on user roles, the number of states, integrations, data migration, availability requirements and the quality of the specification. The analysis stage therefore separates essential features from ideas better suited to later development.

What a web application can include

The scope follows from the work process and the sensitivity of the data. The first delivery should be small enough to validate quickly, yet complete enough for safe real-world use.

Analysis of roles, processes and data
Responsive user and admin interfaces
Database, validation and change history for audit
APIs and integration of external services
Authentication, permissions and security
Testing, deployment, monitoring and backups

Custom web applications - what to prepare for the initial diagnosis

Prepare one typical process, the user roles, sample non-production data, approval rules and the outputs that are currently produced by hand.
For integrations, you will need the API documentation, the owner of the other system and information about limits or a test environment.
Mark personal and sensitive data, the required change history and the retention period.
It also helps to decide who will take over the application, manage users and set priorities.
The first stage can then be defined as a verifiable process instead of an isolated list of screens.

The exact scope and price can only be set based on the environment, the available information and the impact of a potential outage. The full process from first contact to handover is described on the How I work page.

A usable application with operations that can be handed over.

Depending on the scope, I hand over database migrations, environment configuration, a description of the deployment, operational access and the backup procedure. Further development can then build on validated real-world use.

A coherent first version that real users can validate
Roles, permissions and validation of important inputs
Testable code and versioned configuration
Documented deployment, monitoring and data recovery

Indicative prices from the price list

Online shop or web application: from CZK 90,000priced individually by scope
Website management and monitoring: from CZK 400/month

Full price list

In the client’s words

“Above all, we appreciate his matter-of-fact and easy-to-understand explanation of how the individual services work.”

Translated from Czech.

KK-FinTax účetnictví s.r.o.Case study

Let’s talk

Frequently asked questions - Web application development

How long does it take to develop a web application?

It depends on the number of roles and processes, the integrations and the sensitivity of the data. I first define a coherent first version and the risky parts; only from these can a realistic estimate and order of stages be prepared.

Can the application be connected to our current systems?

Yes, as long as they provide a usable API or another secure way of exchanging data. Before the design, I check the available documentation, permissions, limits and behaviour on errors.

Who will run the application after launch?

It can run on the client’s infrastructure or with agreed hosting. The agreement covers responsibility for the server, updates, monitoring, backups and incident handling, so that operations are never left without an owner.

Not sure where to start? Describe the situation.

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.