Hi William, and welcome to the community!
Whether it’s wise to build a base for each product is a deeper subject, but I must assume you have reasons for compartmentalizing your data in Airtable this way. But if you proceed with such a data model by separating product development information in bases, you create a few other challenges such as (but not limited to) -
- There’s no way to search across bases.
- Comments about product (a) could never be seen by users in product (b).
- There would be no way to easily roll up the product information or development status in a unified report.
- I could go on for about an hour…
My reminder is simply that information in a database is typically more useful when it can be aggregated and Airtable bases are more like databases and less like spreadsheets.