Service · Internal business apps

Internal business apps: replacing Excel, records, workflows and approvals

Ignition Labs builds custom internal business applications – tools that replace shared Excel spreadsheets, paper forms and manual email forwarding.

They are meant for small and medium-sized companies in Slovakia whose processes have outgrown spreadsheets, but for whom off-the-shelf software does not fit or is needlessly complex.

We handle order and customer records, approvals, field data collection, reporting and connecting systems that do not talk to each other today.

We design the app around how your company actually works, agree the scope and price in writing up front, and deliver the first working version in 21 days for the agreed scope.

Discuss my project Frequently asked questions

When an internal app makes sense

Most companies start with a spreadsheet and get by with it for a long time. An internal app makes sense once several people edit the sheet at the same time, data arrives by email or chat, and nobody is sure which version is current.

A shared Excel file where data gets overwritten and changes get lost
Approvals by phone or email with no overview of where a request is stuck
Field data (photos, measurements, checklists) retyped by hand into a computer
Management reports assembled by hand from several sources every month
Two or three systems with data carried between them by copy and paste

What we typically build

An internal tool from Ignition Labs is an app for records, orders, bookings or approvals, tailored to the specific way your company works. Users log in, each sees and may change what belongs to them, and the history of changes is traceable.

Records of orders, purchase orders, customers and assets
Approval workflows – orders, invoices, leave, changes
Field data collection on mobile, including photos and checklists
Planning, bookings and capacity allocation
Reporting and overviews from the data the app collects continuously
Connections to accounting, e-shop, warehouse or calendar via API
User roles and permissions matching the company structure

How to replace Excel with an app without losing data

Replacing Excel is not a matter of turning a table into a form. We first go through which columns and sheets are actually used, who changes them and what is produced from them. From that we define the main scenario of the first version – for example creating an order, moving it between states and an overview of open orders.

We transfer your existing data into the app; if it is inconsistent, cleaning is a separate piece of work that we name up front. We keep an Excel export so you lose nothing and can keep processing data in the tools you are used to.

Off-the-shelf software or a custom app

If your process is standard, off-the-shelf software is often the more sensible choice and we will tell you so. A custom app makes sense when the way you work is your advantage, when ready-made tools force people to work around the system, or when you need to connect several existing systems into one whole.

We deliberately keep the first version small: one main scenario that brings relief soonest, and only then extensions based on what real use shows.

How the collaboration works

Four steps from the first conversation to delivery of the first working version – the same for every service.

STEP 1
We clarify the goal
We go through the problem, the users and the outcome the first version should deliver.
STEP 2
We agree on scope and price
We define what will be part of the first version, what stays for later, and how delivery will work.
STEP 3
We build and show progress along the way
We go through the development together so that unclear points and feedback can be caught early.
STEP 4
We test and hand it over
We verify the agreed user scenarios and prepare the handover according to the agreed scope.

We deliver the first working version in 21 days. The timeline applies to the scope of the first version agreed in writing beforehand; larger projects are split into stages.

Price and timeline

We have no flat price list. The price follows the scope we define in step two – the number of user scenarios, roles, integrations and operational requirements. You receive the exact price, timeline and handover terms in a proposal before work begins.

What makes up the price of a first version

Frequently asked questions

How much does an internal business app cost?

The price follows the scope we define together before work begins. It is driven mostly by the number of user scenarios, the number of roles and permissions, integrations with existing systems and data migration. You receive the exact price and timeline in a proposal.

How long does it take to replace Excel with an app?

We deliver the first working version for the agreed scope in 21 days. Transferring and cleaning data from spreadsheets is a separate piece of work we name up front; larger briefs are split into stages.

What happens to the data we have in Excel?

We transfer it into the app. If it is inconsistent, we agree who prepares and checks it. We keep an Excel export in the app, so you can keep working with the data outside it as well.

Will the app work on mobile?

Yes. We build internal apps as web applications usable on mobile and desktop without installation, which matters especially for field data collection.

Can you connect the app to accounting, an e-shop or a warehouse system?

Yes, connecting systems is one of our core areas. What is possible depends on the interfaces and access the given system provides – we verify that when defining the scope.

What running costs arise after launch?

The app needs to run somewhere and often uses third-party services – hosting, a database, email or AI services. These costs are billed according to the providers' prices and depend on usage. You get a specific estimate when we agree on the scope.

What if requirements change during development?

We note them down and decide together whether they belong in the first version or in a later stage. If a request changes the agreed scope, we agree a deadline and price for it before we start working on it.