We build a working prototype of your actual process. If it proves its value, we turn it into a production system.
Where does this fit you? Pick a situation →
A program that pulls information together, runs calculations specific to your company, or helps an employee reach a decision.
Data is collected automatically from several places, joined together, and turned into the result you need.
Part of the work a person does manually, over and over, is handed to software instead.
Pulling information out of documents, then classifying, searching and collating it into the form you need.
The core scenario, ready to show prospective customers and get a first reaction.
A journalist had an idea: upload an audio or video file, get a transcript, and produce a draft article from it.
Sequence: the idea was tested first. Only then was a product built.
Read the case study →An electricity trader had to gather production and market data from several sources, join it to customer information, and run the monthly calculations.
The point: software does not have to be universal — it can be built for exactly one company data flow.
Read the case study →A company director wanted his own system for call-centre work — routing requests, escalation, statuses and communication history.
Today: the choice is no longer so stark — you can start with a €1000 prototype and only then compare.
Read the case study →A forestry company used its own financial model to value properties and work out the maximum price it could pay.
The discovery: in some situations the flexibility of Excel was worth more to users than a new system.
Read the case study →One process. A working program you can interact with and show your team — not a slide deck, not a mockup.
That is a good result too. Maybe an off-the-shelf SaaS does the job better; maybe Excel is genuinely fine. Better to find that out for €1000 than after a project that has run for months.
You can finally try your own solution before you commission it.
Accrela is a Latvian software development company. We work on business situations where simply “writing a program to spec” is not enough.
Six questions before the first line of code
Result one prototype that answers all six questions
Our strength is connecting that business logic to real software development.
We can do more than describe what a solution might look like.
We can show it working.
It depends on how complex the idea is.
Sometimes one detailed conversation and a few clarifications are enough. Other times the bulk of the work is exactly that shared digging in — understanding how the process really works, where the exceptions are, and why people do things the way they do.
We do not try to artificially cut down the communication. The better we understand your work, the better the chance the prototype is not just technically functional but actually meaningful.
This process is often valuable to the client as well — having to explain your own idea forces you to put into precise words things that until then existed only as intuition.
No. An idea, a problem or a process you want to explore is enough.
On the first day we fix the initial direction and the boundaries, but we do not pretend to know all the answers in advance.
New details, exceptions and questions almost always surface while the prototype is being built. Part of the five days is exactly that: uncovering them and sharpening the original idea.
A working prototype that lets you try the core idea in practice and understand what to do with it next.
It may confirm your original intention, change it, or show that the problem should be solved a different way.
The source code we produce is handed over together with the prototype.
Once the project is paid for, the code we produce is handed over to the client.
You can carry on working on it with Accrela, with your own IT team, or with another development partner.
Yes. Depending on the situation we can work with real, anonymised or test data.
What matters is using material realistic enough that the prototype tests more than a theoretical scenario — that it shows how the solution behaves in your actual business context.
Yes. If a confidentiality agreement is needed before we discuss your process, your data or your business idea, we can put one in place before the work starts.
Then we have a far better basis for the next decision.
We can assess the scope, architecture, budget and development plan for a production version. For a small custom solution the next stage is typically 8–10 weeks.
The difference is that by then we are no longer planning a system purely from assumptions — the core idea has already been tested in working form.
No.
The prototype and its code stay with you. You can continue with Accrela, hand the work to your own team or another partner, or decide that further development is not needed.
Briefly describe the process, the problem or the idea. No technical detail needed.
We will be in touch shortly to discuss the prototype.