Implementation had become the bottleneck. With a lean budget and tight timeline, the project needed more than another set of mockups waiting for development. I stepped beyond the design handoff and took ownership of the CRM experience: from brand direction and interface design to working code, developer review and refinement. Outcomes
2026
I started by defining the brand’s essence: playful in identity, calm and clear in everyday use.
I brought six visual references into an AI-assisted exploration and developed ten concepts. Together with the client, we selected a hybrid direction: the information structure of Tangerine Canvas and the quieter palette of Editorial Overview.
The approved direction became a reusable UI foundation: typography, colour tokens, navigation, cards, forms and meaningful interface states.
I extended it across all ten CRM sections, keeping the experience consistent from booking requests and scheduling to campaigns, reporting and settings.
I used AI as an engineering partner to implement the experience inside the existing Playroom application.
This was a functioning CRM, not a static prototype: connected to existing authentication, data flows, forms, roles and venue permissions. The implementation was handed to developers as reviewable code.
I worked through developer feedback and corrected the issues. Further refinement covered navigation stability, session loading, chart behaviour, typography and consistency between screens.
The result is a running implementation with design assets and a team testing guide. QA is ongoing; release remains subject to testing and developer approval.
About 1.5 of the two days went into communication and alignment.
AI accelerated production. My contribution was making product decisions, design, code and team expectations converge—and shortening the distance between an agreed idea and a working product.
2 days — focused design-to-implementation sprint
10 concepts → 1 approved direction
10 CRM sections — one shared interface system
3 languages — English, Russian and Serbian
Desktop + mobile — responsive workspace
Developer review — feedback addressed in code
Team QA in progress — release targeted within two weeks
Implementation had become the bottleneck. With a lean budget and tight timeline, the project needed more than another set of mockups waiting for development. I stepped beyond the design handoff and took ownership of the CRM experience: from brand direction and interface design to working code, developer review and refinement. Outcomes
2026
I started by defining the brand’s essence: playful in identity, calm and clear in everyday use.
I brought six visual references into an AI-assisted exploration and developed ten concepts. Together with the client, we selected a hybrid direction: the information structure of Tangerine Canvas and the quieter palette of Editorial Overview.
The approved direction became a reusable UI foundation: typography, colour tokens, navigation, cards, forms and meaningful interface states.
I extended it across all ten CRM sections, keeping the experience consistent from booking requests and scheduling to campaigns, reporting and settings.
I used AI as an engineering partner to implement the experience inside the existing Playroom application.
This was a functioning CRM, not a static prototype: connected to existing authentication, data flows, forms, roles and venue permissions. The implementation was handed to developers as reviewable code.
I worked through developer feedback and corrected the issues. Further refinement covered navigation stability, session loading, chart behaviour, typography and consistency between screens.
The result is a running implementation with design assets and a team testing guide. QA is ongoing; release remains subject to testing and developer approval.
About 1.5 of the two days went into communication and alignment.
AI accelerated production. My contribution was making product decisions, design, code and team expectations converge—and shortening the distance between an agreed idea and a working product.
2 days — focused design-to-implementation sprint
10 concepts → 1 approved direction
10 CRM sections — one shared interface system
3 languages — English, Russian and Serbian
Desktop + mobile — responsive workspace
Developer review — feedback addressed in code
Team QA in progress — release targeted within two weeks
Implementation had become the bottleneck. With a lean budget and tight timeline, the project needed more than another set of mockups waiting for development. I stepped beyond the design handoff and took ownership of the CRM experience: from brand direction and interface design to working code, developer review and refinement. Outcomes
2026
I started by defining the brand’s essence: playful in identity, calm and clear in everyday use.
I brought six visual references into an AI-assisted exploration and developed ten concepts. Together with the client, we selected a hybrid direction: the information structure of Tangerine Canvas and the quieter palette of Editorial Overview.
The approved direction became a reusable UI foundation: typography, colour tokens, navigation, cards, forms and meaningful interface states.
I extended it across all ten CRM sections, keeping the experience consistent from booking requests and scheduling to campaigns, reporting and settings.
I used AI as an engineering partner to implement the experience inside the existing Playroom application.
This was a functioning CRM, not a static prototype: connected to existing authentication, data flows, forms, roles and venue permissions. The implementation was handed to developers as reviewable code.
I worked through developer feedback and corrected the issues. Further refinement covered navigation stability, session loading, chart behaviour, typography and consistency between screens.
The result is a running implementation with design assets and a team testing guide. QA is ongoing; release remains subject to testing and developer approval.
About 1.5 of the two days went into communication and alignment.
AI accelerated production. My contribution was making product decisions, design, code and team expectations converge—and shortening the distance between an agreed idea and a working product.
2 days — focused design-to-implementation sprint
10 concepts → 1 approved direction
10 CRM sections — one shared interface system
3 languages — English, Russian and Serbian
Desktop + mobile — responsive workspace
Developer review — feedback addressed in code
Team QA in progress — release targeted within two weeks