Case study · Savers App Inc.
Partner Platform
B2B program portal, admin CMS, and member sites
- Role
- Senior Frontend Engineer
- Company
- Savers App Inc.
- Status
- Production
- Live
- Private / partner-gated
Overview
The operator side of the CLO business: partners launch and brand programs, ops run offers and marketing, and members land on tenant-specific marketing sites.
The problem
A card-linked program is not only a member app. Partners need onboarding, billing, brand kits, reporting, and API keys. Internal teams need CMS-grade control over offers, assets, and permissions. Members need legal and FAQ sites that inherit partner identity.
Approach
- 01
clo-partner-portal: CRA + TypeScript SaaS — signup, Stripe embedded checkout, program branding (colors, logos, cropper), marketing kits, reporting, invoices, corporate cards, and API keys, with status gates for in-review vs live programs.
- 02
clo-admin-portal: Next.js 14 + Radix/shadcn + TipTap + Recharts. Programs, offers, deeplinks, banners, categories, messaging, and RBAC.
- 03
clo-customer-portal: multi-domain B2C site that theming itself from org details — FAQ, legal, about, email verification — across *.saversapp.com tenants.
Outcome
A full program lifecycle: partner signs up, pays, brands, and goes live; ops publish offers and marketing; members hit a site that already looks like their program.
Partner SaaS, not a dashboard dump
The partner portal is a lifecycle product. Inactive, in-review, and active programs see different surfaces. Branding is a cropper-and-tokens problem. Reporting covers customers, transactions, earnings, enrolled cards, and referrals. Payments go through Stripe. That is B2B frontend work with real money and real launch gates.
Admin as a design system
The internal Savers Dashboard is a modern operator console: React Query, Zod forms, rich text, charts, and permissioned settings. It exists so marketing and program teams can move without an engineering ticket for every banner.
White-label at the domain layer
The customer portal resolves the host, fetches org branding, and paints FAQ, privacy, and RAF terms for that program. Domain redirects keep legacy partner names pointed at the right tenant. One SPA, many brands.
Next
Let’s build the surface people actually keep.
I am looking for senior frontend work on products with real complexity — platforms, marketplaces, and systems that have to hold up in production.