We digitalise how a company operates — stock, sales,
fiscalisation and accounting held in one system instead of
five. Then we stay on to keep it running.
Three businesses whose working day runs on software
we built — safety compliance, a car parts retailer
and a hospitality business with three locations.
We design, build, launch and keep
software running.
Most of what we build replaces something that already works —
a spreadsheet, a counter book, five systems that do not speak.
That is a harder brief than starting from nothing, and it is
the one we take. Launch is the middle of the job, not the end
of it.
Services
What we take on, and how far we take it.
Most projects start as one of these and end up as three.
Taking a company off paper and spreadsheets: mapping how it actually operates, then building the system that runs it end to end. This is most of what we do, and the rest of this list is usually part of it.
Includes
Process mapping
Custom ERP
Rollout
Training
Stock levels, goods-in, write-offs and traceability — held as movements rather than as a running total, so a discrepancy has a history you can read instead of a number you have to accept.
Includes
WMS
Stock control
Barcode
Reporting
Point of sale tied to fiscal rules and reporting, so what happens at the counter and what the law requires stay in step — including the kitchen display, the mobile till and the receipts.
Includes
POS
Fiscal receipts
Kitchen display
Compliance
Operational data reaching the accountant continuously instead of arriving as a box of documents at month end. The figures they work from are the figures the business is currently running on.
Includes
Live data
Ledger sync
Exports
Reporting
Online stores wired into the same stock, pricing and orders as the rest of the business, rather than run as a separate island that has to be reconciled by hand every week.
Includes
WooCommerce
Stock sync
Payments
Catalogue
Customer conversations on Messenger and Instagram handled automatically where they repeat — availability, pricing, bookings — and handed to a person where they do not.
Includes
Messenger
Instagram
Automated replies
Advice on what to build, what to buy and what to leave alone — then staying on after launch to keep it running, extend it, and answer the phone when something is wrong.
Includes
Advisory
Integration
Maintenance
SLA
Process
Our process is built around solving the
right problems.
We sit with the people who do the work and watch how it is actually done — which is rarely how it is described. Most of what a system has to handle turns up in this week, not in a specification.
What exists already, what has to be kept, what the law requires, and what the business will look like in three years. This is where we argue against building things, and it is usually the cheapest week of the project.
Data model first, screens second. If the model is right the interface is a detail; if it is wrong no interface will save it. Then the flows people will use forty times a day get made short.
Built in short cycles with something usable at the end of each one. Nothing is held back for a single reveal — the client sees the system growing and can change their mind while changing it is still cheap.
Against real data and real edge cases, on the hardware it will run on. A till that is fast on a laptop and slow on the counter terminal has not been tested.
Rolled out with the old process still standing until the new one has proven itself. We are on site or on the phone for the first days, because that is when everything that was missed shows up.
The part most quotes leave out. Systems we built years ago are still running, still being extended, and still ours to answer for. This is the difference between a project and a product.
More work
The rest of the shelf.
Systems running quietly behind other businesses — the
breadth behind the flagship work.
We build software systems for businesses that have
outgrown the tools they started
with.
DevHeist is a software development and consulting company
based in Bihać, Bosnia and Herzegovina, with three years of
work behind it. We are small on purpose: the people who
map the process are the people who build the system and
the people who answer for it afterwards.
DevHeist
