Interesting! Where do you think the biggest advantage is, vs (say) ChatPRD?
kschrader•4mo ago
I'm not 100% clear on what the scope of ChatPRD is at this point (beyond PRDs) but Korey has a fleet of specialized subagents running underneath for everything from status updates to writing specs to breaking them down into subtasks to understanding how much work everyone on your team is doing and suggesting who the right people for the right jobs are (or agents for the job).
Each subagent is tied to and evaluated against different models (mostly Claude currently), so we can keep improving and adding to them independently.
We're also team centric by default, so if you want to see how someone on your team worked through coming up with a spec you can always see all of the work behind it. We're working on a testing and training framework that would apply your standards company-wide (coming soon).
Finally, we bill on interactions, so it's easy to try out and if you and your team are finding it useful and getting value from it then you pay us, if you don't then you don't. Hopefully this best aligns us to keep improving things and making it better for everyone, instead of just billing you by the seat, regardless of how much people use it.
brandonb•4mo ago
Interesting! That makes a lot of sense to me -- and I could see how Korey could get better over time at interacting with other agents (e.g., with Devin to actually fix a bug).
kschrader•4mo ago
One other note: We've seen teams where people are now using Korey as the main surface to their work tracking tool.
They show up in the morning and say "what was I working on yesterday?" "what else do we have to do in this sprint?" "Assign task XYZ to Devin.ai and put Story ABC into the started state and assign it to me"
It's been unexpected and surprising to me how fast the tools that we've used for years have become tools that are only looked at occasionally for some of the teams that are really leaning in here.
brandonb•4mo ago
kschrader•4mo ago
Each subagent is tied to and evaluated against different models (mostly Claude currently), so we can keep improving and adding to them independently.
We're also team centric by default, so if you want to see how someone on your team worked through coming up with a spec you can always see all of the work behind it. We're working on a testing and training framework that would apply your standards company-wide (coming soon).
Finally, we bill on interactions, so it's easy to try out and if you and your team are finding it useful and getting value from it then you pay us, if you don't then you don't. Hopefully this best aligns us to keep improving things and making it better for everyone, instead of just billing you by the seat, regardless of how much people use it.
brandonb•4mo ago
kschrader•4mo ago
They show up in the morning and say "what was I working on yesterday?" "what else do we have to do in this sprint?" "Assign task XYZ to Devin.ai and put Story ABC into the started state and assign it to me"
It's been unexpected and surprising to me how fast the tools that we've used for years have become tools that are only looked at occasionally for some of the teams that are really leaning in here.