Zivrio
I fix the
software
your business runs on, from the
codebase, through the office, to the shop floor.
I'm Robert Blixt, and I run a small team. Mostly that means getting your systems to talk to each other, automating the busywork stacking up between them, dragging an old codebase into the present without breaking it, and adding AI only where it actually pays off. On-site with manufacturers here in Västra Götaland, remote with SaaS teams further out. First call is 30 minutes, free, on one problem you pick. No slides.
Problems I Solve
Most jobs I 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. I take steps like these off your plate, so your team keeps its hours for the work that actually needs a human.
See how I approach thisAI inside the systems you already run.
I put AI on one specific job inside a system you already run. Drafting a first reply in your support queue, say, or boiling a long thread down to the gist. Someone on your side checks it before anything goes out, so it's never off on its own. Your data stays yours. And if AI isn't the right tool here, I'll say so before you spend on it.
See how I 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. I rebuild it in steps you can actually ship, starting with a piece small enough to get in front of real users fast. The old system stays live while I move things across bit by bit, so your roadmap keeps moving instead of freezing for a two-year rewrite.
See how I 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. I wire them together so a number gets entered once and stays right everywhere, whether your ERP is Jeeves, IFS or something else. And I build it to belong to you, not a vendor, so whoever ends up owning your ERP, the person who knows your integrations is still me.
See how I approach thisA second opinion, or a hand on the tiller.
Sometimes the fix isn't more code. It's cutting the work that shouldn't be there, or having someone senior to call when it matters. That can be a few hours (finding where your team's time leaks and what's worth automating, or sanity-checking an architecture or a vendor contract), or stepping in as a fractional or interim CTO when you need steady technical leadership for a stretch. No big project required.
Recent one: a one-off technical advisory for Sifferservice, an authorized accounting firm in Hunnebostrand.
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, I'll scope it, and the call's yours to make.
Book a 30-minute callHow we work
You work straight with the person writing your code, from the first call to handover. Email me 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 me, Robert, not a sales rep. It's free, and you'll walk away knowing whether it's worth a closer look.
Audit
If it is, I dig into the actual code, systems and data — how it really runs day to day, not the tidy diagram on the wall. You get a short write-up: what's risky, what's a quick win, and the one small, reversible piece I'd start with. It's yours to keep either way. And if the honest answer is 'don't build this,' you'll hear it from me.
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 actually use.
Handover
You own the code and the docs to run it without me. Want me back for the next piece? You've got my number.
Robert Blixt Founder
A scrappy team of just a handful of people, working together since 2020. Brief me and I'm the one who writes your code: on your shop floor in Västra Götaland, or remote with your product team.
I studied software engineering at Malmö University, and I've been building software since 2000 — much of it in .NET and C#, and these days Node.js too, including the legacy code most people are afraid to touch.
Along the way I wrote C# at transPA, spent eight years building LLENTAB's in-house software, and worked on SaaS at Captario. I've shipped and maintained real software from the inside, not just advised on it.
Robert on LinkedInOn the west coast,
and independent
My 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. I 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 person 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 I 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
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, run by me, 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. I 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 (I 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 I build the integration layer to belong to you, not a vendor, 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 I 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. I 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 I do. I 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. Not spreading it over everything. 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, I'll say so.
Will connecting or modernizing our systems disrupt production?
No. Your current ERP and production systems keep running the whole time. I 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. I rebuild it in shippable steps instead of one big cutover, so your team keeps releasing while old and new code run side by side. I 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 my on-site work is with manufacturers in the region, close enough that I can spend a morning on the floor watching how orders and stock actually move. Local also means I can show up on short notice, not just on a video call.
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 me, we ship in small steps you can see each week, and the time zones overlap enough for actual conversations, not a relay over email.
Which industries does Zivrio work with?
Two, mainly. On-site, manufacturing and production companies in Västra Götaland, where I connect the systems that run the operation and modernize the software behind it. Remote, SaaS companies, where I 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. This site's at zivrio.com, the Swedish one at zivrio.se, and I 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, I'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.