167 karma · joined February 19, 2022
Vibe slop-ing at supersonic speeds and waiting years to grow aren't the only options, there's something in between where you have enough signal to keep going and enough speed to not waste years on the wrong thing.
I feel that today's VCs have completely disregarded the middle and are focused on getting as big as possible as fast as possible without regard to the effect it's having on the ecosystem.
- are you just using favicons? - how often are you refreshing the logos? - what if no logo is found? - What is your universe set size? (I tried my own business brand.dev and said no logo)
Disclaimer: I run a similar feature on a separate product (https://docs.brand.dev/logolink)
Just shipped the brand.dev logo link, meant as a drop in clearbit logo api replacement.
Wanted to share
It’s used to power onboarding personalization, branded UIs, enriched transactions, AI prompts, and automated styleguides.
The goal is to make it trivial for products and AI systems to be “brand-aware” without asking users to upload assets manually.
The most obvious use-case is to pre-load your onboarding flow based on the user's corporate email so that they only need to "confirm" rather than fill out their information, it provides a pretty significant conversion rate boost for PLG B2B products.
Other use-cases include: - Powering Gen AI (ad makers, brand kits, etc...) - Automatically prefilling brand kits for email marketing platforms - Enriching company profiles for directories, CRMs, etc.. - and more!
Curious to hear your thoughts :)
The idea is that it's supposed to help deals avoid dying through endless email chains where its hard to tell what to do next.
Any time you want to programmatically enrich data with visual data this would come in handy.
It's very much a "this is exactly what i need" or "i definitely don't need this" type of service from what i've seen
My reasoning for creating this are the alternatives are WAY TOO EXPENSIVE (5-10x per api call).
Since it's a one man show, i don't need much margin and i'm happy to just keep it alive since my friends and i use it for other projects that have more significant margin.
Almost all requests goes through a proxy to be honest.
You pay per GB transferred basically which works ok for me at the moment.
Cheers!
However i hired a designer for the landing page. My design skills are decent but for a product named "brand.dev" i thought it was worth it to pay for a proper design.
My train of thought was that i was basically offering a hyper-opinionated scraping service since all im doing is scraping publicly available data and packaging it for a particular usecase (similar to say, zoominfo which also provides logos for example).
I will dive into this.
Out of curiosity, what's your background to have all this info? Are you a lawyer of some sort? It was a great writeup.
The fact you couldn't find it means i need to change something, will start auto generating the keys upon signup.
A work in progress to be honest.
I check what websites are fetching the logos constantly and block any that seem malicious including canceling their api keys.
> How can brand owners opt out of your service's infringing their intellectual property rights in their logos?
I fetch publicly available assets for any brand, i'm not passing them off as my own. Let me know what gave you that impression please :)
i like knives
Yeah that's 100% a fair call-out, adding one now.
> Prices are listed after creating an account: $49/month - Up to 1000 API calls per month $99/month - Up to 3000 API calls per month
Just added a pricing page and linked to it from the navigation bar. https://brand.dev/pricing
> When I tried the cUrl call (copy&paste from the dashboard) I got an error "{"message":"Unauthorized: Invalid token"}"
Yeah this was a ridiculous bug on my end, apologies, it's fixed now!
------
Thanks for the feedback. Happy to throw some credits on your account if you'd like to take it for a whirl! hello@brand.dev
Let me know what you think, thanks!
Ironically both of you launched on the same day.
also regarding the customers you've already onboarded, possibly worth it to make case study blogs?