by ICodeSometimes on 12/1/24, 12:32 AM with 4 comments
by e-clinton on 12/1/24, 12:38 AM
by mhowell on 12/1/24, 2:30 AM
That being said, esp considering the competition above/their more agnostic use case coverage, I think it is a Big Brain move to differentiate/laser focus on this more specialized/niche SaaS sales-pod Data Room concept as products above are not tailored to automate like a sales pitch/demo/discovery call (e.g. white-labeled experience or partnership assets). Brand.dev collab and others with sales-pod-based company networks is killer really — realizing more as the thoughts stream to text ahaha... Anyhow, this is a real need and you don't have overhead of products above, so have significantly cheaper usage-based pricing to understand/better serve this target audience / QC the autogenerated bits, and you will have a real moat through the data/analytics itself that fuels something with massive potential here.
TL;DR IMO if you guys nail Branding and viewer analytics (e.g. X person spent Y time viewing Z page) and bake in the sales-pod 'philosophy/journey' into flows more intuitively from the start.... I'd BET THE HOUSE.
Loosely-held tactical feedback: Sales pods should be pods (suborgs) of the org that registered not Data Room specific to prospect (UX conflates sales pods/Data Rooms IMO), create some defaults/examples with description showing what the purpose is why the example is there and skip step 1+2 in onboarding (just need org creation for admin portal), IDK how notifications work or how to link POCs to the company data rooms — need to be able to create pods of different sales folks (some may be in multiple pods) and need to be able to lockdown access/view of the doc by some optional fields like email SSO with website you entered that you are generating the Data Room for.
More verbose/nitty feedback: agree with e-clinton and more widely just that the UI seems overly complicated and/or distant from the product mission/utility (should be super intuitive and usable by SDRs/BDRs/SDEs/etc).. Auto-setting up subdomains is cool for us devs but folks will not know why you are doing this (or even slugifying data rooms for example companies) so I suggest starting at step 3 (our First Sales Pod), generate default subdomains/slugged BS if needed optimistically and question reason to even show as opposed to just handle on BE but also tooltips/info icons describing importance could help, but low-key move might be to move whatever seems "eng cool" to some settings page/tab...