First, I love this concept and I think your demo is great! Collaboration with existing harnesses makes a ton of sense. Just had a conversation with some folks in the non-tech world raving about using Claude.
A few questions:
- How do you think about competing with ChatGPT Canvas or Anthropic's artifacts, when these are shareable, native experiences in their products where users already work?
- Is a "dashboard" limited to analytics or are you trying to expand it to include written reports?
Since teams are connecting MCPs like Granola, Slack, I imagine BitBoard would facilitate sharing demos, PRDs/briefs, or customer reports. This seems like a natural expansion and trivial functionally, so I'm wondering if that's part of the sell now or something you're looking at expanding into as you grow.
Threw together some of these skills that'll just plug and play with your AI agent. You can download the skill to use them or just copy and paste the ones you like/want to edit.
Lmk if you'd like any added or modified. :-)
It's free btw! Works with any agent that supports skills.
A couple weeks ago I shared a GTM repository that *took off* here. After a bunch of user data and feedback, I wanted to offer a simple way for founders to pitch their products to each other.
It is really hard for early-stage founders to connect with buyers and partners in the B2B world.
So, I was hoping this could be a step in that direction toward making pitching, surfacing great products, & learning from each other that much easier.
Curious what y'all think. I just threw this together over a couple days, so lmk bugs too!
Exciting idea and seems like a well-proven team. Good luck to you guys here and don't mind the endemic snark in the other threads. A couple basic questions --
1. How will you handle one-off events like volcanic eruptions for instance?
2. Where do you start with this too? Do you pitch a meteorology team? Is it like a "compare and see for yourself"?
An idea's existence doesn't mean you can't build it. It's a good sign that it's been validated. Since you're not shooting for the moon, even more so.
I would pick something you're interested in, which you can do for a long time. That'll sustain you when you can't get customers or your product misses the mark.
Another underappreciated effect of dogfooding may be its reduction in bloated functionality.
If you're not dogfooding, you rely harder on a mental user model. Just conjecturing -- not only does that model diverge across your organization, but it could result in more top-down decisions about what a user wants, which probably creates more politics and friction all around your teams.
>> the hard part is contextualizing it in a way it is immediately useful. That depends on understanding the company/domain lingo, understanding users, etc.
How do you control this deterministically? It sounds like the "hard part" is variation in prompting & selectively choosing the right data to include, both of which I could see being good enough right now but hard to deliver definitively.
A few questions:
- How do you think about competing with ChatGPT Canvas or Anthropic's artifacts, when these are shareable, native experiences in their products where users already work?
- Is a "dashboard" limited to analytics or are you trying to expand it to include written reports?
Since teams are connecting MCPs like Granola, Slack, I imagine BitBoard would facilitate sharing demos, PRDs/briefs, or customer reports. This seems like a natural expansion and trivial functionally, so I'm wondering if that's part of the sell now or something you're looking at expanding into as you grow.