CTO & Product Engineer — Massimo De Luisa

About me

Builder, CTO, technologist.

CTO of two software companies: one mobile, one systems integration. I build platforms, mobile apps, and AI-assisted workflows that stay simple under pressure.

I architect backends powered by NestJS with Typesense, Sequin, Redis and Deno; persist data through Supabase; automate workflows with n8n; ship Vue +Tailwind to Vercel powered by Turborepo monorepos; build native experiences with Expo; and orchestrate AI through the AI SDK, OpenAI, Google Vertex and Replicate, so teams move fast without losing clarity or craft.

Product Engineering

From a messy idea to something shipped

I turn constraints into platforms a team can still maintain a year later.

Technical Leadership

CTO thinking with maker speed

Architecture, delivery risk, and product detail. Same conversation, not three decks.

AI Systems

Long-context agents & tooling

Practical AI on large codebases and document piles. Not a demo.

Professional profile

What I build, what I lead, what I am still figuring out.

I am Massimo De Luisa. CTO and product engineer in Udine, Italy. I lead tech for two software companies: mobile, and systems integration. I still write the code. Platforms, mobile apps, AI-assisted workflows. Same point every time: keep the important decisions explicit, and ship something that still makes sense after launch.

Core areas of work

Platform architecture
Backend boundaries, data flows, integrations, deploys. Designed around the product you actually have, not a whiteboard.
Product engineering
From a rough idea and a deadline to a web product the team can keep changing without fear.
Mobile development
Native apps with Expo, wired to services people can actually run a business on.
AI-assisted systems
Agents, model wiring, long-context tools. Useful on real repos and real documents.
Technical leadership
Architecture, delivery risk, product detail. One job, not a relay race.

Key facts

Facts about my professional profile
Fact	Detail
Role	CTO and Product Engineer
Leadership	CTO of two software companies in mobile development and systems integration
Focus	Platforms, mobile applications, product engineering, and AI-assisted workflows
Core stack	Vue, TypeScript, Tailwind CSS, Supabase, Expo, and modern AI tooling
Based in	Udine, Italy, with a planned move to Japan
Site languages	English, Italian, Japanese, Russian, and Ukrainian

Questions about my work

What do I do?

I am CTO and product engineer for two software companies: mobile, and systems integration. Architecture, product calls, delivery, and I still implement. I do not split “strategy” from the repo. If an assumption is wrong, I want to feel it in the product.

What kinds of systems do I build?

Platforms, web products, mobile apps, integrations, AI-assisted ops. They have to stay understandable while the calendar is on fire. I would rather ship a boring foundation a team can extend than a clever abstraction nobody wants to touch.

Which technologies are part of my core stack?

Day to day: Vue, TypeScript, Tailwind, Supabase, Expo, Vercel, Turborepo. Backends may include NestJS, Typesense, Redis, Deno, n8n. AI work uses the AI SDK, OpenAI, Vertex, Replicate. I do not collect tools. I pick what keeps delivery fast and the system coherent.

How do I approach technical leadership?

Architecture, delivery risk, and product detail are the same decision. I work as CTO and stay close enough to the code to see where a plan gets fragile. Trade-offs get named. Boundaries have to be ones a team can keep. New tech gets tried before it becomes a bet.

How do I use AI in software and product work?

AI goes inside a real workflow, or it does not go in. I care about long-context agents, reusable skills, recursive decomposition, and tools for big repos and document sets. Models can chew the repetitive part. Scope and quality stay human. If the process is unclear, automation just hides it.

What work am I available for?

Focused work: technical leadership, platform architecture, AI-assisted product. Start with a concrete problem. An architecture that needs a direction, a platform getting opaque, a mobile foundation that is wobbly, an AI workflow that has to become reliable. 30-minute calls, limited on purpose. I usually reply within 24 hours.