Confidential enterprise software company
Building a Complex Enterprise Platform in Under 30 Days
How Quave designed and built the front end for an API management platform in time for a fixed conference date, while the client team built the backend.
A fixed date and a complex interface
A startup needed the complete front end for a new API management platform before a major conference. Fewer than 30 days remained. The product connects request-based APIs with high-throughput, real-time systems, then helps users turn operational streams into managed data products. Making those capabilities coherent in an interface would normally be a substantial project even without the event deadline.
The client’s own team retained responsibility for the backend and its APIs. Quave’s scope was the product design and front-end implementation, which let both teams work in parallel.
Reuse the system, focus on the flows
An existing design system supplied the underlying components, so the project could concentrate on pages and user journeys instead of rebuilding buttons and fields. Designers used AI to learn the platform’s technical concepts, including streaming protocols and certificate management. Developers used Figma-connected and AI coding tools to accelerate implementation, while reviewing and refining the generated work.
The team selected the core paths first, shared them early and adjusted them through feedback. The resulting interface included an editor for OpenAPI specifications with JSON and AVRO schemas, an API-product catalog, application and subscription hierarchies, role-based access control, team administration and separate development, test and production environments.
Specifications could be managed and deployed as API products, while the catalog showed teams what existed and its current state. The subscription model organized how consumers accessed those APIs and supported authentication and rolled-up metrics across the hierarchy.
Core launch first; later capability later
API-key authentication shipped for the conference release. mTLS certificate management followed later and is not represented as part of the under-30-day delivery. That sequencing kept the deadline legible: establish a usable core, then continue the platform work after the event.
The core front end was ready for the conference and ongoing work continued from that foundation. The source reports interest from prospective clients and new partnerships. Confidentiality agreements prevent disclosure of the company name and further product detail.
The published case credits the existing component system, early communication and frequent sharing of work for reducing rework during the initial sprint. Quave continued refining features and adding capabilities after the conference rather than treating the event build as a throwaway demonstration.
A first conversation