A Pro Bono Policy for Solo Founders — Give Strategically Without Getting Exploited
Pro bono work is how many solo founders build early portfolios and give back — and how many burn six months of margin on requests that felt too awkward to decline. The difference between generosity and exploitation is a written policy.
This guide builds that policy: eligibility criteria, formats that create value without open-ended cost, time budgets, and the scripts that let you say yes to the right causes and no to everything else without guilt.
The short answer
- Unbounded free work expands to fill available hours — most founders who "help out informally" lose 20%+ of capacity to it.
- Free work for businesses (even small ones) is not pro bono; it is discounting with worse positioning.
- Cause-aligned free work generates referrals and portfolio assets at several times the rate of scattered favors.
Who this playbook is for
Built for solo founders who want to contribute skills to causes they care about without becoming the free vendor of half their network.
Step 1: Split "pro bono" from "free work for businesses"
Pro bono serves registered nonprofits, community projects, or individuals in genuine hardship. A friend’s startup, a colleague’s side project, exposure offers — these are business requests. Answer them with business pricing, politely: "For startups I keep the same rates, but here’s a smaller scoped option." Blurring this line is how exploitation gets its foot in the door.
Step 2: Cap the budget in hours, annually and monthly
Decide what you can genuinely afford: commonly 5-10% of working time — one day a month, or two capped projects a year. Put it in your calendar system as a budget. When the budget is spent, new requests join next quarter’s queue. A cap converts guilt into arithmetic.
Step 3: Choose formats with built-in boundaries
Prefer: fixed-scope deliverables (a one-page site, a 90-minute strategy session, a template), group formats (a workshop serving ten nonprofits at once), or advisory slots. Avoid open-ended roles ("we’ll make you a partner on this") — free work with responsibilities is a job with no salary.
Step 4: Qualify causes with three questions
Does the mission genuinely matter to me? Would my contribution be the constraint-breaker (they cannot buy this elsewhere), or a nice-to-have? Is the requesting organization organized enough to receive the help? A chaotic free client consumes triple the planned hours — disorganization is expensive at any price.
Step 5: Decline the rest with a kind, reusable script
"My pro bono calendar is committed this quarter, so I can’t take this on — but here are two people who might, and here’s my [template/resource] if useful." Warm, finite, and it points somewhere. The script exists so the decision was made once, by policy, rather than forever, by mood.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Per request | Run the three qualifying questions | 10 min |
| Monthly | Check the pro bono hours budget | 5 min |
| Per project | Fixed scope, fixed dates, written summary of what’s included | in-flow |
| Quarterly | Review: which pro bono work created real value — for them and you? | 30 min |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Pro bono hours | Within 5-10% of capacity | Over-budget generosity is how solo businesses quietly fail |
| Value created per hour | Reflect and track qualitatively | Formats that serve many people beat one-off favors |
| Requests declined with referral | Most of them | The script working as designed |
| Portfolio or referral yield | Logged per project | Cause work should feed the business, not only the heart |
Common mistakes to avoid
- Taking free work from "startups that will pay later". Later rarely arrives, and unpaid vendor status poisons the eventual relationship.
- Saying yes in the moment of the ask. The policy exists so that the answer is generated by rules when your guard is down.
- Open-ended free roles with no finish line. Every pro bono engagement gets a defined end date and deliverable — like any good project, just unpaid.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Calendar | The pro bono budget as a visible monthly block |
| Notion | Requests log: cause, ask, decision, hours spent |
| Your templates | Fixed-scope pro bono mini-proposals |
| A referral list | Other providers for declined requests |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- Minimum Engagements
- Rush Fees for Solo Founders
- Payment Terms That Get You Paid
FAQ
Q: Is it unprofessional to charge nonprofits?
No — nonprofits pay for services all the time, and paid engagements get better prioritized than free ones. Offer a nonprofit discount (20-40%) if you want to help at scale: discounts preserve the mutual commitment that free work erodes.
Q: How do I handle a friend asking for free work?
Separate the relationship from the request: "As a friend, here’s my honest advice for free; as a vendor, my rates apply if you want me to build it." Advice and coffee are generous; production work at zero signals your work is worth zero — to everyone watching, including other clients.
Q: What pro bono work actually helps my business?
Work that produces artifacts you can show: a designed site for a known nonprofit, a workshop with testimonials, a case study with real numbers. Choose causes where your contribution will be visible and attributable — generosity and positioning are not enemies.
Q: How do I exit a pro bono commitment that grew too big?
Honestly and with a deadline: "I committed X hours and we’re well past them. Here’s where I can finish cleanly by [date], and here’s a handover doc." Most organizations would rather get a bounded delivery than a resentful ghost.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.