STKR News0 of 3 free this monthA founder's look at the hidden costs of AI productivity, the friction of leadership transitions, and how to negotiate for things that actually matter in a builder's career.
Originally on Lenny's Newsletter →Adrian Boysel
Contributor
Oct 3, 2026
4 min read
Photo illustration / STKR News
We are currently obsessed with the idea of a digital second brain. The promise is simple: give an AI access to your emails, your calendar, and your Slack logs, and it will magically organize your life. But as someone who has spent years building and breaking systems, I see a massive red flag that most founders are ignoring. We are trading long-term data sovereignty for short-term convenience.
When you plug a personal AI agent into your primary communication channels, you aren't just giving it permission to read your mail. You are feeding your proprietary network, your unique tone of voice, and your internal decision-making frameworks into a black box. For builders, your process is your edge. If you outsource the synthesis of your day-to-day work to a third-party model, you risk losing the mental muscle memory that makes you effective in the first place.
Instead of full integration, the smart move is compartmentalization. Use these agents for specific, bounded tasks—like summarizing a long research paper or drafting a generic meeting agenda—without granting them access to the sensitive 'central nervous system' of your business. If the AI needs to see your inbox to be useful, it’s probably not the AI you should be using yet.
There is a specific kind of grief that comes with moving from an individual contributor role into management. In the crypto and AI space, we value the 'doers.' We celebrate the person who pushes the code or closes the high-stakes partnership. When you become a manager, your output becomes invisible. You no longer have a tangible 'thing' to show for your eight hours of work.
This shift often triggers an ego crisis. You feel like a fraud because you spent all day in meetings and didn't 'build' anything. But here is the reality: your new job is to build the machine that builds the product. If you try to keep one foot in the trenches by micromanaging technical tasks, you will fail at both. You have to be okay with not being the smartest person in the room anymore.
For founders scaling their first teams, this is the hardest hurdle. The transition requires a total recalibration of how you measure self-worth. You have to learn to find satisfaction in the success of others, which is a lot harder than it sounds when you’re used to the dopamine hit of a successful deployment.
When most people think about job perks, they think about healthcare, equity, and salary. Those are the basics. But if you are a high-level builder, you should be negotiating for things that increase your long-term leverage. I’ve seen developers and product leads get stuck in golden handcuffs because they didn't negotiate for the right kind of freedom.
One uncommon perk to consider is the 'education and experimentation' budget. This isn't just for taking a coding course. It’s a dedicated fund to buy hardware, run experiments on new protocols, or attend niche technical summits that the HR department hasn't heard of yet. In a fast-moving field like AI, the ability to stay on the cutting edge on the company’s dime is worth more than a 5% salary bump.
Another overlooked lever is the 'external output' clause. Many employment contracts are incredibly restrictive about what you can build or speak about outside of work. If you are a founder-type, you need to carve out space to contribute to open-source projects or maintain your own technical brand. If the company owns every thought you have for 40 hours a week, you are losing equity in yourself.
There is a growing trend in the ecosystem where tools are marketed as free or low-cost in exchange for 'training data.' This is a trap for builders. If you are building a startup, your data is your moat. Giving it away to a tool provider in exchange for a slightly better UI is a bad trade.
We need to start looking at our tech stacks through the lens of privacy-first architecture. This means favoring local LLMs over cloud-based ones when dealing with sensitive IP, and being extremely selective about which browser extensions and 'productivity' plugins we install. The convenience of a one-click integration is rarely worth the long-term risk of data leakage.
The common thread in all these challenges is the tension between short-term speed and long-term sustainability. Whether it’s managing your data, your team, or your career, the temptation is always to take the path of least resistance. But builders who last are the ones who are willing to deal with a little bit of friction now to avoid a total collapse later.
Don't let the hype of the current AI cycle rush you into bad decisions. If a tool feels too invasive, it probably is. If a promotion feels like it’s killing your creativity, it might be the wrong role for you. And if a contract feels like it’s boxing you in, it’s time to push back.
Read the original at Lenny's Newsletter →
A six-minute morning dispatch on the markets and the technology shaping them.
Free. No spam. Unsubscribe anytime.
Earn $STKR for published stories on markets, protocols, and culture.
Comments
24 reader responses
