Slopfix

Did that happen to you?

You have an AI-generated codebase that works, but adding a feature now takes days and breaks two other things? This happens to every vibecoded project past a certain size: the agent stops seeing the whole picture and starts duplicating code instead of finding it. We can help.

What we do?

We analyze your codebase for free. If we don't think we can help, we say so and you've lost nothing. If we can, you get a fixed price and a committed reduction target — something like "100,000 lines down to 35,000, same functionality."

Then we do one week of focused work. Before touching anything, we sit down with you and write out exactly what your app does, screen by screen, endpoint by endpoint. That checklist is our safety net and yours. Then we cut: the fourteen date formatters become one, the hand-rolled framework becomes a library, the duplicated logic collapses. Where the code is beyond saving, we distil what it does and rebuild that part clean.

You keep everything. The smaller codebase, the QA checklist, and a set of guardrails — a CLAUDE.md, lint rules, CI checks — that slow the slop down when you go back to building. Plus two weeks of warranty: if we broke something that worked before, we fix it free.

Yes, we use Claude Code too. On a very short leash. The difference is thirty years of combined experience about what maintainable code looks like, and the agent doesn't get a vote.

What it costs?

One week. Three senior engineers. $10,000. We commit to a reduction target up front, and you pay in proportion to how much of it we hit. Promised 50% and delivered only 20%? That's 40% of the target, so you pay $4,000. Hit the target or beat it, you pay full price.

Lines are counted by scc, non-blank and non-comment, and the contract bans code golf. We don't win by deleting your comments or compressing your code into something clever and unreadable.

We are not agents

Talk to us

We're real people and we'd rather talk than exchange forms. If the story above sounds like your last three months, get in touch: maciej@odra.dev.

Bring your repo. The analysis is free either way.