Bugs nobody can find
A 500 on one endpoint, a report that is wrong on Tuesdays, a job that takes all night. I reproduce it, trace it, fix it, and write up why it happened.
Custom software · ASP.NET Core, C#, Angular, Azure
Your .NET app is broken, stuck, or half-finished, and the person who built it isn't answering.
By this time tomorrow you can know exactly what is wrong, what it takes to fix, and what it costs, in writing, for free. Then you decide. No call required, no retainer, no guessing.
- to a written diagnosis
- 1 business day
- quoted before any work
- Fixed price
- for a single bug fixed
- From $150
The developer left. The app didn't.
Hey, I'm Skylor. A few years ago I inherited a set of programs that send benefits enrollment files to insurance carriers for a school district. The developer who wrote them was retiring. There was a handoff meeting, a folder of code, and then he was gone. If those files went out wrong, thousands of people's insurance went wrong with them.
So I did what you do: I read every line, figured out what it actually did instead of what the notes said it did, and ran it through open enrollment myself. It has run clean every cycle since. That is most of what custom software work is. Somebody built a thing, they are not around anymore or not answering, and it has to keep working anyway.
If that is where you are, you do not need a pitch. You need someone to look at it, tell you the truth about what state it is in, and put a number on fixing it. That is the free diagnosis. Send it over, and you will have that answer by tomorrow.
What I fix and build
Features with a date on them
A new screen, a new API, an integration with the system you already use. Spec first, then built behind a flag so your users see nothing until you say go.
Half-finished apps
The last developer left. I read the code, tell you honestly what state it is in, and finish it or tell you what finishing it would cost.
Slow or fragile SQL
Queries that time out, jobs that fail on load, databases that grew past what the code expected. SQL Server and Azure SQL.
Cloud deploys and CI
Azure App Service, staging slots, GitLab or GitHub pipelines, Jenkins. Deploys that happen on a push instead of a prayer.
Apps from scratch
Membership platforms, internal tools, estimating and quoting apps. Built in phases you approve one at a time, each one shippable on its own.
- C# and .NET 8
- ASP.NET Core Web API and MVC
- Entity Framework
- SQL Server and Azure SQL
- Angular and TypeScript
- React and Astro
- Azure App Service
- GitLab, GitHub, Jenkins CI/CD
What you actually get
- Know what is wrong before you spend a dollar, because the diagnosis comes first and it is written down, not talked at you on a call.
- Never get a surprise invoice. Fixed price on anything with a fixed scope, quoted before I start, and it does not move unless you change the scope.
- Stop babysitting the developer. You get a short written update at every milestone, in plain English, saying what changed and what is next.
- Your users see nothing until you say go. New work ships behind a flag or on a staging copy, so a fix never becomes a second outage.
- Understand your own system afterward, because every fix comes with a write-up of the root cause. The next person, or you, will not have to guess.
- If the fix does not fix it, you do not pay for it. That is the guarantee on every fixed-price job.
How the money works
You always know the number before I start. Small things are fixed price. Bigger things are built in phases, and each phase is its own fixed price you approve first.
Diagnosis
FreeSend the repo, a zip, or just a description. Within one business day you get a written diagnosis: what is wrong, what it will take, and a fixed price to do it.
One bug, fixed
From $150Root cause found and fixed, tested, with a short write-up of what changed and why. Two-day turnaround on most.
Feature or module
From $400Spec first, then built, tested and handed over. Quoted fixed after the diagnosis.
Discovery and spec for a new app
$750, creditedA written feature spec, wireframes of the core screens, and a locked price and timeline for the build. Fully credited toward the build if you go ahead within 30 days.
Ongoing or hourly
$75 / hourFor work that does not fit a fixed scope. Billed only for the hours it takes, with a weekly summary of what those hours did.
Why me
Four and a half years as a Software Development Engineer for a public school district, where I built the district-wide employee leave system, helped migrate the student information system to PowerSchool, and own the benefits EDI pipeline that sends enrollment files to insurance carriers. Systems that thousands of people depend on, running in production today.
Master's in Computer Science, 2026. My thesis was an automated debugging tool built on the Roslyn compiler API that reduces failing C# programs to minimal reproductions. Reading unfamiliar code fast and finding where it breaks is the thing I trained hardest.
Before software I ran auto repair shops for fifteen years. I know what it costs a business when something is down and the person who can fix it is not answering. I answer.
Why is the diagnosis free?
Because it is how I earn the fix. Reading your code and writing up what is wrong takes me an hour or two. If the diagnosis is right and the price is fair, most people have me do the work. Some take the write-up and hand it to someone else, or fix it themselves. That is fine. You still got a straight answer, and the next time something breaks you know who to send it to.
One honest limit: I am one developer, not an agency. I take on what I can deliver well. If your job is bigger than that, the diagnosis will say so and tell you what kind of team you need instead.
Free diagnosis
Get your free diagnosis
Describe what is broken or what you need. A repo link or a zip helps but is not required. Within one business day you get a written diagnosis and a fixed price.
Here is what happens next. Fill in the form and hit send. I read it the same day. Within one business day you get an email with what is wrong, what it takes, and a fixed price. If you want it done, reply yes. If not, you keep the write-up.