The company runs on one shared spreadsheet
Several people open it, versions diverge, formulas break, and nobody is certain which copy is current.
An error in a shared file is usually discovered after it has reached the customer or the supplier.
Premium solutions · operations
Management systems built for the way your company actually operates
Stock, production, orders, approvals and records in one system, shaped around your workflow rather than around a vendor's template.
Between the spreadsheet that no longer copes and the ERP that costs more than the problem, there is a gap. Most mid-sized companies live in it. That gap is what we build for.
We reply the same working day. No obligation.
12 years
building operational software
120+
projects delivered
10–20 weeks
typical build time
3+ years
average client relationship
Situations
Three signs you have outgrown your current setup.
You bought an ERP and use a fifth of it
It covers the accounting side but not the part that makes your business specific, so the real work happens beside it.
Every question needs three systems and a phone call
Where is that order, what stock is committed, who approved it. The answer exists, but only in pieces.
Benefits
One source of truth
Stock, orders and status in one place, so the answer is the same wherever it is asked.
Your rules, modelled properly
The exceptions that make your business work are built in, not worked around.
Connected to what you keep
Accounting, invoicing and eCommerce stay where they are and talk to the new system.
No per-user licences
Everyone who needs access gets it, without a cost decision each time.
What you get
What a management system includes.
Not an ERP replacement. The layer that covers what the ERP does not and the spreadsheet cannot.
Operation types
Where this fits.
Stock and warehouse
Multi-location stock, committed quantities, transfers, batches and stocktakes with real reconciliation.
Production tracking
Stages, capacity, materials consumed and deadlines, with the shop floor able to update status itself.
Order and fulfilment management
From order to picking to dispatch, with status visible to sales without asking the warehouse.
Approvals and internal requests
Purchase requests, expenses, leave or document sign-off, with thresholds and an audit trail.
Asset and maintenance records
Equipment, service intervals, interventions and costs, with scheduled maintenance reminders.
Replacing a shared spreadsheet
The most common starting point. We begin from the file itself, because it documents the real process.
Process
Five steps, starting on the floor.
We follow the work
Time in the warehouse, on the shop floor or in the office with the people doing it. The exceptions are never in the documentation.
Model and proposal
Data model, rules, roles and integrations, with estimated hours per module and a suggested order of delivery.
Prototype
The screens people use dozens of times a day, validated before development.
Build in modules
The highest-impact module first, in production and in use before the next one starts.
Migration and adoption
Existing data brought across, training by role, and close support through the first month.
How we build
The exceptions are the system.
Every standard product handles the normal case. Companies differ in their exceptions — the customer with different terms, the product measured differently, the approval that skips a step when the value is small. Those exceptions are exactly why the spreadsheet survived.
Premium solution
Built between the spreadsheet and the ERP
We do not replace your accounting system and we rarely replace an ERP. We build the operational layer that sits between them and the work — the part that is specific to your company, connected to the systems you keep, and shaped by rules that no vendor could have anticipated.
- Fast on the operations that repeatThe action performed two hundred times a day is designed first. Everything else follows.
- Roles, approvals and audit trailWho did what and when, with thresholds and delegation, so control does not depend on trust alone.
- It keeps your existing systemsAccounting, invoicing and eCommerce stay in place and exchange data over API.
- Exceptions modelled, not worked aroundThe rules that make your business specific are built in rather than handled in a side spreadsheet.
- Real stock, not a delayed copyCommitted versus available resolved properly, so what the system says is what the shelf holds.
- You own everythingCode, database and integrations, with no per-user licences and no vendor lock-in.
We have built stock synchronisation between management software and online stores covering hundreds of product lines, and ordering systems where the order reaches the operational screen the moment it is placed.
Worth knowing: if a standard ERP covers your operation, buy the ERP. This is worth building when the specific part of your business is where the value is, and when forcing it into a template would cost more in workarounds than in development.
Connected to your online store
Stock and prices resolved in one place and propagated to the store and to marketplaces, so you never sell what you do not have.
Suited to anyone selling through more than one channel.
Supplier and partner portal
Suppliers confirm orders, upload documents and update delivery dates themselves, in one place with a full history.
Suited when supplier coordination happens across hundreds of emails.
AI on operations
Documents read and filed automatically, unusual orders flagged, demand patterns surfaced from history.
Suited once the operational data is clean and centralised — not before.
| Shared spreadsheet | Standard ERP | Custom system | |
|---|---|---|---|
| Fits your exceptions | yes, manually | no | yes |
| Multi-user reliability | poor | good | good |
| Audit trail | none | yes | yes |
| Initial cost | none | medium to high | high |
| Licence per user | none | yes | none |
| Time to change a rule | minutes, unsafely | vendor dependent | days, safely |
Our rule: The order matters: first simplify the process, then automate it. Building software on top of a broken workflow makes the chaos faster and more expensive. If our analysis finds the process itself is the problem, we say so before quoting the build.
Adoption
If it is slower than the spreadsheet, it will lose to the spreadsheet.
Internal systems rarely fail technically. They fail because the people doing the work found them slower than the method they replaced, and quietly went back.
A concrete example: in an ERP to eCommerce integration we built, stock and prices update automatically across hundreds of product lines — removing the daily reconciliation that used to be done by hand.
What is included
What a management system includes
Projects
View full portfolioWe do not promise. We demonstrate.
Operational systems delivered and used daily by real teams.
Frequently asked questions
How is the price set?
We work on an hourly rate: €50 per hour, excluding VAT. The price comes from the number of estimated hours rather than from a fixed package. You receive a proposal in which each module carries its estimated hours and cost.
Is this an off-the-shelf product?
No. This is a system built around how your organisation already works. We start from your workflow, your rules and your existing software, then build what fits. That is why it costs more than a subscription tool — and why people actually use it.
How long does it take to build?
An approvals or records system takes 8–14 weeks. Stock or production management takes 12–20 weeks. We always deliver in modules, so the highest-impact part is in production and proving itself before the next one starts.
Will this replace our ERP?
Usually not, and we would be cautious about anyone who says it will. We build the operational layer that covers what the ERP does not, and connect the two. Replacing an accounting system is a much larger decision with much less upside.
Why not just buy standard software?
If it fits, buy it — that is genuinely the cheaper answer. We build custom when the specific part of your operation is where the value sits, and when forcing it into a template creates the workarounds that keep the spreadsheet alive.
Can you migrate what we have in spreadsheets?
Yes, and we usually start there, because the spreadsheet documents the real process better than any procedure manual. Migration is a separate stage with its own hours, since the duration depends on the state of the data.
How do you make sure people use it?
By designing the repeated operations first and measuring them against the current method. If an action takes longer than it did before, we rebuild that screen. Adoption is a design problem, not a training problem.
What if our process changes?
It will, and the system is built for that. Rules that we expect to change are configurable rather than hard-coded, and we stay on for ongoing development. A system that cannot change becomes the next spreadsheet.
Who owns the system and the data?
You do. Code, database, documentation and integrations, with no per-user licences. You can host it where you choose and move to another developer at any time.
Estimate
Tell us what you need. We reply with an estimate.
Five steps, under two minutes. The more context you give us, the closer the estimate will be to reality.
ProjectStep 1 din 5
What would you like us to build?
You can pick more than one.
Tell us where the work actually happens.
You do not need a specification. Send us the spreadsheet everyone opens, or describe the process that keeps breaking. We reply with what we would build, in what order and with the estimated hours.
Get an estimateOr email us directly: contact@divasweb.ro+40 755 336 514