Continue validating ambitious idea validation or start anew?

Thanks Pedro for the read and reply.

*Properly managing your record retention without developers"

I think this needs some tweaking but after talking with my company's Risk Manager, the hardest struggle for their risk team is getting the engineering teams involved in the effort.

Aside from initial configuration/connection to the database, the development teams would have a low/no touch for the Risk team to report and execute data cleanup as per the record retention policies.

For context, here is my full pitch:

*****

# Idea
Cross-Team Data Retention Management Software (tentatively called Purgo)

# The Problem
Various groups play a role in complying with data retention policies and following through with cleanup:

1. Risk/Compliance know the importance of data cleanup and often help define and enforce the policies
2. Software teams best understand the data and its intricacies
3. Data Engineers care about reducing the cloud costs especially for unneeded data

Software engineers are critical in the implementation, execution and maintenance of the scripts, but unfortunately they have the least incentive (relative to other work) to actually implement these non-functional data retention policies. Many times the data won't be purged for 10 years or more in the future and tend to deprioritize the effort needed to implement data cleanup when new software and databases are released.

# Benefits
For a monthly fee, Purgo decreases engagement needed from the software teams to implement and maintain data retention rules, offers cross-team visibility for shared databases, and provides reporting dashboards on which databases are adhering to their respective policies. Secondarily, the programmatic cleanup of unused data should ultimately allow the decrease of storage costs for databases especially as data moves to the cloud. Here are the core phases to manage the data cleanup process:

Phase 1: Register databases/tables, control columns (PK & Last Updated), and which team(s) own/utilize the tables
Phase 2: Apply retention policies
Phase 3: Schedule cleanup
Phase 4: Report database health and levels of compliance

By having a standard, repeatable process for data cleanup, the software teams are only required for initial connection setup and basic testing that the cleanup process is functioning as expected.

# Price
Plans start at $99/month and will scale up as more databases are managed by Purgo.

That's the idea....would you pay for it?

Thanks for taking the time to read through this. Again, even if you only have time to answer with a yes or no, it will be a big help.
*****