Blog
Notes from the team.
Field notes on building and running software for operations that can’t fail — engineering, AI, product, and the industries we work in.
Why “boring” software wins in operations
The systems that run schools and hospitals don’t need to be exciting — they need to be there at 7am. How we design for the unglamorous requirement of always working.
Zero-downtime migrations during a live school year
How we moved 14 campuses onto one ERP without ever taking the system offline.
Putting an LLM assistant in front of real users, safely
Guardrails, grounding, and the unglamorous infrastructure that keeps in-product AI from going off the rails.
Measuring whether software actually worked
Shipping is the easy part. We instrument outcomes so “done” means the number actually moved.
Designing point-of-sale that survives a bad network
Offline-first patterns for kiosks and POS that keep selling when the connection drops.
What hospital software gets wrong about clinicians’ time
Every extra click is a minute taken from a patient. Designing HMS around real clinical workflows.
Forecasting demand for unattended retail
How vending and kiosk networks use simple models to keep the right stock in the right machine.
Reconciliation you can actually trust
Building payment flows where the money balances by morning — every morning.
Let’s build something
dependable.
Tell us what you’re operating and where it hurts. We’ll come back with a clear plan, a timeline, and a fixed first milestone.