Yes!!!!!!!! I neeeeeed a read/write API for Notion!!!

I am waiting for this, too. Hopefully not too long away - even Zapier would be good at this point, which I know is on the way.

I respectfully challenge your PM solution comment. You can create relations within Notion that can link a Task table record to multiple projects in a Project table. Notion is very flexible if you take advantage of its relational database features.

I have to second @floringp in that challenge. Notion can do it, but you have to build the databases and relationships yourself. One database for Programs. One for Projects. One for Deliverables. One for Tasks. Every database has a 'Currently With' and a set of Status (selection property) tags for each phase in the house process. I handle intake via forms which get entered into another Database, and tagged in the properties to the Program, Project, Deliverable, or Task as appropriate. Checklists detail the next steps for each team member, and moving things through the system or tasking things out to individual team members is as simple as building into the database a 'People' property. So long as it's in the team's Workspace, it tags the users in their Updates panel of the next thing to do. You can take it a step farther and set up every team member with their own copy of a dashboard view where you set up filters and /Create link to existing database so that they get a list populating there of everything assigned to them currently. Then the team plays "keep away" by trying to finish their action items and give it to the next person in the chain, which is written right into the template of the job folders. You can easily do this. It just takes a little grunt work and some planning on the Process side to build out the tools and databases in the way that makes the most sense for how your team works. It doesn't force you into a pattern out-of-the-box, it just gives you the tools to be able to build out the system for what your specific team needs and is willing to use. Now, if you have an unmotivated or an older team not as digitally savvy or willing to own the whole process overall, then Notion is going to be a tough sell. But my team is younger, very digital, and test users all universally fall in love with the simplicity of the interface and immediately begin building out tools of their own for personal use, even before being introduced to the core databases of the business as a whole. I've wrangled Art Buying, Creative brainstorming, production, web dev, integrated marketing, marketing optimization, SEO, and provided a more collaborative tool than email, plus a common Meeting Notes database with relational fields so that anyone can take Meeting notes in the database by making a new entry, and just tag the project, so they show up associated with the template of the Job jackets. Yeah, it takes a little work to set up. But once set up, it should run for a while without issue. Revisit Notion, please. You missed the forest for the trees.