A back-office console I wrote from scratch as its only author. Staff run customer accounts, contracts, invoices, support and billing from one place, open any customer's own workspace without a password, and ask an AI Document Center questions about internal documents.
Open a customer row, press Ctrl K inside the demo, ask the Document Center a question.
91 seconds: the time-of-day login, overview, requests, pricing, the live card preview and settings. Mock data, no real API.
Account managers, finance and support needed one place to see a customer: contract, invoices, contacts, notes, open tickets.
Customer records lived in a legacy back office. Opening a customer's own marketing panel to reproduce a problem meant asking for credentials. Support had no view of ticket volume by day, agent or customer, and answers to recurring internal questions were spread across Word documents.
I designed and built the whole frontend, the Document Center retrieval service and the scripts that moved about 1,450 legacy customer records into the new CRM tables. I worked with the backend team on the endpoints the screens needed, and asked for a bulk field where the screen would otherwise have made one request per customer.
Violet tint: parts I wrote. The rest existed before.
The customer detail page re-downloaded every list on each tab switch. A small list cache with a 60-second TTL now shares in-flight requests, so simultaneous calls resolve from one network round trip. Refresh buttons clear it.
A "last comment" column would have cost one request per customer, about 1,460 calls. I asked for one bulk field on the list endpoint instead.
Customer names mix ı, İ, ş, ğ, ü, ö and ç with plain Latin spellings. Search folds both sides, so typing isik finds Işık.
Some legacy records carried dropdown values the new lookup lists did not know. The forms keep unknown values on save instead of silently wiping them, and never show raw enum IDs.
When users landed in the wrong tenant, the CRM migration was the first suspect. I pulled the tables touched, the triggers and the timeline in SQL and showed it was not the cause, which pointed the fix at the right place.
The Document Center answers only from retrieved passages, shows numbered sources and abstains when nothing relevant comes back, so staff can check every answer against the document.
The command palette and a Reduced / Full Motion switch were planned in the first week, not added at the end. Keyboard-first navigation and user-controlled animation shaped the render architecture, the store and the component APIs from the start.
Open to full-stack and applied AI roles, remote or hybrid.
Tell me about the role, the team and the problem.