Failure review intake

Submit a stuck AI app

Send a short summary of the project, what is broken, and what decision you need. I will tell you whether it is suitable for a structured failure review.

Submitting a summary does not guarantee a review. I first check whether the case is clear enough and whether a review would be useful.

This is not a replacement for your team. It is a second technical judgment your team can use internally or adapt for client communication when a project becomes unclear, risky, or hard to deliver.

Send a project summary See sample review

What to include

Your name
Email
Are you an agency, builder, founder, or other?
What was built?
What tool or stack was used?
What is currently broken?
Is auth, database, payment, or deployment involved?
What decision do you need: fix, rebuild, handoff, stop, or not sure?
Can you share screenshots, repo access, logs, or a short video?
Additional context

Submit a stuck AI app summary

Share the minimum context needed to identify what is broken, what is risky, and whether the safest path is to fix, rebuild, hand off, or stop.

Your nameYour roleReview typeProject typeCurrent situation

What did you build?Which tool generated or assisted the app?What stack does it use?Is the app live?What is the main concern?What are you trying to decide?EmailDescribe what is currently failing or risky.Link to app / preview / repo / screenshots / short video if available

Do you use Supabase?Do you have production data?Have real users already used it?

What has AI already changed?What should not be broken?

No payment is required before submitting this request.

Do not send production secrets, API keys, customer data, or private repo access in this form. Safe app previews, screenshots, error messages, Loom videos, or public repo links are enough.

Need context before submitting?

Review the agency page or sample report format before sending a real project.

For Agencies Sample Review