Scaling Coda’s Webstores — From Bespoke Builds to Publisher Self-Service

How we combined a reusable Commerce Engine with AI-assisted setup to reduce store creation from roughly two days to a few minutes.

Some numbers, data, and statements have been altered to respect confidentiality agreements.

My role
Product Designer — Full design ownership of Publisher Portal onboarding and Coda Webstore Engine
Project type
Long-term · Zero-to-one · Platform strategy · Service design
Collaborators
Engineers, product manager, operations, legal, finance, and marketing
Core project phase
March–June 2025
The self-serve publisher workflow for configuring and launching a global storefront.

Summary

How might we turn a store-creation process that takes days into a self-serve experience that gets publishers to a working webstore in minutes?

From Manual Publisher Operations to Ai-assisted Store Generation

2023 — Understanding the broader journey When I joined Coda, the broader publisher journey was highly manual and could take more than 90 days. 2024 — Validating D2C and accelerating store creation By the end of 2024, we had validated the direct-to-consumer (D2C) model and reduced one part of that journey—internal store creation—to roughly two days. 2025 — Moving from an internal tool to publisher self-service The next challenge was to remove the operational knowledge and repetitive setup still standing between each publisher and a working storefront. We responded by combining a reusable Commerce Engine with an AI-assisted Store Builder, enabling publishers to generate a working storefront themselves in minutes.

What changed

Self-serve storefront generation

Generate a first storefront in minutes

Publishers can move from initial setup to a working storefront without relying on Coda teams to manually configure each store.

Three differently branded stores with shared gamer ID and product-selection patterns
Reusable Commerce Engine

Reuse commerce capabilities across stores

Shared commerce capabilities, integrations, and LiveOps can be built once and reused across current and future stores.

Store overview with setup progress, remaining configuration tasks, and an applied theme
Faster store configuration

Configure stores with prebuilt modules

Prebuilt commerce and LiveOps modules reduce how much publishers need to configure manually before launch.

Outcome

Outcome overview

Protected case study

Unlock to read the full results and design process.
Outcome overview

Protected case study

Unlock to read the full results and design process.
Outcome overview

Protected case study

Unlock to read the full results and design process.

Like what you see?

Read the full case study

Enter the password to explore the process, decisions, and outcomes.

A note before you enter

This portfolio contains selected work from confidential projects. Sensitive details have been redacted, generalized, or modified, but some context may still be proprietary. Please use the contents only for recruitment purposes and avoid sharing or redistributing them without my permission.

Contact me for the password

Other work