John Steele

How I rebuilt a PI law firm's entire system after their previous developer disappeared with all their data. This is the real story behind Vikki. When I first got on a call with the owner of a PI firm in Oklahoma, the situation was bad. Their last developer had bailed. Months of work. Gone. Their entire case management system... down. All we had was some old code on GitHub and a couple of zip files. No documentation. No handover. No cooperation from the previous dev. Just a firm with 60+ active cases, statute deadlines ticking, and zero visibility into any of it. The first thing I noticed when I dug in? They were managing everything manually. Every document (demand letters, HIPAAs, Letters of Representation) assembled by hand. Staff opening templates, typing in client names, emails, case numbers, provider details. One field at a time. For every single case. We replaced all of that with one-click document generation. Case data flows directly from the system into the template. The document is generated in seconds, stored in the right Drive folder, and logged automatically. What used to take minutes per document now takes less time than it takes to open Word. Here's what the dashboard looks like today: → 61 active cases in the system → $65,000 in settlements tracked year to date → 530 medical providers in the network → 83 insurance companies on file → 103 days average case duration from intake to settlement → 10 statute alerts flagged automatically - cases approaching deadlines the firm would have missed manually We built this from scratch. No existing system to copy. No documentation to reference. Just the vision of what a PI firm's operations could look like when everything actually worked. That system is Vikki. And what started as a rebuild is now something we're opening up to other PI firms. If your firm is still assembling documents by hand... drop a comment or DM me. Happy to show you what this looks like live.

20

1 Comment

Ever notice those two-person seed companies that won't hire, those Series A startups that are hiring tons of engineers, and think about why public software companies are laying people off? Agents aren't (yet) good at turning greenfield companies into legacy businesses

86

5 Comments

Reliability is the only feature that matters when you're responsible for another company’s communication infrastructure. I spent the past weekend deep in the backend code for EngageWorx. There were no new UI buttons to show off or flashy animations to demo. Instead, I was hardening our event processing logic. We were ensuring that payment events provision exactly one account, even in the face of duplicate webhooks or network collisions. When you run a platform that supports white-label SMS, WhatsApp, email, voice, and RCS for CSPs and MSPs, the "boring" stuff is the most critical part. Our partners rely on us to be invisible and invincible. If a payment triggers twice, the system must be smart enough to recognize the collision and self-heal without human intervention. We focus on these unglamorous details because service providers shouldn't have to worry about the plumbing. They need to focus on their margins and their clients. Shipping the boring things is how you build trust. Flashy features might win a demo, but reliability wins the decade. What’s the most "boring" but essential part of your stack? #SoftwareDevelopment #WhiteLabel #SaaS #Backend #Reliability

4

A recruiter email put Archil’s progress into perspective. This morning Shalin Patel shared an update after saturating a single Archil node over TLS with a few file system servers. The run hit 7+ GB/s. From a single client. Minutes later, a recruiter emailed me describing a specialized PB-scale system at a major AI lab, supporting around 2 GB/s per GPU. Side-by-side, it highlights something we see often: one Archil client can deliver almost 4× the single-node throughput of systems built for large training clusters. As AI workloads scale, the limit isn’t compute. It’s getting data to the compute fast enough. Archil is already removing that bottleneck. If you’re running large training pipelines, let me know! Happy to show you what speed unlocks.

43

2 Comments

More AI/Testing news from Joe Colantonio Interesting, people trying to use cursor as a Test Environment And, lovable shipped a baby version of UI test automation inside their development environment. If folks want deeper testing for accessibility or finding bugs in thier app inside their IDE-- free download/trials @ https://testers.ai 🤩

10