When I was researching this product area, I found a bunch of similar tools that summarized on the inbound side. I thought it would be more interesting to experiment on the outbound side as the main initial focus, which I haven't seen.
I do have a generic popup that you can to summarize any passage, so you could copy-paste some long passage (email, article) to piggy back on the functionality. But it isn't tightly integrated into the Gmail UI as of now.
Product tours may be enough for people with Anki and WorkFlowy experience, however, I have no experience with them and, I still have no idea what your product does. A demo video would be great.
Stripe closed my account before I was able to launch as it was "unable to accept payments for crowdfunding"..... Their marketing doesn't match their policies.
> Stripe closed my account before I was able to launch as it was "unable to accept payments for crowdfunding"..... Their marketing doesn't match their policies.
Wow. I understand it's their right to do this, but that's total horseshit IMO. I guess maybe crowdfunding is subject to too many refunds, but IDK.
You could add a tag to feature request issues that it'd read from, maybe as a github app or something. I run an OS repo and it'd be really cool to be able to get through them all faster with a bit of money to pay a freelancer, for example. I imagine the users-paying side would be very hard to find though.
I'd also love to be able to attach a bounty to PRs with this money, although quality control would make me worry it'd be hard.
I imagine Patreon is never an enormous sum for people because the money is goodwill - it isn't tied to receiving anything back. You could make it like this.
I'm surprised there wasn't some other way of doing this - clearly other crowd funding sites exists, what do they use?
For open source issues there's already a few solutions, one to look at is https://issuehunt.io/ (they use Stripe)
Most use Stripe. I guess it's just a case by case thing. I really don't know why they rejected me when they advertise that exact use case [1]. But the policy I was directed to says the opposite [2].
Would be cool to use this tool to read less of incoming email and then dig deeper if I think it's worth it.