A recent experiment6 min read
The Output Looked Good
I built a test to compare local models with the cloud. The first thing it caught was the cloud making something up.
Read the storyA personal work in progressEngineering / Writing / Whatever's next
Kevin Louie.
I notice the frustrating parts. Then I build something to fix them.
01 / Writing
Thinking out loud.
02 / Selected builds
It started with a problem.
Support / Knowledge systems
SupportTopics
The answer is probably in an old ticket. Finding it shouldn't be another investigation.
A knowledge graph built from support tickets, connecting recurring issues with the answers that resolved them.
Connecting what we already know
TicketTicketTicket
A recurring issue
An answer worth keeping
Agents / Durable memory
Context Memory Service
The session ends. The work shouldn't disappear with it.
A local archive that makes agent conversations searchable, carries context between tools, and turns past investigations into reusable playbooks.
The work feeds the next session
The next case improves the next answer.
Commercial / Internal tools
Price Guidance Calculator
A shared spreadsheet grew into a pricing tool used by sales teams worldwide.
Database-backed rates and tested formulas give sales teams clear discount ranges, with every calculation recorded for the pricing team.
From cells to confident decisions
Same formulas. Clearer guidance.
03 / The person behind it
Hi, I'm Kevin.
I've spent 15+ years in support and technical operations. The part I keep coming back to is understanding why something is frustrating, then doing something about it.
These days I'm a Senior Technical Operations Engineer at Enode. Outside of that, I build tools, tinker with my own systems, and write here to work through what I'm learning.
Always interested in what other people are making