I considered BYO OpenAI key for rmflags.com as well and decided against it for the reasons you mentioned. Ultimately if the customer has to sign up for and manage their own OpenAI credits it just adds friction to the entire signup process.
However for simpleotp.com I did force users to supply their own SMTP credentials. I can’t risk ruining my email sending reputation because one user decides to send emails from a bad domain for example
For pricing, I thought about this for a long time and I think I’d rather charge according to the value the customer gets out of the solution instead of considering AI cost in too much detail upfront. I’m not saying I wouldn’t look at the AI cost, but I like to start with “okay, customer would otherwise have to pay an engineer $200/hour to do this task, so I’ll charge close to that” - and if AI spend is > $200/h, work backwards and figure out how to reduce the cost from there, or if not possible maybe it’s a bad business idea.
I considered BYO OpenAI key for rmflags.com as well and decided against it for the reasons you mentioned. Ultimately if the customer has to sign up for and manage their own OpenAI credits it just adds friction to the entire signup process.
However for simpleotp.com I did force users to supply their own SMTP credentials. I can’t risk ruining my email sending reputation because one user decides to send emails from a bad domain for example
For pricing, I thought about this for a long time and I think I’d rather charge according to the value the customer gets out of the solution instead of considering AI cost in too much detail upfront. I’m not saying I wouldn’t look at the AI cost, but I like to start with “okay, customer would otherwise have to pay an engineer $200/hour to do this task, so I’ll charge close to that” - and if AI spend is > $200/h, work backwards and figure out how to reduce the cost from there, or if not possible maybe it’s a bad business idea.