Ex-Silicon Valley CTO → Solo Founder Building in AI, software & startups 10+ years engineering
Digital Nomad
Joined February 2025
- Tweets12.8K
- Following1.1K
- Followers1.6K
- Likes28.1K
Pinned Tweet
I'm Bruno. 29.
I've spent 10+ years in engineering and 7+ years building companies
I've been an engineer, founding engineer, CTO, and founder
I've built products, hired teams, made expensive mistakes, helped companies grow, and learned a lot along the way
Now I'm a solo founder building in AI infrastructure
On X, I talk about:
→ Building startups
→ AI & engineering
→ Sales & marketing
→ Founder mindset
→ Lessons nobody teaches you
I'm here to build, learn, and have fun doing it
If you're interested in AI, let's connect
Don't give up on an idea just because nobody is buying
First, figure out WHY
My rule of thumb: 30 genuine conversations with potential customers. Zero conversions? Time to rethink
Before quitting:
- People objecting? Can you fix the problem?
- Pitch not working? Ask experts for feedback. People are often more willing to help than to buy
- Nobody responding? You might be talking to the wrong people. Find allies inside the company
Remember:
0 conversations = distribution problem
30 conversations, 0 sales = potentially a product positioning, or urgency problem
Learn to tell the difference before spending another 6 months building something nobody wants
6
5
181
Make money in tech while you still can
The next 5 ~ 10 years could be hard for tech workers
Big techs are coming for entire markets
Don't assume your current skills will protect your future
Build assets
Own products
Get equity
Please, don't just sell your time
There might not be much time left
11
17
215
One week away from X
Almost 20 followers gone
Impressions dropped
Engagement slowed down
After a full year of showing up every single day, I took one week off
The lesson is the same:
Consistency compounds, but momentum can go away insanely quick
Back to building 🤝
40
51
1,064
₿runo retweeted
Vibecoders, 𝗜'𝗺 𝗯𝗲𝗴𝗴𝗶𝗻𝗴 𝘆𝗼𝘂, open your messiest project and paste this into Claude Code or Codex:
"Find all of the implicit state machines in my app. Make the best decision that will elevate all three: the user experience (UX), developer experience (DX), and agent experience (AX) always, without breaking anything."
Found a repository to test your business before you launch it
Perfect for my solo founders friends
First comment 👇
11
16
281
In 2002, Ray Kurzweil predicted we'd have full dive VR by 2029
A world where you can't tell if it's simulation or reality
We're 3 years away.
Or are we still 3 decades away?
🤖 Made with AI
5
10
166
My friend with a side project and a "stable" job:
"I know how you're feeling"
Me who quit my job to start a startup:
"No, you don't"
Or do they ??
22
24
530
There's no bigger shame than looking down on someone because you make more money than them
Recently, I met a guy whose company makes around $50k/month
Rude, disrespectful, acting like he's above everyone else
I've seen my own company hit $250k MRR. That doesn't make me better than anyone
I've never judged someone by how much money they make or how many followers they have
STAY HUMBLE
Not everyone is here to lick your balls, mate
₿runo retweeted
Most MCP servers are just API endpoints wrapped as AI tools.
And that's probably why some agents waste so many calls getting simple work done.
If you're building an MCP server, here are 6 things worth thinking about:
1. Build tools around actual tasks. If an agent needs five API calls to investigate a failed payment, consider giving it one tool that gathers the relevant information. Let the server handle the predictable steps.
2. Don't make the model do your database's job. If you're returning thousands of records so the agent can find five matches, move that filtering into the tool. Return the matches and enough context to explain them.
3. Give the agent a way to investigate further. A summary is useful, but it shouldn't hide where the answer came from. Include relevant IDs, timestamps and references so the agent can inspect the original records.
4. Make failures recoverable. If a payment lookup fails because an invoice ID is missing, say exactly what's missing. Give the agent enough information to retry correctly instead of guessing.
5. Keep dangerous actions separate. Investigating a failed payment and issuing a refund shouldn't be the same operation. Let the agent investigate freely within its permissions, but enforce authorization and approval for sensitive actions.
6. Study what your agents actually do. Look at their tool-call traces. Where are they repeating searches, passing invalid parameters or fetching the same information multiple times? Those patterns tell you where your MCP design needs work.
Here's an experiment worth trying:
Take 20 real tasks from your agent's workflow and record the tool calls needed to complete each one.
Find one sequence of 3–5 calls that keeps repeating.
Build a new MCP tool that handles the predictable parts of that sequence internally.
Now run the same tasks using the original tools and your new implementation.
Compare:
- How many tasks were completed correctly?
- How many agent-level tool calls were needed?
- How much context did the tool responses consume?
- How long did the tasks take?
If the new tool achieves the same or better results with fewer calls and less context, you've found a useful optimization.
The interesting part of MCP engineering is deciding which work belongs inside a deterministic tool and which decisions actually need the model.
What can AI copy today?
Wrong question!
If you're building a company, you should be thinking 5 years ahead
What will the world look like in 2031?
What will AI be able to do that it can't do today?
What will still be valuable?
Build for the future, not the present
12
16
157
I'm not a native English speaker
I use AI to shape my posts. The ideas and first drafts are always mine. Replies are 100% me, no AI.
"I would have written a shorter letter, but I did not have the time" (Pascal)
Nowadays we don't have time to make everything shorter and more polished
Do you use AI to write ??
9
12
283
In 2021, everyone wanted to build a unicorn in 6 months
Today, those who survived the hype understand:
Building a great company takes years!
You'll make mistakes, nearly go broke, and make bad decisions
The advantage is staying in the game, alive
17
23
375
Your prospects can smell a template
Personalize as much as you can, not just the name
I saw the difference in reply numbers firsthand during my last validation cycle
It heavily depends on the product/service you're offering
But usually....
Relevance beats volume
19
23
509
Nothing sells itself
Do this:
> Talk about the pain you solve
> Show how much money or time you save
> Share proof that your product works
> Let your customers tell the story, promote it
> Show how easy it is to get the result
What would you add ??
21
25
606