My company is building something in the messaging/comms space, but focused on B2B rather than internal team chat like Slack/Teams. Seeing all the dislike for those two makes me wonder if we should enable intra-team messaging as a (free?) bonus feature.

As for PerfectWiki: fantastic hyper-targeted product and writeup. Congrats to Ilia

A tool to address friction in B2B interactions (mostly between large companies) I've seen in my career. Main innovations are in comms and contract management. Leaning in on some hardcore dev talent in the team for the stack: there's Rust and Gemini in the mix. I'd say we're past the halfway point of MVP development

Very valuable, thanks for posting. The author understandably leaves out the dollar figures (even approximations) for what that exist looked like, but the tone suggests it's above decent. The concrete advice for startups requiring cold pitching and network effects was particularly good.

Thank you (and the whole team of course) for creating something so amazing

Fantastic, inspiring post. Congratulations x 200!

The story is great on its own, but that ending was absolutely magnificent

Don't mean to sound aggressive, but no professional organization worth its salt does systematic password sharing of any kind. Password sharing is almost always a security violation and, even if shared securely, can generate licensing complications for the product or service you're authenticating into. Better to have one account per service per person who's going to use it and systematically revoke licenses/accounts that go unused. Also use official methods for resetting passwords (email link, TOTP generated by the app itself from an admin console) rather than sharing passwords.

Lastly, of course like everyone said: SSO is your friend!

First-time founder working on a B2B comms web app. Have had trouble locking down technical co-founder but recently made great inroads with a childhood friend of all people. If an MVP comes out of it, I'll post it here!

The water cooler thing is a myth. I've spent my fair share of time in tech company offices and have never seen, nor cannot think of, anything worthwhile coming out of those encounters. Like other posters said, a shared meal with colleagues is a different story, though it will typically increase social connections rather than generate new productive/business outcomes

I used to work for a large multinational ($80b market cap; 55k+ employees) with a penchant for in-house development because vendor exhaustion is real and under-discussed in the business world.

Their trick for doing it was recruiting heavily in regions of the world with great junior dev talent at comparatively low costs (in their case Latin America, but it could be eastern Europe or elsewhere) and have them work with more senior middle and top managers to guide the architecture and technology decisions. At any given time, if you took a snapshot, you'd simultaneously have numerous SaaS subscriptions, numerous devs as described working to replace those same SaaS subscriptions, and numerous completed projects that, if purchased on the market, whether SaaS or not, would have cost exponentially more than the developers' salaries. No freelancing, no subcontracting, only proper employees - but yeah, you need to make the economics work and your milage will vary.

Full disclosure: I have since left that company and work as a consultant doing precisely that kind of work for others, it's only fair to note