Avuso Software

Software engineering from Berlin

Make work easier.Simplify workflows.Achieve more.

I automate recurring steps, digitise workflows, and build custom tools, directly and pragmatically around the way your organisation actually works.

Discuss a workflow

For businesses, organisations, and public institutions.

Explore

Spot the potential

Many things that take several steps today can be made simpler.

That rarely requires replacing everything. A focused automation, a connection between existing tools, or one small purpose-built application can already make a meaningful difference.

Today · 01

Recurring steps

Moving data, preparing reports, sorting files, or entering the same information more than once.

Possible

More capacity

The same team can handle more work.

Today · 02

Disconnected systems

Information moves between email, spreadsheets, files, and specialist software, often by hand.

Possible

Fewer errors

Recurring steps become more consistent and traceable.

Today · 03

Searching instead of finding

Documents and knowledge exist, but are not quickly available where they are needed.

Possible

Faster workflows

Waiting time and manual intermediate steps are reduced.

Today · 04

Processes kept in people’s heads

A workflow works as long as someone remembers every step, exception, and dependency.

Possible

Easier collaboration

Less knowledge depends on individual people or handovers.

Services

The solution follows the task, not the other way around.

From one manual step to a connected workflow.

Selected work

Technology that made real work simpler.

Selected improvements from my previous engineering work.

Internal development workflows

Reduced a complex verification process to one action

A manual verification process before software integration was turned into one clear pre-merge workflow.

Internal development workflows

Selected work

Reduced a complex verification process to one action

Problem

Before a merge, developers had to know and account for numerous build checks. Mistakes could block other developers and trigger time-consuming investigations.

Solution

I combined the relevant checks into a centrally triggered pre-merge workflow that provided automated feedback before the actual integration.

Impact

Process knowledge moved from individual developers’ memory into the tool itself. Critical problems could be found earlier and risky integrations were easier to avoid.

Engineering quality

Selected work

Turned code formatting into a tooling problem

Problem

Formatting questions consumed attention during code reviews despite contributing little to architecture, correctness, or maintainability.

Solution

I introduced ClangFormat and helped establish shared rules so development environments could automatically format new code consistently.

Impact

Formatting became more reproducible and reviews could focus more strongly on the substance and quality of the code.

Technology adoption

Selected work

Brought an AI tool from experiment into everyday use

Problem

AI-assisted programming tools were new, and their practical value, limitations, and organisational adoption were still unclear.

Solution

I evaluated GitHub Copilot in day-to-day work, documented the findings, obtained the required approval, and supported its introduction to the team.

Impact

The technology became practically usable across the team and could take over repetitive typing and straightforward code completion.

Collaboration

Work directly with me. From the first conversation to handover.

I clarify the requirements, design the solution, build it, document it, and hand it over myself. Context stays intact, decisions remain direct, and coordination stays lean.

To keep it that way, I deliberately take on only a small number of projects at the same time.

  1. 01

    Understand

    We look at the actual workflow, the people using it, and the improvement you want to achieve.

  2. 02

    Define

    You receive a clear proposal covering outcome, scope, approach, price, and timeframe.

  3. 03

    Build

    I develop in clear steps, test the solution carefully, and keep you informed without unnecessary meetings.

  4. 04

    Hand over

    You receive clear documentation, a clean handover, and a solution that remains practical in everyday use.

Vadim Demkiv

About me

Software engineering with a view of the whole system.

I have been building software since 2008, from low-level programming to web applications, computer vision, and AI. Today I combine that broad experience with a clear standard: reliable, modular solutions that solve real problems at the root, are well documented, and remain maintainable.

M.Sc.
Human-Centered Computing
Direct
one point of contact from the first conversation to handover
DE · EN
collaboration in German and English

Experiences from working together

What others value about working with me.

Feedback from people I have worked with.

“Vadim always excelled at trying to understand my necessities, and he would not only provide a functional tool, but he would do it in the most user-friendly way.”

Pablo Lafora Rey

Experiences from working together

Pablo Lafora Rey

Senior Level & Quest Designer

Worked together at Black Forest Games GmbH

I've worked with many programmers and Vadim has a trait that I really wish I would see more often.

As a level/mission designer, I'm very used to requesting features and tools. Vadim always excelled at trying to understand my necessities, and he would not only provide a functional tool, but he would do it in the most user-friendly way.

He would always proactively start a conversation with me to understand what the tool needed to do exactly wanted (to the point of making me understand it better), and what struggles I might run into when using it. He would design tools that not only did what they were meant to do, they did it in such a way that would save me hours and hours when using them. He would always be open to receiving feedback and polish the tools. I once gave him a list of how we could improve the parkour system we were creating, and he surprised me with his own list (which included all of my points and then some) and a very casual "yeah, I was thinking the same, those will be integrated with the next phase".

In addition to this, he was always fast, neat, and a pleasure to work with. Vadim always manages to keep the information both ways and is the opposite of a black box.

I wish there were more coders like him.

Pricing

A model that fits the work.

I prefer fixed pricing for clearly defined work. When scope or value is still uncertain, flexible alternatives are available.

Predictable

Recommended

Fixed price

Tailored quote

Before work begins, you know what outcome you will receive and what it will cost.

  • Clear scope and agreed acceptance criteria
  • Budget certainty
  • Ideal for clearly defined projects

Flexible

Time & materials

€100/h

For open-ended work, changes, consulting, or tasks whose scope only becomes clear during the work.

  • High flexibility
  • Transparent billing
  • Scope can be adjusted at any time

Share the upside

Partnership model

Tailored quote

You bring the use case, I invest development capacity. Ongoing compensation is linked to the economic value the solution creates.

  • Low barrier to getting started
  • No large upfront investment
  • Shared interest in lasting value

Public & nonprofit rate

20%

lower hourly rate

for public and nonprofit organisations.

Outcome guarantee

For suitable fixed-price milestones, the agreed outcome is protected.View terms

If an agreed milestone still fails to meet its documented acceptance criteria after one correction opportunity at no additional cost, I refund the price of that milestone.

The exact pricing, scope, and applicable terms are documented transparently before work begins.

Contact

What would you like to make simpler?

You do not need a finished specification. Simply describe the workflow, task, or idea. I will reply personally with an initial assessment.

Prefer email? vdemkiv@proton.me

Privacy policy