Twelve questions about the state of your project. You get a straight answer at the end, along with a list of what to do about it, most important first.
You do not need to be technical to answer any of them, and there is nothing here you have to buy.
Your result appears on screen. No email address required to see it.
This is a starting point for a conversation, not a survey of your code. It is built from what usually goes wrong on software projects, weighted by how expensive each thing is to unpick later. Ownership questions carry the most weight, because whether you control your own domain, hosting and code is both the biggest predictor of a painful takeover and the cheapest thing on the list to put right.
Most of what it recommends costs nothing and does not involve changing developer. If your answers show the project is fine, it says so.
If it turns out you do want someone to look properly, that is what the rescue page is about, and how to rescue a failed software project covers the whole process in detail.