@davidu Hey David it's a great question. On the technical side we'll go the other way around by opening our API so that you can update things remotely. It's a bit hard for us to understand and handle all the use cases because the KRs/goals tracked by our customers vary a lot. But we can make it super easy for them to build their own integrations (and we'll create some in the future as we grow). Now, there's another question that is interesting. _Should_ we automate updates? Our answer is generally no because a lot of the value comes from people having to look at the data and offer their perspective: - Are we on-track? - If not, why is that? And what's our action plan? When things are too automated we risk going back to having a bunch of dashboards that are never really looked at by the team. Of course we can have alerts when things go off-track but we believe in the value of having a periodic reminders of what you should be focused on, as well as the enriching data with human feedback. That's not to say that we're fully against automated tracking (also my background is in continuous delivery and automation) but this is a case where we think that a lot of the value comes from looking at progress regularly and sharing feedback with the broader team. To be clear we want to make it as easy as possible to share updates, and there are absolutely valid use cases to automate inputs, but our primary role is to create fast feedback loops on outcomes. Sorry for the long answer!