Applications and AI · 01

Custom business applications built around how your team works.

When you copy the same data between spreadsheets, messages and off-the-shelf software, we build a single application around your process: every task has an owner and a status. We add AI where it helps with a specific step.

01

When a custom application makes sense

For teams that re-enter the same data, lose track of decisions or cannot see the status of a case. Below are three illustrative use cases.

Managing quote requests

A single form collects requirements, an account manager adds the cost calculation and the responsible person approves the quote. Missing information and the change history are visible. Optional AI prepares a draft for review.

An operations dashboard

A work order moves through agreed stages, with an assigned owner and all its attachments. The manager can see overdue tasks, while each team member knows what is needed for the next step.

An internal team portal

Requests, forms and information from several tools are available in one place. Access depends on the user's role, and changes are sent to the agreed source system.

02

Systems we have built

Two systems we designed and continue to develop for specific teams, and our own BI system for companies. We do not name the clinic.

Kreator Formy - a platform for a personal trainer →

The trainer prepares training and diet plans and runs the session calendar and questionnaires. In the phone app, the client sees their plan, records measurements and progress photos and chats with the trainer. Plans can be downloaded as PDF.

Dental clinic - administration and stock

One platform organises costs and the invoice workflow, payroll and bank statements. The stock module tracks materials from the purchase document to the stock level. Access to data depends on the user's role.

Dental clinic - AI modules

AI-assisted analysis of X-ray images to support the dentist, call recordings transcribed with speaker separation and analysed, BI dashboards with an AI assistant and a knowledge base for the team. Some of the models run on a local GPU server.

Our BI system for companies using an ERP

Our own analytics system, deployed on the company's server. It copies data from the ERP system - read-only - and uses it to calculate the profit and loss statement, a budget with versions and approval, cash flow from open items, receivables and payables by age, costs, sales, purchases, stock, and production with a material plan. It also includes financial statements, a pivot table and an AI assistant that turns a question asked in Polish into a data query - by default on a model running locally. It runs in the browser, including on a phone.

03

What the agreed scope includes

Screens and workflow logic

We design views, forms, statuses and validation. We define who can read, change and approve information, including when unusual situations arise.

Data connections

We agree on integrations, imports and error handling. The scope of a connection to an ERP, CRM or another tool depends on its interface and the permissions available.

Launch and handover

We prepare the agreed environment, user documentation and deployment instructions. The contract sets out access to the code, licences, updates and ongoing maintenance.

04

What to prepare for our first conversation

Describe one process: who starts it, what information they collect and how they know the case is complete. Anonymised forms, sample spreadsheets, a list of current software and examples of where work gets stuck will help.

We will need a decision-maker and a user who knows the exceptions that arise in daily work. We will also agree on system access, data storage requirements and infrastructure constraints. Confidential material should only be shared through an agreed channel.

05

From your process to a pilot version

  1. 01

    Define the boundaries

    We describe the process, users, required data and acceptance criteria. We separate the first version from ideas for later development.

  2. 02

    Review the screen designs

    Together, we walk through a typical case and its exceptions. Users assess whether the layout fits the way they work.

  3. 03

    Build the selected workflow

    We connect the agreed features and integrations. The pilot uses an agreed data sample and a selected group of users.

  4. 04

    Accept the result and plan development

    We check the criteria, fix the issues found and agree on the conditions for launch. Further features are informed by actual use of the application.

06

How we check that the application works

A user should be able to complete an agreed case from start to finish. We check data accuracy, role permissions, change history and behaviour when an integration fails. We also test resuming an interrupted task and using the agreed devices.

If the aim is to reduce manual work, we compare how the task is carried out before and after the pilot using the same sample. We assess the result against agreed criteria; we do not assume savings or a return on investment in advance.

07

What affects the cost of an application

The number of roles and workflows, integrations, data migration, availability requirements and test coverage matter more than the number of screens alone. We define development, infrastructure, licences and maintenance separately. We propose a cost and schedule once we understand the scope.

FAQ

Frequently asked questions

Does the application have to use AI?

No. Forms, rules, workflows and integrations are often enough. We add a model when a specific task involves working with language and the quality of its output can be checked.

Do we need to replace our current system immediately?

Not necessarily. The application can complement your existing tools. We first check data access and integration options, then determine which changes are needed.

Who receives the code and documentation?

Before work starts, we define how the code will be handed over, the documentation provided, the rights to develop the solution further and the licences of its components. These arrangements form part of the contract.

Can we start with a small scope?

Yes. We select one complete workflow that can be assessed and accepted with users. We price subsequent stages according to the agreed development scope.

How does custom software differ from an off-the-shelf program?

An off-the-shelf program has its own predefined way of working. Custom software is built around your process and can complement your existing tools instead of replacing them. In return, it requires an agreed scope, testing and a maintenance plan.

→

Related services

Tell us about a process that needs a better tool.

Describe who works with the data, which software they use and where the problem occurs today. We will use this to define a practical starting scope.

Prefer email? biuro@entrada.pl