Case files
Every system here is one I built and run. Each file covers the problem, how data moves, what was built and the decisions that mattered, including the ones that didn’t work the first time. Client names and client-owned metrics are withheld; my own products are linked so you can open them.
Client work
3 systems · client not named
- AI support employeeAn AI member of the support team that takes a case from first message to closed, across tickets, live chat and its own widget
- Support IntelligenceA morning read of a support desk for people who don't read tickets
- Community SignalTwo small internal tools that each replaced a weekly manual task
Own products
3 products · live, open them
- NEPSE CopilotA multi-account investing copilot for the Nepal Stock Exchange that grades its own calls
- offScriptA rehearsal partner for actors: two speech engines, a directing room, and a cue engine that knows the line
- NarratelyYour own books read aloud, with the text in view, narrated on demand and kept for offline listening
Taking new projects · start within 2 weeks
Tell me about the process that eats someone's week.
What it is, who does it, how often, and what goes wrong when it’s late. I reply within one working daywith a scoping call or an honest reason it isn’t worth automating.