Part 2 of our velocity series. Once one dev-hour stops shipping one point, the things built on that assumption — how you plan, how you hire, how you build capability — break next. And nobody has the playbook yet.
Linear assumes one dev-hour ships one point. With Claude Code, it ships four to seven. Here's how we rebuilt velocity tracking to learn each person's real multiplier from history.
Most legacy ERPs were never bad at their job — they were just painful to use. With AI and MCP, you can wrap a modern interface around the old engine instead of replacing it.
A walkthrough of how we set up serverless GPU infrastructure for speech-to-text and speaker diarization: what the setup looks like, what the costs are, and what didn't work on the first try.
Six modules. Four backend types. Two transports. One binary. Here's how we wired our entire operations stack into a single MCP server.
No single search strategy is good enough. Combining semantic, structured, and fuzzy search hides each method's weaknesses while stacking their strengths.
Sales tools are everywhere. Most are built by people who've never sent a cold message. We built our own — 64 releases later, here's what's inside.






