Regularly, yes — and we’d rather find out what we’re actually dealing with than quote blind. New codebases start with a short paid audit: a few days going through the code, the hosting setup, and whatever documentation exists (often not much), so we can tell you honestly what state it’s in before committing to a timeline or a price. Sometimes that audit changes the recommendation entirely — a plugin conflict that looked like it needed a full rebuild turns out to be a one-line fix, or a database that looked slow just needs better indexes instead of a replatform.

If the audit turns up something genuinely unsalvageable, we’ll say so, and we’ll say why — not just because the code is unfamiliar or written differently than we would have written it. Inheriting someone else’s decisions is a normal part of this work, not a reason to recommend starting over.

Something in here sound like your project?

Tell us what you're building and we'll tell you honestly whether we're a fit.

From the blog

More from the blog

All posts