Service Marketplace — Admin Flow & Landing Page Extension
An extension scope designed inside an existing system, not around it.
A service-hiring and project-management platform connecting clients with enterprise and specialist providers — service requests, quotes and a construction-works timeline. My scope was the extension: the dedicated admin back-office flow and a new, validated landing page and homepage version, designed inside the existing design system rather than around it, reusing its component architecture and tokens so the addition did not fork the product. The base product, the identity and the original design system were other designers' work, as was the client-side flow.
- Role
- UI designer on the extension scope — Admin flow and the new landing page
- Timeframe
- Sept 2023 – Jan 2024
- Stack
- Figma
- Evidence
- Design file
UI designer for an extension scope of an existing service-hiring and project management platform (solicitação de serviços, orçamentos, linha do tempo de obras) connecting clients with specialist contractors. Designed the dedicated Admin back-office section (4701:14752) and the new validated marketing landing page and homepage within an existing design system authored by Tiago Araújo, ensuring seamless visual and token continuity without fracturing the established component architecture.
Agency engagement at Sagitta between September 2023 and January 2024. Tiago Araújo authored the original product concept, brand identity, and base style guide; Sagitta was contracted for a scope extension divided between two designers: Juan owned Section Admin and the updated landing page; Viviane Batista designed Section Cliente. Juan operated strictly inside the established token and component conventions.
System extension: designing inside someone else's architecture
- 131
- frames on the core Design canvas across Admin and Cliente
- 2
- collaborative sections authored by two separate designers
- 1
- unified design system extended without visual drift
- 100%
- token and component reuse from the established style guide
In commercial software delivery, designers rarely start from a blank canvas. More commonly, agencies are hired to build complex operational extensions onto established products. The true test of a designer's maturity is whether they can step into an existing design system authored by another designer, absorb its token logic and typographic hierarchy, and deliver substantial new modules without introducing visual drift or component bloat.
The Admin back-office workflow: governance and service oversight
Asent connects property owners with specialized architectural and construction contractors (Empresas Prestadoras / Especialistas). While the consumer application handles quotes and job timelines, the platform lacked an operational console to govern transactions. Inside Section Admin (node 4701:14752), I architected the back-office management console:
- Contractor Verification & Vetting — Multi-stage administrative review workflows for onboarding specialist construction teams and reviewing corporate credentials.
- Quote and Proposal Auditing — Oversight tables allowing administrators to inspect pending quotes, verify price breakdowns, and resolve scope disputes.
- Construction Timeline Monitoring — Milestone tracking consoles linking contractor status updates with client escrow payments.
- Financial Clearing & Billing — Payment status dashboards managing instant Pix and bank boleto clearing states.
The updated landing page: commercial clarity for high-ticket services
Alongside the admin portal, I designed the new validated marketing landing page and homepage version (Home & Landing Page atualizada e validada). Contracting architectural renovations involves high financial commitment; the previous marketing presence suffered from ambiguous value propositions. The new landing page articulated the step-by-step journey: from quote request to contractor matchmaking, contract formalization, and milestone-based escrow release.
Agencies frequently hire designers to extend existing products. The ultimate test of seniority is whether you can work inside someone else's component library so seamlessly that nobody can tell two different people touched the file.
Disciplined component reuse over bespoke fragmentation
Rather than drawing detached buttons or arbitrary card wrappers, every administrative table, input field, and navigation header on the Admin page was instantiated directly from Tiago Araújo's existing Style Guide (NavBar 23:10547, NavItem 23:10527, Select 40:13794). This discipline ensured that when engineering began implementation, the developer could reuse existing Bubble/CSS classes, dramatically reducing build time and eliminating maintenance debt.
Evidence
Delivered to engineering and deployed live to production at asent.com.br. The client subsequently abandoned the initiative and the domain went offline. Demonstrates high-value design system discipline: extending a third-party design system and component architecture cleanly without introducing visual fragmentation or design debt.