Nonprofit program expansion planner

What goes in and out

You give it

• Outcome evidence for your program
• How the program is delivered
• Staff capacity and financial reserves
• Funding set aside for growth (optional)
• The new community or group you want to reach
• Document (optional)

You get

• A readiness memo with a go, no-go or not-yet call
• A table of what must stay fixed and what can change
• A recommended way to expand
• A pilot plan for one new site
• A plan to check results and fix problems

How the task works

• Check readiness first. Review outcome evidence, model clarity, staff capacity, funding, and demand in the new area.
• Protect what makes it work. Separate essential program parts from details that can change for a new location or group.
• Pilot before wider growth. Choose a delivery route, plan staff and systems, and set checks and correction rules for a first new site.

Full instructions

• Open Claude, ChatGPT or Gemini. No code or paid tool is needed.
• Paste the skill text, or upload your files if your AI accepts them.
• Add your outcome evidence, how the program runs, staff and reserves, growth funding and the new community.
• Read the readiness memo first. If it says not yet, fix the gaps before you plan the expansion.
• Ask frontline staff to check the fixed-versus-flexible table, since they know what really drives results.
• Have your board or a nonprofit advisor review the plan before you commit money or staff.

Full instruction file

Nonprofit Program Scaling

Before you start

Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait.

What you need (use your own material or the linked skill):

• Your question (yours): the decision or problem, and what a good outcome looks like.

Makes it better (optional):

• A document (yours): a finished document, such as a Word file, a PDF or a page of notes.

How to start:

1. Look first. Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name.
2. Check what's missing. Look for your question, a document. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps.
3. Do the job. Follow the skill below with the facts and tools you have. Mark each gap with MISSING: where it belongs and never invent a fact to fill it.

Tools that do this best:

• A chat AI that can read your files: The skill works from records and drafts you provide. Research tasks also need current, checked public sources.

When to Use This Skill

Use this skill when a program has already shown evidence it works and the question is how to grow its reach — to more people, more sites, or new geographies — without losing what makes it effective. Concrete triggers:

• "Is this program ready to scale?"
• "We want to expand this program to three new cities — how do we do that without diluting it?"
• "Should we franchise/license this program to other organizations, or run it ourselves at new sites?"
• "How do we adapt this program for a different population/cultural context?"
• "Build a replication toolkit / program-in-a-box for affiliate sites."
• "What staffing and systems do we need to support this growth?"

Boundary — read before starting:

• Designing the original program's logic model/theory of change is nonprofit-program-design — this skill assumes a working model already exists and is being extended, not created.
• The evaluation methodology used to establish that the program works in the first place is nonprofit-outcomes-measurement — this skill uses evaluation results as a scaling-readiness input but doesn't design the evaluation itself.
• Broader organizational revenue-model diversification (earned income, social enterprise) is nonprofit-revenue-diversification — this skill is about programmatic reach, not revenue mix, even though scaling usually requires new funding.
• Formal merger, consolidation, or fiscal sponsorship structures with another organization are nonprofit-mergers-fiscal-sponsorship; use this skill for scaling your own program, not combining organizations.

Core Frameworks

1. Readiness-to-Scale Assessment

Before recommending any scaling path, assess against these dimensions (commonly used by scaling intermediaries like the Bridgespan Group and Duke's Center for the Advancement of Social Entrepreneurship):

• Evidence strength: Is there credible outcomes data (not just outputs) showing the program works, ideally from more than one cohort/site? Weak evidence is the most common reason a scaling attempt fails later — surface this gap and route back to nonprofit-outcomes-measurement if the evidence base is thin.
• Model clarity: Can the "active ingredients" of the program — the specific elements that actually drive the outcome — be named and separated from context-specific or founder-dependent elements? If nobody can articulate what must stay fixed versus what can flex, the program isn't ready to codify for replication.
• Organizational capacity: leadership bandwidth, financial reserves, back-office systems (HR, finance, data) able to support multi-site operations, not just program delivery capacity.
• Funding runway for scale: growth capital is categorically different from program funding — expansion requires upfront investment (staffing, systems, site start-up costs) before new revenue or outcomes materialize; undercapitalized scaling is a leading cause of failed expansions.
• Market/demand validation: confirmed demand and receptivity in the new site/population (treat this as a mini needs assessment for the new context — coordinate with nonprofit-needs-assessment if it hasn't been done for the target location).

2. Fidelity vs. Adaptation Framework

The central tension in all program replication:

• Fidelity = replicating the program faithfully to preserve the elements that produced the proven outcome.
• Adaptation = adjusting the program to fit a new context's culture, resources, population, or regulatory environment.
• The core task is distinguishing "core components" (must stay fixed) from "adaptable periphery" (can and should flex). Common core components: dosage/intensity (how much service, how often), staff qualifications/training model, curriculum sequencing, target population eligibility criteria. Common adaptable periphery: language, specific examples/materials, delivery location, partnership structure, minor scheduling.
• Document this explicitly as a fidelity matrix: component | core or adaptable | rationale | acceptable range of variation | how fidelity will be monitored at the new site.
• Failure to distinguish these leads to two opposite failure modes: rigid over-fidelity (forcing an urban curriculum unchanged onto a rural site where it doesn't fit, causing poor uptake) or fidelity drift (so much local adaptation that the new site no longer delivers the elements that actually drove the original outcome, and results don't replicate).

3. Replication Models (name the model explicitly when advising)

• Direct expansion (branching): the original organization opens and directly operates new sites. Highest fidelity control, highest capital and management burden.
• Affiliate/licensing model: independent local organizations run the program under a license, using a shared brand, standards, and training, with a central "hub" providing training, quality monitoring, and sometimes a licensing fee (e.g., Boys & Girls Clubs, Habitat for Humanity affiliate structures). Lower capital burden for the originator, harder fidelity control.
• Open-source / toolkit dissemination: publishing curriculum, training materials, and implementation guides for any organization to adopt with light or no central oversight. Fastest, cheapest reach; weakest fidelity guarantee and weakest ability to track aggregate outcomes.
• Government/systems adoption: embedding the model into a public system (school district, Medicaid, workforce system) so it scales through public infrastructure and funding rather than nonprofit replication. Requires policy/advocacy capacity, not just program capacity — coordinate with nonprofit-legislative-advocacy if this path is chosen.

Match the model to the readiness assessment: weak central capacity + strong desire for reach often points toward toolkit/open-source; strong evidence + need for fidelity control often points toward direct expansion or a tightly managed affiliate model.

Instructions

1. Run the readiness-to-scale assessment (evidence, model clarity, organizational capacity, funding runway, market validation) before committing to any expansion. If evidence is weak, stop and recommend strengthening measurement first rather than scaling on hope.
2. Name the program's core components vs. adaptable periphery in a fidelity matrix, built with the people who deliver the program, not just leadership — frontline staff usually know which elements are load-bearing.
3. Choose a replication model (direct expansion, affiliate/licensing, open-source toolkit, systems adoption) matched to the organization's capital, control needs, and desired speed of reach.
4. Build the "program-in-a-box": codified training curriculum, staffing/qualification requirements, operations manual, data collection tools, and quality/fidelity monitoring instruments — this is the standard deliverable new sites or affiliates need to start consistently.
5. Assess the new site/population before launch — treat this as a scoped local needs/context check (partner with nonprofit-needs-assessment methodology): local demand, cultural fit, competing/complementary providers, regulatory differences.
6. Pilot the adaptation before full rollout — run a single new site as a controlled pilot, measuring against the same core outcome indicators as the original program, before scaling further; treat divergent results as a fidelity-matrix signal, not just a new-site execution issue.
7. Build the staffing and systems plan for scale: multi-site program management structure, data systems that roll up across sites, a training/certification pipeline for new staff, and a quality assurance/monitoring cadence (site visits, fidelity checklists, outcome dashboards by site).
8. Secure growth capital explicitly — separate "program funding" asks from "scaling/growth capital" asks (systems, staffing, site start-up) when approaching funders; conflating the two under-resources the transition.
9. Set a fidelity monitoring cadence post-launch (e.g., quarterly fidelity checklist plus annual outcomes comparison against the original site) rather than assuming replication succeeded because the program launched.
10. Decide and document a course-correction protocol in advance: what happens if a new site's outcomes lag — retrain, adjust the local adaptation, or sunset the site — so this isn't improvised under funder or board pressure later.

Common Failure Modes

• Scaling on weak or single-cohort evidence — expanding before the evidence base can support claims the model reliably works, then facing credibility damage when new-site results disappoint.
• No fidelity matrix — either rigidly forcing the original model onto an incompatible new context, or allowing so much local adaptation that the new site no longer resembles the program that produced the original outcome.
• Undercapitalized expansion — treating growth capital as a rounding error on the program budget instead of a distinct, often multi-year funding need (systems, training, site start-up lag before revenue/outcomes catch up).
• No new-site context assessment — assuming a model that worked in one community will transfer without checking local demand, culture, or competing providers.
• Founder-dependent model — a program whose success actually depends on one irreplaceable staff member's relationships or charisma, not the codifiable pieces of the program; this is a readiness failure, not a replication-toolkit problem, and needs to be surfaced honestly.
• No ongoing fidelity monitoring — treating "we opened the new site" as the finish line rather than the start of an ongoing quality-assurance cycle.
• Choosing direct expansion when capacity can't support it (or choosing open-source dissemination when the funder/board actually needs outcome attribution) — mismatching the replication model to organizational capacity and control needs.

For Advisors/Consultants

• Lead every scaling engagement with the readiness assessment as a distinct, sometimes disappointing, deliverable — clients often arrive already committed to a specific expansion (a new city, a board member's pet site) and need an honest capacity/evidence gap-check before the advisor helps them build the expansion plan itself.
• Facilitate the core-vs-adaptable-periphery exercise (fidelity matrix) directly with frontline delivery staff, not only executive leadership — this is where advisors most often catch a model leadership believes is "the curriculum" but staff know is actually "the relationship the coordinator builds," which changes the whole scaling strategy.
• When a client wants to move fast via open-source/toolkit dissemination for reach or visibility, make the fidelity/attribution tradeoff explicit in writing — funders sometimes want the aggregate outcome story a franchise/affiliate model can deliver, which open dissemination cannot.
• Standard advisory deliverable: a scaling readiness memo (with a go/no-go or "not yet" recommendation and what would need to be true to proceed), a fidelity matrix, a replication model recommendation with rationale, and — if proceeding — a program-in-a-box outline and growth-capital funding ask separate from the core program budget.

Standard Deliverables

• Readiness-to-scale assessment memo (evidence, model clarity, capacity, funding runway, demand)
• Fidelity matrix (core components vs. adaptable periphery, with rationale and monitoring plan)
• Replication model recommendation (direct expansion / affiliate-licensing / open-source / systems adoption) with rationale
• Program-in-a-box materials outline: training curriculum, operations manual, data tools, fidelity checklists
• Growth-capital funding ask, separated from ongoing program budget
• Post-launch fidelity monitoring and course-correction protocol

After this

When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:

• The Program keep-or-cut reviewer. It takes the plan.
• The Revenue partnership program planner. It takes the plan.
• The Nonprofit strategy planner. It takes the plan. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.