Senior .NET engineer.I build web apps, SaaS MVPs and internal tools for small businesses, start to finish.
You work with me directly, from the first call to launch day. I'll give you a fixed price before I start, show you working software
every week, and hand everything over when we're done.
You get one price in writing before I start, and it doesn't creep.
A demo every week
Every week you see what's working, not a status report.
You own the code
It lives in your GitHub and your cloud account from the first day.
A proper handover
Docs, tests and a recorded walkthrough, so anyone can pick it up after me.
Services
What I can build for you.
Every project starts with a short call. After that you get a written proposal with a fixed price.
01
Web app or SaaS MVP
THIS IS FOR YOU IF
You have an idea, or a way of working, that off-the-shelf software doesn't handle well.
WHAT YOU GET
Sign-in and user roles, your core workflow, payments if you charge for it, an admin area, and hosting on your own account. Enough to put in front of real customers.
Your team runs things on spreadsheets, email and a lot of copying and pasting.
WHAT YOU GET
One place for your data, the forms and approvals your team actually uses, the reports you keep rebuilding by hand, and connections to the tools you already pay for.
You have a .NET app that's slow, keeps breaking or is stuck on an old version, and the person who built it has moved on.
WHAT YOU GET
I start with a review and a written plan. Then I upgrade it to current .NET, fix what's breaking, add tests and a proper deploy, and write it all down.
Health dataMany agencies, one systemWeb, desktop and phone
Software that runs a home care agency, built start to finish by me.
I started Accrenza after hearing the same complaints from home care agencies over and over. I built it the way I build for clients: a
written plan, every screen designed before it was coded, and small releases that actually work. It's the best example of what I can do.
The screens below use made-up data.
The problem
Home care agencies here run their visits, payroll and billing out of spreadsheets, a state portal and a lot of phone calls.
Starting July 2026, Minnesota wants 80% of visits verified electronically. Most agencies only find out they're behind when the
quarterly review shows up.
What made it hard
It handles health data, so each role sees only what it needs and every access is logged.
Each agency's data is walled off in the database itself, not just in the app code.
The state changes its rules every year, so the rules live in settings an admin can edit.
It's just me, so I cut fifteen features before writing any code.
What I built
An office app where the schedule, the verified visit, the claim and the payroll come from the same record, so the numbers always
agree. Accrenza Connect handles calls, texts and a shared inbox. Accrenza Mobile is what caregivers use during a visit. There are AI agents too,
but they only make suggestions. A person always signs off.
.NET 8BlazorPostgreSQLAzure
From the design · made-up data
1 / 5 Agency dashboard. What the office sees first thing in the morning. Anything with a legal deadline sits at the top.
2 / 5 Master schedule. The day's visits on one board, with open shifts next to them and the hours each client has left.
3 / 5 Claim management. Billing, from the claim to the payment. When a claim is denied you see why and how long you have to fix it.
4 / 5 EVV compliance. The number the state checks: how many visits were verified. Every problem visit is listed until someone fixes it.
5 / 5 Connect inbox. Calls, texts, voicemail and email in one inbox, with the client each message is about shown alongside it.
Twenty minutes to hear about your business and what's getting in the way. You don't need to prepare anything. If I'm not the right
fit, I'll tell you and suggest someone who is.
02
A fixed-price proposal
A few days later you get a written proposal: what's included, what isn't, the milestones and one price. You'll know the cost
before any work starts.
03
Weekly demos
Every week I show you working software and send a short note on what's next. If something needs to change, we catch it early,
while it's still cheap.
04
Handover
The code is already in your account. At the end you also get documentation, tests and a recorded walkthrough. Any support after
launch is written into the proposal.
What you get
You own all of it. Nothing depends on me.
The source code, in your repository from day one
Hosting on your own cloud account, in your name
Documentation another developer can follow
Automated tests for the parts that matter most
A recorded walkthrough of the finished system
A signed scope and a fixed price before we start
Working with me
A few things worth knowing.
What I build with
Mainstream tools with long support lives, so you can still hire people for them years from now.