The Shop That Knows You
It’s Saturday afternoon. You walk into your favorite bookstore. The bookseller at the counter remembers your name, asks about the novel you bought last month, and pulls something off the shelf. “I set this aside for you. Just came in, thought you’d love it.”
No algorithm did that. No recommendation engine. Just a person who knows you.
This is what independent shops do better than anyone. The barista who knows your order. The game store staffer who saves you a seat at Friday Night Magic. The record shop clerk who texts you when that rare pressing arrives. Every person on the floor has their own regulars, their own recommendations, their own running conversations.
Behind the counter, that shop is stitching it all together by hand. Staff toggle between Square, a spreadsheet of members, email, and sticky notes from last week’s event. Between them they remember most of the regulars. Most isn’t all, and the ones who slip through quietly drift away.
The best experience in retail is delivered by the people with the worst tools in retail.
What’s Actually Broken
Every system the shop touches captures a slice of the customer and none of them talk. The POS knows purchases. The event platform knows RSVPs. The newsletter knows opens. The membership list lives in a Google Sheet. The rest lives in the heads of whichever staff happened to be working that day.
So the staff become the integration layer. They’re the ones translating “Eric came to the last three signings” into “invite Eric to the next one,” from memory, on a Tuesday, between customers. It works until the shop grows past the number of faces any one person can hold, and until the bookseller who knew Eric best has a day off. After that the care thins out, and only the most frequent regulars still feel seen.
Meanwhile Target knows, in real time, what’s selling in every store it runs. Costco negotiates prices no indie can get near. Amazon’s recommendation engine knows what you want before you do. The gap between chains and independents isn’t about taste or craft. Chains have the infrastructure, and independents have had to get by without it.
Guild is how we close that gap, without asking shops to turn into something they’re not.
What Guild Is
Guild is the shared backend independent shops have never had. It sits underneath the shop rather than on top of it, and it comes in four parts that build on each other.
1. One profile per person, across every surface
Purchases from the POS, event attendance, check-ins at the door, membership status, what they read, what they play, the thing they mentioned last time. It lives in one place and updates in real time. Staff stop being the integration layer and can walk the floor again. The bookseller who just clocked in sees what the closing bookseller saw last night.
The shop that knows who’s standing in front of it, what they bought last month, and roughly why they’re here today is running a different business than the shop squinting at a Square receipt trying to remember a face.
2. A loyalty engine that actually rewards showing up
Most loyalty programs are passive. Punch cards. A points balance nobody checks. Guild is built as a game. Tiers, multipliers, seasonal challenges, achievements for the things that matter to the shop (came to three events this month, bought from a new section, brought a friend). Members level up by being regulars. They can buy into a membership that multiplies everything.
The game layer does real work. It turns a one-time buyer into someone who plans their Saturday around the shop, and it gives staff a reason to message a member that isn’t just another coupon.
3. The network
A bookstore in Brooklyn and a game store in Seattle will never fight over the same customer. But they’re running blind in the same way. Neither one can see what the other is selling, what’s actually moving across the country, what a title is doing in shops the same size as theirs. Publishers and distributors can see all of it. The shops, one at a time, can’t.
What Guild does at the network level is pool the boring back-office half of running a shop. Real-time sell-through flows into one place. When a buyer sits down to order, they’re not guessing from a rep’s pitch or a Publishers Weekly list, they’re looking at what shops like theirs are actually moving this week. Shops chasing the same titles can coordinate their orders. Over time the network learns which titles overperform in which kinds of shops, and that knowledge lives with the operators instead of the suppliers.
For shops that feel under-allocated, the network does more. A few hundred buyers coordinating demand is a different conversation with a publisher than one buyer on one phone line. Scarce titles get assigned against sell-through that can actually be checked. Terms that used to be fixed start moving. For shops that already have deep rep relationships and steady shipments, the allocation fight isn’t the point. The demand intelligence still is, and so does the option to participate in group terms when it’s useful and sit out when it isn’t.
None of this touches the storefront. A shop’s taste, its curation, its regulars, its identity, all of that stays exactly where it was. The parts that pool are the parts nobody ever wanted to do alone in the first place.
The Hanseatic League worked this way eight hundred years ago. Independent merchants who kept running their own houses, coordinated trade, shared market intelligence, and negotiated with counterparties as a group. Staying independent was the whole point. The coordination layer was what made the independence hold up against people who were bigger than them.
4. The supply chain (eventually)
Demand intelligence doesn’t solve everything. Upstream of the publishers sits a handful of at-scale book printers worldwide, already running near capacity with Amazon’s pre-orders taking most of the headroom. A title the network can see breaking out can still take two weeks to restock, and a publisher who knows the demand is there still can’t always get it printed. Knowing what will sell makes indies smarter inside that system. Real leverage eventually means operating further up the stack.
At enough scale, coordination can become distribution for the shops that want it. Aggregated demand across hundreds of shops opens a direct line to publishers and manufacturers, and eventually to printers themselves. Large shops become regional hubs and redistribute to smaller ones. The network sits alongside existing distributor and rep relationships rather than replacing them; shops keep the channels that already work and lean on the network for the ones that don’t.
For a lot of shops, that eventually means ordering inventory the way you’d order anything else online. Open the app, see what the network has, place the order. For others, it’s a backstop when a rep can’t get them a title or a distributor is short. Either way, the shop decides how much of its supply chain to route through the network.
Nobody else in the loyalty space is building toward this, because nobody else sees shops as a network in the first place. We do, because we run one of them.
The Shape of the Company
Guild is a game company and a commerce company at the same time. The game layer (tiers, quests, achievements, seasons) is what customers feel. The commerce layer (POS integration, inventory coordination, eventual distribution) is what shops feel. The company only makes sense if both get built together.
The closest architectural comp is Roblox, not Shopify. Every shop builds its own experience (its store, its quests, its loyalty loop) inside a shared platform with shared identity and a shared economy. The difference is that Guild’s experiences are backed by real inventory and real members walking through real doors. The game is how we get into the infrastructure underneath.
Why This Is Defensible
The loyalty engine on its own isn’t a moat. Anyone with a Square integration and a weekend can build tiers and points. The moat builds up one layer at a time as the platform grows.
The deeper you get into the stack, the harder it is to copy. Cross-shop demand data accumulates with every transaction and every member. A platform built and governed by shop operators looks very different from a platform built inside Block or Toast, who ultimately compete with their sellers for consumer attention. The shops that join early help shape the coordination rules, which makes the later network harder to clone from the outside. And the game layer creates member identities that travel between shops, which is the kind of consumer-side lock-in a pure B2B tool can’t replicate.
Square could ship loyalty features tomorrow (they already have some) and it wouldn’t touch layers three and four. A POS vendor can’t credibly run a cooperative of the businesses it’s selling to.
Why Now
A few things are true at once that weren’t five years ago.
Square passed four million active sellers globally at the end of 2025, which means the integration surface is finally standardized across most of the US independent retail footprint. The American Booksellers Association counted 2,863 member bookstores across 3,281 locations at the end of 2025, with 422 new stores opening that year, up 24% from 2024, and membership has roughly doubled in the last five years. The beachhead vertical is growing while the industry narrative is still stuck in 2010.
AI has made personalization cheap enough that a shop with one owner can run the kind of guest recognition that used to require a concierge. And the wholesale layer (Faire, Lightspeed, Ingram) has proven that B2B coordination tools for independents are fundable and fast-growing, which clears the path for the supply chain play once the network is large enough to matter.
None of that requires a miracle. The four layers build on each other in the order they naturally stack.
The 2035 Vision
The more digital life gets, the more the physical third place matters. The bookstore, the game shop, the record store, the cafe, the corner boutique. These places stay open because the people who walk in feel known there, and that’s always been what they’ve been good at.
By 2035, the independents that want to should be running on shared infrastructure. Data fluency chains take for granted, purchasing leverage on the scale of a co-op, a supply chain that points the same direction the shops do. None of it costing them what made the shop worth walking into in the first place.
A customer carries one identity across their favorite shops in a city, and every one of those shops treats them like the regular they already are. Staff get their Mondays back, ordering is quick, allocation reflects what actually sold, and the coordination work that used to eat half the week happens in the background.
Our phones and our apps already know us pretty well. The places we actually spend time in should know us at least that well, and we should feel better for it when we walk in.
That’s what we’re building.
Where We Are Today
- Live at Dungeon Books since April 2026. Twelve members signed up in week one.
- Pilot conversations underway with three bookstores/game stores in Jersey City.
- Platform is a running Next.js plus Payload application with Square webhooks, Stripe subscriptions, a tiered loyalty engine, point redemption, NFC check-in, and customer sync back to Square so the POS sees the tier at the register.
- Loyalty engine is decoupled from any single payment processor, which keeps us off the hook if Square changes terms or pricing.
- No outside funding yet. Bootstrapping from store revenue while the platform builds out.
Metrics the platform already instruments, reported honestly from week one:
- Member signups and tier mix
- Check-ins per week, per member
- Member vs. non-member average basket
- Points redemption rate
- Stripe MRR and churn
The numbers are small today. They’re real, they’re instrumented from day one, and we’ll be able to show spend lift from member status the moment the sample stops being a rounding error.
How We Get to Thirty Shops
The first thirty aren’t going to come from cold outbound. They come from three expanding rings.
The Jersey City cluster first. A handful of bookstores inside walking distance, sharing events and customers already. Density is the thing that makes the network story legible, so the first cross-shop member profile and the first shared demand signal both need to light up inside one city before we leave it.
The indie bookstore network second, through the channels bookstores already trust: IBID, IndieCommerce, Edelweiss, ABA events, and the handful of operators who’ve already signaled interest. The ABA doubling since 2016 means there’s a live, organized community of operators who talk to each other every week.
The adjacent verticals third. Game stores, record shops, and cafes running Square POS, seeded through the same relational path rather than paid acquisition. The product underneath is the same in each of these; the vocabulary on top is what changes.
No performance marketing in this phase. The cost of convincing a skeptical operator with a paid ad is higher than the cost of one honest in-person meeting, and the shops we want first are the ones who are going to help us shape the network rules anyway.
Who’s Building This
Two people, both software engineers, both running a bookstore.
Panat is the engineering and architecture lead. Platform design, the creative and game-layer work, most of the code that ships. Background in engineering and a long-running interest in how game systems shape behavior, which is where the tier and quest mechanics come from.
Carrie is the business and operations lead. Same engineering background, now pointed at running the shop, managing staff, publisher and distributor relationships, and the parts of the company that touch the real world. Her read on what a shop actually needs is what keeps the platform from drifting into abstractions.
The skills overlap almost completely, so nothing has to be translated across the divide. Product decisions get challenged by someone who could have built them. Operational decisions get challenged by someone who’s shipped the code behind them.
Pitch Deck Arc
- The Saturday bookstore moment.
- The gap: soul in the shop, infrastructure at the chains.
- Guild layer one, one profile per person.
- Guild layer two, loyalty as a game.
- Guild layer three, the network and the Hanseatic logic.
- Guild layer four, becoming the supply chain.
- Why this is defensible, and why Square can’t build it.
- Why now: Square at 4.1M sellers, ABA up 24% YoY, cheap AI, proven B2B wholesale comps.
- Traction and instrumented metrics.
- How we get to thirty shops: JC cluster, ABA channels, adjacent verticals.
- Team: two software engineers running a bookstore. Panat on engineering, architecture, and the creative/game layer. Carrie on business, operations, and distributor relationships.
- Ask: seed round to get to thirty shops and prove the network layer.