Skip to content
Capabilities

Dawid Bartczak / Working together

Custom business applications and dashboards

I design and build web applications around business workflows, from customer and sales tools to management interfaces. Explore BILO and InVault as examples.

Let’s discuss your project

When it makes sense

A custom application can help when an existing tool cannot support an important workflow and spreadsheets, messages and manual coordination get in the way. The starting point is a specific task: handling an order, configuring a service or handing work to the next person. That determines what the system needs to do.

Possible scope

An interface for everyday work

Data views, search, statuses and actions for the right users. The scope follows who uses the application and what they need to accomplish.

The complete workflow

Connecting the interface, business logic and data. Alongside the normal path, the system needs to account for errors, corrections and administrative actions.

Integrations and launch

Connections to the necessary services, environment configuration and verification of agreed scenarios. API access and maintenance requirements inform the choice of solution.

Where we start

We start with the current workflow and criteria for correct behaviour. Then we choose the smallest useful scope, design the data and screens, and investigate difficult integrations. The first version should support a real workflow; further features follow from using it.

Examples of my work

In BILO, I connected ticket purchasing, payments, organiser tools and event operations. InVault uses a web interface to configure data sources and schedules and monitor backups. The project pages explain my contribution and technical decisions.

Before we begin

Do I need a complete system straight away?

Not always. You can start with one workflow and a limited set of users. If configuring an existing tool solves the problem, it is worth considering before building an application.

What determines the estimate?

The workflows and user roles, the state of the data, integrations and deployment requirements. An example of one task is more useful at the start than a long list of technologies.

Describe your project

Describe one workflow you want the application to support. Who uses it, where is the data today, and what gets in the way?

Email Dawid