@Atlas audits the catalog the day the store is connected and ships a CRO plan, instead of handing back a list of things to go read. Audit to plan, same session.
BoostEcom DemoDemo
Founder
From nothing to a live Shopify store.
Brand identity, a real store from the pool, and the content that fills it. One flow in the chat, not three tools scattered across a menu.Brand kitReal dev storeGenerationTheme edits
The numbers
The launch stack
- Launch milestones
- 29
- Automated by cron
- 13
- Human checkpoints
- 16
- Pre-provisioned stores
- Pool
What launch covers
Three steps that used to look like separate products. First the brand kit: name, palette, typography and voice, from a brief, uploaded assets or a Figma file read over OAuth. Then a real Shopify development store claimed from a pre-provisioned pool, with the custom app already installed, followed by twenty-nine launch milestones of which thirteen run on their own via the launch-tick cron. Then generation and theme editing in the same conversation: pages, sections, product copy, Liquid files, inside the Custom App scope you granted.
Shopify has no public API that creates a merchant store for you. We claim a real Partner-side dev store from DevStorePool, run the playbook, and stop at ownership transfer: that invite is always human.
Four jobs that used to look like four products
Brand kit, turnkey store, generation and Liquid edits live in the same Launch path. They are modes of @Atlas, not separate SKUs.
- Brand kitName, palette, typography and voice from a brief, uploaded assets or a Figma file. Tokens can export as W3C format.
- Turnkey Shopify storeAtomic claim from DevStorePool: Custom App already seated. Then launch-tick runs the automated milestones every fifteen minutes.
- GenerationPages, product copy and image variants from the brand inputs, inside the chat that already holds the kit.
- Theme editsLiquid and settings_data changes through the theme-editor skill, scoped to the Custom App, preview-first.
Figma is read-only via OAuth. We extract palette and type; we never write back into the Figma file.
How it runs
Chat composers open the wizards. The cron finishes what the wizards start.
- Brand kitSeven-step wizard. Upload assets, describe the brand, or import paint and text styles from a Figma file you duplicated. Exports W3C design tokens as JSON.
- Turnkey storeCreates the Store row, claims a DevStorePool entry atomically, and starts the launch playbook. The operator never pastes a token.
- PopulateThirteen automated milestones: theme, products, collections, pages, menus, blog, accessibility, SEO meta, structured data, crawl surface, legal docs, pricing, webhooks. Sixteen human checkpoints stay human on purpose.
- Generate and editAsk @Atlas to generate pages, sections and product descriptions, or to read and write theme files. Every write is logged against the Custom App scope.
Who opens Launch
- From nothing to a draft storeA founder with a brief and no Shopify login yet. Pool claim plus brand kit in one path.
- Agency kickoffBrand system first, then a disposable dev store the client can accept later.
- Refresh an existing brandRe-run generation and theme edits against a kit that already exists, without a second product.
When to use it
- Use it whenWhen you are starting a brand or a store from scratch and want the OS to carry the first weeks instead of a pile of apps and a freelance brief.
- Do not use it whenWhen the store already exists and you only need one page rewritten. Open the chat and ask. Launch is the on-ramp, not the daily editor.
What Launch will not pretend
- No create-store APIIf the pool is empty you wait. We do not invent a Shopify endpoint that does not exist.
- Human ownership transferAccepting the Partner transfer invite is always a person. The cron only detects acceptance.
- Figma reads, never writesOAuth extracts styles. Writing into the design file is out of scope.
Limitations
What the feature does not do. Knowing beforehand costs less than finding out after.
- Shopify does not expose an API to create development stores. The pool is pre-provisioned by ops. An empty pool waitlists you.
- Ownership transfer still needs a human invite in the Shopify Dev Dashboard. The platform detects acceptance. It cannot send the invite.
- Figma is read-only. We extract styles. We do not write tokens back into the file.
- Sixteen of the twenty-nine milestones are human checkpoints: payments, domain, legal approval, publish. The OS does not pretend otherwise.
Not on this page as shipped
- Bidirectional Figma sync.
- Creating Shopify stores via Admin API (impossible on Shopify's side).
The neighbouring features
Same family, same product surface.
Is the Shopify store real?Launch a store
Yes. It is a development store claimed from a pool the ops team filled. The custom app is already installed, so the playbook can write theme and catalogue immediately.
What does the Figma import actually do?Launch a store
After OAuth it reads paint and text styles from a file URL you paste, and pre-fills the brand kit. It does not sync both ways.
When do I own the store?Launch a store
When you confirm the handoff in the wizard, ops sends the Shopify transfer invite, and the cron detects acceptance via plan_name. That last step is automatic. The invite is not.
Where did Generation and Theme editing go?Launch a store
Here. They were never separate products. They are what @Atlas does after the brand and the store exist, so they sit on this page.
One operator, the full stack: Maya runs the email calendar, Marco curates collections, Otis watches fulfilment. One team, one thread.
BoostEcom DemoDemo
Head of Growth
The work gets done rather than suggested. Voice mode with @Atlas turns the morning check-in into a conversation. It operates.
BoostEcom DemoDemo
Store owner
@Maya rewrites product descriptions, queues them for review, pushes the approved batch live, then runs the campaign around them. End-to-end, with approval gates.
BoostEcom DemoDemo
E-commerce lead
Every action the AI Team takes is graded against real Shopify Analytics after the observation window closes. Outcome attribution, not vibes.
BoostEcom DemoDemo
Marketing lead
OAuth scopes, audit log, store-scoped credits, no shadow data. The agents work inside the admin, not around it.
BoostEcom DemoDemo
Engineer
Permission mode decides what ships on its own and what waits for a human. Autonomy you dial in.
BoostEcom DemoDemo
Operator
Multi-store from one console, each with its own connectors, memory and budget. Per-store context.
BoostEcom DemoDemo
Agency owner
@Atlas audits the catalog the day the store is connected and ships a CRO plan, instead of handing back a list of things to go read. Audit to plan, same session.
BoostEcom DemoDemo
Founder
One operator, the full stack: Maya runs the email calendar, Marco curates collections, Otis watches fulfilment. One team, one thread.
BoostEcom DemoDemo
Head of Growth
The work gets done rather than suggested. Voice mode with @Atlas turns the morning check-in into a conversation. It operates.
BoostEcom DemoDemo
Store owner
@Maya rewrites product descriptions, queues them for review, pushes the approved batch live, then runs the campaign around them. End-to-end, with approval gates.
BoostEcom DemoDemo
E-commerce lead
Every action the AI Team takes is graded against real Shopify Analytics after the observation window closes. Outcome attribution, not vibes.
BoostEcom DemoDemo
Marketing lead
OAuth scopes, audit log, store-scoped credits, no shadow data. The agents work inside the admin, not around it.
BoostEcom DemoDemo
Engineer
Permission mode decides what ships on its own and what waits for a human. Autonomy you dial in.
BoostEcom DemoDemo
Operator
Multi-store from one console, each with its own connectors, memory and budget. Per-store context.
BoostEcom DemoDemo
Agency owner
A question that is not here?
Ask it, and it joins this page if it comes back.