Simulated POCPublic source
Zentix Office — Showing an AI-team idea without faking activity
Zentix Office is a bilingual concept site and control-room simulation for explaining how a team of AI agents might be evaluated before any real integration.

30-second brief
I reframed the concept, designed the bilingual acquisition and demo journeys, built the TypeScript implementation, and added privacy boundaries and automated checks.
The public POC lets someone inspect the concept, switch languages, and explore the simulated control room while the page continuously identifies the experience as a simulation.
What I noticed
A prospective customer needs to understand a complex agent system before connecting data or tools, but a polished simulation can easily be mistaken for live operational activity.
What I worked on
- 01
I separated the acquisition, demo, and privacy journeys and kept the simulation label visible throughout the control room.
- 02
I built the sample team, activity, and status interactions, then added input controls, browser-local recording boundaries, and automated QA.
One decision that mattered
I chose a permanent simulation label instead of a one-time disclaimer. The distinction between sample activity and real telemetry should remain clear at the exact moment someone sees a status or event.
What I learned
This project was a useful reminder that transparency is part of the interface. A caveat hidden in documentation cannot correct a misleading product screen.
Current status
The bilingual static experience and public repository are available. Zentix Office remains a simulated POC, not an operating AI team.
See it in action
Zentix Office
Public, synthetic, or simulated screens only. Customer and account data stay out of the portfolio.
I separated the acquisition, demo, and privacy journeys and kept the simulation label visible throughout the control room.
I built the sample team, activity, and status interactions, then added input controls, browser-local recording boundaries, and automated QA.


A short tour of the labeled simulation, sample team, activity, and status controls.
Read the visual transcript
The walkthrough opens with the visible simulation notice, moves through the sample AI-team cards and activity, and finishes on the status board. The events and statuses are fictional examples and do not come from a live operation.
Technology
- Vite
- TypeScript
- HTML
- CSS
- Vercel Functions
- Playwright
- Lighthouse