Norbert Sowinski Freelance web developer

Web application development

A web application built around the way your work actually happens.

When a standard website is no longer enough, a web application can turn a manual process into a structured tool. I build dashboards, client portals, internal systems and SaaS features around real users and workflows.

The aim is not to collect features. It is to make the process easier to understand, reduce avoidable steps and leave a technical base that can evolve without becoming fragile.

From process to product

Turn a complicated workflow into a clear interface

The best applications make the underlying process easier rather than simply moving the same complexity onto a screen.

Centralise information

Bring the data users need into one place instead of spreading it across documents and tools.

Structure workflows

Roles, statuses and actions make responsibilities and next steps clearer.

Grow without a rewrite

A clean separation of concerns makes it easier to add features as the product proves itself.

Typical products

Applications for customers, teams and new products

The same technical foundation can support very different use cases. What matters is the workflow and the people using it.

The first version can stay deliberately focused on the priority features, then grow based on real usage and user feedback.

Dashboard

Bring key data and actions together in a practical operational view.

Client portal

Give customers secure access to documents, status, requests or account data.

Internal tool

Replace spreadsheets and repetitive manual steps with a tailored interface.

SaaS product

Build the first solid version of a web-based product with room for iteration.

What the project covers

Features should follow real usage

The application is shaped around the actions people need to complete, not a checklist copied from another product.

User accounts

Authentication, account recovery and account states suited to the product.

Roles & permissions

Access rules that reflect who can see and change each part of the system.

Data management

Forms, lists, filters and validation designed around the underlying data model.

Workflows

Statuses, approvals and business rules that mirror the process being supported.

APIs & integrations

Connections to payments, CRMs, external services or internal systems.

Responsive interface

A layout that remains usable when people need to work away from a desktop.

Process

Understand the workflow before choosing the architecture

Architecture decisions are easier once users, data and critical actions are clear.

  1. 01

    Users & requirements

    We identify the users, pain points, constraints and the minimum useful scope.

  2. 02

    Workflow & architecture

    Data, permissions, screens and integrations are mapped into a maintainable structure.

  3. 03

    Development & integration

    The core product is implemented incrementally and connected to required services.

  4. 04

    Validation & evolution

    Real scenarios are tested and the next priorities are based on what the product actually needs.

Architecture & technology

The technical stack depends on the product being built

Technology choices depend on functional complexity, integrations, data volume, hosting constraints, expected maintenance and the environment the application needs to fit into.

Depending on the project, I can work with React, Vue.js, Laravel, Node.js, Spring Boot and other technologies in my stack. The aim is to choose a coherent architecture, not to add frameworks without a reason.

Front end

React, Vue.js, Angular, Alpine.js, Inertia.js, HTMX and Tailwind CSS.

Back end

Laravel, Node.js, Express.js, Spring Boot and services suited to the project.

Data & APIs

Data modelling, REST APIs and integrations with external services.

Deployment

Docker and a deployment architecture adapted to the product requirements.

Connecting systems

A web application does not have to work in isolation

A web application can communicate with the tools you already use: CRM systems, payments, SaaS platforms, internal services or external data sources.

These connections reduce manual re-entry and allow the application to become part of your existing environment instead of creating another isolated tool.

An application can connect to:

  • • CRM systems;
  • • payment systems;
  • • SaaS platforms;
  • • internal tools;
  • • messaging services;
  • • automation workflows;
  • • external or internal APIs.
Explore API integrations

Existing application

Already have an application that needs to evolve?

Rebuilding an existing product is not always necessary. The work may focus on a specific feature, an integration, an interface or one part of the architecture.

An initial review helps understand the state of the code, the technologies in use and the problems you are facing so we can choose a realistic way forward.

I can help with:

  • • developing a new feature;
  • • improving an existing interface;
  • • adding or fixing an API integration;
  • • evolving roles and permissions;
  • • improving a workflow;
  • • restructuring part of the codebase;
  • • preparing for a larger product evolution.

Frequently asked questions

Questions about web application development

What is the difference between a website and a web application?

A website is mainly used to present content and guide visitors. A web application usually adds more business logic, data and interaction, such as user accounts, dashboards, advanced forms, workflows, roles or operations specific to the business.

What kinds of web applications can you build?

I can build dashboards, client portals, member areas, internal tools, business interfaces, SaaS modules and applications connected to APIs or external services. The scope depends on the process being digitised and the people who will use it.

Can you handle user accounts, roles and permissions?

Yes. An application can include authentication, several roles, permissions and personalised areas. Those rules are defined from the business requirements so each user only sees the features and data they are meant to access.

Can the application connect to my existing tools?

Yes. Web applications can connect to CRM systems, payment providers, SaaS platforms, internal tools and other services that expose an API or another suitable integration mechanism.

Can you take over an existing web application?

Yes. Depending on the state of the project, I can build a feature, improve the interface, fix a workflow, integrate an API or revisit parts of the architecture. A review first helps determine the right approach.

How does a web application project get started?

We start by analysing the problem to solve, users, data, business rules, integrations and priorities. Those elements define the first functional and technical scope before development begins.

Your project

Have a process that should become an application?

Describe who uses the process today, where information lives and which steps are frustrating or repetitive. That is enough to start shaping a useful first version.