8,677 karma · joined July 13, 2011
Segment8.com - a full-stack competitive intelligence platform — from raw signal to finished battlecard, grounded in real win/loss outcomes. Capture competitive intelligence and win/loss data in real time, distribute to your team, and turn it into the battlecards and launch plans that win deals.
I do think that these pieces sometimes smuggle in a nostalgic picture of how engineers "really" learn which has only ever been partly true.
The big pinch of salt I throw in with advice like this though is that startup failure rate hasn't dramatically shifted despite two decades of lean startup methodology, accelerators, and an entire cottage industry of startup advice. It's never the fault of the framework, mind you.
I don't know about that. More usage means more support, which means more docs and open source projects, wrappers, harnesses built around them etc.
Way less demand to build tooling around open weight models if they remain hobbyist.
My very strong advice would be to pick one of these use cases and niche hard. Multi channel, multi party scheduling isnt a problem anyone thinks they have (even if they actually do). They wake up thinking they have 40 truck driver shifts to fill tomorrow.
Deputy cleaned up by going after rota scheduling for independent coffee shops. Logistics sounds like a great shout. Each have messy edge cases which you can develop a strong solution around but you'll get crushed trying to go horizontal in this space. Best of luck!
1. New power introduced after crisis or scandal, justified as exceptional and targeted
2. Enforcement is patchy or politically difficult. Police either lack resources or big tech platforms don't want to or can't play ball
3. Failure or abuse case becomes public and reported in chattering classes tabloid press
4. Response is not "use existing powers better" but expand powers, broaden scope, lower initial 'targeted' thresholds
5. Cycle repeats
Issue is compounded because you have politicians who will either not understand things or pretend not to understand things.
If you asked 'Would you support weakening encryption in messaging apps if it helped catch some criminals, even though it could make it easier for hackers to read your messages and steal your passwords, bank details, or personal photos?' I'd bet a large proportion of the general population would say no.
But that side never gets explored, or there's an assumption that there's some way of only letting the good guys access the information.
This has been the story for every trend empowering developers since year dot. Look back and you can find exactly the same said about CD, public cloud, containers, the works. The 'orchestration' (read compliance) layers always get routed around. Always.
If you're SAP, Workday, Procore, maybe even HubSpot, you have a shout. Growth won't be fast, but you're okay for now and might even be able to position yourself as an integrator.
If you've raised large rounds and you're just a system of workflow that won't trigger a years long political fight to get you out - a document review startup, good luck.