RAPIDITERATION — SOFTWARE SUSTAINMENT PLAN
Version: 2026-11-01
Guide: https://rapiditeration.com/insights/grant-funded-software-after-the-grant/

A blank planning template, not funding advice or a cost estimate. Complete
it during the proposal, before the build is scoped, and attach it to the
project file. Amounts are yours to establish with your own suppliers.

ORGANIZATION:
SYSTEM / PROJECT:
FUNDER AND GRANT PERIOD:
PLAN OWNER:
DATE COMPLETED:

ANNUAL OPERATING COST AFTER THE GRANT
Record an amount and the person accountable for each line.
Hosting, storage and backups:
Domain and certificates:
Dependency and security updates:
Third-party services and licences:
AI or messaging usage (include the cap and who is alerted):
Content maintenance and user support (staff time):
Contingency:
ANNUAL TOTAL:

WHERE THE MONEY COMES FROM AFTER THE GRANT
Core budget line (named and approved?):
Member, service or user revenue:
Subsequent grant (named, and what happens if unsuccessful):
Confirmed / intended / unfunded:

OWNERSHIP — CONFIRM BEFORE DEVELOPMENT BEGINS
Domain registered to the organization:
DNS access held by (at least two staff):
Hosting account in the organization's name:
Application and third-party accounts:
Source repository and who controls access:
No credential held solely by a contractor or a personal email address:

HANDOVER INCLUDED IN ACCEPTANCE
Current deployment and recovery guide:
Credentials transferred and verified:
Known issues recorded:
Documentation sufficient for an unfamiliar developer:

DESIGN CONSTRAINTS FROM THE REALISTIC BUDGET
If capacity after the grant is limited, record what that removes from scope.
Integrations we will NOT build:
Features requiring regular staff curation, and who will do it:
Managed service chosen over self-hosting (where and why):

INTENDED ENDING — CHOOSE ONE NOW
[ ] SUSTAIN — budget line, named owner, maintenance arrangement:
[ ] TRANSFER — receiving organization, and arranged by what date while the
    original team is still available:
[ ] RETIRE — notice period, data export format, where users go, records to
    preserve, how long URLs stay alive:

Conditions that would move us from one ending to another:
Review date and who calls the review:

RapidIteration — Vancouver, BC — hello@rapiditeration.com