Roberto Drago · Italy Product / People / Systems

I lead ideas
from ambiguity
to shipped systems.

Software architect, product builder and technical leader. I move between strategy, system design, infrastructure and hands-on delivery—turning complex products into something teams can understand, build and run.

Software ArchitectLead DeveloperProduct BuilderTechnical Leader

01 / Core experience

The Wave is where range became a leadership system.

The WavePrimary experience

I operate where product decisions, people and technical systems meet.

Across a broad portfolio of client products, internal platforms, AI initiatives and team foundations, I translate business ambiguity into architecture, delivery plans and working software. My range is practical: I can hold the client conversation, shape the system, unblock the team and stay with the work through release.

“The role changes with the problem. Ownership does not.”
01

Frame

Turn needs, constraints and weak signals into a product direction people can make decisions around.

02

Architect

Choose boundaries, data flows and infrastructure with delivery reality—not diagram elegance—as the test.

03

Lead

Create clarity, standards and feedback loops that let developers grow while the product keeps moving.

04

Ship

Own the last mile: migrations, environments, security, release gates and the operational handoff.

Range in practice

One leader, multiple altitudes.

Client roomProduct modelArchitecture

Hands-on buildTeam systemProduction

React / Next.jsVue / NuxtAngularNestJS / NodeReact Native / ExpoSupabase / PostgreSQLStrapiDockerVercel / CloudflareAzure / MSALAI / RAG

02 / Selected systems

Products, platforms and bets—built across the stack.

A curated map of current and recent work. Delivered products, internal systems and venture theses are intentionally separated by status.

Filter projects

10 systems

01Platform delivery

Vertical SaaS · multi-product ecosystem

A salon operating platform spanning a public marketplace, a B2B workspace and a superadmin product inside one coherent system.

The challenge

Make three products evolve independently without fragmenting data, identity, environments or the customer journey.

What I owned

I shaped the monorepo and deployment boundaries, pre-launch funnel, consent and email flows, multilingual routing, fiscal-readiness path and production handoff.

Next.jsTypeScriptTurborepoSupabaseVercelResendPostHog
System & outcome
System built

Three separately deployed Next.js applications, shared Supabase foundations, explicit environment ownership, transactional communications and observable acquisition flows.

Outcome

A platform structure that can move from validation to commercial operations without rebuilding its delivery model.

02Release engineering

Consumer mobile · marketplace operations

MatchRoom

View live

A social mobile marketplace for finding people, spaces and opportunities—engineered through backend recovery, safety hardening and launch operations.

The challenge

Move a feature-rich mobile product toward release while closing the less visible gaps across data integrity, trust, legal surfaces and real-world operations.

What I owned

I led targeted Supabase repair, RLS and safety controls, blocking and reporting, self-deletion, Edge Function delivery, landing persistence and the launch operating model.

React NativeExpoSupabasePostgreSQLEASSentry
System & outcome
System built

Expo application, Postgres and Supabase services, auth-bound deletion, moderation boundaries, release checks, observability and a production lead funnel.

Outcome

A clearer and safer path to store submission, with code readiness separated from legal, account and operational gates.

03Product engineering

Hospitality · multilingual lead platform

Ionian Experience

View live

A multilingual hospitality platform that turns destination storytelling into qualified enquiries while keeping operational data protected.

The challenge

Create a premium public experience without weakening the privacy boundary between an open contact flow and the internal lead database.

What I owned

I traced and rebuilt the submission path across validation, APIs, email and database policies, then secured server-side writes without exposing CRM reads.

Next.jsTypeScriptSupabaseRLSResendnext-intl
System & outcome
System built

Next.js internationalized frontend, server APIs, Supabase RLS, service-bound lead capture, transactional email and GDPR-oriented data flows.

Outcome

A production-facing commercial surface whose public forms can operate safely across five languages.

04Built MVP

Cross-platform media · event experience

Gran Finale

A creator-paid party experience where guests capture private prompted clips and receive a delayed, automatically edited film.

The challenge

Make an emotionally simple guest experience work across identity, private media, asynchronous rendering, payments and an event-day operating reality.

What I owned

I designed the product end to end: party entry, anonymous-to-creator identity, sealed media permissions, rendering workers, payments, notifications and retention.

ExpoReact NativeSupabaseFFmpegStripeDocker
System & outcome
System built

Expo clients, Supabase permissions and storage, FFmpeg workers, Stripe payments, notifications and a manual fallback for pilot operations.

Outcome

A pilot-ready cross-platform product with the privacy and release boundaries required for creator-paid events.

05Venture design

B2B fintech · construction operations

SAL Zero

A revenue-protection thesis for construction subcontractors, designed around the gap between work executed, documented, billable and collected.

The challenge

Prove whether revenue leakage is painful and frequent enough to justify software before over-investing in OCR, AI and construction integrations.

What I owned

I developed the ICP, competitive framing, service-first validation model, economics, technical boundaries and explicit invest-or-stop rules.

NestJSPostgreSQLObject storageOCRLLMEvent workers
System & outcome
System built

A Billability Engine connecting field evidence to contractual items, with an Evidence Graph, human approval and auditable asynchronous processing.

Outcome

A decision-ready venture thesis that protects capital by making commercial validation precede full automation.

06Internal platform

Standards · tooling · organisational leverage

The Wave Delivery OS

A connected internal operating system for repeatable delivery: project protocols, documentation flows, AI-assisted workflows and reusable engineering foundations.

The challenge

Turn expert knowledge that usually stays in people’s heads into a system teams can apply consistently across different clients and stacks.

What I owned

I translated delivery practice into operating rules, technical templates, onboarding surfaces, decision frameworks, automations and quality gates.

TypeScriptNext.jsNestJSAI workflowsCI/CDDocs
System & outcome
System built

A modular layer of documentation standards, reusable project foundations, AI workflows, delivery tools and CI/CD conventions.

Outcome

Less reinvention between projects and a stronger shared language for scope, architecture, quality and handover.

07Shipped experiment

Interaction design · playful commerce

Boost Mart

A deliberately high-energy commerce experiment exploring reward loops, micro-games and a tactile, character-led interface.

The challenge

Test how far an intentionally dopamine-forward interaction language can go while remaining coherent, responsive and technically shippable.

What I owned

I shaped the product concept, interaction system and release boundary, isolating it from the larger personal-brand workspace as a standalone application.

Next.jsReactTypeScriptGame loopsResponsive UI
System & outcome
System built

A responsive Next.js product combining commerce UI, animated feedback, game loops and lightweight arcade interactions.

Outcome

A deployable product experiment that treats play as a product mechanic rather than surface decoration.

08Local-first system

Personal operations · source-of-truth design

Casa OS

A local life-admin register where readable Markdown remains the durable source and generated summaries and dashboards stay disposable.

The challenge

Make household payments, instalments and deadlines queryable and date-aware without trapping personal records inside an opaque application.

What I owned

I designed the information architecture, record model, natural-language operations, validation pipeline and strict source-versus-generated boundaries.

PythonMarkdownHTMLValidationLocal-first
System & outcome
System built

Human-readable Markdown records, Python validation and generation, and a browser dashboard that calculates recurring and upcoming obligations.

Outcome

A maintainable personal operating system whose source data stays portable, inspectable and independent of its views.

09Live product

Private reflection · phone-first PWA

An immersive private journal for noticing the gestures, silences and fragments through which people—and we ourselves—communicate.

The challenge

Translate a poetic, atmospheric concept into an installable experience without turning intimate observations into cloud data or analytics.

What I owned

I carried the original visual language into a real product, designing the mobile flow, ambient motion, clue model, privacy controls and offline behaviour.

ReactTypeScriptVitePWALocal storageOffline
System & outcome
System built

A phone-first React PWA with local-only persistence, installable offline support and explicit JSON export, import and deletion controls.

Outcome

A live, coherent product in which the privacy architecture reinforces the emotional premise: the user keeps the only key.

10Closed-beta build

Creator platform · art community

Fabbrichiere

A curated platform where Italian visual artists can publish portfolios, exchange meaningful feedback and prepare their work for future commerce.

The challenge

Unify portfolio, community and monetisation without reproducing the noise of global social platforms or exposing print-quality originals.

What I owned

I designed and built the closed-beta foundation: product model, artist workflows, auth, data and storage policies, social interactions, admin controls and phased commerce architecture.

Next.jsReactTypeScriptSupabaseRLSStripe
System & outcome
System built

Next.js and Supabase across artist profiles, artwork discovery, private originals, RLS, feedback loops and a future Printful and Stripe operating model.

Outcome

A working invite-only foundation that can validate community value before activating the heavier commerce and fulfilment layer.

03 / Capability map

Deep enough to build.Broad enough to lead.

My edge is not knowing a long list of tools. It is knowing which layer is constraining the product—and being able to work there.

01

Direction

Product discovery, scope design, technical due diligence, roadmap pressure-testing and client-to-team translation.

02

Architecture

System boundaries, monorepos, data models, APIs, RLS, asynchronous workflows and infrastructure decisions that survive growth.

03

Hands-on build

TypeScript, JavaScript, Python, SQL and Swift across React, Next, Vue, Nuxt, Angular, NestJS and React Native.

04

Infrastructure

Supabase, PostgreSQL, Vercel, Cloudflare, Docker, object storage, CI/CD, observability and production release controls.

05

Applied AI

RAG, evidence-grounded generation, prompt architecture, CMS-integrated AI, evaluation boundaries and anti-hallucination guardrails.

06

Leadership

Team enablement, reviews, standards, hiring exercises, career frameworks, facilitation and calm ownership under ambiguity.

Languages & environments

Technology is a medium, not an identity.

I choose the stack around product constraints, team capability and operating cost—then go deep enough to make it real.

TypeScriptJavaScriptPythonSQLSwiftHTML / CSSBashPostgreSQLNode.jsReact Native

04 / How I lead

Calm systems.High standards.

Leadership, to me, is the craft of making good decisions easier for the people around you—especially when the context is messy.

01

Reduce ambiguity, not ambition.

I make the problem legible, define the decisions that matter and give teams enough structure to move without flattening the idea.

02

Trace the whole system.

A feature is not finished at the interface. I follow data, permissions, infrastructure, operations and the last mile to production.

03

Make quality repeatable.

The strongest technical decision is often the one that becomes a template, a guardrail or a better default for everyone after you.

Client-facing

Architecture-owning

Hands-on

Team-multiplying

05 / Start a conversation

Bring me the problem that crosses boundaries.

Product leadership, software architecture, fractional technical direction or senior hands-on delivery. I am most useful when the challenge needs both breadth and depth.