case · 2025 role: architecture + launch duration: 1 day status: in production

Flower shop platform · v2
×2 · one codebase

A second shop on the same engine under a different brand. Proof that one product can power a line, not just a one-off.

[ visual · second brand on the same engine ]
01 / context

Why it
was needed

V2 was a maturity test: if the first storefront was a successful launch, the second had to prove the product was not a one-off workaround.

V1 already had storefront, admin, roles, and Telegram operations. The hard part was changing the face of the shop without splitting the codebase into forks.

IRIS BLOOMS got a different tone and a more premium first screen while staying on the same catalog, order, and operations logic.

02 / solution

How the engine became
repeatable

I separated the brand layer from business logic: visuals, text, product selections, and communication change, while cart, orders, roles, and statuses stay shared.

  • I
    One codebase
    Different storefronts run on one product: less support, fewer divergences, faster next launch.
  • II
    Brand settings
    Text, visual slots, product selections, and tone change without rewriting core code.
  • III
    Repeatable admin
    The team gets familiar tables, statuses, and roles. The second launch does not require retraining.
  • IV
    Fast launch
    The day goes into configuration, visuals, and scenario checks, not rebuilding the store.
  • V
    Room to scale
    Future brands can be added as a product line, not a graveyard of forks.
[ visual · new storefront ]
[ visual · brand settings ]
[ visual · admin ]
[ visual · telegram order ]
live / interactive

Live IRIS BLOOMS storefront

Static export captured from the local Laravel storefront: homepage, catalog, product, cart, checkout, contacts, and services use the real templates and assets.

embedded demo
03 / result

What we could
measure

×2 · one codebase. Here are verifiable outcomes and visual materials from the source projects.

×2
shops on the engine
1
codebase
0
full rewrites
v2
validated model
The value of the second launch was not another page. It proved the first product had been built as a system.
- project breakdown
04 / how it is built

Stack,
and why

01
Filament
Repeatable admin logic without rebuilding a new panel.
02
Laravel
Clear structure for separating brand, catalog, and orders.
03
CSS tokens
Visual changes without rewriting components.
04
Telegram
Operations stay in the channel the team already uses.
05
AI assistants
Speed up repetitive transfer and scenario checks.
05 / next work
Yandex Maps Outreach
Parser · enrichment · outreach
06 / contact

Similar task? 30 minutes, no brief.

Describe what you need. I will say honestly whether I take it, how much it costs, and whether AI can speed it up.

book 30 min message on telegram