Case Study · 2024

NovaVista:
spiritual
meets product.

Co-founded it and was the first designer in, then built the team. A platform connecting users with 200+ vetted spiritual coaches, from blank canvas to funded product, including the AI systems running inside it and behind it.

RoleProduct Designer · Co-founded
DurationJan 2024 – Present
PlatformiOS · Android · Web
Team size8 people · 3 designers I hired
Visit the live product · novavista.it ↗
NovaVista cover
NovaVista product overview

Product overview · platform scope

Impact

Numbers that matter.

Designed and shipped a full-stack product that grew to real users, real revenue, and a funded round. I was the first designer in, then built the team.

2K+
Paying users acquired in under 12 months
€50K
Monthly recurring revenue at peak
€500K
Pre-seed round closed, late 2025
The Challenge

Spiritual professionals had
no real home.

Coaches were juggling 5+ platforms: WhatsApp for messages, Instagram for visibility, Google Calendar for bookings, PayPal for payments. No unified solution existed for this underserved market.

"Every minute spent on logistics is one less minute for your art, and less income. We built NovaVista to fix that."

Pain point 01

Fragmented communication

Coaches used 5+ separate tools for bookings, payments, messages and client management with no single source of truth.

Pain point 02

Zero social proof engine

Reviews were scattered across Google, Trustpilot, and personal sites, impossible to centralise or use for growth.

Pain point 03

Payment friction cost revenue

53% of professionals lost clients due to limited payment options and slow, multi-step verification flows.

Pain point 04

Poor discoverability

67% struggled to attract new clients: no clear service presentation, no structured SEO, no unified profile.

User research and personas

User analysis · 4 primary personas across age groups

Platform pillars and market data

Platform pillars: freedom · income · loyalty

Process

How I approached it.

As co-founder and the first designer in, I owned the entire design function, from discovery to shipped product. Every decision had to balance user needs, business viability, and dev constraints.

01 · Discover

User Research

30+ coach interviews, 50+ user sessions. Built 4 detailed personas across spiritual backgrounds and tech comfort levels.

02 · Define

Problem Framing

Synthesised pain points into 3 platform pillars: creative freedom, income diversification, and long-term loyalty mechanics.

03 · Design

System & Flows

Full IA, core user flows for both coach and user sides, design system with 200+ components, and responsive specs.

04 · Deliver

Handoff & Iterate

Structured documentation and edge case specs that enabled a team of 8 to ship consistently without design bottlenecks.

Why NovaVista, pain points

Problem space · pain points validated through research

Solution

One platform. Every tool.

NovaVista became the first chat-commerce platform in the spiritual market, combining marketplace discovery, instant booking, integrated payments (Apple Pay, Google Pay, Klarna, Satispay), and coach analytics in a single cohesive product.

Booking and payment flows
Chat-commerce interface

Shop in 24h · booking system & chat-commerce

AI in the product
Conversational assistant & matching

A model that knows
when to stop talking.

Two AI systems run inside the product. I designed the conversation flows, the prompts and the context they sit on, working alongside the people building the model. The hard part was never the confident answer. It was designing what happens the rest of the time.

The assistant handles the questions that used to land on the team: what a service actually involves, which practitioner fits, what happens after booking. Next to it, an AI matching and recommendation flow between users and practitioners. There the design questions were what to show, what to deliberately hide, and how the result gets explained. A recommendation nobody understands is a recommendation nobody books.

Design decision
Confidence is a state, not a footnote
The interface changes shape depending on how sure the system is, and the user is told which one they are in.
Confident
  • Direct answerShort, in plain language, grounded on the real catalogue of services and practitioners.
  • TraceableThe answer points back to the listing or the service it came from.
  • Ends in the productBook, open a profile, start a path. The conversation is a route, not a destination.
Not reliable
  • The model says soIt admits the gap instead of filling it. A confident wrong answer about someone's booking or payment costs more than no answer.
  • Explicit exit to a human operatorThe handover is designed as a normal path, with the context already carried over, not as an error screen the user has to escape.
  • Why it mattersThis is the difference between an assistant that demoed well and one that survived contact with 2,000+ paying users.

The uncertainty model, drawn as a pattern

"I chose admitting uncertainty over conversational fluency. It reads worse in a demo and works better in production."

AI behind the product
Process automation

The other AI layer:
the one that runs the company.

This one users never see. It sits behind the product and it is the reason a small team can operate a two-sided marketplace across three surfaces. We built it in n8n, and I designed what it says, when it fires and who it is talking to.

01 · Lifecycle email

Personal because of the data, not the merge tag

Sending is triggered by what a person actually did on the platform. The content is then assembled from their stated preferences, the kind of service or practitioner they were browsing, and what they have bought before.

The email arrives about a thing they were already looking at. Not a template with a first name in it.

02 · Scheduling

The calendar fills itself from our conversations

Agendas and internal meetings get booked by a workflow that reads our internal chats and takes commands we send from WhatsApp, Telegram or Notion.

The design decision was the surface. We schedule from where we already are, not from a tool someone has to remember to open.

03 · Analytics

Three readers, three different outputs

Data collection and reading run through AI, and land in three places on purpose. An alert when a number moves. A dashboard the team watches. And the reports our investors read.

Same pipeline underneath, three formats, because a founder scanning a phone and an investor reading a quarterly need very different things.

See how I work with AI, in full →
Visual Design

Calm. Clear. Trustworthy.

The visual language needed to feel grounded and safe: spiritual, but not esoteric. Clean surfaces, intentional space, and a minimal palette where colour always carries meaning.

Light-Black
#3D3B40
Smoke
#E1E1E1
Pale Teal
#2EAD85
White Smoke
#F8F8F8
Silver
#EBEBFF
Color palette and UI screens

Visual design system · key screens

More UI screens

Visual design · extended screen set

Brand Extension

Beyond the screen:
physical tarot.

To deepen brand equity and open a new revenue stream, I designed a full set of custom illustrated tarot cards, printed and distributed to coaches as a loyalty product. Illustration direction, layout, and print specs all handled in-house.

Physical tarot cards brand extension

Physical tarot deck: brand extension · illustration direction by Mirko Olindo

Tools used on this project

The toolkit.

Design
FigmaAdobe IllustratorAdobe PhotoshopAffinity Designer
Motion
After EffectsPremiere Pro
Research
User InterviewsMiroNotion
AI · build
Claude CodeCursorCodexMCPChatGPTComfyUI
AI · automation
n8nPrompt & context designRAGTelegram · WhatsApp · Notion triggers
Reflection

What I took away.

Designing as a co-founder means every decision carries real stakes: budget, investor confidence, user trust. I learned to move fast without breaking the system, shipping iteratively while keeping the design language tight enough for a team of 8 to stay consistent without me in every room.

Takeaway 01

Business context sharpens design

Sitting in on investor pitches and growth reviews fundamentally changed how I frame design decisions, always tied to a metric or a milestone.

Takeaway 02

Systems beat one-off screens

A well-documented design system let the dev team move independently. Dev revision cycles dropped ~40% after the system was in place.

Next project

YELDO: Investment Marketplace

Fintech · B2B2C · Design System · 2022

View case study →