It comes off as disingenuous. A better way is to tell a specific success story. If some unknown brand has a story to tell about how your tool 10x'd their productivity, I'm all ears.
It comes off as disingenuous. A better way is to tell a specific success story. If some unknown brand has a story to tell about how your tool 10x'd their productivity, I'm all ears.
Eventually she left (to get an MBA) and the guy who took over her territory had trouble reaching the customer on the phone. Eventually he did get a meeting and when he visited discovered that all our packages (software and printed docs) were on a shelf in a cubicle, and that they were uninterested in renewing. It seems someone had the budget to spend and everybody liked having the saleswoman come visit. But they didn't care about a visit from Norm.
A rather extraordinary waste of money, but helped our bootstrapped company!
> It comes off as disingenuous.
And if the product is valuable to you AND it has logos, I can guarantee you will still use it. This feels like the typical developer trope here of "ads don't work on me".
The reality is that even if products (like Posthog) have developers as users, there is usually someone paying for it that's not the developer. So while you might not like logos, the person opening the wallet usually does.
> A better way is to tell a specific success story. If some unknown brand has a story to tell about how your tool 10x'd their productivity, I'm all ears.
Totally agreed (albeit this isn't mutually exclusive)
It doesn't have to be a difficult process either. An email interview with 8 initial questions and then another round if I need to dig deeper has worked for me. I turn it into a blog post after a light round of editing.
Depending on the size of the company, there may be additional review on their side, but most of the time I've had folks be happy to be featured.
This is a great way to share success stories, build content, and I was surprised at the various ways people used our software. The stories can also be used by marketing and/or a sales team. (Not typically great for posting on sites like HN unless they dig really deep into a technical topic, though.)
Edit: make it clear that folks know the interview will be published.
What are you actually trying to convey here to potential clients? Having a bunch of consumer tech brands when your potential base is actually more about universities, sends the message that you're not a serious company in the field and won't have their best interests at heart. Worse, it can make you seem very generic, as most sites flaunt Google/Microsoft all over the place.
This also applies to success stories. Highlighting irrelevant success stories also sends the wrong message. If a potential client in finance is looking at your tool, ready to drop substantial funds, but all they can find are success stories relevant to gamer brands, they're gone they aren't going to do the work for you to find out if you're good enough.
You have to be selective even if that feels counter intuitive at first. So I don't mind the row(s) of brands related, just make sure it's sending the message you want to send.
Otherwise, just a list of logos and/or company names does feel lazy and non-convincing to me.
So if the office manager of the IBM facility in Mobile, Alabama uses your SMS service to coordinate the contract janitorial staff, then boosting the IBM logo without this context sends the wrong message to the long tail of small companies who don't pay "IBM" prices for anything.
If you're in an organization with any type of compliance needs (SOC 2), that "used by" signals that the business is organized enough to pass security/audit requirements by that company. While it may be a single team using the product, they're still held to wider organizational standards.
In your example, it's actually worse than annoying. If you're basing SOC2 compliant requirements on a "used by" signal, then the misdirection is potentially catastrophic.
I'm absolutely not basing it only on that, but it is an early signal. There are likely many options for any specific tool. "Used by" can help me differentiate between the side-project and the meaningful company before I go too far down the rabbit hole.
It's so obviously just that the other company was like checking to see how your product and there's integrates. They weren't actually using it. But now they're in the "Trusted by" panel on the homepage.
And customer references are a big deal. Companies absolutely want to see other companies in their industry which are using your product and even have conversations with their peers about it.
I am running my own Saas company (https://www.usecloudpress.com/) and I ask explicit permission from companies that use my product whether I can use their name, logo, and some testimonial text on my website. I would never even consider using it without their permission.
you should be specific, especially when marketing to developers. So, I’d rather write the product is "used by X developers or Y companies."
in a past experience at an early-stage company that was starting its sales motion, we highlighted a testimonial from a customer in the headline as a workaround. Another option could be adding a short description of the use case, too.
show, don’t tell.
I think the best option would be a mix of the two (which AWS does). You have a tileset of companies which "use" your product, but you also back that up with individual testimonials which link back to case studies on your blog.
Case studies are a much better validation imo.