First Fruits Farm

First Fruits Farm: Dubsado for Nonprofits, From Volunteers to Harvest Requests

If you are weighing Dubsado for nonprofits, this is what it looks like when one inbox has to handle volunteers, tours, sponsors and food requests. First Fruits Farm is a nonprofit farm in Louisburg, North Carolina that grows fresh produce for hunger relief. I built a done-for-you Dubsado setup that gave each of those groups its own path, from the first form they fill out to the last thank-you email, so the farm’s small team could spend more time in the field and less time in their inbox.

Dubsado for nonprofits: results at a glance

• Service: Done-For-You Dubsado Setup
• 9 Dubsado workflows across speaking, tours, volunteers, harvest requests and sponsorships
• 74 workflow steps, 70 of them automatic, plus 24 emails
• 5 appointment schedulers and 4 inquiry forms
• 4 proposals, 3 questionnaires, a volunteer waiver and a speaking contract
• 21 project statuses and 3 payment plans

Service Provided

Done-For-You Dubsado Setup

About the Client

First Fruits Farm grows produce to give away, teaches agriculture to the next generation and trains volunteers to serve their communities. Alongside the farm work, it hosts farm tours, school field trips and corporate team days, and its founder speaks at events. Partner organizations request harvests and pick them up at the farm stand, and other organizations support the work as sponsors.

That is a lot of different relationships for a small nonprofit. On any given week, the same few people might be answering a teacher, scheduling a volunteer group, confirming a harvest pickup and following up with a sponsor, all while the crops still need tending.

The Problem

Every one of those people needs something different. A school wants to know what a field trip costs and what to bring. A volunteer wants a Saturday slot and needs to sign a waiver before they set foot in the field. A partner organization wants to know what is being harvested this week and when they can pick it up. A company wants to see sponsorship options. An event planner wants to book the founder to speak and needs a contract and an invoice.

Without a system, each of those requests needs a personal reply, and the next step depends on someone remembering to send it. Volunteers already had a separate sign-up page, but tours, harvests, sponsors and speaking requests each needed their own back-and-forth. For a small team that spends most of its time outdoors, a process that depends on memory is a process where things slip.

How We Mapped It

When I map a nonprofit, I start by sorting people by what they want from the organization, not by what the organization calls them. At First Fruits Farm, that gave us five groups: people who want to book a speaker, schools and groups who want a tour, individual volunteers, organizations, and people we have to say no to. Organizations were the interesting one, because the same organization might want to receive a harvest, bring a volunteer group or become a sponsor. So instead of three separate forms, they get one organization opportunities form, and their answer decides which path they go down.

We also decided early which paths needed money attached. Speaking, tours and sponsorships have payment plans. Volunteers and harvest requests never see an invoice. Their workflows run on forms, schedulers and status updates alone, which keeps the experience simple for people who are giving their time or receiving food.

The Solution: One Dubsado Workflow for Each Kind of Request

Speaking engagements

When an event planner fills out the speaking inquiry form, Dubsado sends them a link to book a discovery call. After the call, they receive a proposal with the speaking contract and a 50/50 payment plan, and if they do not respond, Dubsado follows up for the farm. Once the deposit is paid, a second workflow takes over. It sends an onboarding call scheduler and a questionnaire about the event, reminds the planner when the questionnaire is due, and moves the booking from upcoming to complete after the event, with a request for a review.

Farm tours and school tours

Tours share one inquiry form, which splits into a farm tour workflow and a school tour workflow. Each sends its own proposal and tour scheduler, collects payment up front, and sends reminders a week and a day before the visit with what to expect. Schools also receive a tour information packet, so teachers have everything they need to plan the trip.

Volunteers

An individual who fills out the volunteer interest form receives the volunteer waiver to sign right away, along with a link to the farm’s volunteer page. Volunteers who never follow through move into their own status, so the team can see at a glance who is new and who has gone quiet without digging through email.

Organizations: harvest requests, group volunteering and sponsorships

The organization opportunities form feeds three workflows. A harvest request receives a short questionnaire about what the organization needs and a scheduler for picking up at the farm stand, followed by a reminder the day before. The request moves from new, to upcoming pickup, to distributed. A group that wants to volunteer receives the group sign-up link and information about group volunteer opportunities. A sponsor receives the sponsorship guide and a proposal with sponsorship options and a payment plan, and the project is tracked until it is paid or marked lost.

A clear “not available” response

Some requests the farm simply cannot take, whether it is a date that is already full or a request that does not fit. For those, the team starts a short workflow by hand that sends a kind reply, so every inquiry still gets an answer.

The Results

• Every kind of request starts from a form and lands in its own workflow
• 70 of the 74 workflow steps happen on their own, and the 4 that do not are reminders for the team
• Tours, harvest pickups and calls are booked through schedulers instead of back-and-forth email
• Volunteers sign the waiver as part of signing up
• Project statuses show where every speaking event, tour, volunteer, harvest request and sponsorship stands

When the setup was finished, I walked the director through it on a recorded offboarding call so the team could rewatch it later, and they had email support with me while they put it to work.

Frequently asked questions

Can Dubsado work for a nonprofit?

Yes. Dubsado treats each person or group as a project, so a nonprofit can run volunteers, partner organizations, sponsors and paid programs like tours side by side. At First Fruits Farm, only tours, speaking and sponsorships carry payment plans. The volunteer and harvest workflows run on forms, schedulers and statuses alone.

Related case studies and reading

• Case study: TeenWorks: running a teen summer employment program in Google Workspace
• Case study: Artist residency application and guest system
• Case study: The Party Bar: Dubsado for party rentals
• Read: Nonprofit systems

Want a setup like this for your nonprofit?

I build done-for-you Dubsado setups for organizations that juggle volunteers, programs and partners, and I build nonprofit systems in Airtable and Google Workspace when Dubsado is not the right fit for a job.