Software delivery resources for the work after the demo
Choose the resource that matches the problem: recover control of software that has lost its owner, or prepare an AI-generated prototype for real users, real data, and ongoing maintenance.
Ownership recovery
Software Rescue Checklist
A GitHub-ready README and documentation pack for recovering source, deployment, access, data, integrations, workflows, runbooks, and a named operating owner before choosing rescue or rebuild.
- Copy-ready README and docs structure
- Measurable UTM backlink plan
- Rollback and authorization boundaries
Production readiness
Prototype to Production Checklist
A publishing kit for explaining the eight production-readiness areas behind a maintainable AI-generated app, with dev.to, Medium, LinkedIn, canonical, and measurement instructions.
- Platform-ready educational drafts
- Canonical and UTM instructions
- 48-hour and day-7 readback plan
Handoff control
Software Handoff Publishing Kit
A publishing kit for teams whose original developer left, whose outsourced build stopped, or whose vibe-coded app has no maintainer, with dev.to, Medium, LinkedIn, canonical, and measurement instructions built on the software handoff guide.
- Seven handoff facts to recover control first
- Canonical and UTM instructions
- 48-hour and day-7 readback plan
Use the resources as an operating sequence
- 1 · InventoryRecord what exists, who controls it, and which workflows must keep working.
- 2 · DecideChoose the smallest responsible path: stabilize, rescue, harden, replace one capability, or rebuild.
- 3 · MeasurePublish or share one useful resource, retain its campaign labels, and read back referrals, clicks, and search discovery.
Need a next-step decision instead of another checklist?
Use the diagnostic for a short recommendation, or open the Software Problem Clinic when one workflow, integration, or prototype is blocking the team.