Change & Scale Try D4S (free) →
EN · ES

About the author

I'm Daniel Picatto. I work at the intersection where the technical hits the business.

With founders, CTOs and engineering teams. I don't replace them. I don't teach them process. I create the conditions for them to reach the conclusions on their own — the result is theirs, that's why it lasts.

Honey badger as senior operator, takeaway coffee in hand
The Operator. Caretaker of margins, slayer of vanity roadmaps.

The verifiable trifecta

Over 20 years working with technology, the last eight as Solutions Architect & DevOps in production. Advertising (UCES 2009), MBA (ESEADE 2018). Five years of marketing and sales consulting before pivoting to tech. That means I understand how the CEO and the board think, not just how the CTO thinks. Almost no one in DevOps has an MBA. Almost no one with an MBA has Advertising. The intersection is practically empty in Spanish-speaking markets — and it's exactly where technical-business decisions get stuck.

Credentials, for the people who care about them: AWS Solutions Architect, seven GitLab certifications, Red Hat OpenShift, AISA certified by ELVTR (December 2025), plus coursework at University of Chicago (2022). The work is what matters.

What I'm not

I'm not a fractional CTO — a fractional CTO operates, writes the roadmap, hires, replaces. I don't operate.

I'm not an agile coach — Scrum/SAFe certificates teach process for teams of 30+. At Seed–Series B that's rarely the problem.

I'm not a coach — the category is burned by generic ICF life-coaches. I don't do 1:1 personal development.

I'm not a consultant — consultants diagnose and impose. The team doesn't take ownership. I work differently: I create the space where the team finds the answer on its own, and it stays.

Where I've been

Senior Solutions Architect at knowmad mood. Senior DevOps Consultant at Hubbing LATAM (freelance, 2021–2024). Senior DevOps Manager - Solutions Architect at GoJiraf. DevOp at ClicOh. DevOps Contractor at Red Hat / OpenShift. Solutions Architect on the Birjam lottery platform, where the job was keeping 99.95% uptime through 40× traffic spikes on draw nights — every hour of downtime ran around $15K. The cases I write about most often are ClicOh, GoJiraf and the Hubbing engagements — that's where the lessons that became D4S got tested.

I'm not a CTO. Never was.

I write from the seat next to the CTO — the DevOps lead in the room when the call is being defended, not the executive making it. The cases I cite (ClicOh, GoJiraf, the Hubbing engagements, Birjam) are real work where I was an employee or contractor.

I write because there isn't enough content out there that treats technical-business decisions as what they are: business decisions with a heavy technical component. The rest we discuss on a call.