For partner firms
I take Microsoft Access off your plate.
Whether you run IT for your clients, build their software, or advise them on the numbers, they have Microsoft Access applications you'd rather not own. Undocumented, fragile, written by someone long gone, and running some part of the business anyway. That's the work I do, so it doesn't have to be work you do.
Who this is for
Find yourself below.
MSPs and IT service firms
Your technicians handle networks, servers, and Microsoft 365. Then a ticket arrives about an Access application some employee built fifteen years ago, it runs part of the client's business, and it isn't a problem an infrastructure team should have to solve. Hand me those tickets. Your client stays yours, and your board loses a ticket nobody wanted.
Custom software shops and .NET consultancies
A client wants their aging Access system replaced, but the rewrite takes a year and the old application still has to run while you build. I keep it stable and dependable through the transition, and I take the small Access engagements you'd rather not staff. I write C# and .NET myself, so your team and I speak the same language, and I'm not bidding on the rewrite; that work is yours.
CPA firms and fractional CFO practices
Your client's month-end reporting, billing, or check writing runs through a fragile Access file, and when it misbehaves they ask you who can fix it. Introduce me. I make the application dependable again in a bounded engagement, and you stay the advisor who knew the right person.
What I take off your plate
The Access work your team shouldn't have to own.
Fifteen-plus years of professional engineering, with deep Microsoft Access and VBA experience backed by C# and .NET development.
Applications that misbehave
Errors, crashes, and fragile behavior in databases the client depends on daily. I find the cause, fix it, and harden the weak spots.
Features the client needs
New reports, forms, and automation added to the existing application without destabilizing what already works.
Code left by a departed developer
Undocumented VBA nobody at the client understands. I read it, document it, and make it maintainable again.
Aging back ends to SQL Server
When an Access back end has outgrown itself, I move the data to SQL Server and keep the front end the client knows.
How the engagement works
The client relationship stays yours.
The engagement works whichever way suits you. I can operate under your brand as your Access resource, invisible to your client, or you can introduce me directly as your specialist partner. Either way, the client relationship stays yours.
- Fully remote. Your team handles any on-site presence; I handle the code.
- White label or direct referral, your choice per engagement. Referral partners like CPA firms simply make the introduction; there's nothing else to manage.
- I document what I find and what I change, so the work is auditable and the knowledge stays with the client.
- When the engagement ends, your client has a healthier application and you have a solved problem with your name on it.
Keep my information
The next Access problem doesn't have to be yours.
If your clients depend on Access, and most do whether they like it or not, keep my information on hand. The next time one of those problems lands on your desk, send it to me instead of turning it away.
rob.evans@evanscoapps.com