the-dispatch — summer 2026 — unravel

unravel@dispatch ~ % cat q3-2026.md

# A brittle engine, rebuilt in two weeks.

The quarter in one screen: what we shipped, what we learned, and what you can use whether or not we ever work together.

at_a_glance

time to ship2 weeks
reverts after cutover0 (was 28)
less code, larger API~50%
shipped to prod, Jun–Aug116
team grew this year15 → 20

case_study

A client's AI music-video engine, written in Java, had grown brittle: frequent reverts and mobile apps breaking in production. We rebuilt it in Python, contract-first and verified against the real clients, and shipped the cutover in two weeks with nothing rolled back.

the fix for a slow, breaking engine is rarely a bigger team. it is a disciplined rebuild.

lets_talk

Weighing a rebuild? Thirty minutes, and we tell you straight whether it is worth doing, what it would take, and how fast we could do it.

% book-a-call

Book a 30-minute call →

or reply to this email — it reaches us directly. kapil@unravel.tech