Settle — Product Document

The UX Journey Map

What it feels like to lose a parent, face an avalanche of paperwork, and find one thing that actually helps.

Journey Phases 6
Personas 2
Time horizon 12 months

Primary + Secondary Personas

Two people. Two experiences of the same impossible task.

DR
Diego Reyes, 34 First-time executor. Father died unexpectedly. Functional, barely.
SK
Sandra Kowalski, 68 Second time through. Wants control, the full picture, no surprises.

This map covers the moment the phone rings at 6 AM through the twelve-month anniversary — the administrative aftermath that grief doesn't excuse you from.

Emotional Architecture

The arc from rock bottom to relief

Emotional intensity is not a bug in this experience — it is the primary design constraint. Every interaction decision must be made with respect for where the user actually is on this curve.

Emotional State Over Time

Wellbeing score — higher is more functional, lower is more overwhelmed

Diego (primary path)
Sandra (power user path)
Functional Coping Overwhelmed
Aha Discovery Frustration
Phase 1The Worst Week
Phase 2The Interview
Phase 3Daily Three
Phase 4Discovery
Phase 5Hard Middle
Phase 6Long Tail
Numb. Overwhelmed. Can I trust this?
Someone organized it. I can do this.
The pile is shrinking.
I didn't know this existed.
Still here. Still moving.
I got through it.

The Six Phases

Every moment, mapped

From the call that changes everything to the twelve-month anniversary — what Diego experiences, what he needs, and where Settle intervenes.

01
The Worst Week
Day 0 – Day 4
Emotional State Numb. Then overwhelmed. Then a cautious, exhausted hope.
The Trigger

His aunt calls at 6 AM. His father is dead.

Diego is 34. He has a mortgage, a four-year-old, a job he can't miss on Monday. His father, Carlos, was 61. Nobody expected this.

The next 48 hours are logistics he can barely process: funeral home, relatives flying in, food at the house, his mother who can't be left alone. He is running on adrenaline and not sleeping.

Day 3. The funeral is done. The house is still full of people but somehow it feels emptier. Someone — maybe an uncle, maybe the funeral director — says the phrase that will haunt him for weeks: "You're the executor. You need to start on the paperwork."

Diego does not know what an executor does. He Googles it at 11 PM from his childhood bedroom. The results are a mix of law firm landing pages, government forms, and a Reddit thread that makes him more anxious than when he started.

The Search
"what to do when someone dies checklist" — 11:17 PM, Day 3. He scrolls past the first three results. He clicks the fourth one. It says: "We're sorry for your loss. There are things that need to be handled. We'll guide you through them." He reads it twice.
What Diego Needs Right Now
To feel like someone has done this before and knows what comes next
To not be asked to make decisions he doesn't understand yet
Permission to not do this tonight
Pain Points Eliminated
Search results that require legal literacy to parse
Not knowing if he's missing something critical
Cold law firm language in a moment of grief
Landing Page — Not Yet Built
Above the fold: No hero image. No stock photo of a family. Plain, warm background. The Settle wordmark. One sentence: "We're sorry for your loss. There are things that need to be handled. We'll guide you through them." One button: "Start when you're ready." No pricing, no features list, no testimonials above the fold. The first thing the page does is give permission to take a breath.
Design Constraint
The landing page has one job: earn trust from a person who is exhausted, skeptical, and grieving. Do not list features. Do not show pricing. Do not use the word "seamless." Every word must acknowledge the weight of this moment before asking for anything.
The Intake

Eight minutes. No jargon. A plan appears.

Diego opens the intake. The first screen says: "Let's get to know your father's situation. Take your time. You can always come back." The first question is not about assets or legal documents. It is: "What was his name?"

The questions move at a human pace. They are written the way a thoughtful friend would ask, not the way a form would demand. "Did he own a home? Just your best guess is fine." "Did he have any accounts at banks or credit unions? You can add more later if you find something." "I'm not sure" is always an option. There is no wrong answer.

Eight minutes later, Diego hits submit. The screen transitions. A plan loads — 34 tasks, organized by phase, sequenced so that task 3 can't happen until tasks 1 and 2 are done. The chaos has a shape now. He can see the beginning and the end of it.

The Aha Moment
The plan loads. 34 tasks. Organized. Sequenced. Diego stares at it for a full minute. He has been staring at an undifferentiated pile of anxiety for four days. Now it has rows. It has columns. It has a phase called "First 30 Days" and he can see what goes in it. This is the first moment he believes he can do this.
Screen: 01-intake.html
Intake Design Principles
One question per screen. No scrolling to see what's next.
"I'm not sure" always present — never trapped
Progress indicator in small, soft type — present but not pushy
Questions use the decedent's first name after it's given
Plan Generation Logic
The personalized plan is dependency-ordered, not alphabetical or chronological. Tasks that unlock others come first. Time-sensitive tasks (e.g. death certificate ordering, social security notification) are flagged. Tasks where "I'm not sure" was answered are listed as "Verify this" rather than skipped.
What Diego Feels After
"I thought it would take hours. It took eight minutes. And now I have a list that makes sense. I don't have to figure out what to do next — it's already figured out."
Pain Points Eliminated
Starting from a blank page with no map
Not knowing what you don't know
Fear of doing things out of order and causing problems
02
The Interview
Day 4 – Day 5
Emotional State Cautious hope. The sense that someone has organized the chaos.
03
The Daily Three
Day 5 – Month 2
Emotional State Small accomplishments accumulate. "The pile is shrinking."
The Routine

Three tasks. Fifteen minutes. A green checkmark.

Day 5. Diego opens Settle on his phone while his daughter watches cartoons. He's not ready to do anything hard. But he opens the app. Three tasks are waiting.

The first task: Call the bank to notify them of Carlos's death. Below the task title is something Diego didn't expect — a phone script. Not instructions. Not steps. A script. Words he can actually say.

Phone Script — Diego reads this verbatim
"Hi, my name is Diego Reyes. I'm calling because my father, Carlos Reyes, passed away on March 2nd. I'm the executor of his estate. I'd like to understand what steps I need to take to notify the bank. Could you direct me to the right department?"

He reads it to the representative. He doesn't have to compose the words himself. He doesn't have to think. He reads. He answers their questions. He hangs up. The task has a green checkmark.

The screen says: "You've completed 3 tasks today. That's significant."

Not "Great job!" Not a confetti animation. Just: that was significant. Because it was.

Day 8 — Automatic Task Completion
Diego logs in. Five subscription cancellations are marked complete. He didn't do them. Settle did — through automated cancellation via API integrations with the major streaming services and subscription platforms. He reads the completed list. He feels something he hasn't felt in eight days: relieved.
Screen: 02-daily-three.html
The Three-Task Principle
Three tasks is the product's core commitment. Not five, not ten. Three. Grief research and caregiver burnout studies both point to the same thing: in high-stress periods, the ability to complete a discrete, finite unit of work is a meaningful psychological win. Three tasks is completable. It is not overwhelming. It is achievable today.
What Makes This Work
Phone scripts eliminate the cognitive load of composing words
Automated tasks complete without user action (Tier 1)
Acknowledgment language respects the weight of the work
Mobile-first: all of this works from the couch, in pajamas
Pain Points Eliminated
Not knowing what to say on calls to institutions
Being put on hold and not knowing if the call was right
Hours spent canceling subscriptions individually
Celebration Tone
The product must resist the urge to celebrate in a way that feels inappropriate. No confetti. No trophy animations. The acknowledgment is plain, warm, and specific: "You've completed 3 tasks today. That's significant." This is the difference between a product that respects the user and one that treats grief as a gamified obstacle course.
Discovery

A policy he didn't know about. $2,180 he almost missed.

Week 3. Diego is going through his father's filing cabinet — something he has been avoiding. He finds a life insurance policy from 1994. His father never mentioned it. The company on the letterhead doesn't exist anymore — they were acquired three times.

He adds it to Settle. He takes a photo of the first page with his phone. Settle reads the policy number, identifies the successor insurer from the acquisition trail, generates a claim initiation task, and slots it into the plan at the correct sequence point — after the death certificate arrives but before the estate bank account needs funding.

On the same day, Settle's benefit scan returns results Diego didn't ask for.

Benefit Scan Results
Social Security survivor benefit: Diego's aunt, who was partially dependent on Carlos, may qualify for $1,840/mo. Settle generates the form and the appointment script.

Illinois unclaimed property: A dormant savings account from 1987 — $340 in Carlos Reyes's name, held by the state comptroller's office. Settle links to the claim form and pre-fills what it knows.
"I didn't know this existed. How much would I have missed without this? How much do people miss every day because they don't know where to look?"
The Benefit Scan
Settle proactively checks every case against: Social Security survivor/dependent benefits, VA benefits (if applicable), unclaimed property registries (all 50 states), pension plan databases, life insurance policy locator services. This is not a feature users ask for — it is a feature they are grateful for in retrospect.
Adaptive Planning
When a new asset or obligation is added to Settle, the plan does not append tasks to the end. It re-sequences. The new tasks are dependency-analyzed and inserted at the correct point in the workflow. Diego never has to figure out when to do the new task — Settle figures it out for him.
Emotional Weight Here
This phase carries grief of a different kind. Finding a policy in a filing cabinet means handling your father's physical things. The design must acknowledge this. Task language like "You found this — now let's figure out what to do with it" is different from "New asset added."
Pain Points Eliminated
Benefits left unclaimed because no one knew to look
Tracking down acquired/merged insurance companies alone
Discovering a benefit too late to claim it
04
Discovery & Adaptation
Week 3 – Month 1
Emotional State Surprise, then gratitude, then growing trust. "I would have missed this."
05
The Hard Middle
Month 2 – Month 4
Emotional State The acute grief has passed. The work hasn't. Diego is back at work. He is tired in a different way now.
The Long Slog

Back at work. Still here. Three tasks, fifteen minutes.

Month 2. The condolence cards have stopped arriving. His colleagues have moved on. Diego gets up, makes lunches, goes to the office. At 8 PM he opens Settle. Three tasks. He does them. He closes the app.

This is the phase most estate administration tools lose users. The early urgency has faded. The finish line is not visible. The Daily Three is the only thing keeping Diego moving — not because it's motivating, but because it is a container for the work that doesn't ask him to feel anything. Three tasks. Fifteen minutes. Done.

Then he hits a wall.

The Complex Task
His father owned property in Mexico — a small house in Oaxaca where Carlos grew up. Settle flags it with a yellow badge: "This may require a Mexican estate attorney. Here's what to bring to a consultation." It generates a briefing document: what Carlos owned, its approximate value, the relevant questions to ask. Diego doesn't have to explain his situation from scratch. Settle explains it for him.
Attorney Escalation Flow
When a task requires professional help, Settle does not drop the user. It generates a case brief — a PDF summary of everything Settle knows about the estate — formatted for attorney review. The attorney receives context before the first call. Diego doesn't spend $400/hr explaining what he already put into Settle.
Sandra's Experience Here
Sandra (68, second time through) switches to Full Plan view in Month 2. She doesn't want three tasks curated for her — she wants to see all 38, with their dependencies, deadlines, and completion states. She exports the plan to a spreadsheet. Settle accommodates her without friction. Power users are not punished for wanting more.
Fatigue Design
The product must hold Diego's place in the sequence without requiring constant re-engagement. If he skips a day, the tasks are still there. No guilt messaging. No "you missed 3 days!" notification. When he comes back, the plan is exactly as he left it. The product waits for him.
Pain Points Eliminated
Losing momentum when grief fatigue sets in
Explaining the full estate situation to every new professional
Hitting a hard task with no guidance and stopping entirely
Closure

Month 12. Most of it is done. He got through it.

Month 6. The task count is in single digits. Settle transitions quietly into monitoring mode. No fanfare. The active task queue has a note: "Most of your required tasks are complete. Here's what to watch for in the coming months."

Month 12. Settle sends a message — not a notification badge, a message: "One year ago, you started this. Some institutions may send final statements in the coming weeks. Here's what to expect and what to do with them." It also notes that the tax filing deadline for the estate's final return is in April. One task remains.

Diego completes it. The plan closes.

The Outcome
Diego recovered $2,180 in benefits he would not have known to claim. He navigated 34 administrative tasks over 12 months without an attorney for 31 of them. He spent approximately 15 minutes per day during active periods. He did not miss a deadline.

Three months later, a colleague tells him her mother is in hospice. Diego says: "There's something you should know about. It's called Settle."
Monitoring Mode
After task completion, Settle does not end the relationship. It shifts to a low-frequency monitoring state: upcoming deadlines surfaced proactively, expected institutional communications described in advance, and a one-year anniversary message with forward-looking guidance.
The Referral Moment
Diego's referral is not driven by a referral program or incentive. It is driven by the specific, concrete experience of having been helped through something hard. This is the product's most powerful distribution mechanism: the moment when someone who has been through it tells someone who is about to go through it.
Closure UX
The plan closure should feel like an ending, not a system state. Language matters: "The estate is settled" rather than "All tasks complete." An optional summary can be generated — a record of what was handled, what was found, what was recovered. Some families want this for their own records. Some want it as evidence of their work for siblings.
Pain Points Eliminated
Missing a late-arriving deadline (tax filing, final statements)
Not knowing when you're actually done
No record of what was completed for future reference
06
The Long Tail
Month 4 – Month 12
Emotional State Relief. Quiet closure. "I got through it. I didn't miss anything. I'm done."

Persona Branching

One product, two experiences

Diego and Sandra are both handling estates. They need fundamentally different relationships with the product's complexity. The design must serve both without asking either to adapt to the other's mode.

DR
Diego Reyes
34, father died unexpectedly, first-time executor
Primary Interface
Daily Three — mobile, single-session, minimal cognitive load
Session Length
10–20 minutes, usually evenings or weekends
What He Needs
Decision elimination. He doesn't want to choose what to do next — he wants Settle to tell him. The phone script is the epitome of this: no cognitive work, just action.
What He Fears
Missing something. Doing something wrong. Being on a call with an institution and not knowing what to say or what they'll ask.
Defining Win
A green checkmark after the bank call. Three tasks done. "That's significant." The sense that something, today, moved forward.
Diego's Path Through the Product
Landing page → Intake (8 min) → Daily Three (mobile) → Benefit discovery → Attorney brief → Monitoring → Closure → Referral
SK
Sandra Kowalski
68, second time through, wants full visibility and control
Primary Interface
Full Plan view — desktop, all 38 tasks visible, phases and deadlines shown
Session Length
45–90 minute focused sessions, usually mornings at her desk
What She Needs
Comprehensive visibility. She's done this before. She knows how much can go wrong. She wants to see the whole map, not just the next three steps. She trusts the product more when she can see its logic.
What She Fears
Being surprised. Missing something a product didn't show her because it was trying to be simple. Feeling like the product is condescending to her about complexity.
Defining Win
Exporting the full task plan to a spreadsheet. Having a date-stamped record of every task completed, every document filed, every institution notified. The comprehensive receipt.
Sandra's Path Through the Product
Landing page → Intake (14 min, more complete) → Full Plan view (desktop) → Exports to spreadsheet → Attorney coordination → Monitors all deadlines herself → Exports closure record

Screen Architecture

Three screens, the whole journey

The core product experience runs through three screens. Each one corresponds to a critical moment in the journey. Together they are complete.

1
Phase 2 — The Interview
Guided Intake
The onboarding interview. One question at a time, in plain language. Builds the personalized plan from the user's answers. Designed for grief fog: "I'm not sure" is always present, no judgment, no jargon. Takes 8–14 minutes depending on estate complexity. Outputs a dependency-ordered task plan.
The Aha Moment: The plan loads. 34 tasks. Organized. The chaos has a structure.
01-intake.html
2
Phase 3 — The Daily Three
Today's Tasks
The daily workhorse. Three tasks, always three, ordered by dependency and urgency. Each task includes all the context needed to complete it — phone scripts, document checklists, form links. Designed for mobile use on the couch at 8 PM. Automated tasks (subscription cancellations) complete silently without user action.
The Daily Win: "You've completed 3 tasks today. That's significant."
02-daily-three.html
3
Phase 5 — The Hard Middle
Full Task Plan
The power user view. All tasks, all phases, all deadlines. Dependencies visualized. Benefits discovered shown in a summary panel. Attorney escalation brief generation. Export to spreadsheet. Sandra's interface. Diego can access this too — but he doesn't need to. The Daily Three is his default view.
Sandra's Win: Exports the full record. Sees every task in its phase. No surprises.
03-task-plan.html
Flow
Landing Page 01 Intake 02 Daily Three 03 Full Plan Monitoring Closure
$2,180
recovered for Diego in benefits he would not have found alone
Social Security survivor benefit + unclaimed property
34
administrative tasks navigated over 12 months
3 required attorney involvement; 31 completed independently
15 min
average daily time investment during active phase
Daily Three: 3 tasks, scripts included, mobile-first
0
missed deadlines in a 12-month estate administration
Proactive monitoring and advance notice throughout

Before / After

What changes when Settle exists

Not a features matrix. A comparison of what it actually feels like to go through this — without support and with it.

Situation Without Settle With Settle
Day 3 — Diego Googles what to do Law firm SEO results. Government forms with no context. A Reddit thread that raises three new fears. Closes the laptop. "We're sorry for your loss. There are things that need to be handled. We'll guide you through them." He keeps the tab open.
The bank call Diego stares at the phone for 20 minutes. Doesn't know what to say. Gets transferred twice. Hangs up unsure if he did it right. Does not mark it done. He reads the script. He stays on the call. He completes the task. Green checkmark. "That's significant."
Subscription cancellations Diego finds his father's Netflix, Spotify, three magazine subscriptions, a gym membership, and a streaming service he forgot existed. Calls and chat sessions spread over a week. Some charge another month before he catches them. Eight subscriptions cancelled automatically. Diego sees the completed list on Day 8. He didn't do them. They are done.
The life insurance policy in the filing cabinet Diego finds it. The company on the letterhead doesn't exist. He Googles the name and gets nowhere. Sets it aside. Forgets about it. Never claims it. He photographs it. Settle identifies the successor insurer. New task appears, correctly sequenced. Claim initiated within the week.
The Social Security survivor benefit Diego's aunt never applies. Nobody tells her she might qualify. $1,840/month goes unclaimed indefinitely. Settle's benefit scan flags it. Task generated, form pre-filled, appointment script included. His aunt applies and qualifies.
Month 2 — Diego back at work The pile of papers on the kitchen counter is still there. He doesn't know where he left off. The thought of dealing with it makes him feel sick. He does nothing for three weeks. He opens the app. His three tasks are waiting. No guilt message. No streak counter. He does two of them and closes the app. Progress.
The Mexican property Diego doesn't know this requires a Mexican attorney. He tries to handle it through the U.S. probate process. Months of delay. Eventually an attorney charges him for time explaining what the situation is. Settle flags it in Week 3. Case brief generated. Attorney receives context on the first call. The first hour is solving, not explaining.
Sandra's experience She's been through this before and resents being treated like she hasn't. Every software tool gives her a simplified view that hides information she wants. She builds a spreadsheet from scratch. Again. She switches to Full Plan view in Week 1. All 38 tasks. Phases. Deadlines. Exports to spreadsheet as a backup. The product respects her experience.
Month 12 — the tax filing Diego doesn't know the estate requires a final tax filing. The deadline passes. He gets a letter from the IRS six months later. Penalties. Settle surfaces the filing in February. One task. Document checklist included. Completed before the deadline. No surprises.

Design Principles

What this product believes

These are not aspirational statements. They are the constraints that every design decision must pass through before it ships.

01
The user arrived in the worst week of their life.
Every product decision is made with this in mind. Onboarding that would be acceptable for a productivity tool is not acceptable here. Copy that would be fine for a task manager is not fine here. The bar for care is higher than anything you have shipped before.
02
Eliminate decisions. Don't just organize them.
The goal is not to show Diego all his options. It is to remove the need for him to have options at all. Three tasks. A script to read. A checkmark. Cognitive overhead is a tax on grieving people. Settle's job is to lower that tax to zero wherever possible.
03
No confetti. No streaks. No gamification.
Acknowledgment is not celebration. "You've completed 3 tasks today. That's significant." is the right register. A trophy animation is the wrong register. The product must hold the weight of this work — not lighten it artificially. The user's grief is real. Treat it as real.
04
The product waits. It does not chase.
When Diego doesn't log in for four days, the plan is exactly where he left it. No "You missed 3 days!" notification. No re-engagement email. The tasks are waiting, without judgment. Grief is not a productivity failure. The product's job is to be there when he comes back, not to pull him back.
05
Power users are not punished for wanting more.
Simplicity is not the same as restriction. Sandra needs to see all 38 tasks, all deadlines, all dependencies. She needs to export data. She needs to feel in control of the full picture. The Daily Three default should never become a ceiling. The Full Plan view exists, and it is first-class.
06
Proactive beats reactive. Always.
The benefit scan is not a feature users request. The upcoming tax filing notification is not a response to a question. Settle's highest value is finding what Diego doesn't know he's missing. Every proactive surface — benefits, deadlines, upcoming milestones — earns trust that no reactive feature can replicate.
UX Journey Map — April 2026