banyan.

THE BANYAN PITCH

The next nonprofit
should start
one step ahead.

Connect what nonprofits learn
to what funders decide.

01 / THE PROBLEM

The lesson exists.
The next team may
never see it.

Reports sit in one place. Spreadsheets sit in another. A nonprofit facing the same question starts again.

While working on childhood-cancer awareness in India, co-creator Aarav Reddy faced a difficult question: how could his project support families beyond treatment—through transport, lodging, or education?

Had another organization already learned something that could guide that decision?

02 / THE PRODUCT

Learning and funding,
in the same conversation.

Two workflows. A shared commitment to evidence.

FOR FUNDERS

Investigate where
you can help.

Search locally, compare nonprofit records, and draft a funding plan with the supporting sources beside it.

  • Compare financial records and community context.
  • Keep evidence strength and uncertainty visible.
  • Review a proposed allocation before acting.
Explore the donor workflow
Demo comparison of Aster Table and Cedar Meal Collective, showing fiscal period, financial records, service areas and planning caps.
Banyan’s donor comparison view. All organizations and values shown are synthetic demo data. Program spending is not a measure of impact.
FOR NONPROFITS

Learn before
starting again.

Find lessons from similar programs, examine the context, and decide what is worth testing in your own setting.

  • Check similarities, differences, and evidence gaps.
  • Combine results only when their definitions and cohorts are compatible.
  • Choose what others may see and use.
Explore the nonprofit workspace
Evidence to investigate view showing a synthetic household follow-up lesson labeled descriptive observation, with context matches, differences, failures and adaptation questions.
Banyan’s nonprofit learning view, using synthetic food-security evidence. Contextual similarity does not establish causality.

Sources stay attached

Follow a claim back to its supporting record.

Context stays visible

A result from one setting may not transfer to another.

Sharing stays deliberate

Nonprofits control permissions for contributed evidence.

A PRACTICAL START

Use the records
you already keep.

Begin with a spreadsheet. Check the mapped fields, review the result, and choose what to share. Adoption and ease of use still need to be tested with real participants.

  1. 01

    Upload

    Start with existing program summaries and records.

  2. 02

    Check

    Review mapped fields, definitions, and missing information.

  3. 03

    Learn & share

    Use the evidence and set permissions for further use.

03 / THE BUSINESS MODEL

Funders pay
for the workflow.
Nonprofits contribute
for free.

We propose an annual foundation-team subscription for research, reporting, and monitoring. Funders could later sponsor nonprofit onboarding.

Payment would never buy a higher rank.

PROPOSED PRICE · TO BE TESTED

$6,000per foundation team / year

25 teams × $6,000$150,000 annual revenue scenario

Pricing and willingness to pay are unvalidated. Billing and donation transfers are not built.

A FOCUSED FIRST MARKET

Start with
community foundations.

Local funders have a natural reason to compare organizations and understand community needs. We would test the reachable, suitable subset first.

900+

community foundations operate in the United States, according to the Council on Foundations.

900 teams × $6,000 = $5.4M / year

An illustrative 900-account scenario at the proposed price, not a sales forecast or validated addressable market.

Finding an organization is only part of the decision.

Candid already provides nonprofit and funder research. Banyan’s focus is connecting that research to context-rich lessons nonprofits choose to share. This describes our focus, not an exclusive capability claim.

04 / PROGRESS & THE NEXT PROOF

The demo is built.
The next proof is a real decision.

PROPOSED BALTIMORE FOOD-SECURITY PILOT
1

funder to sponsor
a focused local trial

15–25

nonprofits to contribute
and test the workflow

These are pilot targets, not enrolled participants or confirmed funding.

What we would measure

  • Research time: the same task before and after Banyan.
  • Repeat use: whether people return without a prompt.
  • Useful learning: a lesson applied and why it fit.
  • Willingness to share and pay: concrete next commitments.

Early conversations

We have begun conversations with four student-led organizations as we prepare for our first pilot.

  • Downright Perfect Bake Sale
  • IG Food Drive
  • Care4
  • Amity

We have also begun conversations with Maryland Food Bank about a possible free trial. These discussions are at an early stage; a pilot has not yet been confirmed.

05 / THE TEAM

Close to the question.
Committed to building.

AR

Aarav Reddy

Johns Hopkins · BME + EE

NGO experience and product building, with three published computer-science papers in IEEE and Springer venues.

LK

Leyun Kim

Johns Hopkins · CS + Cognitive Science

Venture scouting through RECON by FORGE.

PROPOSED EXPANSION

  1. First

    Prove one local use case

    Test a Baltimore food-security pilot and document useful decisions.

  2. Next

    Repeat what works

    Try another city and cause, guided by participant feedback.

  3. Later

    Learn across countries

    Work with local partners, country-specific sources, permissions, and review.

THE NEXT STEP

Let the next nonprofit
start one step ahead.

We are seeking introductions to a foundation and local nonprofits for a first pilot.

Research & assumptions

Our pricing, revenue scenarios, pilot targets, and expansion plans are proposals to test with participants. The demo uses synthetic data; it does not demonstrate real-world impact.

Market and sector references: Council on Foundations — community foundations; Candid — nonprofit and funder research.