Why I'm building Tellagen

Hi, I'm Andy Kohv. I've spent 15+ years building SaaS products and getting involved in production incidents, sometimes as the engineer writing the code, sometimes as the person on call cleaning up the mess.

I've seen the tooling evolve from email and phone chaos to Slack channels, PagerDuty rotations, Grafana dashboards, and every integration under the sun.

And still, when things break for real, it often feels like controlled chaos at best.

Alert fires. People pile in. Ten browser tabs open. Someone starts a war room. Someone else asks who owns what. Another person asks what customers are seeing. You can feel the minutes burning.

That exact pain is why I'm building Tellagen.

Where incident response keeps breaking

No matter how mature a team is, I keep seeing the same weak spots:

• critical context is spread across too many tools;
• ownership and next actions are not obvious enough;
• impact is guessed, not measured clearly in the moment.

At 3:00 AM, those gaps hit harder. You're tired, pressure is high, and nobody needs one more system that turns into admin work.

What Tellagen should feel like

Tellagen is meant to make incident handling feel tighter, faster, and way less noisy.

The core idea is simple: one clear incident workspace where the team can actually operate.

• one place for timeline, decisions, severity, and status;
• clear ownership so handoffs do not stall the response;
• live impact signals, including business impact, not just technical metrics;
• better communication flow for internal teams and customer updates.

If we do this right, teams spend less energy coordinating and more energy restoring service.

Why I'm personally excited about this

I've been in too many incidents where the fix itself was straightforward, but the surrounding process wasted hours. Strong engineers can solve hard technical problems. What kills momentum is confusion.

Tellagen is still early. That's the exciting part. We get to build it the right way, based on real-world needs.

What I'll share here

This blog will include product updates, but also practical lessons from real incident work: severity models, better on-call habits, communication patterns, and postmortems that actually improve operations.

Some posts will be about Tellagen. Some will be useful even if you never use Tellagen.

If this is your world too, follow along. If you want early access, sign up at tellagen.com.