Rico Fritzsche

From problem to production

Tell me the problem. I build the solution.

Rico Fritzsche

I’m Rico Fritzsche, software engineer and architect with 30+ years of experience. I take responsibility for understanding your problem, designing the solution, and delivering working software, at a fixed price from 15,000 EUR, delivered in 4 to 12 weeks.

Tell me what you need solved

Situations

Problems I take on

  • Too much work still happens by hand.

    Spreadsheets, emails, copy-and-paste, and workarounds keep an important process running.

  • Something needs to be built, but the team can’t get to it.

    The need is clear, but delivery keeps slipping behind other priorities.

  • A part of the system has become a liability.

    It is slow, fragile, or so awkward to change that every modification becomes risky.

  • Systems that should work together don’t.

    Data has to be moved, reconciled, or fixed manually because the handover isn’t reliable.

  • You know the outcome you need, but not yet the software.

    The business problem is clear. The right solution still needs to be shaped and built.

What I take on is one bounded piece of software: a feature, a service, an integration or an API, with a scope that can be agreed before I start.

How I work

The whole solution is my responsibility

  • Understand the actual problem

    I first make sure we understand what really needs to be solved and what a useful result looks like.

  • Design the right solution

    I shape a solution around the problem, the business, and the environment it needs to work in.

  • Build and integrate it

    I deliver working software and connect it to the systems and workflows it needs to support.

  • Make sure it holds up

    I take responsibility for robustness, security, and testing, with code that remains understandable and maintainable after delivery.

Examples

Work I have delivered

  • Make one slow endpoint fast without touching the rest of the system

    Logistics, 2025. Delivered in 4 weeks.

    Problem
    A critical endpoint in an existing system had become too slow for the process that depended on it.
    Solution
    I built a separate endpoint in Rust that is deployed on its own. It reads from a read-only data artefact built and optimised for this one query. The existing system did not have to change.
    Outcome
    The process runs against the new endpoint, and the existing system was left untouched.

  • Resolve logistics addresses correctly in under 5 milliseconds

    Logistics, 2024. Delivered in 12 weeks.

    Problem
    A logistics company needed a geocoding endpoint whose query logic covers the cases that make logistics addresses hard to resolve.
    Solution
    I designed the query logic for these logistics-specific cases and built the endpoint around it.
    Outcome
    Lookups answer in under 5 ms.

  • Know when a vehicle leaves its zone while it happens

    Automotive, 2023. Delivered in 8 weeks.

    Problem
    Vehicles send position events continuously, millions of them, and operations need to know when a vehicle enters or leaves a defined zone.
    Solution
    I built the geofencing API: ingestion that keeps up with the full event stream and zone evaluation on every incoming position.
    Outcome
    The API handles millions of ingest events, and zone entries and exits are detected from the live event stream.

Thinking

How I think about software

Contact

Tell me what you need solved

Describe the problem, what you need to achieve, and anything else you think is relevant.

I reply within one working day to arrange a first conversation, free of charge. Within two working days after that conversation you receive a written offer with the scope, the fixed price and the delivery date.