Back to Blog
7 min read

Core Flows Explained: The Only Scope Metric That Actually Works

A practical way to scope and price product work using core flows, with real examples and screen ranges.

Core Flows Explained: The Only Scope Metric That Actually Works

Most product quotes fall apart for one reason: scope gets measured in the wrong units.

Counting screens sounds logical until you realize a “screen” can be a simple profile page or a complex multi-step workflow with branching logic, validation, permissions, and error recovery. Two “10-screen” products can be completely different projects.

That’s why the most reliable way to scope a product experience is by core flows.

What is a core flow?

A core flow is one complete user journey from entry to success. It represents a real goal a user is trying to accomplish.

Examples:

  • Browse listings, open a detail page, save an item, contact a seller
  • Pick a service, choose a time, submit details, confirm a booking
  • Create a project, set options, review, submit, see success and status

A flow is not one screen. A flow typically includes multiple views, key modals, and the states that make it function like a real product.

Why screen counting fails

Screen counting ignores complexity. It also hides the true causes of time and cost.

Here’s where “one screen” turns into scope:

  • Validation rules and error messages
  • Loading, empty, and offline states
  • Permissions and role-based differences
  • Conditional steps and branching paths
  • Data dependencies and retry behavior
  • Micro-interactions that make a product feel polished

A pricing model that only counts pages or screens usually produces one of two outcomes:

  • The quote is too low and the project becomes a constant “out of scope” conversation
  • The quote is padded to cover uncertainty and the client pays for ambiguity

Core flows solve both.

Core flow anatomy (what it typically includes)

A well-defined flow usually includes:

  • Entry point (where the user starts)
  • Steps (the journey)
  • Decisions (conditions, branching)
  • States (loading, empty, error, success)
  • Exit point (what “done” looks like)
  • A few “real world” variants (e.g., first-time vs returning user)

Flow complexity: simple, standard, complex

Not all flows are equal. A practical way to estimate is to classify flows by complexity.

Simple flow

Clear steps, minimal branching, light validation (Typical range: 6–10 screens/views)

Examples:

  • Update profile basics
  • Submit a simple form
  • View a list and open a detail page

Standard flow

Multiple steps, moderate branching, richer states, confirmations (Typical range: 10–16 screens/views)

Examples:

  • Booking a service (select → calendar → details → confirm)
  • Creating a basic item (form + preview + submit)
  • Search + filter + detail + save

Complex flow

Conditional logic, multiple entities, advanced interactions, heavier error handling (Typical range: 16–25+ screens/views)

Examples:

  • Multi-step onboarding with conditional paths
  • Creating a listing with media uploads, draft saving, and rules
  • Checkout with coupons, shipping logic, payment failure recovery

Real-world examples of core flows (with screen ranges)

Booking platform: “Book an appointment” (Standard)

Typical screens/views:

  • Browse services
  • Service detail
  • Calendar view
  • Time slot selection
  • Details form
  • Review & Confirm
  • Success
  • Reschedule/cancel states

Typical range: 10–16 screens/views plus key states

Marketplace: “Browse and save” (Standard)

Typical screens/views:

  • Browse listings, Search results, Filters panel, Sort options
  • Listing detail, Save/favorite state, Empty results state

Typical range: 8–14 screens/views

Marketplace: “Create a listing” (Complex)

Typical screens/views:

  • Choose category, Multi-step details, Upload images
  • Pricing rules, Shipping or delivery options
  • Preview, Publish, Draft saved state
  • Validation and error recovery

Typical range: 16–25+ screens/views

How core flows map to Protiva tiers

This is the practical benefit: flows translate cleanly into tiers and predictable quotes.

  • Tier U1: Starter User Experience
    • 1–2 core flows
    • Thin-slice validation and alignment
    • Best when you want to prove the idea quickly
  • Tier U2: Demo Ready User Experience
    • 2–4 core flows
    • More polish, edge cases, and stakeholder-ready quality
    • Best for demos and investor conversations
  • Tier U3: Build Ready Plus User Experience
    • 4–8 core flows
    • Deeper component system and clearer behavior rules
    • Best for handoff to experienced dev teams with minimal rebuild

A simple way to define your flows today

If you are trying to scope your own product, start here:

  1. List the top 3 user goals (what they came to do)
  2. Turn each goal into one flow (start → steps → finish)
  3. Mark each flow as simple, standard, or complex
  4. Decide what must exist now versus later

You will instantly see the real shape of the project and how to phase it.

The bottom line

Core flows are the most honest unit of product scope because they measure outcomes, not pages. They make pricing fair, timelines clearer, and handoff cleaner.

If you want to avoid scope surprises, start by defining your flows before you count screens.