What CSA Operators Actually Need From Software

My wife Alana runs Brookfield Blooms, a flower farm in Baltimore. Before I started building Picket, I watched her manage bouquet subscriptions on a spreadsheet: one tab for members, one for payments, one for pickup locations, one for weekly notes. It worked until it didn’t.

The breaking point was a Tuesday in July. A pickup location had moved the week before and three members didn’t get the update. Two showed up at the old spot. One texted at 6 AM asking where their flowers were. Alana was already at the farm harvesting dahlias and spent 45 minutes on her phone sorting it out instead.

I’m a software engineer. Watching that happen, I started researching what tools existed for farms like hers. What I found surprised me, not because the options were bad, but because they consistently missed what farmers actually need. So I went deeper. I read every Reddit thread, farmer forum post, BBB review, academic study, and post-Harvie-shutdown commentary I could find. This is what I learned.

The spreadsheet breaking point is real

Nearly every CSA farm starts the same way: a Google Form for signups, a spreadsheet for tracking, Square or Venmo for payments, and Mailchimp for the weekly email. It works beautifully at 20 members. By 50, it’s showing cracks. By 100, it’s held together with duct tape and prayers.

Simon Huntley, who founded Harvie before it shut down in December 2024, put it simply: farmers approaching 100 members should start thinking about software because they can no longer keep track of everything in their heads. But member count isn’t the only trigger. Farms offering add-ons, flexible pickup days, or any kind of share customization can hit the wall much earlier. Some platforms report CSAs with as few as six members using dedicated software, because a solo operator juggling three sales channels doesn’t have time for spreadsheet gymnastics.

The pattern is always the same. A farmer described reaching a breaking point: spending too many hours on email and phone while navigating overly complex spreadsheets. Despite best efforts, mistakes kept happening. After switching to dedicated software, that same farm saw its add-on store increase weekly CSA delivery value by 50%.

The barriers to switching are just as consistent. Cost anxiety tops the list. Existing platforms start at $99 per month and climb to $299, with no free or low-cost entry point. That’s a hard sell when your CSA generates $18,000 in a season. Fear of platform dependency is real too, especially after watching 150 farms scramble when Harvie shut down overnight. Learning curve dread is the quiet killer: adding one more system to manage feels impossible when you’re already stretched thin. And migration has to happen during an already-packed growing season.

The five pain points farmers won’t stop talking about

After reading hundreds of farmer comments across Reddit, Facebook groups, industry publications, and BBB reviews, the same five problems surface over and over.

Payment collection eats hours every week

CSA farms juggle checks, credit cards, Venmo, SNAP/EBT, sliding-scale arrangements, and work-share volunteers — often across different systems with no unified view. The industry’s shift from full-season upfront payment to monthly installments (now nearly universal) multiplied the number of transactions farms track by four to six times, without corresponding tool support. One farm noted they require credit card payment specifically because it reduces administrative burden — revealing that payment method choice is driven by admin pain, not customer preference.

Member requests create cascading chaos

Skip weeks, pickup location changes, box size adjustments, vacation holds, add-on orders — each one requires updating spreadsheets, reprinting packing lists, adjusting route sheets, and confirming with the member. As one platform put it: members often don’t understand what a challenge their requests represent for the farmer. Every change ripples through harvest planning, packing, and delivery logistics. A single skip-week email at 7 AM can derail a morning’s harvest plan.

Retention is the existential threat

This is the number that should keep every CSA farmer up at night: average retention rates hover between 45% and 63%. ATTRA’s widely cited figure puts it at 45%. A rigorous 2019 academic study of 80 California CSAs found a mean of 62.9%, with some farms as low as zero.

The Practical Farmers of Iowa surveyed 124 lapsed CSA members and found the top reasons for leaving: the CSA didn’t meet expectations, shares weren’t worth the price, inability to choose produce, and inconvenient pickup logistics.

The most counterintuitive finding was what researchers call the “customization paradox.” Former members consistently cite lack of choice as their primary reason for leaving. But farms that offer customization show no statistically higher retention rates. The problem isn’t really about box contents — it runs deeper into communication, community, and perceived value. Which leads to the next pain point.

Communication matters more than anything else for retention

The weekly newsletter about what’s in the box. Recipe suggestions. Pickup reminders. Farm updates. Billing notifications. Together, these consume hours every week. One farmer described spending hours preparing their Mailchimp newsletter separately from their CSA management tool, paying $168 or more per month across four disconnected systems, where managing communications became cumbersome.

The research is clear: members who view communication with their CSA farm positively are significantly more likely to renew. Communication quality correlates with retention more reliably than share customization. This was the most useful finding in all the research I did, and the one most platforms underserve.

Multi-site pickup logistics are a daily headache

Farms managing multiple pickup locations deal with minimum member thresholds, specific time windows, host relationships, and no-show management. Flowers left unclaimed can’t be rescheduled. They go to waste. Produce goes to food banks. Either way, the farm absorbs the labor cost of packing a share nobody picked up. One farm stated it plainly: regularly shifting pickup days or temporarily changing them makes the farm more prone to mistakes.

What Harvie got right — and what its shutdown revealed

Harvie’s December 2024 shutdown is worth examining in detail. The platform served over 100,000 consumers across 150-plus farms. Understanding what it offered and what the market lost maps directly to what any CSA platform should prioritize.

Harvie’s signature feature was preference-based algorithmic box building. Members rated every crop on a one-to-five scale at signup. Before each distribution, the farmer entered a harvest estimate. The algorithm built individualized shares — randomizing the member list for fairness, filling each box with highly-rated items first, and pricing to a target share value. Members got a preview email 48 hours before pickup and could swap items or add extras.

The numbers were good. Farms using Harvie reported 15 to 30 percent higher retention rates and 10 to 30 percent more revenue from the same production.

But the supporting features mattered just as much. Harvie generated packing labels in assembly-line order, staffed a customer service team that handled member emails, provided marketing support, and offered auto-renewal — so farmers could spend more time recruiting new members instead of chasing renewals.

The shutdown was ugly. One farm described it as a huge disruption mid-season, forcing hours of office time demoing replacement software during their busiest harvest period. Another told members bluntly to use remaining credits before the December 31 cutoff because accounts would be gone.

Why did a product with clear market fit fail as a business? The likely causes: a tiny addressable market (CSA serves only 0.4% of U.S. households), expensive pricing that captured 10% of farm revenue, a labor-intensive service model with hands-on marketing staff and customer service teams, and a funding structure that couldn’t sustain both a tech platform and a regional distribution operation.

The gap Harvie left remains largely unfilled. GrownBy, a farmer-owned cooperative, is the closest successor — they’ve developed AI-powered custom shares in partnership with the Harvie team. CSAware offers a box-building tool. But Local Line, the most common migration destination, explicitly acknowledges it may not be ideal for CSAs that rely heavily on customizable box-builder features. No platform replicates the full package of algorithmic building, swap windows, packing labels, and delegated customer service that made Harvie indispensable.

Flower CSAs are completely underserved

This is the part that’s personal for me. There is no purpose-built subscription management platform for flower farms. None. I watched Alana manage Brookfield Blooms across Squarespace, Square, Google Sheets, and Mailchimp — and every flower farmer I’ve talked to describes the same stack.

Flower farmers manage bouquet subscriptions through spreadsheets. The dominant website platform is Squarespace (chosen for visual aesthetics), with payment through Square or Stripe, and email through ConvertKit or FloDesk. That’s a minimum of three disconnected tools before you’ve even dealt with logistics.

Flower CSAs differ from produce CSAs in ways that matter for software:

Designer’s choice is the default. Unlike produce CSAs trending toward customization, flower CSA members almost universally accept grower’s-choice bouquets. As one micro-farm stated: “We cannot accommodate custom orders.” This simplifies the share-building workflow but elevates the importance of visual communication — members want to see photographs of what they’re getting, not a text list of varieties.

Perishability is measured in hours. Cut flowers must be in water immediately. Missed pickups cannot be rescheduled — every flower farm I’ve researched enforces strict no-makeup policies. Pickup reminders and vacation hold management become even more critical.

The season is shorter and more fragile. Most flower CSAs operate May through October. A single hailstorm can wipe out weeks of production. Farmers keep three to four backup focal flowers at any given time and sometimes source from neighboring farms.

Pricing is remarkably consistent. Standard bouquets run $25 to $35 each, with seasonal passes from $200 to $800. Full-season revenue for a small flower CSA with 30 members is roughly $18,000. Operations with 60 to 100 members generate $36,000 to $60,000 from subscriptions alone.

Pickup logistics involve creative partnerships. Flower farms partner with coffee shops, vintage stores, and gyms as pickup hosts — the business gets foot traffic, the farm gets distribution points. Managing these relationships and tracking per-location inventory is a workflow no existing tool addresses.

The flower farm industry has grown seven to eight times in the past decade, driven by the Slow Flowers movement and consumer demand for local, seasonal blooms. About 80% of U.S. cut flowers are still imported. The market is growing, the farms are underserved, and the tools haven’t caught up.

What the ideal CSA platform actually looks like

Taking the pain points, the Harvie post-mortem, the academic research, and the forum complaints together, a clear picture emerges.

Member self-service is the feature that matters most. Every skip-week request, pickup-location change, and payment update that a member handles themselves is admin time returned to the farmer. This is the feature that determines whether the platform saves the farmer time or adds to their workload.

Flexible payment processing is baseline. Monthly installments, sliding-scale pricing, and ideally SNAP/EBT support. Full-season upfront payment is fading. A platform that only handles simple credit card charges misses how CSA payments actually work.

Automated communication has to be built in, not bolted on. The weekly share preview, pickup reminders, and farm news shouldn’t require a separate Mailchimp account. Communication is the proven retention lever, and it needs to be as effortless as possible.

Packing workflows need to connect to member data. Packing lists and labels that update in real time when a member skips, swaps, or changes their pickup location. Sounds basic, but it’s the thing farmers on spreadsheets spend the most time reconciling manually.

Multi-location pickup management with per-site capacity, no-show tracking, and separate packing reports. Farms don’t deliver to one location. They manage a network.

The platform should handle more than CSA. Only about half of the average CSA farm’s revenue comes from subscriptions. The rest is farmers’ markets, online store sales, wholesale, events. A tool that only manages the CSA but can’t see the rest of the business is solving half the problem.

And pricing can’t punish growth or seasonality. Percentage-of-sales models penalize success. Monthly minimums charge farms during off-season months with zero revenue. Setup fees discourage experimentation. The farmers I’ve talked to want something flat and predictable.

What we’re building

Picket is a platform for small growers — flower farms, market gardens, CSA operations. It’s built to handle subscriptions, delivery logistics, and an online store in one place, without the app tax you’d pay stitching together Shopify plugins or the $100-plus monthly fees of existing farm platforms.

We’re starting with flower CSAs because that’s the market I know best through Brookfield Blooms, and it’s the market nobody else is serving. But the subscription management, payment processing, and member communication tools we’re building work just as well for a produce CSA, a meat share, or a mixed farm with multiple sales channels.

If you’re running a CSA on spreadsheets and thinking about making the jump, or if you’re on a platform that’s not quite right, I’d like to hear about your experience. What’s working, what’s not, what you wish existed. That’s what’s shaping this product.

You can reach me at hello@mypicket.app.