About Tech Fundamentals
I’m a software engineer as well as tech founder (SaaS & web dev agency) who spends most days inside modern tech stacks. I build products, ship software, integrate AI into real workflows, and deal with the boring parts that rarely make it into investor decks: costs, dependencies, scaling issues, and things quietly breaking under load.
I also invest.
That combination shapes how I look at tech companies, AI startups, and crypto protocols. Not as tickers or hype cycles, but as products with incentives, constraints, and failure modes.
What this publication is about
Most tech investment mistakes don’t come from missing information.
They come from misreading systems.
At Tech Fundamentals, I focus on questions like:
Where is value actually created in this system?
Who controls the cost curve as usage scales?
What looks like a moat but is really a dependency?
What breaks when growth stops being subsidized?
Why do some impressive products fail to compound?
A lot of modern tech, especially in AI, looks powerful on the surface while quietly outsourcing its economics. Many “AI-native” products are wrappers on top of providers like OpenAI, Google, or Microsoft. That doesn’t make them useless, but it does change who really owns the upside.
The same lens applies to cloud platforms, SaaS companies, and crypto protocols.
What you’ll read here
AI as infrastructure, not magic software
Hidden cost structures behind “AI-native” products
Why wrapper businesses often look better than they are
How architecture decisions show up in margins years later
Crypto protocols as software systems with incentives and limits
Survivorship bias in tech winners and why it misleads investors
This isn’t about predicting prices or chasing the next breakout. It’s about understanding why some businesses quietly disappoint while others survive multiple technology resets.
Who this is for
Engineers and founders who invest
Investors who want technical clarity without hype
Crypto-native readers tired of narrative-only analysis
Curious non-technical investors who want honest explanations
You don’t need to be deeply technical to read this, but the thinking comes from working with these systems every day.
