Sergio Lozano

AI engineer, building Nobs with @rmahamudg 🛠️ Two of us shipping AI agents,
automations and internal tools into production. Posting whascratch | #BuildInPublic

[Sergio Lozano @sergioforfun]

@alvarombt a veces no tienes opción por ejemplo dentro un iframe

[Sergio Lozano @sergioforfun]

cloud is for burst.
local is for secrets.

if your competitor’s docs never leave their LAN
and yours live in a SaaS chat log…
that’s the moat.

[Sergio Lozano @sergioforfun]

your company can run serious AI on one desk machine.

no GPU cluster.

no data leaving the building.

the 2026 shopping list is shorter than you think ↓

[Sergio Lozano @sergioforfun]

weekend path (no lab required):

1. buy the box for the job above
2. Ollama if it’s mostly you. vLLM if the team piles on
3. put the API behind your VPN
4. start 30B–70B quant. scale when someone’s actually waiting

[Sergio Lozano @sergioforfun]

early looks like failure if you’re measuring against the finished product. most of the first two years is shipping to almost nobody and still showing up.

[Boardy @boardyai]

don't give up

stripe had 50 users in the first 2 years

[Sergio Lozano @sergioforfun]

that’s it.
less theatre. more production.

[Sergio Lozano @sergioforfun]

i ship AI systems into production with a tiny team.

if your engineers are already full and the roadmap keeps growing, this is my honest advice:

[Sergio Lozano @sergioforfun]

6) start with the one thing that isn’t getting built

not “ai strategy.”
the concrete initiative stuck because you don’t have seats.

name it. scope it. ship it in *your* repo, behind *your* review — or consciously kill it.

[Sergio Lozano @sergioforfun]

monday. staring at a sheet tab labeled DO NOT TOUCH.

not sacred. just whoever named it already lost that fight once.

[Sergio Lozano @sergioforfun]

@lewislovelock Cofounder from Spain here lets connect!

[Sergio Lozano @sergioforfun]

AI generates a huge amount of code, and now the bottleneck is reviewing it.

So we’re also trying to automate the review with AI.

But a code review isn’t just for deciding whether the code is good or bad.
It also helps people learn, share knowledge about a feature, or teach a junior.

I’m worried we’ll automate that part without thinking about how we’re going to keep all the rest.

[Sergio Lozano @sergioforfun]

A decision made in slack six months ago is effectively lost.
then someone rebuilds the same thing because they can’t find the first one.
that’s not a culture problem. that’s missing search over your own work.