VBA programming: your macro keeps running – even without the colleague who built it.
Excel and VBA are still the backbone of day-to-day business in many companies – calculations, planning, reports, entire departments depend on them. The problem starts when the colleague who programmed it retires or leaves. That is exactly when we step in: we take over the VBA programming of your existing systems – adaptations, extensions, bug fixing and documentation. Honest advice, clean execution.
Legacy code? No problem
We work through third-party VBA code in a structured way – without documentation and without the original author.
Honest advice
New development in VBA is possible but rarely advisable – we show you alternatives before you invest.
More than VBA
Python data analysis, web applications, C# desktop apps: when it should go beyond VBA, we can do that too.
Does this sound familiar?
VBA systems are rarely documented but almost always business-critical. The typical situations in which companies call us:
The developer is gone
The colleague who built the calculation tool ten years ago has retired, left or is unreachable. Nobody dares to touch the code – but the business needs a change.
The macro suddenly fails
After an Office update, a new machine or a Windows migration the macro stops working – and an entire process stands still with it.
New requirement, old code
New pricing logic, a changed report structure, an additional processing step: small on paper, risky to implement in organically grown code.
It gets too slow
What worked with 1,000 rows crawls at 100,000 – poorly optimized VBA code does not scale by itself.
Nobody knows what it does
The tool produces numbers everyone relies on – but nobody can explain how they come about. A risk for audits and decisions.
Excel hits its limits
Multiple simultaneous users, central data, interfaces: sometimes the adaptation is only the first stage – then we talk openly about replacing the legacy system.
What our VBA programming covers.
From a small bug fix to a thorough modernization of the existing code – you get exactly as much intervention as your system needs.
- Adaptation & extension – New features, changed business logic, additional evaluations – implemented in the existing code without breaking what works.
- Bug fixing – Crashes, runtime errors, wrong results: we find the cause in the legacy code and fix it traceably – including tests against real data.
- Code comprehension & documentation – We read the grown code, document the business logic and make your company independent of individual heads.
- Performance optimization – Speeding up slow macros – often by orders of magnitude, without touching the logic.
- Interfaces & database connections – Connecting VBA to SQL Server, Access, CSV/API sources or your ERP – no more copy-and-paste between systems.
- Hardening & cleanup – Removing outdated constructs (e.g. problematic ActiveX elements), adding error handling, bringing version states in order.
Typical entry point
You send us the file or show it via screen sharing – we give a first assessment of effort and risk before you commit.
Environments
Excel VBA · Access VBA (forms, reports, database logic) · Word/Outlook automation
Looking ahead
If the system stays important long-term, an orderly replacement often pays off – see our VBA legacy modernization page.
The macro is on strike and nobody knows what to do?
Send us a short description – you get a first assessment of cause and effort before you commission anything.
New development in VBA? Possible – but rarely advisable.
We could easily build you a brand-new tool entirely in VBA. In most cases we advise against it anyway – and tell you why. For new projects we are happy to discuss alternatives that last longer:
Python for data analysis
Where VBA reports hit their limits, pandas & co. play to their strengths: large data volumes, reproducible evaluations, clean automation – with Excel as input and output if you wish.
Web applications
Multiple users, central data, access from anywhere: a lean web app replaces the emailed-around Excel file with a single source of truth.
C#/desktop applications
When it should be a full Windows program: robust desktop apps with a real database instead of a spreadsheet as data storage.
And if it should be VBA after all?
There are legitimate reasons – existing infrastructure, small budget, short-lived purpose. Then we build it properly: structured, documented, with error handling. But only after we have honestly discussed the alternatives.
How a VBA adaptation runs with us.
Review
You describe the problem, we look at the code – via file handover or screen sharing. First assessment free of charge.
Effort estimate
Honest effort forecast and a transparent hourly rate – existing code is billed by the hour, with a check-in before the agreed budget is exceeded.
Implementation with a safety net
Changes are made on a copy and tested against real data – your running tool stays untouched until the new version is ready.
Handover & documentation
You receive the changed version with an understandable documentation of the changes – no new knowledge monopoly.
On request: ongoing care
Continuous maintenance for your VBA landscape – or the orderly modernization once the system is ready for it.
Frequently asked questions about VBA programming.
Do you also take over VBA code written by someone else?
Yes – that is our normal case. We work through third-party legacy code in a structured way, even without documentation and without the original author. After the review we tell you honestly what state the code is in and what the desired change costs.
What does a VBA adaptation cost?
Work on existing code is always billed by the hour – organically grown code holds surprises, so a serious fixed price is not possible. After the free initial assessment you receive an honest effort forecast and our hourly rate, and we check in before the agreed budget is exceeded.
Do you also program completely new tools in VBA?
We can – but we usually advise against it: Microsoft no longer actively develops VBA, it does not run in web and mobile Office, and it scales poorly. For new projects we prefer to discuss alternatives such as Python, a web application or a C# desktop app. If VBA is still the right choice in a specific case, we build it cleanly and documented.
My macro stopped working after an Office update – can you help?
Yes, a classic: changed library references, removed functions, stricter security settings or 32/64-bit transitions. The cause is usually found quickly – send us the error message and the file.
When does replacement pay off instead of adaptation?
When many users need to work simultaneously, data must be central, interfaces are required or the adaptations keep piling up. Then orderly modernization often pays off faster than expected – our VBA legacy modernization page shows how. Adapting today and replacing tomorrow are not mutually exclusive: we gladly prepare the code so the later migration becomes easier.
Do you work remotely or on site?
Both: most VBA engagements run efficiently remotely via file handover and screen sharing. On-site appointments work well in Dresden, Leipzig and Chemnitz – overall we work across the DACH region.
Related services.
VBA Legacy Modernization
When adapting is no longer enough: migrating legacy systems into modern software in an orderly way.
Learn moreCustom Software Development
Web, desktop and data analysis – the alternatives to new VBA development.
Learn moreExcel Courses & Workshops (German)
Getting your team up to speed – from formulas to VBA basics.
Learn moreYour VBA system needs a change?
Briefly describe what the tool does and what should change – we will get back to you with an honest first assessment of effort and approach.
Send a VBA inquiry.
Briefly describe the tool and the desired change – first assessment usually within 24 hours.
We usually reply within 24 hours.
Remote & on site – working across the DACH region (DE, AT, CH), with international project experience.