I didn’t set out to build another project management tool. There are enough of those. I set out to kill the management nobody needs: the check-ins, the status-chasing, the meeting you run just to find out what’s behind. And to help teams keep their rhythm and momentum.
For years, the rhythm of running projects looked the same no matter what tool I was using. Monday morning, get everyone in a room, or a call, and go around the table: what are you working on, what’s blocked, what’s slipping. By the time we’d finished, we knew what was behind. The problem is that “by the time we’d finished” was already too late. The thing that slipped had been slipping for days. The meeting didn’t catch it. The meeting just told me it had already happened.
The status meeting was never the solution
At some point it clicked that the status meeting wasn’t a solution to anything. It was a symptom. It existed because the tools we used couldn’t answer one simple question on their own: what’s falling behind right now? Every board, every list, every Gantt chart held the raw material for that answer: due dates, dependencies, who’s stuck on what. But none of them would actually tell me. I had to go digging. Open twelve boards, scan filters, ping people, assemble the picture in my head. And I’d still miss things, because no human checks twelve boards every morning.
That’s the part that bothered me most. Not that work slipped. Work always slips. It’s that I found out too late, when the only options left were the expensive ones: the apology, the weekend, the awkward “so, about the deadline” conversation.
So I built what I actually wanted
So I started building the thing I actually wanted. Not a tool that holds more information. A tool that reads the information you already have and tells you what needs you.
That’s the whole idea behind SRP. It watches your work (the due dates, the blockers, the dependencies, the decisions that have gone quiet) and computes what’s at risk across every project you’re running. You don’t open it and start hunting. You open it and it’s already answered: this is overdue, this is blocked, this initiative is at risk because a task is late and another is waiting on it. The conclusion, not just the chart.
What I won’t pretend SRP does
I want to be honest about what that does and doesn’t mean, because I think the overpromising in this category is part of why people are tired of it. SRP doesn’t run your projects for you. It doesn’t take you out of the loop, and it won’t catch literally everything. No tool can, and anyone who tells you otherwise is selling. What it does is take the hunting off your plate and warn you earlier. It turns “go find out what’s behind” into “you’ll be told while there’s still time to fix it.” That’s a smaller promise than most tools make. It’s also one I can actually keep.
A few things I cared about getting right
A few things fell out of that core idea that I care about.
It watches the work, not the worker. SRP reads tasks and dates and dependencies. It does not count keystrokes, track idle time, or demand a daily check-in. I’ve worked under tools that treated visibility as surveillance, and I never wanted to build one. The signal comes from the work itself, so nobody has to perform being on track. If you’re looking for a way to monitor your team, SRP is the wrong tool, on purpose.
It does deliberately less. No fifteen view types, no fields to configure for a week before anyone gets value. You should be useful in minutes. The restraint is the point. Every feature I didn’t add is one less thing standing between you and the one answer you came for.
It doesn’t make you abandon what works. SRP is a complete tool on its own. Projects, iterations, files, team availability, client portals, all of it lives here, and plenty of teams run everything in it. But if your engineers live in GitLab and have no intention of leaving, good. Keep them there. Their work still rolls up into the same initiative, watched by the same risk engine. GitLab works today; Linear and GitHub are next. You shouldn’t have to migrate your whole company to get one honest view of what’s slipping.
And if you work with clients (agencies, I’m looking at you), there’s a quiet bonus. The same work that SRP watches internally turns into a client-ready portal automatically. The status update you’d normally write by hand on a Friday afternoon mostly writes itself.
Who I really built this for
I built SRP for teams that want to keep work moving without the project management theatre. Not project management itself, which is real and hard, but the theatre around it: the standup that exists only to surface what’s stuck, the status report nobody enjoys writing, the dashboard someone has to babysit. That ceremony eats the time of the people who are supposed to be steering the work.
If you run projects for a living, SRP is on your side. It does the grunt work you never signed up for, chasing updates, keeping the board current, spotting what’s at risk, so you get that time back for the part that needs a person: deciding what to do and unblocking the team. It doesn’t replace you. And it fits the teams who feel that weight most, the ones with no PMO, a lot of projects, a lean crew, and clients who notice when something slips. That’s who I built this for, and who I’d love to have try it.
An open invitation
So this is the invitation. If you’ve ever run a meeting just to find out what’s behind, if you’ve ever found out too late, I think you’ll feel the difference in the first week. SRP is free to try, takes minutes to set up, and there’s no credit card and no onboarding call. We’re a small team, so if you sign up and email us, you’ll be talking to the people who built it. Probably me.
Come try it. Tell me what’s still falling behind. I’ll want to know.