PRODUCT

Build Fam Mode on noon to enable seamless household management empowering multiple users to act independently while the owner retains full control.

Problem description

Problem description

Problem description

Background and context

Managing a home today means coordinating multiple people, multiple needs, and constant decisions. Busy professionals often act as the central operator for their household: balancing work, family, and daily logistics. While noon already saves time by delivering essentials, the next leap is enabling shared household commerce without adding complexity.
With Fam Mode, noon evolves from a single-user shopping app into a household operating system allowing families and helpers to act independently, while the owner stays securely in control.

Personas

Household Owner / Manager (Primary User)

  • Busy professional or parent

  • Owns and pays through the noon account

  • Manages budgets, permissions, and addresses

  • Values trust, visibility, and peace of mind

  • Wants to offload execution without losing control

Family Members (Delegate Users)

  • Spouse, kids, or extended family

  • Have specific needs and contexts (food, essentials, social plans)

  • Need freedom within clear boundaries

  • Prefer autonomy without friction

Helpers (Delegate Users)

  • House help, nanny, caretaker

  • Closest to day-to-day household requirements

  • Knows what’s running out and when

  • Needs limited access to act quickly and responsibly

Current story line

A working parent is busy through the day.

'The house help notices groceries are running low'
'The nanny realizes baby essentials need restocking'
'Kids want to order snacks for a get-together'

Each case results in reminders, calls, screenshots or shared OTPs. The household owner must repeatedly open the noon app, search, verify, and place orders often distracted, sometimes missing items or exceeding budgets.
Despite e-commerce being designed to save time, household shopping remains mentally taxing and inefficient because all actions bottleneck through one person.

Problem statement

Today, noon accounts are designed for single-user ownership, but homes function as multi-user systems with shared responsibility.

  • The people who understand the need cannot place orders

  • The person who can place orders lacks real-time context and time

  • Informal workarounds (OTP sharing, shared passwords, screenshots) are insecure and unscalable

How might we enable families and helpers to shop independently within clear roles, budgets, and permissions so household owners can truly step back from execution while staying fully in control?

What needs to be built?

Participants should imagine launching this as a real product at noon. Core expectations include:

  • A clear product vision for shared household commerce

  • Thoughtful end-to-end product flows

  • A scalable and secure system design

  • A magical, intuitive, role-based UX

  • A working prototype demonstrating Fam Mode in action

Product use cases - Participants should clearly explain how they’ll solve the below use cases :  

  1. Account and Identity

    • Role-based profiles under one master account

    • Easy invite, pause, and revoke access

  2. Permissions and Controls

    • Spend limits, category access, time windows

    • Auto-order vs approval-based flows

  3. Privacy and Trust

    • Delegates only see what’s relevant

    • Payments and sensitive data stay hidden

    • Full audit trail for accountability

  4. Address Management

    • Delegates can select from saved addresses

    • Editing restricted to the owner

  5. Product Discovery

    • Restricted catalog views per role

    • Strong reorder-first experiences

  6. Ordering Journey

    • Instant checkout within limits

    • Approval flows when limits are exceeded

  7. Orders and History

    • Clear attribution of actions

    • Unified household order timeline

  8. Payments and Audit

    • Owner-controlled payment methods

    • Real-time spend tracking by user

  9. Notifications

    • Smart alerts for approvals, limits, anomalies

    • Feedback loops for delegates

  10. Returns and Exchanges

    • Delegate initiation with owner approval

    • Clear responsibility tracking

  1. Success metrics - Define how you would measure success post-launch

  2. Scalability and future thinking - How does this system extend to other cohorts ?