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.
It’s a formal acknowledgement that humans make mistakes, implicit assumptions are dangerous and that code should be validated before it runs. That’s literally the whole point, and if developers by type were YOLO I’ll push it anyway, TS wouldn’t have got anywhere near the traction it has. Static typing is a monument to distrust.
The core idea (designers solving problems instead of pushing pixels) is sound. But these kinds of posts are always packaged with this kind of missionary zeal, as if discovering the usefulness of sketching or systems thinking is some kind of personal enlightenment.
I can see how re-editing can make the ideas more coherent within pg's frame of representation, but I'm struggling with the idea that it makes them any more true.
It's cheeky because it frames itself as rejecting the status quo, when actually what it is doing is saying "accept the status quo wholesale and just move to somewhere the status quo hasn't reached yet." And of course, if enough people do that, no one will be around to fight against the status quo anymore. The main difference between this and Thoreau's cabin in the woods is that Thoreau could have chosen to do differently.
This one seems like a classic Prisoner's Dilemma. Defecting (hiring only seniors) is rational in isolation, but if everyone defects, everyone loses. What incentive for a smaller company to hire and invest in training the junior if in two years they'll leave for a larger company anyway.
At the moment post 1997 when Britain was starting to change and become more diverse and sure of it itself it reinforced an identify of Britain as it used to think of itself: silly voices, binary identities and oddballs.
It has more in common with Love Thy Neighbour than anything that came after.
You couldn’t make Little Britain today mostly because it wasn’t very good, and the standards of the time were lower.
You could absolutely remake The Day Today, Brass Eye, Goodness Gracious Me or Peep Show today and they’d be just as good.
Game studios - a low touch way of getting around smurfing, botting and ban evasion, cheap farming accounts, and likely already think in terms of proxy/VPN abuse. Reach them through Unity and Unreal forums, dev groups, GameSec Twitter/LinkedIn
FinTech / Crypto compliance teams - position yourself as a plug in to KYC or KYB platforms. Behavioural analytics is a big play in fraud prevention, whether someone is using a VPN won't be the whole picture, but is part of it.
Deprioritise marketers, content teams - they're promising but ultimately false positives as no one but the very biggest players amongst them are losing sleep over this.
The key more than anything for both is going to be to emphasise in your positioning the ease of integration. Remember how Stripe had the exact code you needed to use on its homepage for ages? You've got to give the impression that integrating this is going to be super simple.
I feel like you spend quite a bit of time on your homepage selling why someone would want to do it, but not so much on the how and why you make it so easy fo them. Clicking into your docs it looks super simple, but the minute someone's had to click into your docs if they’re a non-dev audience, you're losing people.
You also absolutely must have a GDPR story. You’re detecting proxies and VPNs. This means you’re inspecting user connection data, possibly in real time, and possibly storing flags or identifiers. Even if you’re not processing names, emails, or cookies, under GDPR, IP addresses, device signatures, and behavioural data = personal data if it’s tied to a user.
Your GDPR story needs to cover data type transparency, what exactly what you collect: IP, device type, headers, connection method? If you’re processing requests in memory and returning results via API, that’s low risk. Highlight it. Offer EU hosting or at least say “data processed within EEA-compliant infrastructure." IANAL but you'll want to have a lawyer look at it.
USE CASES For a million reasons. Here's a few.
This is a common pattern ('We serve everyone!'), but you'd be well advised to actually pick a use case early on - you'll find that ecom, gaming, finance (especially), content, security, marketing all have their own specific needs and requirements, and they will want to see how you fit them before signing up.
This also makes your marketing efforts a little easier, as instead of having to spread thin across six different verticals, you can target for instance communities of indie gamers, bloggers, small shops who face this problem. when you've got validation from one of these, its easier to scale, but trying to go too broad too early in targeting is one of the most common errors founders make.
nicely designed site though and a lot of other stuff is on point.
EDIT: Your branding is also a little opaque. I wouldn't naturally associate "visitorquery" with what you were trying to do. Going for a domain like detectvpn even if you had to drop down to something like detectvpn.me feels like more of a direct match.
Providing services like virtual machines, managed databases, and Kubernetes clusters wasn't a groundbreaking innovation by the time DO came out in 2011. Even Heroku had been around for four years by then.
Apparently the market disagrees.
That can easily be said of most Product Manager > SWE relationships too though