Brand planning
Planning workflows, materials, ranges, allocations, approvals, scenarios, and decision support shaped around how fashion teams actually operate.
hyranAn enterprise-grade platform for connected fashion operations
A multi-product software platform connecting brand planning and factory execution through secure contracts, durable workflows, and a shared design foundation.
Embedded technical partner across platform architecture, enterprise product delivery, design systems, migrations, security, and operational readiness.
View live productSee the brand. Then see the system behind it.
Public brand view. Private customer data and internal operations are intentionally excluded.
01
Fashion planning was stuck in spreadsheets.
Plans crossed brands, factories, suppliers, emails, calls, and files. By the time everybody agreed, the numbers had already changed.
02
Connect the brand to the factory.
Give each team the product it needs. Keep the data boundaries clean. Let changes move through the network without another spreadsheet relay.
03
Change the plan in seconds.
Planning, production, materials, capacity, and delivery risk now sit in a platform built for the actual work, not a tidy demo of it.
What I actually built.
Embedded technical partner across platform architecture, enterprise product delivery, design systems, migrations, security, and operational readiness. These are the systems and foundations I directly shaped, built, repaired, or brought into a dependable delivery model.
Factory execution
Production planning, work orders, machines, downtime, materials, capacity, and shop-floor workflows with clear operational ownership.
Connected product architecture
Brand and Factory kept as separate products and data boundaries, connected through explicit platform contracts rather than accidental coupling.
Enterprise tenancy and access
Organisation-scoped identity, role-based access, row-level security, fail-closed services, and auditable tenant isolation.
Forecasting and optimisation
Model and scoring services integrated behind stable application boundaries, with operational fallbacks and observable failure modes.
Migration and parity
Legacy-to-platform transformation managed as evidence-backed slices across information, actions, permissions, exports, failures, and responsive behaviour.
Hyran Loom
A shared, governed design foundation for consistent product experiences, reusable patterns, Storybook evidence, and faster delivery without collapsing product ownership.
Environment and release discipline
Separate production, preview, and demo channels with schema, deployment, health, and drift checks treated as distinct proof gates.
The foundations that hold up after launch.
01
Separate product and database boundaries
02
Versioned cross-product contracts
03
WorkOS organisation identity
04
Row-level security and tenant isolation
05
Domain repositories and typed services
06
Design-system governance
07
Migration and parity evidence
08
Independent environment verification
Tell me what is stuck.
I will tell you what is actually broken, what I would build, and whether I am the right person to do it.
Email me