One system instead of ten spreadsheets.

Jobs, stock, approvals and reports in one place. The system adapts to you, not the other way round.

Preview of the video about enterprise systems

What does a system of your own involve? Play the video and see how one comes about here.

Marek Kejda, founder

When a system of your own pays off

Not every company needs one. But almost everyone who writes to us is in one of these three spots.

Spreadsheets no longer carry it

There are fifteen versions of the file and the one person who knows which is current is on holiday.
The data sits in five tools

The same number gets retyped from an e-mail into the stock list and from there into accounting. Every retype is a place where an error is born and later hunted.
The box dictates how you work

A finished product bends only so far. Past that the company starts bending around it, and people quietly keep a spreadsheet of their own beside it.

When we will talk you out of it

Sometimes buying something finished, or doing nothing at all, is faster and cheaper. We say so straight away, even when it costs us the job.

It still fits in one spreadsheet

A handful of jobs a month and two people who know what the other is doing. A spreadsheet is enough there, and a system would cost more than the problem it solves.
A finished product fits

If there is a product for your field that covers nearly everything, we will say so. We will help you set it up, connect it and tune it, but we will not rewrite it.
The process is still being found

When it is not yet clear inside the company how the work should go, software will not decide it for you. Agree on the process first, then it is worth writing down.

How we build a system

Three steps. At each one you know what you get and what we need from you.

We map the operation

We sit down with the people who actually do the work, not only with management. Out of it comes a description of the processes and the order in which the system should take them on.
We build the core

We start with whatever eats the most time. You see it running as we go, not only at the end, so the direction can still change while changing it is cheap.
We connect it and run it

We add the connections to the surrounding software, take over the old data and keep looking after it. The system then grows with the company as the work grows.

We connect it to what you already have

A system is not meant to replace everything. Accounting, the e-shop or payroll can stay exactly where they are. If they have an interface, we connect to it. If they do not, we agree on exchanging files.

Most things that cannot talk on their own can be made to. Before we commit to a connection, though, we always check that the interface exists and what exactly it can do. Promising something we have not seen pays off for nobody.

Pohoda and Money S3 accounting
ABRA Flexi and ABRA Gen
Helios, SAP and other ERPs
Fakturoid and iDoklad
E-shops built on Shoptet
WooCommerce and Shopify
Bank APIs: Fio, ČSOB, KB
GoPay and Comgate payments
ARES company register
Czech data boxes
Attendance and shift planning
Payroll systems
Warehouse and barcode readers
Carriers: Packeta, PPL, DPD
EDI document exchange
Microsoft 365 and Outlook
Google Workspace
Shared calendars
CRM: Raynet and Pipedrive
GPS and trip logs
Phone exchanges
Slack and Teams
SharePoint and Google Drive
Custom APIs and webhooks

A system that can think as well

We bring artificial intelligence in where it saves work: it reads a document, finds in your data whatever you ask for in your own words, drafts the reply a person only has to approve.

What we do with AI

An interface people can work in

We draw the interface ourselves, and as carefully as the logic underneath it. Every screen shows what is done on it most often, and people learn it in an afternoon rather than in a training session.

How we do design

What we can build together

Data and roles

One record Jobs, stock, people and documents on a single data model.
Roles and rights Everyone sees and changes only what they should.
Change history Every record shows who changed it, when and to what.
Attachments on the record Documents and photos on the job, not scattered across e-mails.

Daily work

Forms that follow the process Only the fields that make sense at that step.
Approvals Who approves, what is missing and where it is stuck.
States and queues You see what is waiting on you and what on everybody else.
Notifications In the system and in your e-mail when something moves.

Overview

A view for management The numbers you ask about every week on one screen.
Reports They put themselves together and go where you say.
Exports To a spreadsheet or a PDF when something has to leave the house.
Search Across the whole system, not separately in every agenda.

Running and growing it

Hosting It runs with us or with you, whichever suits you.
Backups and restores When we run the system, we test restoring from the backup regularly.
Changes while it runs The company changes and the system with it. We handle changes as they come.
The code is yours You can take the source code and the data with you at any time.

What you ask most often

What does a system like this cost?

It depends on what it has to cover. We never open with a number off the top of our heads: first we draw a line around the first step, price that, and only then do you decide. A system can be built in parts, so it does not all get paid for at once. We start from €1,600.
How long does it take?

The first usable part is usually running within weeks, not months. We build in pieces: as soon as one piece makes sense on its own, it goes live and we carry on.
What happens to the data we already have?

We take it over. From spreadsheets, from the old system and from exports. Most of the time it has to be cleaned up on the way, and that we do together with you: only you know what is still valid.
Who owns the system?

You do. The source code and the data are yours and you can take them with you. We do not hold anyone by making it hard to leave.
What if people will not use it?

That is the most common reason systems die. Which is why we bring the people who will work in it into the design, and build it to take work away from them rather than add it. Training and changes after the first weeks of use are part of the job.