One system instead of spreadsheets and email
Orders, approvals, records and reporting in one place. We build it from smaller services: we start with the process that slows you down most and add the next ones step by step, while your team keeps working.
Order 2041
Created
- 09:12Anna created the order
- 09:40Peter approved it
- 10:05The warehouse picked the goods
- 10:06The invoice went to accounting
What an internal system is
An internal system is software your company does its daily work in: records, approvals, planning and reporting. Only your people use it, and its rules follow how your company actually works.
Some systems carry a single process, others are the core the whole company runs on.
Approvals and workflow
Requests, purchases and contracts moving from person to person.
What to keep in mind
Clear rules and a full history. Everyone has to know what waits on them, a deputy has to take over during holidays, and months later you still see who decided what and why.
Records
Contracts, assets, documents or people in one place.
What to keep in mind
One version of the truth. Today the same contract often lives in three places. In a system there is one record, access by role and a search that finds it in seconds.
Reporting and dashboards
Numbers from several systems, together and up to date.
What to keep in mind
Data you can trust. A report pieced together by hand is out of date when it is finished. Calculated straight from the source, it is ready whenever someone needs to decide.
Core system
The heart of the company that every other system connects to.
What to keep in mind
Stability and change without stopping. The company cannot pause while it is rebuilt, so the new system grows next to the old one and takes over piece by piece. Every other application talks to it through one API.
Internal systems for healthcare
Healthcare is where we build most. Behind every portal and every result there is an internal system that has to run every day, without a break.
Core system
The system daily operation stands on, with portals and apps connected to it.
Sample intake and processing
From the collection to the result, every sample with its status and history.
Schedules and staff
Clinics, rooms and shifts planned in one place, without clashes.
Billing to insurers
Procedures recorded once and prepared for insurers without retyping.
Sensitive data
Roles, encryption and a record of every access.
Rebuilt while running
The new system grows next to the old one, operation never stops.
Connected systems
Portals, devices and other systems exchange data through one API.
Full history
Who changed what and when, ready for every audit.
The same work, with less retyping
Most internal processes work today. They just cost too much time: retyping, forwarding, looking for the latest version. Pick a process and see what changes once a system built for exactly that process carries it, instead of a spreadsheet and an inbox.
Today
Branches email their orders in a spreadsheet
Every morning someone copies them into one file, chases missing items and forwards the result to the warehouse. One typo in a product code and the mistake travels all the way to the invoice.
- Each branch enters its order in a form that knows its range
- The system checks codes, quantities and prices as you type
- The warehouse sees the order at once, nothing is forwarded
- The branch can follow its status without calling anyone
One process first, then the next
We do not build an internal system all at once. We put it together from smaller services (microservices), so each part can be launched, changed and extended on its own. Your team starts working in the first part as early as possible, not after a year of waiting, and every next step is based on what they learned using it.
- 01
We sit in on the work
We see how the team runs the process today, including the spreadsheets and the exceptions nobody wrote down. You get a clear scope and price before any code is written.
- 02
The first module
One process as its own service, with sign‑in, roles and change history. You try working software regularly as it grows, instead of reading status reports.
- 03
More modules
Further processes arrive as new services. They share data and sign‑in but do not depend on each other, so a change in one never stops the rest.
- 04
Connections
The system connects to accounting, the warehouse or older systems, so nothing is retyped by hand. What already works in your company stays where it is.
Systems that daily work depends on
In healthcare we are rebuilding a core system that has run for years, without stopping it. The old system remains the master, we keep its data in sync, and the other applications gradually move over to the new one. In retail we built a system for supplier tenders. Behind both are 10+ years of experience with systems that people rely on every day. AI speeds up the routine part of the work, which keeps the price unbeatable, and developers write or review every line of code.
Healthcare
- A new core system next to the historic one
- Data kept in sync with the original system
- Portals for doctors and collection centres
- First phase delivered, development continues
Retail
- Tenders and supplier offers in one system
- Offers compared without spreadsheets
- A clear overview of every tender
Everyone sees and edits only what they should. A new colleague gets the right access in a few clicks.
Who changed what and when, on every record. Useful for audits and for settling disputes.
Search, filters and bulk edits, even with a lot of data. People who used spreadsheets feel at home.
Other applications read and write data through it, never around it. New connections can be added later.
References

Integrating a CRM with backend services
Integrating a CRM with backend services to improve process effectiveness and enhance customer experience.
„Blume is an innovative partner in the area of IT and system development, they have software development squared and are not scared even of complicated projects with integrations with legacy systems with a large amount of data.“
Before a system replaces the spreadsheets
Analysis comes before the first module, connections and moving the data come after.
- AnalysisA clear scope, priorities and a price you can plan with.
- IntegrationsWe connect what you already run, even on days when one system is down.
- System rebuildsReplacing an old system step by step, without stopping the work.
- AI & automationThe routine runs by itself, people approve what matters.
- Maintenance & supportA developer who knows your system, for a fixed monthly fee.
Tell us about your project or problem
Describe a process that runs on spreadsheets and email today and who works in it. A few sentences or a sample spreadsheet is enough. We reply with questions and, once the scope is clear, a quote.
Questions about internal systems
Not sure where to start?
A consultation helps you decide what to build now and what can wait.