If I don't know with local knowledge, I just ask the hotel reception for any hospital/doctor where they speak English.
I think my health insurance provider can also provide me with contact info of relevant parties.
We ran into the same question with WIP where initially it was all based on Telegram usernames, but we then made having a Telegram account optional. Same with BetaList where we only used Twitter OAuth, but more recently added regular signups.
There isn’t a super clean solution.
What I ended up doing is letting the user choose their own username, but pre-fill it with their OAuth service name if available.
It hasn’t lead to any issues.
One extra benefit is that it gives people an incentive to sign up early to claim their desired username.
For what’s it’s worth I’m never a fan of this approach, as it temporarily exposes part of my email address to other users. Assuming the username is public.
How does it expose the email address? These names come from the creators' names on platforms like Twitch/Twitter/Discord. So twitch.tv/jaku my link would be mywebsiteservice.com/twitch/j….
I suppose if jaku is part of my email this is true, but they'd have to assume the rest of the email and what provider I'm using to receive email?
Unless I'm missing something here?
Being able to access GPT-4 anywhere seems super useful. However, for me those triggers words never feel that intuitive. I'd much prefer having auto-complete like Copilot provides. You just type and see suggestions you can tab to auto-complete. That feels a lot more natural.
As for the "roast", there's A LOT of competition in this market. And all apps seem to do roughly the same thing. I think it will be very hard to build a competitive business, if your main selling point is providing a keyword trigger for the OpenAI APIs.
I'd really niche it down to something specific (sorry, not sure what that should be). Or come up with a more streamlines UX that's harder to replicate.
The direction going forward really depends on your unique strengths and interests. I'd focus on those.
Having said all that, major props for shipping this! Most people get stuck at the idea phase. You actually delivered. Now all you need to do is keep going 🙌
+1 to what Marc said – the internet is flooded with products right now that all do some version of “We pre-prompt your prompt and give you no-code access to GPT API”
That’s good, iff you have a niche non-technical market you can reach better/cheaper/faster/moretargeted than competitors. Or as Marc said, you make the integration suuuuper buttery smooth for your target users in an existing app they’re already using.
For example: I would love a ChatGPT interface inside VSCode that understands the entire context of at least the local file, full project would be even better, and is as easy to use as TypeScript-based autocomplete.
But even if that existed, my head of security would never let me use it 💩
Thanks Swizec. I actually have a same idea, but not sure if I could make it better than Github copilot haha.
As of security/privacy, I think a paid opensource could work. WDYT? :D
Thanks a lot for your reply, @marc. And I agree with everything you said.
I gave myself 1 week to ship this product and would then collect feedback from my early customers. Hopefully I could find some niche use case that make this really useful.
Otherwise, yeah, it's quite hard to build a competitive business with the current feature.
Assuming you currently own 50% of the business, then a $5k buyout imputes a $10k valuation on the business. That's less than 1x your annual revenue which seems extremely low.
If you no longer want to work on the business, I agree it's fair to your co-founder to sell your share (or at least the majority of it) but it should be for a more reasonable valuation IMO.
A 3x annual revenue multiple for 100% of the business is a typical valuation, if you have decent profit margins and the site doesn't require on-going work to keep running as-is.
So that would be a valuation of $54k or $27k for your half. Let's call it $25k to simplify.
Rather than your co-founder having to pay it all upfront (which would be quite risky as perhaps the revenue implodes, etc), you can structure it such that you continue to get X percent of the revenue (maybe even 100%) until you've received the $25k.
Whether it's $25k or something isn't just an accounting matter, but also subjectively what seems fair.
If you're basically "walking out" of the business and leaving your co-founder hanging, then maybe it's fair for you to walk away with less than 50%. Many companies have a vesting clause built-in for this.
On the other hand, you derisking the buy-out by having it done through revenue-based payouts might already make up for the fact that you're moving on.
One final thing to consider is that you'll need to make it worth it to your co-founder to continue. If your demands are too high, it's likely they won't want to continue either and you're both left with a dying business and no payout.
Thanks Marc. Appreciate your response! I have to think about it maybe 5k is indeed not that much. I have to take into account that the code base is bad and he has to find someone to continue with. It has a lot of potential but it takes a lot of development time.
Looks like you're hotlinking to some images hosted on googleusercontent.com that don't load for us. Possibly, because they hosted behind a login?
Did you copy/paste them from Google Docs or Gmail or something like that? It didn't actually copy/paste the image, but just the URL. Which we cannot access.
If you download the image to your computer first and then add them to your post, they should upload to our servers where they are visible to everyone.
Haven’t tried it, but would be interested to know as well 👍