Technical leadership
Product teams of 5 to 15 people: technical roadmap, code review, mentorship, hiring, standards. The operational target is a team that ships better each quarter.
Juanklagos
Software. Architecture. Strategy.
Ten years turning founder ideas into real platforms. CTO at Praxis Studio, founder of independent products. Also put together an open-source guide for applying Spec-Driven Development with AI.
Author of "Solo con IA (…hasta cierto punto)". Open-source guide for applying SDD with AI.
Let's talk about your project
The inflection point
"Solo with AI, up to a point."
With today's tools a founder can go much further alone than five years ago. AI, no-code, modern stacks — the first product ships, the first customers come in. Good. Up to a point.
That point has a face: the team starts growing and every change breaks something. Decisions nobody documented come back as problems. What you built to validate doesn't hold what's coming. And AI, used without judgment, speeds up the chaos instead of fixing it.
That's when it makes sense to talk. Not at the first MVP — when it already works and you need it to last.
What I do
A typical week mixes these areas in different proportions depending on where the product is.
Software architecture
Multi-tenant SaaS architectures, microservices, REST APIs, per-tenant isolation. Design oriented toward systems built for three years, not the next sprint.
Technical strategy and decision-making
Active participation in product and business meetings. Translation between architecture and outcomes. Decisions documented so they outlive the team that made them.
AI applied with judgment
AI and automation integrated according to the decision matrix published in "Solo con IA": what to automate, what to delegate to a model, what to keep human. No cult, no experimental spend.
Infrastructure and deployment
AWS administration, Docker containerization, traceable CI/CD. Infrastructure that scales by configuration and not by rewrite.
Sustained partnership
Continuity as part of the work, not an extra. Code review, product, hiring, and the 2 AM rollout — a technical right hand that stays for as long as it is needed.
How I work
Three stages that structure any project. The full discipline is published — available before we even talk.
- 01
Clarify
Before implementation: definition of what success looks like, what the system has to do, and which decisions are being made explicitly. Approved specs, traceable plan, documented gates. The team and the business see the same picture.
- 02
Architect
Design oriented toward the company that will exist in three years, not the one that exists today. Multi-tenant, microservices, infrastructure that scales by configuration. Automation where it compounds, AI where it is measurable.
- 03
Build and evolve
Hands-on implementation. Serious code review. Real mentorship inside the team. The exit from the role is conditioned on a team capable of sustaining and evolving without dependency — the implicit guarantee in every engagement.
PORTFOLIO
All work →
What I've built
01 
Praxis Studio
Leading Spanish-language online medical education platform. 80,000+ active specialists across 138+ countries. Video courses, weekly live classes, and a digital library in one place.
ROLE
CTO · Architecture · Full-Stack · Infrastructure
SPECIALISTS
+80K
+138 countries
Read full case →
02 
Ruletaxpress
Gamification SaaS that converts contact lists into immediate sales. Spin-to-win campaigns, campaign editor, email automations, and an embeddable widget for any platform.
CONVERSION
+3%
of the list into immediate sales
CTO · Architecture · Full-Stack
Read full case →
03 
CRM Xell
In-house CRM for lead management and sales pipelines. Architecture design, end-to-end development, API integrations, and a real-time Kanban for sales teams.
SYNC
Real-time
Architecture · Backend · Frontend
Read full case →
04 
American Fest
Web platform for Cucuta's largest multidisciplinary festival. 180,000 attendees, 5 days, 3 stages, and 37+ activities. Design, development, and digital experience for the 4th edition.
ATTENDEES
180K
Web Development · Frontend · UX
Read full case →
Engineering with purpose,
architecture with judgment.
Ten years building systems that run in production. CTO at Praxis Studio, founder of independent products. The work lives at the intersection of code and the business decisions that make it necessary.
CTO · Tech Lead Multi-Tenant SaaS AI applied Spec-Driven Dev
Working philosophy
Clarity before code
Implementing without a spec is expensive rework. Every engagement starts by defining what success looks like, what the system has to do, and which decisions are being made explicitly.
Measurable impact
Code is a means. The right question is not how many lines were written — it's what changed in the business after the system went live.
Systems that last
The exit from the role is conditioned on a team capable of sustaining and evolving without dependency. The goal is to make one's own work redundant — that is the signal of success.
Track record
Most recent roles. Full CV available if you need it.
-
Jan 2022 — Present · Remote
CTO
Praxis Studio SAS
Defining and leading the company's technical strategy. End-to-end design and build of multi-tenant SaaS platforms and microservices architectures. AWS administration and leadership of frontend, backend, and infrastructure teams of up to 5 people.
-
Jun 2020 — 2023 · Remote
Tech Lead
Cuemby Inc
Technical leadership on high-impact projects. Coordinating teams of up to 5 developers, technical evaluations, defining solutions under Scrum/Agile.
By the numbers
A decade, distilled.
- 0 +
years of work
- 0 +
companies as CTO, Tech Lead, or Full-Stack engineer
- 0
people in the largest team led
- 0
frameworks published (book and open source)
From the book
Readings from "Solo con IA"
-
AI is power. Used well, it multiplies. Used badly, it slows you down.
— Solo con IA · The promise and the cost -
The right question is not "what can I do with AI?". It is "what should I do myself, what delegate, and when?".
— Solo con IA · The decision matrix -
Clarity before execution. Speed without structure is just expensive rework.
— Solo con IA · The operating principle
Published
Open work. What I use with clients, published so you can see it before we talk.
Book
Solo con IA (…hasta cierto punto)
Decision framework for founders: what to build alone, what to accelerate with AI, when to bring specialized help. The thesis describes the exact moment a team needs a senior technical profile — and why.
Read the book → Open-source framework
Spec-Driven Development Template
Operational discipline applied in every engagement, fully published: GitHub Spec Kit workflows, MCP support, approval gates. Public for review before, during, and after the joint work.
- 10 stars
- 1 forks
Let's talk about your project
Contact
If your product works and needs to scale, or your engineering team needs direction — that's what I do. Tell me about it.
hello@juanklagos.devWorking remotely