← All work
Case study
- Product Platform
- Internal Tools
- Nuxt
- Architecture
Dropt Developer Hub
The control layer for a multi-tenant delivery platform, bringing sites, layouts, schedules, content, services, and AI-assisted workflows into one operating system.
Role
Engineering lead, architecture, product UI
01 / Context
The operating problem
Client delivery depended on work spread across teams and systems. Each launch required repeated setup, coordination, and manual checks.
02 / Ownership
What I owned
I led the architecture and product engineering for the internal hub, including its information model, UI system, release workflows, and links to platform services.
Constraints
- One interface had to support many clients without hiding tenant-specific state.
- The team needed to ship new capabilities while continuing active client delivery.
Key decisions
- Modelled sites, layouts, schedules, content, and services as related operational objects.
- Made system state and release readiness visible in the interface instead of relying on handoffs.
03 / Result
Reduced client onboarding from 7–10 days to under 4 hours.
- Cut client onboarding from 7–10 days to under 4 hours.
- Created a shared control layer for product, engineering, and delivery work.
Evidence and references