Ben Cpnd

Survived Web3, now building autonomous AI agents

[Ben Cpnd @ben_cpnd]

Proud of this new chapter for Braille. 🎉

What started as a clear mission to tackle bad UX in Web3 naturally evolved as the market did. AI matured, crypto matured, and expectations around products changed fast.

Today, teams don’t just need better interfaces. They need products that make sense, systems that scale, and experiences people can actually trust and use.
@braille_studio reflects that evolution.
More product-centric, more end to end, and better aligned with where AI and Web3 are heading.

This shift reflects how our approach has expanded:
 • From focused deliverables to end-to-end product thinking
 • From one-off projects to tailor-made product packages
 • From early-stage exploration to scaling and restructuring products, across AI and Web3
Pre-seed, seed, Series A to C, or Web2 to Web3 migration.

Same standards. Broader scope.

Excited for what’s coming next

[Braille Studio @braille_studio]

Braille becomes Braille Studio.

To our past and current partners, thank you.
To our future collaborators, we can’t wait to work with you.

Onwards to simplifying how people interact with technology.

Check out our new website:
https://t.co/Ap97T2vsJ4

[Ben Cpnd @ben_cpnd]

@marclou Thanks for hosting this @marclou, was really nice meeting and sharing this run with you!

[Ben Cpnd @ben_cpnd]

@AdamFard_ interested :)

[Ben Cpnd @ben_cpnd]

Co-builded this with @sadhikasethii, limited waitlist is open, few spots already taken.

If you run a studio, agency, product team, or you're a freelancer done absorbing misalignment that isn't yours, join the waitlist 👇 https://t.co/2kVvW1egLN

[Ben Cpnd @ben_cpnd]

After years working in product, agencies, and startups, one problem kept showing up everywhere.

Teams move faster than their decisions do.

Designers trying to make sense of conflicting feedback because nobody resolved it before it reached them.

Agencies eating revision rounds that had nothing to do with the actual work.

Freelancers absorbing the cost of decisions that were never theirs.

Founders slowly losing control over their own direction.

It always plays out the same way: work starts before the team is aligned, and someone downstream pays for it. We got tired of watching this happen.

So we built Sen.

Sen structures what happens before execution starts. It surfaces conflict, forces resolution, and makes sure direction is clear before the team moves forward. AI spots the friction. Humans make the call.

[Ben Cpnd @ben_cpnd]

One of the best ways to test if your product has real demand: put it in front of people who don't know you.
MakePRD is now live on @ProductHunt 🚀

An AI-powered tool that helps you go from idea to structured specs in minutes.

1/ Chat with Feature Finder to figure out the right feature to build
2/ Describe what you want and get structured user stories, acceptance criteria, edge cases, and success metrics
3/ Connect your project and get live AI recommendations

Export to Linear, GitHub, or feed specs into Claude Code, Cursor, or whatever you're building with. 19 languages 🌐

Few beta seats left. Links below 👇 https://t.co/iIIGmJ5Hcj https://t.co/VGnpzcdYT6

Every vote and share helps 🙏

[Ben Cpnd @ben_cpnd]

Been spending the last few weeks exploring how AI agents and vibe-coding can actually improve my day to day workflows. Not the hype, the practical stuff.

One area that kept coming up and based on my experience: product specs.
PMs spend hours writing specs that engineers never read, or founders skip specs entirely and ship chaos. So I built something.

MakePRD is an AI-powered tool that helps you go from idea to structured specs in minutes.

Three ways to use it:

1. Not sure what to build next? Start a conversation with Feature Finder, an AI chat that helps you figure out the right feature based on your goals and users.

2. Already know what you want? Describe your feature and MakePRD generates structured user stories, acceptance criteria, edge cases, and success metrics.

3. Want ongoing guidance? Connect your project and get live AI recommendations based on what's happening in your product.

Push everything to @linear or @github with one click, or export and feed your specs directly into Claude Code, Cursor, or whatever you're building with.

19 languages supported.

Early access is open 👉 https://t.co/VGnpzcewIE

This is part of a bigger shift for me. Instead of just talking about AI and agents, I wanted to actually build with them and see where the real value is.

More experiments coming. What's working for you?

[Ben Cpnd @ben_cpnd]

@Anthony_Francis Looking forward to this 👀

[Ben Cpnd @ben_cpnd]

@Jacobsklug Currently doing it with @braille_studio, happy to have a talk!

[Ben Cpnd @ben_cpnd]

Your brand is your first UX.

Before anyone uses your product, they experience your brand. Website, messaging, visuals. That's the first interaction.

Most teams treat it as an afterthought.

Here's what I keep seeing in Web3 and AI:
🧩 The tone of voice changes at every touchpoint, docs, socials, and product all sound like different companies
🎨 No clear positioning, so every investor, partner, or user gets a slightly different story
💬 The pitch deck tells a great story but the website tells a different one
📉 The product has traction but the brand still looks like a hackathon project

The result? People bounce before they even try the product. Not because it's bad. Because the brand didn't earn enough trust to get them through the door.

Here's how I think about it:

1. One voice across every touchpoint
Create a simple tone guide and make it the default for anyone who writes, designs, or ships anything public. Consistency builds trust faster than any redesign.

2. Positioning before visuals
If you can't explain who you're for and why it matters in one sentence, no logo or color palette will save you.

3. Your website has to match your best pitch
If someone can sell the product perfectly in a meeting but the website can't, the brand isn't doing its job.

4. Your brand has to keep up with your product
A brand that matched at pre-seed can hold you back at Series A. If the product grew but the brand didn't, people feel it.

This is why we built the Signal Package at @braille_studio. Full rebrand and website in one sprint. Positioning, messaging, visual identity, and a full fledged website ready to go live.

Because shipping a great product with a weak brand is like writing something brilliant that nobody can read.

DMs open.

[Ben Cpnd @ben_cpnd]

@mbaril010 @OctavFi 🔥🤝

[Ben Cpnd @ben_cpnd]

Tight sprint, fast feedback loops, clean execution.

Shipped a full website rebuild for @OctavFi in time for Devconnect.
From Figma to Framer, aligned with their new brand and core offerings.

Big thanks to @mbaril010 and the team for the trust.
If you need branding or a website that actually ships, happy to chat.

[Braille Studio @braille_studio]

.@OctavFi had a new brand but an outdated website, with only three weeks until Devconnect 2025.

They reached out to rebuild their site around the new branding and two core offerings: Octav Pro & Octav API.

We redesigned from scratch in Figma, then built the full site in Framer.

The new website was shipped on time, ready for a successful event!

"Braille onboarded quickly, executed cleanly, and delivered a result that gave us confidence going into the event." — @mbaril010 , CEO & Co-Founder

[Ben Cpnd @ben_cpnd]

@WatanabeSota Congrats on this launch guys!

[Ben Cpnd @ben_cpnd]

@braille_studio This is why at @braille_studio we built MVP Ready: a 2-week sprint to design, build, and launch a functional MVP. Strategy, key flows, core integrations. Something you can demo, ship, and iterate on.

DM me if you want the sprint structure.

[Ben Cpnd @ben_cpnd]

Most “MVPs” fail for one boring reason: they are not actually MVPs.

They are usually:
– a feature soup that never ships
– a pretty prototype with no real usage
– a technical demo with no product story
– a product missing the one flow that matters

🧵

[Ben Cpnd @ben_cpnd]

@braille_studio 4) A story that matches the product
Clear product with weak narrative kills conversion.
Strong narrative with confusing product kills retention.

[Alex Houdz 🍉 @houdz_kek]

"Every successful product requires product management."

Product management is about orchestrating all the expertise into features that users love.

It's also about understanding your audience, show empathy, going farther than what your users expect.

That's what outstanding user experience is about, and how you win against competition.

I think this part is still one of the few areas where AI haven't done great yet.

With YC calling for startups on this topic will change that.

That's exciting. We'll have more time and energy to experiment about other features.