How Bronzly uses Conduit — case study of a vertical SaaS on a marketing platform

Bronzly is Conduit's first vertical SaaS customer. They embed Conduit's inbox, scheduling, and communication primitives directly into their product. Here's how the integration works and what we learned.

What is Bronzly?

Bronzly is a SaaS platform for spray tanning artists — solo operators who run mobile / studio-based spray tan businesses. Bronzly handles client management, booking, payments, and content for their artists. Founded by Abbey Wolfe (60% owner) in partnership with Bamberg Digital's Jason Bamberg (40%).

The platform serves spray tan artists who typically run 30-60 clients per week as solo operators. Marketing is critical to fill the chair — but most artists don't have time to manage multiple tools.

The build-vs-buy decision

When Bronzly was being designed in late 2025, the team had three options for the marketing layer:

1. Build inbox + scheduling + communication from scratch (6-9 months of engineering)
2. Integrate with external tools (Twilio, SendGrid, Buffer) via API (3-4 months + ongoing integration tax)
3. Embed Conduit modules into Bronzly (2-3 weeks)

The team chose option 3. The reasoning: Conduit already shipped all the primitives Bronzly needed, with the right abstraction level for a vertical SaaS to reuse.

Architecture

Bronzly's production setup:

• Bronzly app frontend (Next.js, hosted on Vercel)
• Bronzly backend (Supabase, with Bronzly-specific tables for tanning-artist-specific data)
• Conduit Embed components for inbox, scheduling, content publishing — iframe-mounted into Bronzly app
• Conduit OAuth: artists authorize Conduit via Bronzly's OAuth flow, link Bronzly client IDs to Conduit contact IDs

From the artist's perspective, Bronzly looks like one product. The Inbox tab inside Bronzly is actually a Conduit-hosted iframe. The Content Calendar is Conduit Publisher. The Marketing tab is Conduit Outreach.

What Conduit modules Bronzly uses

• Conduit Inbox — IG DM, SMS, email unified in the Bronzly app for each artist
• Conduit Outreach — Birthday + recall + reactivation SMS / email sequences
• Conduit Publisher — IG + TikTok scheduling for tanning content
• Conduit Link-in-bio — Each artist gets a branded link-in-bio page
• Conduit Docs — Consent forms + membership signup with Stripe Connect

What Bronzly built on top

Bronzly handles the tanning-artist-specific layer that Conduit doesn't cover:

• Client onboarding workflow (tan history, skin tone, product preferences)
• Booking calendar with artist-specific service menu (spray tan, contouring, prep, etc.)
• Payment with Stripe Connect (Bronzly takes 2.99% platform fee)
• Inventory tracking (tanning solution, supplies)
• Artist-to-artist community + content library

How customers flow through Bronzly + Conduit

A typical flow:

1. Client books via the artist's Bronzly booking page (link from IG bio)
2. Bronzly stores the booking + sends to Stripe for payment
3. Conduit Flow fires: confirmation SMS, reminder 24hr before, reminder 2hr before
4. After the appointment: post-visit SMS with review request link
5. 7 days later: SMS asking how the tan held up + product upsell
6. 30 days later: SMS suggesting next booking
7. Birthday: SMS with birthday discount code

From the artist's perspective, all of this is "Bronzly automation". Under the hood, it's Conduit Flows. The artist never sees Conduit's brand inside Bronzly (Conduit Embed supports full white-label).

The business model

Bronzly charges tanning artists:

• Glow tier: $79/mo (solo, up to 30 clients/week)
• Studio tier: $189/mo (multi-room studio, up to 80 clients/week)
• Empire tier: $299/mo (multi-location operator)

Each Bronzly subscription includes the Conduit modules they use. Bronzly pays Conduit a wholesale rate per active workspace; Bronzly marks up to retail. The arrangement works because Conduit is dramatically cheaper at scale than Bronzly building this layer themselves.

What we've learned

Three things have surfaced from the Bronzly integration over the first 3 months:

1. Embed components need to feel native

Initial embed UI had subtle styling differences that made the artist tabs feel like a different app. We invested 3-4 weeks of Conduit dev time into making the Inbox / Publisher embed components fully theme-able — colors, fonts, spacing all configurable per-customer.

2. OAuth deep-linking is critical

When an artist clicks a Bronzly notification (e.g. "new DM from client"), the deep-link needs to land them in the right Conduit Inbox view inside Bronzly, not in the Bronzly app home. We rebuilt the OAuth deep-link flow to preserve context across the auth boundary.

3. Customer support has to be coherent

When an artist has an issue, they don't know if it's a Bronzly bug or a Conduit bug. Bronzly handles tier-1 support; complex Conduit-level issues get escalated to Bamberg Digital's support team via a shared Slack channel.

What this means for other vertical SaaS

If you're building a vertical SaaS (legal practice management, dental software, wellness platform, etc.) and you need marketing primitives — inbox, sequences, publishing, scheduling — Conduit's Embed components are a real alternative to building from scratch.

Standard offering:

• White-label embed components (your brand, our infrastructure)
• OAuth + deep-link integration
• Wholesale pricing per active workspace (typically $20-$50/workspace/mo for vertical SaaS)
• Support escalation path

Contact us if you're building a vertical SaaS and want to evaluate the embed path.

What's next for Bronzly + Conduit

The 2026 roadmap for the Bronzly + Conduit integration:

• Native mobile app (iOS / Android) wrapping the Bronzly + Conduit experience
• AI-powered content generation for tanning-specific posts (Mistral via Conduit)
• Multi-language support (Spanish first, given the tanning artist demographics)
• White-label option for tanning chains to host their own Bronzly variant

If you're curious about Bronzly the product, bronzly.app. If you're curious about Conduit for your own vertical SaaS, see the modules or start a 14-day trial.