01
Analysis
2 to 3 weeksWe talk to the people who actually do the process, not only to those who commission it. We map the systems, verify what can be read from them, and name the decision the new view is meant to improve.
How we work
From the problem
to a solution without risk.
We do not ask for trust up front. We work in steps, and after each one you can say whether we continue — and the first step cannot break anything, because nothing is written.
The sequence
Four steps.
After each one, you decide.
The durations are indicative for a first module of moderate complexity. A firm estimate follows the analysis — not before, because before that it would only be a guess.
02
Design and prototype
2 to 4 weeksWe show a clickable version before development starts. You see a concrete screen in your own vocabulary. Comments at this stage cost a fraction of what they would cost later.
03
Pilot
4 to 8 weeksOne module, one department, real data, read-only. At the end we evaluate whether it delivered what it was supposed to — including the option to conclude that it did not.
04
Growth
ongoingWe add further sources and roles in your order of priority. Writing or approvals are switched on only when you ask for them.
Principles
What we hold to,
even when it slows the project.
These rules have complicated our schedule more than once — and it has been worth it every time.
The source always wins
If our number disagrees with the one in accounting, the mistake is ours. The source system is the authority and we never try to “correct” it.
Nothing is written without agreement
Read-only is the default state, not a temporary restriction. Writing is a separate decision with its own brief and its own testing.
We say the uncomfortable things
If a module turns out not to be worth it, or an interface does not exist, you will hear it from us before you hear it from anyone else. We would rather lose the work than the trust.
We adopt your permissions
We do not decide who may see what. We take the rules that already apply in your systems and stay within them.
What we need
Your side
of the work.
Projects that stalled almost always stalled on these three things — never on the technology.
01
One person on your side who decides on content and has the time to do it.
02
A contact at your accounting software vendor, in case we need their consent or their interface.
03
Access to test data. It need not be production — a copy or a sample is enough for design.
Who is behind it
Firemné riešenia is run by
idea machine s.r.o.
There is no anonymous brand here. The service comes from a Slovak software company based in Brezno — one that designs and builds the software itself rather than brokering it.
Twenty-five years in IT
A quarter of a century of building software and running IT projects. Most of the problems that hold a project up we have already met once — which is why you hear about them in advance rather than in the minutes of a meeting.
Development, AI and project leadership
Alongside integration work we build web and mobile applications and tools based on AI. Where it helps, we also take over running the project, including the dealings with your existing vendor. More about the company at ideamachine.sk.
Continue
Start with one process
Tell us which numbers
take you longest to find.
In the first consultation we go through your systems, establish what can actually be read from them, and propose the one view that saves you the most work.
Book a consultation →