Platform Exit Readiness Review (Handoff)

Platform Exit Readiness Review (Handoff)

1. 01

   Inventory every app, table, workflow, and integration the client depends on

   Walk the live environment rather than the original scope doc. List each connected data source (Airtable bases, Google Sheets, HubSpot objects) and mark which ones the client's staff touch daily.

2. 02

   Score each build against the platform's hard ceilings before promising portability

   Record row limits, API call quotas, automation run caps, and file storage per app. A client portal built in Noloco on 20+ connected sources behaves differently at 50,000 records than at 500.

3. 03

   Export the data model and a full record dump to a client-owned destination

   Deliver CSV plus schema documentation into storage the client controls. Confirm restore works by loading the dump into a scratch environment and reconciling record counts.

4. 04

   Document logic that lives outside the data layer

   Write down every workflow trigger, conditional branch, and AI agent prompt in plain language. Visual builders hide this logic in configuration screens that disappear the moment the subscription lapses.

5. 05

   Test the rebuild path on one representative module

   Pick the highest-traffic screen and reproduce it in a second environment, whether that is Bubble, WeWeb, or a conventional stack. Time the rebuild and use that number to price the migration clause.

6. 06

   Separate white-label assets from platform-bound assets

   Custom domains, RBAC roles, and branding configured inside AINIRO or Taskade do not travel. Capture screenshots and config exports so the client's brand layer can be recreated elsewhere.

7. 07

   Set the ownership and access clause in the retainer renewal

   Name who holds the platform account, who pays the seat bill, and what happens to the app if the engagement ends. Ambiguity here is the most common source of post-handoff disputes.

8. 08

   Schedule a 90-day portability recheck

   Re-run the ceiling scores against current usage. Growth in records or integrations is the signal that a rebuild decision is now cheaper than staying put.