Why We Built a Wolfpack Instead of Buying Loyalty

In This Guide

• The Pitch Richie Said No To
• What Loyalty SaaS Actually Rents You
• What the Wolfpack Actually Is
• The Pre-Launch Math
• The April 15 Send
• What Ownership Unlocks Long-Term
• Build vs Rent Over Five Years
• Every Platform Pitch Is a Rent Decision

The Pitch Richie Said No To

A few weeks before Moon Wolf opened in Richardson, the SpotOn rep walked through the standard playbook. POS, payments, online ordering, gift cards — and a loyalty program. Stamp cards turned into an app. Points, tiers, push notifications. Most coffee shops would have signed on the spot.

Richie said no.

Not because the loyalty product was broken. It works. It just works for SpotOn. The list lives in their database, the relationship is mediated by their interface, and when you change POS systems someday — and most operators do, eventually — the audience stays behind. You take your inventory and your menus. You leave the people.

That trade-off is invisible the day you sign. It compounds the day you leave.

What Loyalty SaaS Actually Rents You

The pitch sounds like access. The reality is rental. There is a difference between using a tool and being its tenant, and the difference shows up the first time you try to do something the tool wasn't designed for.

Look at what a typical loyalty platform actually owns:

• The list. You see it through their dashboard. You can export it, sometimes, in a format that loses the segmentation. You cannot move the relationship.
• The voice. Emails go out in the platform's templates. The brand sands down to fit the form.
• The cadence. They decide what an "opt-in" looks like, when re-engagement fires, what counts as a milestone. You inherit their assumptions about your customers.
• The signal. Open rates and click rates exist behind their analytics view. You see what they show. The rawer signals — bounce reasons, send-time variance, segment overlap — usually do not surface.
• The exit. The unsubscribe button lives on their domain. So does the re-engagement flow. Both are theirs.

None of this is malicious. SaaS economics require it. The vendor's moat is the friction of leaving — the more of your audience that lives inside their walls, the harder it gets to migrate. That's the model working as designed.

It's also why "we'll just plug in the loyalty add-on" is one of the most expensive sentences a small operator says. The cost is paid later, in a currency that doesn't show up on the invoice.

What the Wolfpack Actually Is

What we built for Moon Wolf is not a product. It's an architecture.

A signup form on the site collects first name, email, phone, and SMS opt-in. The form posts to a Next.js API route. The API route writes to Supabase, fires a welcome email through Resend, segments the contact by source, and stages the SMS opt-in for Twilio. None of those pieces is exotic. The point is which entity owns each of them.

Resend gives Moon Wolf the list, not access to the list. Supabase holds the contact records under Moon Wolf's schema, with row-level security and RLS policies the team can read. Twilio routes SMS through a number that belongs to Moon Wolf's account. When the team opens any of those dashboards, they see their own data, not a vendor's interpretation of it.

On top of the rails sits a 9-email choreographed sequence:

• Welcome — fires on signup, sets voice and expectations
• Tease without date — "The Den is almost ready," no opening date named
• Date confirm — once the date locked, the list got it first
• Tomorrow — sent the night before doors opened
• Recap — week-of follow-up with photos
• Last call — for the soft-launch tasting block
• Drip — nudge — for non-openers, re-sent at off-peak time
• Drip — social proof — opening-week photos and quotes from the line
• Drip — closer — converts non-clickers to a different ask

Each email goes out in Richie's voice. Not a vendor-templated subject line. Not a "your loyalty rewards await" automated touch. Sentences a human wrote, with the rhythm of how the brand actually speaks. The reason the open rates ran where they did is partly the list quality and partly the fact that the writing didn't read like marketing.

That's the architecture. List, sequence, voice, signal — all owned, all portable, all editable without filing a feature request.

The Pre-Launch Math

The doors opened on Saturday. By that morning, 200 of the eventual 233 Wolfpack signups had already joined.

That is 86% of the list, captured before the business existed in any operational sense. No POS to plug into. No transactions to retarget. No lookalike audiences. The signups came from the website, the seeding posts, and the cult Richie had already built in the years before Moon Wolf was a brick-and-mortar.

The reason that number matters is not the count. It's the timing.

A loyalty SaaS, almost by definition, captures customers after they transact. The flywheel needs the first sale to spin. A pre-launch list captures intent before the transaction — which means by the time the doors open, the warm audience is already there. The 200 wasn't a marketing result. It was a reservoir.

We could only build the reservoir because the architecture didn't depend on a POS being live. The Wolfpack signup ran from the marketing site, not the order system. That separation — what owns identity vs what owns transactions — is the kind of decision that is easy to make on day zero and almost impossible to retrofit on day 200.

The April 15 Send

Twelve days before the doors opened, the list got an email titled "The Den is almost ready." It went to 203 people. The email did not name an opening date. It teased.

Here's what the send returned:

• 99.41% deliverability, 0.59% bounce
• 76% open rate
• 54% click-through rate

For context, restaurant industry average open rates run 20-30%. Click-through rates run 2-5%. The Wolfpack send was three times the open benchmark and ten times the click benchmark.

The reason isn't a clever subject line. It's that the list was self-selected, recent, and emotionally invested. The people on it had opted in within the prior 60 days, mostly through Richie's social posts, and they had signed up specifically because they wanted to know what was coming. That's an audience that wants to hear from you, not an audience that tolerates hearing from you.

You cannot rent that. SaaS lists drift toward the average because they pool indistinguishable contacts across hundreds of customers. An owned list, written to in the brand's actual voice, is composed differently from the start.

The site spike the day after the email landed: 277 users on April 16, on a Wednesday, twelve days before there was anything to buy. The send didn't just tell people something. It moved them.

What Ownership Unlocks Long-Term

The April 15 numbers are the headline. The architecture underneath is the story.

Owning the list means Moon Wolf can do five things that a rented loyalty program cannot:

1. Rewrite the cadence without asking permission. When the soft-launch tasting got moved up by 48 hours, the next email rewrote in twenty minutes and shipped the same afternoon. No support ticket, no template approval.
2. Segment by signal, not by tier. "People who opened the tease but didn't click" is a more useful audience than "Bronze members." The first cuts you a 30-person follow-up list. The second cuts you a generic discount.
3. Run parallel SMS without paying double. Twilio sits next to Resend. Same database, same opt-in field, two channels. A loyalty platform that sells "SMS module" as an add-on is selling you the integration you already have.
4. Carry the list across tools. Supabase exports clean. Resend exports clean. The list is not in the format of any specific vendor. The day Moon Wolf changes any tool, the list does not need a migration plan — it needs a copy paste.
5. See raw signal, not vendor-summarized signal. Bounce reasons, time-of-open distributions, click-by-segment heat maps. None of it is hidden behind a "Pro" feature gate.

Each of those is a small thing on its own. Stacked, they are the difference between a list that works for you and a list that works for the platform that hosts it.

Build vs Rent Over Five Years

The cost question is the part operators usually frame wrong.

A loyalty SaaS at $79 to $299 a month looks cheap on day one. Over five years, that's $5K to $18K — not counting per-message overage fees, premium-tier upgrades when the list crosses 5K contacts, or the inevitable pricing hike when the platform raises a Series C.

Building the Wolfpack architecture cost a fraction of that, paid as part of the Brand Ops Growth stack inside a 30-90 day build. The rails — Resend, Supabase, Twilio — are usage-priced, which means they get cheaper relative to value as the list grows, not more expensive.

But the dollar comparison is the smaller half. The bigger half is portability cost. When a rented platform sunsets a feature, raises pricing, or changes its terms — and most do, on a 24-36 month cycle — the operator either eats the change or undertakes a migration. Migrations of audience data are messy, expensive, and lossy. Owned data has none of those costs because there's nothing to migrate to. The audience already lives on infrastructure the operator controls.

Five years of owning the list is structurally cheaper than five years of renting it, even before the rented platform raises prices.

Every Platform Pitch Is a Rent Decision

Here is the wider point. Loyalty SaaS is one example. Email marketing platforms are another. Booking platforms, review platforms, scheduling platforms, "creator monetization" platforms — every one of them is a pitch to host your audience inside their walls in exchange for a tooling shortcut.

The shortcut is real. The walls are also real.

The decision to rent is a tactical decision dressed up as a tooling decision. Most founders don't notice the difference until they try to leave, and by then the cost of the tools they accumulated is the cost of the audience they no longer control.

The diagnostic isn't "build everything yourself." Some things genuinely belong in SaaS — payments, taxes, transactional infrastructure where the cost of getting it wrong dwarfs the cost of renting it right. The diagnostic is: separate the rails from the relationship. Rent the rails. Own the relationship.

For Moon Wolf, the relationship is the Wolfpack. The rails are Resend, Supabase, Twilio, and the Next.js site that wires them together. Switching any rail tomorrow does not touch the relationship. Switching the relationship — the list, the voice, the cadence — would only happen if Moon Wolf decided to.

That is the difference between a brand that scales and a brand that pays rent. The work to set it up is not large. The compound cost of skipping it is —