Longer pieces,
straight from the studio.

1. SPost · 001
   26 Sep 2026 · stripe

   Stripe Payment Succeeded, but SaaS Access Is Wrong: A Billing Test Checklist

   A practical acceptance checklist for Stripe subscriptions: payment, invoices, subscription status, app access, durable webhooks and reconciliation.

   Read post
2. Post · 002
   25 Aug 2026 · ai-code-rescue

   Is Your AI-Built App Production-Ready? A 12-Gate Audit

   Audit an AI-built application against twelve evidence gates for ownership, authorization, data, dependencies, recovery and release—without mistaking a working demo or green scanner for production readiness.

   Read post
3. Post · 003
   25 Aug 2026 · software-takeover

   Your Developer Disappeared: The First 72 Hours

   A safe recovery runbook for a live product when its developer or agency is unreachable: preserve evidence, regain authorized control and avoid changes that turn an access problem into an outage.

   Read post
4. Post · 004
   25 Aug 2026 · technical-due-diligence

   Technical Due Diligence for a Small SaaS: Evidence to Verify Before You Buy

   A practical evidence-led technical due diligence guide for small SaaS acquisitions—covering source, production, data, access, suppliers, AI risk and operating continuity.

   Read post
5. Post · 005
   25 Aug 2026 · application-modernization

   Rewrite, Refactor, or Replatform: An Evidence-Based Model for Inherited Software

   A seven-factor decision model for inherited software that separates evidence, unknowns and hard blockers before choosing stabilization, refactoring, replatforming or staged replacement.

   Read post
6. Post · 006
   25 Aug 2026 · enterprise-readiness

   How to Answer an Enterprise Security Questionnaire for Software You Inherited

   A U.S. SaaS guide to scoping a customer security review, answering from current evidence, describing SOC 2 and ISO correctly, sharing artifacts safely and turning unknowns into owned work.

   Read post
7. Post · 007
   03 Aug 2026 · software-takeover

   Software Project Takeover Checklist: A 30-Day Handover Plan

   A practical 30-day plan for taking over live software: establish ownership, verify what runs in production, prove recovery, map release risk and make the first safe change.

   Read post

Let’s build what’s next
and keep it moving.

From an inherited codebase or a new product idea to long-term delivery — we define, build, modernize and operate software your team can truly own.