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 challengeMake three products evolve independently without fragmenting data, identity, environments or the customer journey.
What I ownedI 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 builtThree separately deployed Next.js applications, shared Supabase foundations, explicit environment ownership, transactional communications and observable acquisition flows.
OutcomeA platform structure that can move from validation to commercial operations without rebuilding its delivery model.
02Release engineering
Consumer mobile · marketplace operations
A social mobile marketplace for finding people, spaces and opportunities—engineered through backend recovery, safety hardening and launch operations.
The challengeMove 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 ownedI 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 builtExpo application, Postgres and Supabase services, auth-bound deletion, moderation boundaries, release checks, observability and a production lead funnel.
OutcomeA clearer and safer path to store submission, with code readiness separated from legal, account and operational gates.
03Product engineering
Hospitality · multilingual lead platform
A multilingual hospitality platform that turns destination storytelling into qualified enquiries while keeping operational data protected.
The challengeCreate a premium public experience without weakening the privacy boundary between an open contact flow and the internal lead database.
What I ownedI 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 builtNext.js internationalized frontend, server APIs, Supabase RLS, service-bound lead capture, transactional email and GDPR-oriented data flows.
OutcomeA 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 challengeMake an emotionally simple guest experience work across identity, private media, asynchronous rendering, payments and an event-day operating reality.
What I ownedI 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 builtExpo clients, Supabase permissions and storage, FFmpeg workers, Stripe payments, notifications and a manual fallback for pilot operations.
OutcomeA 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 challengeProve whether revenue leakage is painful and frequent enough to justify software before over-investing in OCR, AI and construction integrations.
What I ownedI developed the ICP, competitive framing, service-first validation model, economics, technical boundaries and explicit invest-or-stop rules.
NestJSPostgreSQLObject storageOCRLLMEvent workers
System & outcome+
System builtA Billability Engine connecting field evidence to contractual items, with an Evidence Graph, human approval and auditable asynchronous processing.
OutcomeA 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 challengeTurn expert knowledge that usually stays in people’s heads into a system teams can apply consistently across different clients and stacks.
What I ownedI translated delivery practice into operating rules, technical templates, onboarding surfaces, decision frameworks, automations and quality gates.
TypeScriptNext.jsNestJSAI workflowsCI/CDDocs
System & outcome+
System builtA modular layer of documentation standards, reusable project foundations, AI workflows, delivery tools and CI/CD conventions.
OutcomeLess 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 challengeTest how far an intentionally dopamine-forward interaction language can go while remaining coherent, responsive and technically shippable.
What I ownedI 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 builtA responsive Next.js product combining commerce UI, animated feedback, game loops and lightweight arcade interactions.
OutcomeA 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 challengeMake household payments, instalments and deadlines queryable and date-aware without trapping personal records inside an opaque application.
What I ownedI designed the information architecture, record model, natural-language operations, validation pipeline and strict source-versus-generated boundaries.
PythonMarkdownHTMLValidationLocal-first
System & outcome+
System builtHuman-readable Markdown records, Python validation and generation, and a browser dashboard that calculates recurring and upcoming obligations.
OutcomeA 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 challengeTranslate a poetic, atmospheric concept into an installable experience without turning intimate observations into cloud data or analytics.
What I ownedI 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 builtA phone-first React PWA with local-only persistence, installable offline support and explicit JSON export, import and deletion controls.
OutcomeA 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 challengeUnify portfolio, community and monetisation without reproducing the noise of global social platforms or exposing print-quality originals.
What I ownedI 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 builtNext.js and Supabase across artist profiles, artwork discovery, private originals, RLS, feedback loops and a future Printful and Stripe operating model.
OutcomeA working invite-only foundation that can validate community value before activating the heavier commerce and fulfilment layer.