AI Product experiment that resulted in 421 leads during the first month.
‍

FamigliApp shared calendar on iPad
FamigliApp shared calendar on iPad
FamigliApp shared calendar on iPad

"I noticed that many households are disorganized, no one really knows where the money goes or how tasks, events and expenses are being coordinated. This creates a mental load that gets distributed across family members."

Not mockups, the shipped app.

Every screen below is the actual FamigliApp UI, pulled straight from the live production routes. Click any image to see it full size.

FamigliApp shared calendar on iPad

One household, at a glance

The dashboard is meant to answer one question: are we OK? It shows pending tasks, what we've spent this month, what's coming up, and anything running low, with tasks and shared expenses next to each other.

FamigliApp shared calendar on iPad

Get organized, on one place

The inventory turns "where did we put it?" into a searchable list of the household's stuff, labeled and located, so nobody buys something that's already in the closet.

The butler is one tap away

Tap the bubble. Ask anything about your home: expenses, the shared calendar, what's running low.

The butler pulls from the same data as your dashboard and answers instantly, in plain language.

Tap plus to add an expense
1 · Tap to open
Tap plus to add an expense
2 · Ask anything
Tap plus to add an expense
3 · Instant answer

"The app acts as an AI-powered household manager, making it easier to live together under one roof. That is the problem my product is solving."

An expense in five seconds

Amount, category, who paid, how it splits.

The new-expense sheet is built to use with one hand while you're standing at the checkout.

If logging an expense takes more effort than the expense is worth, people stop after the first try.

Most of the work here went into keeping that habit alive past the first week. Making it look nice was secondary.

From V1 to V2

FamigliApp generalist V1 homepage, light themeFamigliApp couples V2 homepage, light theme
Before · generalist V1
After · couples V2

The commit journey

Cadence · Commits per day

The shape of a solo sprint.

Each bar is one working day. The pace eased off on purpose toward the end, as I shifted from building the product to polishing it and setting up the commercial side: landings, SEO, billing, reactivation emails.

806040200
72
64
59
36
Apr 7Apr 15Apr 22Apr 30May 10May 25
Day with > 5 commitsLow-activity day (≤5)Y axis: commit count (max 72 on Apr 9)

The three calls that shaped the product.

01
Decision #1 · Strategy
Same code, EN/SP audiences with different rules
Options considered

One funnel for everyone · Translate everything but keep one gate · Two locales, two purposes.

Why this path

Test the app with real users from Argentina, while sharing an english version for Hiring Managers.

What I learned

These two audiences want opposite things, and one shared funnel would've done a bad job for both.

02
Decision #2 · Design system
Narrow the target audience for couples first
Options considered

Keep V2 and A/B test copy · One landing per ad campaign · Bento system with reusable cards per persona.

Why this path

With the bento template, every persona page has to use the same pieces, so I stopped piling up design debt.

What I learned

Forcing every persona onto the same components is the only reason the design stayed manageable as it grew.

03
Decision #3 · SIGN UP WORKFLOW
Signups were breaking for people on Outlook and Hotmail.
Options considered

The confirmation emails just weren't showing up. I spent May 17 to 19 pulling out the email setup and redoing it from zero.

Why this path

I moved sending all my transactional emails with, and switched from a magic link to a 6-digit code.

What I learned

I'd filed this as a minor bug, and it was actually stopping people from signing up at all. I almost left it for later.

Code was the easy 5%.

Shipping a product is mostly not coding.

5% · Code95% · Distribution + Desirability
Distribution
Getting discovered.

SEO, launching in multiple locales (Spanish open beta and English gated demo),

Desirability
Making people want it.

This is all design work, and it's what decides whether people stick around.

Legal & Accounting
What you don't vibe-code.

Terms, privacy and data handling, billing, taxes, invoicing.

Trust

Each household's data stays separate

  • Shared household money meant I couldn't get data isolation wrong.
  • Every household is walled off at the database level with row-level security.
  • One household can never see another's expenses, tasks or balances.
Row-level security on every table
Platform

Why it's a web app,
not native

  • Mobile-first PWA with web push, not a native app.
  • One codebase, every deploy is live instantly.
  • No app-store reviews and no two native apps to keep in sync.
1 codebase · instant deploys

What I'd do next

This is still early, so I'd rather end on the open questions than a victory lap. I still think narrowing the audience down to couples was the right call, but I haven't actually proven it converts better yet.

What I want to do next is measure the couples loop properly: where people drop off in the task and expense flows, and how it compares head to head against the old version.

Young couple using FamigliApp on a tablet