[bjarocki]

I agree. The landing page isn't the nicest one. I'm not a designer, though, and I'd rather spend that time improving the product. Is there anything you'd like to see in the extension that'd convince you to pay for it? Happy to improve!

[brysonreece]

I totally understand the use of Tailwind UI for an easy way to achieve professional looking components; I use it every single day at my job.

At the same time, you're targeting this product towards customers who are already developer-oriented — a crowd that is familiar with, or can easily recognize, the same technologies you've used to build Monito. Tweaking the designs to have a more custom flair so it doesn't seem so copy and paste, avoiding the same icons for multiple figures, and especially lowering your price are all things that would probably help with early and continued adoption IMO.

As for things you could include to justify the existing price, I really don't know. There's a heavy difference between paying for a desktop-application license vs a browser extension.

[bjarocki]

Valid point. I started noticing Tailwind UI everywhere, and it starts to be a bit annoying indeed. Will def work on it.

We'll see about the price. So far, it sells ok. I'd rather focus on improving the quality and adding useful features.

Regarding the icons, I've just noticed and fixed that, thank you!

[bendotero]

we developers are a stingy lot. I wouldn't base any pricing decision on what technical/developers say. The ultimate customer for this is a support person who is going to give feedback to a developer. To them and/or a QA team, you could be saving them a ton of time with this product. Consider that birdeatsbug starts at free for personal use and then $39/month. You might actually be leaving money on the table if you go $39 one time. Just something to consider.

[bjarocki]

At this point the price is 39$ because the product itself isn't polished yet. Now I can see it's actually needed and I'm going to add some nice features. Then it'll go up to ~59$ as it won't be an 'early access' anymore.

[jacekm]

> anything you'd like to see in the extension that'd convince you to pay for it?

Different pricing scheme, at least in the beginning. While $39 (or even $59) is acceptable as one time payment, I am not sure if I am willing to pay this for a product that's been on the market for only 3 weeks and whose future is unknown. Charging something like $1-$2 per month will earn you more in the long term and will provide a safer option for the customers (they won't loose too much if you disappear in a couple of months).

BTW, at the organization where I work, we can only make payments to established entities, i.e. someone who has address, account number and can issue an invoice. I guess Gumroad, as a middle party, can provide all of these, still it would add to your credibility if you had an "About" page with the necessary data. Oh and a Privacy Policy would be nice too - some organizations won't allow installing any extensions that are not reviewed by a security team and such reviews often involve checking privacy policies.

[bjarocki]

Good point about credibility. I'm going to improve the landing page with a proper about page. I'll also add a privacy policy. From the start, I wanted it to work 100% locally, so I don't have to worry about sensitive data. Now it only uses some ids needed for trials and licenses.

About pricing, I don't think that model would be better. As a solo developer, it's better to charge more and provide better support to fewer customers. I'm not saying no, but it seems to be working well for now. Thank you for the suggestions!