Money Moves

Money Moves are scheduled, actionable financial tasks delivered to users on a regular cadence. They are the engine that turns a financial plan into real behavior.

The three task types

Every Money Move cycle contains a mix of three task types:

Type	Code	Purpose	Points
Do	do	A concrete financial action with a dollar amount	50
Learn	learn	An educational task to build financial knowledge	10
Reflect	mind	A mindset or journaling exercise	10

Example cycle (weekly, savings goal):

• DO: "Transfer $150 to your emergency fund" — amount_cents: 15000
• LEARN: "Read: the difference between needs and wants"
• MIND: "Write down one financial habit you want to build this week"

Cycles

A cycle is one scheduled period. Each cycle has:

• A due_date — when the user should complete it
• A status — scheduled, available, completed, or skipped
• A list of tasks — the specific actions for that period

Cycle (due: 2024-01-15, status: available)
├── Task: DO   — Transfer $150 to savings    [pending]
├── Task: LEARN — Read about emergency funds [pending]
└── Task: MIND  — Journal reflection         [done]

Lifecycle

POST /money-moves/generate
        │
        ▼
   Cycle created (status: scheduled)
        │
        ▼  (due date arrives)
   Cycle available (status: available)
        │
        ▼  (user completes tasks)
   Cycle completed (status: completed)

Cycles are generated on demand via POST /money-moves/generate. Ozzie creates the next cycle based on the user's goal, plan, cadence, and personality.

Points and gamification

Each completed task awards points:

• DO task: 50 points
• LEARN task: 10 points
• MIND task: 10 points
• First ever completion (welcome bonus): 150 extra points

Points accumulate in the user's profile and can be surfaced in your UI to drive engagement.

What drives move generation

Money Moves are personalized using:

1. Goal type and amount — savings moves vs debt payoff moves differ significantly
2. Financial plan — the DO task amount comes from the plan's target allocation
3. Personality profile — tone, framing, and task types vary by personality
4. Past completions — Ozzie avoids repeating the same moves in consecutive cycles

Integration pattern

Typical integration flow:

1. User completes onboarding (intake + goal + plan)
2. Call POST /money-moves/generate to create the first cycle
3. Display the cycle and its tasks in your UI
4. When the user completes a task, call PATCH /money-moves/{move_id} to mark it done
5. When the cycle is done or skipped, generate the next one

→ See Money Moves API Reference