Zivrio
We fix the
software
your business runs on, from the
codebase, through the office, to the shop floor.
We're a small software team based in Västra Götaland. We get your systems talking, automate the busywork piling up between them, bring old codebases into the present without breaking them, and add AI only where it pays off. On-site with manufacturers nearby, remote with SaaS teams further out. The first call is free: 30 minutes on one problem you pick.
Problems we solve
Most jobs we get called in for look like one of these. Manual work eating your team's week, an old system nobody dares touch, systems that won't share data, or AI you want to add without it going off the rails.
Automate the repetitive work that fills your team's week.
A new customer gets set up by hand across billing, support and your own app. Every Monday, someone rebuilds the same report from the same exports. We take steps like these off your plate, so your team can spend its hours on work that needs a person.
See how we approach thisAI inside the systems you already run.
We put AI on one specific job in software you already use, like drafting a first reply in your support queue or boiling a long thread down to the gist. Someone on your side checks the result before anything goes out, and your data stays with you. If AI isn't the right tool for the job, we'll tell you before you spend money on it.
See how we approach thisModernize the core system no one dares to change.
Your core app still runs, but every change is slow and risky, and the people who built it are long gone. We rebuild it in steps you can ship, starting with a piece small enough to put in front of real users quickly. The old system stays live while we move things across, so your roadmap keeps moving during the work.
See how we approach thisMake your systems agree.
When the systems that run your business won't share data (ERP, MES, e-commerce, logistics, EDI, BI), people end up re-keying orders and stock by hand, duplicates creep in, and one wrong number can hold up a shipment. We wire them together so a number gets entered once and stays right everywhere, whether your ERP is Jeeves, IFS or something else. The integrations are yours and documented, so they keep working whoever ends up owning your ERP.
See how we approach thisA second opinion, or a hand on the tiller.
Sometimes the fix isn't more code. It's cutting work that shouldn't be there, or having someone senior to call when it matters. Busy owners, managers and small teams usually lose hours to the same few things, and the right setup wins them back:
- AI that knows your workAn assistant set up around your documents, email and routines, so drafting, summarizing and looking things up takes minutes, not an afternoon.
- Automate the recurring stuffThe weekly report, the invoice reminder, the copy-paste between two systems. Done in the background, the same way every time.
- Small custom toolsA focused app or script for the one job your off-the-shelf software handles badly.
- A machine set up rightYour computer, apps and shortcuts configured so the tools stay out of your way and the busywork shrinks.
It can be a few hours, a sanity check of an architecture or a vendor contract, or stepping in as a fractional or interim CTO for a stretch. None of it requires a big project.
Recent one: a one-off technical advisory for Sifferservice, an authorized accounting firm in Hunnebostrand.
Start with a free 30-minute call with Robert. Prefer email? We reply within a working day.
Book a 30-minute callHow we work
You work straight with the people writing your code, from the first call to handover. Email us and you'll hear back within a day.
Discovery
We spend 30 minutes on one problem you pick. Maybe two systems that disagree on stock, or an old codebase that's made every release a gamble. You talk to Robert, the founder, not a sales rep. It's free, and you'll walk away knowing whether it's worth a closer look.
Audit
If it is, we find the real problem, which isn't always the one you called about, and where fixing it pays off for the business. You get a short write-up and the one small, reversible piece we'd start with. If the honest answer is 'don't build this,' you'll hear it.
Pilot, then build
Then we build that piece for real. One integration, or a single feature behind a flag, or one production line on the factory floor. You watch it run on something small and reversible before anything bigger moves, and every week ends with something you can use.
Handover
You own the code and the docs to run it without us. Want us back for the next piece? You know where to find us.
Built for the person who uses it
Software only pays off if people want to use it. So before we design a single screen, we sit with the people who'll use it every day, on the shop floor, at the order desk, in the support queue, and learn how the work gets done. Then we sweat the details.
-
Focused screens
Each screen does one job, and what you need is where you look for it.
-
Help built in
Sensible defaults, clear messages, and checks that catch the typo before it reaches a customer.
-
No surprises
Buttons do what they say, and the system behaves the same way every time. Nothing happens behind your back.
-
The extra pass
The last ten percent (shortcuts, loading states, the wording on a button) is where software goes from usable to liked. We never skip it.
When people feel safe in a system, enjoy using it, and it does exactly what they expect, they stop working around it. That's when the business value starts to grow.
Robert Blixt Founder
A handful of people, together since 2020. Brief us and you get me: on your shop floor in Västra Götaland, or remote alongside the team.
I've built software since 2000, mostly .NET and C#, now Node.js too, legacy code included. Eight of those years were inside LLENTAB, so I know software from the side that has to live with it.
Full background on LinkedInOn the west coast,
and independent
Our on-site work is along Sweden's west coast, with manufacturers where two systems disagree on stock and someone ends up typing the same order in twice. We stay independent of any one vendor, so when the system you lean on gets bought or merged, the person who knows your setup is still a short drive away. The SaaS work is remote, for product teams elsewhere in Europe and further out.
We're a good fit if your systems don't talk to each other, if you're on Jeeves or IFS, or if you've got a legacy system you're nervous to touch and want the same people to still know it next year. Probably not a fit if you need a big offshore team, or a fixed-scope RFP answered to a deadline.
On the floor in Västra Götaland
On-site with the manufacturers we work for, on the production line itself, watching where the numbers stop matching
Node.js and .NET
The two stacks most of this work runs on, built and maintained in production
People-driven outcomes
Software built around the people who use it and the team who'll maintain it
Measured in years, not sprints
Two Swedish manufacturers we've worked with for years, on the same systems, with the same people.
Frequently Asked Questions
Answers to common questions about Zivrio and how we work
What does Zivrio do?
Zivrio is a software consultancy in Västra Götaland, Sweden, founded and run by Robert Blixt, with a small team since 2020. We do four things: AI inside existing products, business-process automation, legacy modernization, and system integration (wiring your ERP, like Jeeves or IFS, to the tools around it). On-site work is with manufacturers on Sweden's west coast; the SaaS work is remote. We also take on a few technical-advisor roles.
Is Zivrio a fit for my project?
Probably yes if your systems don't talk to each other, you run Jeeves or IFS, or you've got a legacy system you're nervous to touch and want direct access to the person doing the work. Probably not if you need a big offshore team, staffing for a fixed-scope RFP on a deadline, or a vendor to hand the whole thing to and check in on once a quarter. Not sure? A 30-minute call sorts it out fast for both of us.
What systems do you integrate?
The systems that run your business, and the gaps between them. ERP (we work with Jeeves and IFS most), MES, e-commerce, EDI, logistics, BI. The point is that orders and stock counts get entered once instead of re-keyed into each one. And the integration layer belongs to you, so it still holds when someone else owns your ERP.
Can you automate manual or back-office work?
Yes, that's one of the four things we do. It's usually the repetitive bridging between systems: a number re-typed from one tool into the next, an approval chased down over email, a report rebuilt by hand every week. We take those over so your team keeps its hours for the work only a person can do. The best candidates are the spots where someone's stuck standing between two systems, re-keying.
How does Zivrio use AI?
One of the four things we do. We put it on narrow, well-defined jobs inside systems you already run: drafting a first-pass support reply, boiling a long thread down, routing tickets by topic. A human stays in the loop and signs off before anything reaches a customer, and nothing you feed it trains someone else's model. And if a problem's better solved without AI, we'll say so.
Do you design the user interface too?
Yes, and it's where we put a lot of care. We spend time with the people who'll use the system, then design screens that are focused, quick to learn and hard to get wrong. Even an integration often needs a small UI, like an approval screen or a status view, and those get the same attention.
Will connecting or modernizing our systems disrupt production?
No. Your current ERP and production systems keep running the whole time. We start on one line or one integration, make sure it holds, then roll it wider. There's no big switchover, so nothing stalls and no delivery gets missed while the work's underway.
Can you modernize a SaaS codebase without freezing our releases?
Yes. We rebuild it in shippable steps instead of one big cutover, so your team keeps releasing while old and new code run side by side. We move one area at a time behind a flag, and you can roll any step back on its own if it acts up.
Where is Zivrio based?
Västra Götaland, on Sweden's west coast, and that's on purpose. Most of our on-site work is with manufacturers in the region, close enough to spend a morning on the floor watching how orders and stock move. Being local also means we can be there on short notice.
Do you work with clients outside Sweden?
Yes. The on-site manufacturing work is tied to Sweden's west coast, but the SaaS side is remote, with product teams across Europe and further out. It works the same way the local work does: you talk straight to the people doing the work, we ship in small steps you can see each week, and the time zones overlap enough for real conversations.
Which industries does Zivrio work with?
Two, mainly. On-site, manufacturing and production companies in Västra Götaland, where we connect the systems that run the operation and modernize the software behind it. Remote, SaaS companies, where we build and improve the product and add AI where it helps. The common thread is operational software a business leans on every day. The sector matters less than that.
What languages do you work in?
English and Swedish, both fluently. The Swedish version of this site is at zivrio.com/se, and we run projects, calls and docs in either, whichever your team prefers. For manufacturers in Sweden that's usually Swedish on-site, English for anything that has to reach an international team or codebase.
How do I start a project with Zivrio?
Book a free 30-minute call, or email [email protected] with a line on what you want fixed. We use the call to map one problem. Anything past that is your call, nothing committed up front.
Let's scope your problem
Book a time below and we'll spend 30 minutes on one problem you're facing. No obligation to carry on after that. If a first step makes sense, we'll scope it, and the call's yours to make.
What happens next
Prefer to write first? Email [email protected] in English or Swedish, whichever's easier.