Est. reading time: 6 minutes

This case study covers the platform and architecture decisions behind the Helvetia Cider Company engagement. The full build story, including the email sequencing and the Meta program the stack was built to receive, is here.

The Situation

Helvetia Cider Company is a family-owned cidery on a peach farm in Helvetia, Oregon, and most of its revenue moves through tap houses and distributors before it ever touches a checkout page.

When the engagement started, nothing existed online. The ask was a website, and before any page could be designed, the stack underneath it had to be chosen. Platform, email tool, and site architecture all had to fit a business where the buyer is usually a tap house or a distributor, and only sometimes a consumer.

The category has default answers to every one of those questions. Helvetia was the wrong business for all of them.

Key Outcomes

• Full brand system, WordPress site, and Mailchimp email platform built from zero and handed off
• Three dedicated capture paths matched to intent, with consumers routed to email signup, tap houses to an interest form for getting Helvetia on tap, and distributors to their own inquiry line
• No storefront subscription for ecommerce the business did not need
• An email platform simple enough for the Helvetia team to send their own one-off messages while the automation runs untouched
• Site and email foundation later fed by a Meta program that produced 3,678 leads at $1.72 CPA

The Primary Challenge

Beverage brands building from zero get handed the same stack by default. Shopify for the site, Klaviyo for the email, a checkout at the center of everything. Those defaults exist because most brands going online are chasing direct-to-consumer revenue, and for that business the stack fits.

Helvetia’s revenue comes from wholesale and distribution. A Shopify build would have billed them monthly for a storefront the business did not need, and the two audiences that carry the revenue, tap houses and distributors, would have been squeezed into capture flows designed for consumers buying products. Klaviyo carried the same mismatch on the email side. It rewards an operator who lives in the platform daily, and Helvetia is a small team with a cidery and a farm to run.

Choosing the default stack would have meant paying every month for someone else’s business model. The challenge was choosing for the business that actually existed, and getting it right the first time, because a small team that inherits the wrong platform does not replatform. It just stops using the tools.

Our Approach

We ran every decision in the build through two filters. Where the revenue actually comes from, and who operates the tools after handoff.

Brand as the First Decision

We built the brand system before any platform work, because the site, the ads, and the emails were all going to inherit its voice. A family cidery on a working peach farm has a real story, so the brand was built to sound like the actual business instead of an imitation of larger, more corporate cideries.

The voice that came out of that work is plainspoken and direct, with room for one well-earned clever line per piece and no posturing against beer or the rest of the category, because a working farm has nothing to prove. Everything built since, from site copy to Meta ads, runs on it.

Three Audiences, Three Front Doors

A wholesale-first cidery gets three kinds of visitors, and they want three different things. A consumer wants to know where to drink the cider and how to stay in the loop. A tap house or restaurant wants to know how to get it on tap. A distributor wants a direct line to talk business.

We built the site architecture around those intents instead of around a product catalog. Consumers route into email capture. Tap houses get an interest form built for the on-tap conversation. Distributors get a dedicated inquiry path. Each visitor lands on a next step that matches why they came, and nobody gets funneled toward a checkout that was never the point.

A storefront template would have served the consumer path and orphaned the two that pay the bills.

The Platform Followed the Revenue

WordPress won because a wholesale business needs flexibility from its site. Three custom capture paths, a content structure built around the brand story, and no ecommerce framework forced around B2B inquiries.

Shopify would have been the faster build and the wrong one. The monthly storefront cost buys checkout infrastructure, inventory management, and payment processing, none of which a tap-house-and-distributor revenue model uses. Paying for it anyway is how small brands end up funding features their business will never touch.

An Email Tool the Team Would Actually Open

Mailchimp over Klaviyo came down to the operator. Klaviyo earns its keep when someone works inside it every day, and nobody at Helvetia was going to. Mailchimp delivered the automation the welcome series needed while staying simple enough for the team to log in and send a one-off message themselves whenever the moment calls for it.

A more powerful platform that goes untouched after handoff is worth less than a simpler one the team actually uses. The tool was chosen for the year after launch, not the week of it.

Results

Platform decisions prove themselves after handoff. Years later, the Helvetia team still operates every layer of the stack themselves, which is exactly what the choices were made to allow. The automation runs untouched, and nobody has needed us to send an email for them.

The site converts across all three paths, and the downstream numbers belong to the system built on this foundation. The Meta program that eventually ran on top of it produced 3,678 leads at $1.72 each, with efficiency improving deeper into the engagement. That story is covered in the full engagement case study.

Strategic Takeaway

Category defaults encode assumptions. Shopify assumes the revenue arrives through a checkout. Klaviyo assumes an operator who lives in the dashboard. When a business matches those assumptions, the defaults are the right call. When it does not, the defaults quietly bill the business for a model it does not run.

The two questions that route around the trap are simple. Where does the revenue actually come from, and who runs the tools after handoff. Helvetia’s answers ruled out the entire standard stack, and the build that replaced it works because it was shaped like the business from the start. Defaults are decisions someone else made for a different company.