Party games that do good.

01 / 07 · Product Management

1. 01

   Product Management

   Scope first, sprints after

   Workflows mapped, MVP decisions made and the scope estimated upfront, then a sprint rhythm that stayed on schedule and on budget.

   This engagement ran the way we work when the vision is already sharp. Before any code, we went deep into product management and business analysis with Brandon, mapping user workflows, separating MVP capabilities from later ideas and turning the vision into a scoped plan with a rough order of magnitude estimate against it.

   That upfront work is what kept the rest light. Development ran in bi-weekly sprints with recaps and planning every two weeks, immediate questions answered the same day or the next, and no heavier process than the project needed. The scope agreed at the start is the product that shipped, on schedule and within the budget we had set together.

2. 02

   Design

   A site that fit the brand

   A redesign of the initial website concept around the playful card identity, so the site finally fit the brand.

   Goin Out Games already had an identity worth keeping. Playful card faces, a warm orange, a rounded typeface with personality. What it did not have was a website that looked like any of it.

   We redesigned the initial website concept around that identity, with Figma as the main design tool, where the interface took its final form. The brand typeface leads the headings, the card artwork carries the how-to-play story, and the palette runs through everything from buttons to empty states, so the site reads as part of the game rather than a storefront bolted onto it.

   We had been experimenting internally with v0, the generative UI tool Vercel opened to the public in late 2023, and this project was the chance to try it on real work. A written idea becomes a working page in minutes, which is a fast way to see how a layout holds up before designing it properly in Figma. The tool is still young and it shows. It produces one static screen at a time, the output rarely matches a brand without rework, and nothing it makes is ready to ship. As a way to test ideas quickly and discard the weak ones cheaply, it earned its keep.

   

   

   

   

3. 03

   Headless Storefront

   Shopify underneath, Next.js in front

   Shopify runs the catalog, the cart and the checkout while a Next.js frontend renders the whole shop on the server.

   The shop runs on the Shopify Storefront API. Products, collections, filters and the cart all come from Shopify data, and checkout hands off to Shopify itself, so payments, taxes and order handling stay with the platform built for them. The store sells physical decks and digital products through the same catalog, with customer reviews collected and shown on every product page.

   In front of it, every page is rendered on the server by Next.js. Collection and product pages arrive as real HTML, quick to load and fully indexable, and a sitemap is generated from the live catalog so new products reach search engines without anyone thinking about it.

   The same machinery carries the content. Stories, the blog behind the brand, is written in Shopify and served through the site, so a post published in the admin appears on the site within a minute with no deployment.

   goinoutgames.com

   One Next.js storefront, rendered on the server

   • Shopify

     The commerce engine

     • Catalog and collections
     • Cart and checkout
     • Orders and payments
     • The Stories blog

   • Game platform

     Postgres behind the play

     • Parties and teams
     • Bumps and comments
     • Charity leaderboards
     • Location search

   • Admin backoffice

     Run by the Goin Out Games team

     • Game setup
     • Bulk card artwork
     • Leaderboard reporting

4. 04

   The Game Platform

   From a printed card to a live party

   Printed cards resolve to live parties nearby, and a bump takes one tap with no account required.

   Setting up a party takes a code and a few taps. An organizer enters the code that ships with their deck, names the party, sets the date and the timezone and picks the location with address autocomplete, then chooses the charities each team will play for.

   The cards do the rest. Every printed card carries a QR code, and scanning one opens the parties happening right now for that game, sorted by distance, so a guest lands in the right party in seconds. From there they can bump, pushing their team’s charity up the board, follow the countdown to the party’s end and leave comments.

   Friction stayed where it belongs, at zero. A guest can bump once before ever being asked to sign in, and someone who bumped one team cannot bump the opposing team, which keeps the leaderboard honest without putting a login wall in front of the game.

   

5. 05

   The Charity Leaderboard

   Bumps become giving

   Real causes ranked by bumps monthly and all time, with 1% of monthly sales going to the top cause.

   The causes are real charities, drawn from the every.org nonprofit network rather than a hand-kept list, so a team can play for almost any cause its players care about. Bumps roll up into leaderboards for the current month, any past month and all time, shown on the landing page for everyone to see.

   The commitment behind it is simple. 1% of each month’s sales goes to the top cause receiving the most game play bumps, so winning a party is not the end of the loop. The more people play, the more the leading charity receives.

6. 06

   The Back Office

   A deck prepared in one pass

   Games and card artwork managed in an admin application, with whole decks created in one drag and drop.

   An admin application manages the catalog of games. New games are created with their codes and their teams, and the dashboard shows the same leaderboards the public sees, month by month.

   Card artwork got the most attention, because a deck means dozens of images. The whole set of designs can be dropped in at once, and the system reads the game, card and team identifiers out of each upload, stores the artwork and wires every card to its game in one pass. Preparing a new deck is a drag and a drop rather than a data entry session.

7. 07

   Launch and Running Costs

   Built to be cheap to keep

   Launched in June 2024 on an architecture chosen to keep the monthly bills small.

   A startup platform is judged twice, once at launch and then every month on its bills. We architected for the second judgment too. The database and the hosting are serverless and cost only what they use, media is served from a CDN, and calls to paid third-party services are cached so the platform never pays twice for the same answer.