Connect your systems.
Your team copies information between systems every day. We build the connection and make it clear what was processed and what needs attention.
bluvolve · Custom software agencyWe build the software
We build the software
that solves your problem.
A process depends on too much manual work. Your systems do not work together. A product idea needs someone to build it.
bluvolve takes responsibility for the technical delivery, from understanding the problem to the agreed, usable solution. Led by Rico Fritzsche, who has been building software since 1993.
01 / The starting point
What needs to work in your business?
Your problem is the starting point. It determines what software is worth building.
Make the workflow work.
An important process lives in spreadsheets and manual decisions. We define the rules together and build an application that supports the workflow and makes exceptions understandable.
Bring a product to life.
You know what digital product is needed and want someone to deliver it. We define a usable first release and build it through agreed steps.
02 / How we work
You can see how the result will be judged.
Usable progress says more than a promise. Rules and acceptance examples make the agreed result concrete.
Define the outcome.
Who needs what to work better? Which rules matter? What examples will show that the agreed scope has been delivered?
Build in manageable steps.
You see usable progress and can check the direction early. Dependencies, unanswered questions and changes are discussed explicitly.
Check the behavior.
We use concrete examples, business rules and relevant failure cases. Repeatable calculations are checked against fixed inputs. We make uncertain data or AI results visible and agree how to handle them.
Make the handover practical.
The agreed package includes the application, source code, agreed rights and the information needed to operate and develop the solution.
AI agents support development and verification. Rico is responsible for technical delivery and the decisions about what gets built and how it is checked.
See a concrete delivery example03 / After deliveryYour product.
Your product.
Your way to operate it.
We discuss the right route during scoping. Source access and the agreed rights are part of delivery, whoever operates the application.
Your team takes over.
We deliver into the agreed environment and prepare a handover so your team can operate and develop the solution.
You want us to operate it.
We can assess a separate arrangement for hosting, maintenance and support. Responsibilities, costs and availability are agreed before that service starts.
04 / Our own workWe also build
We also build
for our own questions.
Our own products and services have a purpose of their own. They also make particular bluvolve engineering work available to inspect.
Our own initiative / Research case study
TellMeWhere
How does the picture of walking access to everyday shopping change when different data sources and business rules are considered? The Rostock study presents calculated results, sources and unresolved data questions.
Read the Rostock study (German)Fictional method example
When is a data merge correct?
Two stock files, conflicting values, a clear result: this example sets out rules, acceptance cases and a handover package. It is a fictional illustration, with no client or shipped application.
Read the example05 / Rico FritzscheBuilding software since 1993.
Building software since 1993.
Accountable today.
1993Started as a freelancer
2007–2017Ran a custom software company; sold in 2017
Since 2017Independent engineer, architect and consultant
I'm Rico Fritzsche. I combine experience in engineering and running a software business with agent-assisted delivery.
I started my software career as a freelancer in 1993. From 2007 to 2017, I ran a company developing custom business software, including work for public-sector organizations. I sold that company in 2017.
Since then, I have worked independently as an engineer, architect and consultant for large companies. My experience spans logistics, automotive, telecommunications, energy and the public sector.
At bluvolve, I define the rules that matter, structure the implementation and take responsibility for the technical work. I also write publicly about software, architecture and behavior that can be verified.
Read Rico's writingRecent work in logistics has deepened my knowledge of geodata and location intelligence.
More about this experienceThe next stepWhat needs to
What needs to
work better?
What does not work today? What should change? Which systems or data are involved? A short message is enough to begin.
We then establish whether to scope the build directly or start with a bounded technical clarification. Scope, timing and price follow from that understanding.
Describe your problem by emailrico@bluvolve.dev