You're at the intersection of growth and constraint. Demand for your services exceeds capacity. You could hire more staff. You could contract out specific functions. You could partner with another organization. Or you could slow growth. These aren't small decisions—each shapes organizational culture, financial sustainability, and mission impact for years to come.

Yet most nonprofits make these decisions reactively, without a framework. "We're drowning, so let's hire someone" or "We can't afford staff, so let's contract it out." This approach misses the strategic considerations that separate sustainable growth from unsustainable sprawl.

The Three Capacity Models

Before choosing, understand your options. You have three fundamental approaches to capacity: internal staff, contractors/consultants, and partnerships. Each has different financial, operational, and cultural implications.

Internal Staff

You employ full-time or part-time employees. Advantages: you control quality, build organizational culture, create career pathways, maintain institutional knowledge. Disadvantages: significant fixed costs, responsibility for employment compliance, management overhead, commitment during slow periods.

Full-time staff cost roughly 1.3-1.5x salary (when you add benefits, payroll taxes, and overhead). A person earning $50K likely costs $65K-75K total. This is fixed cost—you pay it whether they're at full capacity or not.

Contractors/Consultants

You pay for specific projects or hourly work. Advantages: flexibility, no fixed overhead, access to specialized expertise, scalability. Disadvantages: expensive at hourly rates, no institutional knowledge building, less control over quality, difficulty with continuity.

Consultants might charge $75-200/hour depending on expertise. A project that would cost $30K annually with staff might cost $60K with consultants because hourly rates include their own overhead.

Partnerships

You collaborate with another organization to expand capacity. This might be formal (shared staff, joint programs) or informal (referral networks, work-share arrangements). Advantages: shared cost and risk, access to expertise and reach, mission alignment. Disadvantages: complexity, loss of control, potential conflicts.

The Decision Framework

Use these criteria to decide among your options:

1. Is This Core to Mission or Peripheral?

Core mission activities should typically be internally staffed. You need direct quality control, accountability to your community, and cultural alignment. If you're an education nonprofit, education programming should be internal. Finance might be outsourced.

If activity is peripheral (IT support, bookkeeping, legal compliance), you're a good candidate for outsourcing or partnership. You don't need to build expertise; you need the service reliably.

2. How Consistent Is the Work?

If work is steady and year-round, internal staff makes sense. You need someone consistently. If work is seasonal or project-based (that grant writing is intense for three months, then light), contracting or partnership works better. You don't want to employ someone full-time for three months of work.

3. Do You Have or Can You Develop the Management Capacity?

Hiring requires management. Someone must onboard, train, provide feedback, handle performance issues, plan development. If you lack these management systems or bandwidth, hiring will be painful. Outsourcing or partnership might be better until you build management capability.

4. What's Your Financial Reality?

What can you actually sustain? Calculate true cost: salary, benefits, overhead, management time. Can you commit to this for 3+ years? If not, you cannot hire. You might contract instead. If you have funding for three years but not a permanent position, structure the hire accordingly (grant-funded position with transition plan).

5. Is Specialized Expertise Required?

If you need deep expertise that's hard to find and expensive to employ full-time, contracting makes sense. Hiring a CFO might be overkill if you don't need someone full-time. Contracting with a bookkeeper handles the core work; contracting with a financial consultant handles strategic planning.

6. Is Institutional Knowledge Crucial?

Some functions benefit from deep understanding of your organization: program leadership, development strategy, operations. These should be internal so knowledge builds. Other functions are more commodified: basic bookkeeping, IT support. These can be external.

7. Does Another Organization Already Do This Better?

If a peer organization is excellent at something you need, partnership might beat building it yourself. If a coalition partner is already doing community outreach, you might partner rather than hire a dedicated outreach person. Avoid duplicating excellence.

Practical Decision Tree

Work through this sequence:

Step 1: Is this work essential? If not, consider reducing scope rather than adding capacity. No work you can eliminate is better than the best contractor.

Step 2: Is this core mission? If yes and you have stable funding, hire internally. If yes but funding is unstable, contract or partner while you stabilize. If no, move to step 3.

Step 3: Is this work consistent year-round? If yes and you need it ongoing, hire or partner. If no, contract for specific projects.

Step 4: Do you have management capacity? If yes, you can hire. If no, contract or partner, or invest first in management systems.

Step 5: Can you afford it sustainably? If yes, move forward with your preferred model. If no, reconsider scope or timeline.

The Partnership Option: Often Overlooked

Partnerships deserve special attention because they're powerful and underused. A shared staff person (you and another org each pay 50%) cuts your fixed costs. A referral network reduces need for hiring by distributing clients. Programmatic partnerships (you run programming, they do evaluation) divide labor.

Partnerships work best when:

  • Organizations have complementary (not competitive) missions
  • Goals are clearly aligned
  • Decision-making processes are documented
  • Financial arrangements are explicit
  • There's a trial period before full commitment

Partnerships fail when organizations assume alignment without discussing it, don't formalize agreements, or don't have mechanisms to resolve conflicts. The best partnership is one with a clear exit strategy if it's not working.

Hiring Well If You Choose That Path

If you decide to hire, do it strategically. First, define the role clearly. What are actual responsibilities versus assumed responsibilities? How much of the person's time is spent on them? This prevents role inflation that leads to burnout.

Second, secure funding. You should fund at least three years of salary plus benefits before hiring. If you cannot, you're setting up for layoffs or the burnout discussed in lecture 2-7-1. Funders understand this—many will fund positions for multiple years.

Third, hire for growth. Hire someone slightly ahead of where you are, not just to fill current gaps. This helps the person grow and prevents them from becoming overwhelmed as the organization evolves.

Fourth, have succession plans. Before hiring someone into a critical role, understand what happens if they leave. This forces you to create systems and documentation rather than relying on person-dependent knowledge.

Avoiding Common Mistakes

Don't hire to solve management problems. If a process is broken, hire won't fix it—it'll just add another person to a broken system. Fix the process first, then hire if needed.

Don't hire permanently for temporary work. If you have a grant-funded project that lasts two years, hire for two years with explicit end date and transition planning. Don't create permanent staff for temporary funding.

Don't hire without asking: "Could we solve this through partnership?" Many nonprofits default to hiring when smarter collaboration would work better.

Don't underestimate management cost. If you're hiring your first employee, expect management to cost you 10-15 hours per week. This is real—account for it in your own capacity planning.

Making the Final Decision

Bring your leadership team and board to the decision. Use your framework to make it transparent: "We need capacity in X. Here's why hiring makes sense (or partnering, or contracting). Here's the cost and commitment. Here's the alternative." This builds buy-in and ensures board understands the implications.

Document your decision. "We chose to hire internally rather than contract because X is core to mission and we have stable funding. We chose to contract Y because it's not core and we don't have management bandwidth to add another employee." This prevents revisiting the decision when it gets hard.

Then monitor the decision. Check in after 6-12 months: "Is this working? Are we getting what we expected? Should we adjust?" Growth decisions should be revisited, not set and forgotten.

Frequently Asked Questions

Can we hire now and figure out funding later?

Not responsibly. Hiring commits you to three-year cost of roughly 1.5x salary per year ($50K salary = $150K commitment). This is a major financial decision. You should secure funding first or have clear plan to raise it. If you hire speculatively, you're vulnerable to funding gaps and may face having to lay off someone. This damages your reputation and the individual. If funding looks promising but isn't confirmed, you might structure a temporary or part-time position that converts to full-time once funding is secured.

How do we know if a partnership will actually work?

Start small. Before committing to a major partnership, try a smaller collaboration. Share resources on one program or project. Spend three months seeing how you work together, how decision-making happens, whether values align. Then decide whether to expand. A structured trial period (with clear success metrics and exit plan) protects both organizations from bad partnerships. It also surfaces problems early when they're easier to address.

Is it ever better to stay small rather than hiring?

Yes. Not every nonprofit should grow. Some organizations do excellent work at current size and adding staff would actually reduce quality or mission focus. Before deciding you must hire, ask: "What would we lose if we stayed this size? What would we gain?" Sometimes the answer is "we'd limit impact" and you hire. Sometimes the answer is "we'd preserve quality and culture" and you don't. This should be intentional, not a rationalization for avoiding growth.

What if we contract someone and they become indispensable?

This is a risk with contractors—you become dependent. Manage it by documenting processes, rotating contractors where possible, and planning transitions before they're necessary. If a contractor becomes genuinely indispensable, you might convert to internal staff (if the work justifies it) or identify and develop backup capacity. The worst outcome is discovering months into a contractor relationship that you have no contingency if they leave.

How do we transition from contracting to internal staff?

If you've contracted with someone and want to bring them on staff, handle it thoughtfully. Offer the position directly if it makes sense. Be clear about the transition: "You've been consulting with us at $X per month. We'd like to offer a full-time role at $Y salary plus benefits." This is typically more generous than the contractor rate since benefits have value, but they're moving from project work (where they had other clients) to exclusive employment. If the math doesn't work for them or you, it might be cleaner to stay with the contractor relationship.

The best capacity decision is the one made intentionally with full information. It balances mission needs, financial reality, organizational culture, and growth strategy. It's rarely just "hire" or "don't hire"—it's "hire for this, partner for that, contract for this other thing, and accept reduced capacity in that area."