| First of all, thank you for taking the time to write this, I appreciate it! - you re spot on the pricing - I have no clear plan yet on the tiers and the exact figure per month - there are 2 options for me here as I see it: a) implement token based pricing to cover pricing for workflows that use my service’s OPENAI key
b) allow users to just use their own API key, and just charge the extra organisation layer that my app provides - this would probably be in ~3-5 p.m - why consider codii - thanks for calling out the inconsistency bit, I ll update that to be phrased more correctly, the basic idea is - code reviews on every pull request as an extra QA check. - your 3rd point is bang on - 10 is pretty low, and ideally I d be able to sustain a free tier with more scans per month(logistics a bit complex to get right). I ve actually updated that to 100 but have not reflected on the landing page, definitely something I need to do.
Re target audience, you ve spotted my confusion there as well, this is indeed aimed for solo devs for now, in which case I should not be claiming team-based benefits.
So I want to evolve this slowly starting from solo devs and working my way up to small teams. The action I’m taking from this is to focus on realistic target audience not the one I d like to have in 2 years time. - re clunky landing page, again you’ve got a solid point there, clunkiness can feel repulsive, this is me basically sacrificing UI for functionality in the chase of feedback, the action I’m taking is to polish up th landing page so that it doesn’t scare people away . Thank you for the encouragement and the solid feedback! This is exactly what Im after in the current stage! |