You got further than most people do
Lovable, Bolt, Replit, Cursor and Claude Code can get you a working app in a weekend. That's a real accomplishment, and we use some of the same tools ourselves. The trouble tends to show up later. Each new prompt breaks something that used to work, or you're about to let customers in and you can't tell whether their data is safe.
Each fix breaks something else
You ask for one change and two other screens stop working. The bigger the app gets, the more often it happens.
Nobody has checked it
It works when you click through it yourself. That says little about what happens with real customers, or with someone trying to get in.
We read the code first
We start by running your app and reading what's there, then we tell you what we'd keep and what we'd change. These are the things we look at first, because an app can feel finished while all of them are still open.
Who can see whose data
Can a logged-in customer read another customer's records? We try it, and we check the database rules that are supposed to stop it.
Passwords and keys
Keys that ended up in the browser or in the code get moved somewhere safe and replaced.
Backups
We restore one, because that's the only way to learn whether it works.
Knowing when it breaks
We add monitoring, so you hear about an outage before your customers tell you.
Fix it or rebuild it
Honestly, we'd rather keep your code when we can. A rebuild makes sense when the foundation is wrong, like a database that can't represent how your business works. Even then, the app you made is the clearest brief we could ask for. It shows what you meant better than a document would.
What usually stays
Your screens, your flows, and anything your customers already like.
We've made this call before
The We Believe Foundation brought us a rough prototype of a scripture-study app in 2021. We rebuilt it as native iOS and Android apps and submitted the first version to Apple about ten weeks later. That was before anyone called this vibe coding, but it's the same decision.
You can keep building
Finishing your app doesn't have to mean giving it up. One of our clients wanted to keep vibe coding on production work, so we set up a repo with safeguards and Claude skills. When he has a pull request ready, it drafts the message to our developer for him.
Checks before anything goes live
Tests run on each change, and you see a preview before your customers do.
Someone to hand it to
When you hit something you don't want to trust to AI, our developers take that part.
Apps we've built
Frequently asked questions
HQ can. We're a software design and development agency at 2411 Kiesel Ave in Ogden, Utah, started here in 2012 by Matt Sutherland and Zarin Ficklin. We take over apps built with AI coding tools, and the office is open if you'd rather meet in person. We work with clients outside Utah too.
Lovable, Bolt, Replit, Cursor, Claude Code, v0, or anything else that produces code you can get a copy of. The tool matters less than what it produced.
Only if we think keeping it would cost you more. We'll show you why, and you can get a second opinion.
Maybe not. An internal tool used by a few people you trust carries much less risk than an app holding customer data. If that's what you have, we'll tell you.
It depends on what we find in the code, so we don't publish a number. We'll give you an estimate once we've read it.
Yes. We can set up the repo so your changes go through a review before they reach your customers.
Not sure what you've got?
Show us what you built. We'll tell you what we'd do first, or that it's fine as it is.
Book a consultation