mx_abhishek

The idea is to eliminate the endless tabs we have opened in our browser when looking through job listings. Save them to your Notion database in a click, and manage them from their.

Currently works on a limited number of job portals: - linkedin.com - weworkremotely.com - justremote.co - nodesk.co - remote.co - remote.com - workingnomads.com

Support for lever, workable, yc jobs coming this week

Hey guys,

The app workflow is quite straightforward. You upload a picture from your gallery, or click one from your cam, and it converts it into a lego-themed avatar for you.

Typical generations take anywhere between 20 - 60 seconds. I think it could be made a bit faster, but waiting to first gauze the initial response from the community.

Would love to know what you guys think.

Cheers!

So, either month-on-month or a one time fee with money back guarantee. Makes sense

Support pages exist. Some businesses use documentation, faqs. Some use systems like intercom. Some simply leave an email up there for customers to reach out at.

It works. But is it good enough? Probably not. And even though there are competitors out there, I also think the market is large enough for a good enough opportunity for a new product to exist.

But yeah, the problem seems to be real and painful enough.

That's the very assumption I want to stay away from. Hence not launching a full-blown product, but a barebone version of it. I want to see which type of customers are most drawn to it, and which ones off them use it the most.

Yes, no current users and no churn data is a bummer, but since I am just starting this, that's pretty much the hand that's dealt to me.

Thanks for taking the time in writing a detailed note. Took notes. :)

Since it is a knoweldgebase, the customers are businesses. Given any business would be spending at least $20/mo on hosting alone, I thought $100/yr would be a good price point to start with.

As far as ideal customer profile goes, I have not yet zeroed down on that. I thought I would let customer response/affinity to guide me towards discovering that.

AI chatbot custom trained on the customers' data would be the next logical step in this. But at this stage I am more inclined to testing the water. Shipping out something quick and then build it up from there as and when I successfully onboard paying customers. Do not want to spend weeks building a product and then be the only one using it. Thought I would gauze the interest first.

Almost every single response has been this - both here as well as elsewhere I posed this question. Thanks. :)