We just launched teams for Zaprite, allowing colleagues to collaborate on their bitcoin (and fiat) payments, reporting etc… This is the third time I’ve built teams functionality for a web app (Stack Overflow and Unchained prior), and by far the earliest in a product’s lifecycle. It’s a testament to John and Tom’s forward looking architectural decisions making a feature that is usually a slog a breeze. I love this team.

https://blog.zaprite.com/teams-for-zaprite/

Reply to this note

Please Login to reply.

Discussion

Do you have some basic discovery page/index aggregating all (your clients) accepting Bitcoin in the roadmap?

You can just maintain them in an XML - *list of online businesses who are reliably accepting btc* , and let someone else to build the user facing frontend for it. You can monetize it later too.

If it starts adding significant traffic to your clients, it will be a solid external value prop for adopting Zaprite.

Good idea. I hadn’t thought to do it, but as an opt in that is obviously valuable. Thank you!