Do not begin with “how much to rebuild it?”
That question is too early. A half-built product may contain plenty that is usable. It may also depend on accounts, services, credentials, or code you do not control. The useful first step is an inventory.
Start by finding the pieces
- Source code repositories such as GitHub, GitLab, or Bitbucket
- Hosting and deployment accounts
- Domain and DNS access
- Database and backend services
- Payment accounts and integrations
- Email, storage, analytics, and third-party APIs
- Design files, specs, credentials, and any existing documentation
Do not send passwords through a contact form or email. The point is simply to establish what exists and which accounts belong to you.
Then we separate three questions: what works, what is recoverable, and what is worth keeping.
Sometimes the code is not the biggest problem.
You may discover the product is technically farther along than you thought but badly scoped. Or the frontend may look finished while the important backend flow was never completed. Or the product may be salvageable with a few targeted fixes instead of a full rewrite.
I can help you make that diagnosis before you commit to another large build. If the next step requires a specialist engineer, security review, or infrastructure migration, I will say so rather than pretending one person should do everything.
Get a clear read before spending again.
The Unstuck Session works well for this kind of mess. Send the product, repo access details you are comfortable describing, screenshots, old scope, and whatever communication or handoff material you have. We can turn “I have no idea what they left me” into a concrete next-step list.
Start the recovery ↗
Product rescue for stuck founders