Yes, you’d do for them what they don’t know how to do for themselves and don’t want to learn how to do. They want to concentrate on running their business and not becoming an OSM mapper. It’s a good idea that can help OSM, and it’s worth charging a fee to do. I don’t know how much that fee could be, but supply and demand will sort that out. Already OSM is better than other maps for certain things in certain areas, and your idea could help it be even better if done well. Tell them that! Also show them how Google Maps is now almost completely enshittified and shows you not what you are looking for but what someone paid you to see. Finally they came clean last November with this:
Maybe the way to approach it is to just collect data, then daily or weekly, upload it to OSM. I do this with EV charging stations, but I just use a text file for each station. What’s in the text file? The OSM tags, in text form, and lots of notes. Even with the in-browser iD editor, you can copy/paste the text tags, and that’s quick.
Often I am waiting on a station to be constructed, in which case I cannot map it on OSM because there’s nothing yet on the ground (one of OSM’s most basic rules is “Map what’s on the ground”, and that means right now, not what was there yesterday and not what might be there next week). After construction is started and we get photo confirmation, I can map it with construction:amenity=charging_station. Only addr:housenumber=* shows up in the default OSM renderer. Then we wait for the construction to be done and the station taken live. At that point, from the charging company website I’ll get the final station name, branch, address, and some other details. From street-level photos I’ll get the number of ADA accessible stalls. At that point I remove construction: to leave amenity=charging_station, and then the EV charging icon
and station name will get rendered. Here’s an example in metro Denver, CO.
I don’t use a database but just use the file system on my computer, with a few levels of nested folders to contain the text file and any related photos (and sometimes drone videos). Would there be a better way? Maybe. I could use a database on my computer (or a server somewhere), but then I create a database problem of my own. You’d have the same problem. If you used a database and it could export a set of text tags ready to be copy-pasted into OSM, you’d have no data conversion import issues, but if you try to connect up the two databases, then your life gets complicated and that’s why you’re here.
Sometimes a simple approach, or a simplified approach that’s not 100% automatic, works well. The danger of 100% automation is that with 1 click you accidentally insert 1000 POIs into OSM that have bad or incomplete data.
Then you (or someone else) has to fix it. This happened last summer for US Tesla Supercharger stations, though it was an intentional bulk import that was severely half baked. Almost a year later we are still fixing the bad data because after being criticized for the bogus bits, the importer refused to fix all the issues, packed up his toys, and went home.