🏠 RE Agent CRM — Research Report

# Real Estate Agent CRM Market Analysis
## Australian Solo Practitioner Focus

---

## COMPETITOR DEEP-DIVES

---

### 1. FOLLOW UP BOSS

**Target:** US-focused, solo agents to mid-size teams (2–50 agents)

**Monthly Price:** USD $69/month solo, $499/month for teams of 10

**Core Features:**
- Lead aggregation from 200+ sources (Zillow, Realtor.com, etc.)
- Smart lists and automated lead routing
- Email/SMS/calling built-in
- Activity timeline per contact
- Mobile app (genuinely decent)
- Integrations with Zapier, Google, major US portals

**UI Strengths:**
- Clean dashboard, relatively modern design
- "Today" view shows tasks clearly
- Fast contact search
- Mobile app is functional and frequently updated

**UI Weaknesses:**
- Setup is overwhelming for a solo agent — designed for teams with an admin
- Lead automation features are overkill and clutter the interface
- Calling features irrelevant to Australian VOIP landscape

**What Users Complain About (G2/Capterra):**
- *"Takes weeks to set up properly"*
- *"Too expensive for a solo agent who just wants simple follow-ups"*
- *"Built for US portals — Australian agents get almost no automatic lead capture value"*
- *"Support is US timezone — useless for Australians"*
- Onboarding assumes you have a team admin to configure it
- Price-to-value poor for solo operators

**Australian Relevance:** Low. No REA/Domain integrations. Pricing in USD hurts. No local support.

---

### 2. LIONDESK

**Target:** Solo agents and small teams, US market

**Monthly Price:** USD $39/month solo, $139/month for teams

**Core Features:**
- Contact management with tags and custom fields
- Built-in calling, texting, video email
- Drip campaigns and mass texting
- Task reminders and pipeline stages
- AI lead follow-up ("AI Texting")
- Zapier integration

**UI Strengths:**
- Cheapest full-featured option in the US market
- AI texting is genuinely innovative for lead response
- Pipeline view is simple and visual
- Mobile app exists (iOS/Android)

**UI Weaknesses:**
- Interface looks dated — early 2010s aesthetic
- Mobile app is slow and frequently crashes (major App Store complaint)
- Notification system is unreliable
- Drip campaign builder is clunky

**What Users Complain About (G2/Capterra/App Store):**
- *"Mobile app is basically unusable — crashes constantly"*
- *"UI looks like it was built in 2012 and never updated"*
- *"Customer support is terrible — takes days to respond"*
- *"Too many features I never use cluttering the screen"*
- *"Sync issues between mobile and desktop"*
- 2.8/5 average App Store rating — consistently poor mobile experience

**Australian Relevance:** Very low. Built entirely around US calling/texting infrastructure. AI texting doesn't work in Australia. No local portal integrations.

---

### 3. TOP PRODUCER

**Target:** Established US agents and small brokerages (5–20 agents), been around since 1992

**Monthly Price:** USD $109/month solo, $179/month for teams

**Core Features:**
- Contact and lead management
- MLS integration (US-specific)
- Market Snapshot automated reports sent to clients
- Smart drip campaigns
- Social Connect (social media lead gen add-on)
- Pipeline and transaction management

**UI Strengths:**
- Deep feature set — genuinely powerful for US agents
- Market Snapshot is a strong client retention tool
- Long track record means stable, bug-tested core

**UI Weaknesses:**
- Interface is visually outdated — feels like legacy software
- Navigation is confusing, too many menus
- Onboarding is a multi-hour commitment
- Mobile experience is an afterthought

**What Users Complain About (G2/Capterra):**
- *"Feels like a 1999 piece of software with a fresh coat of paint"*
- *"Mobile app is embarrassingly bad for 2024"*
- *"Took me 3 months to actually use it properly"*
- *"Price keeps going up, features don't improve"*
- *"Market Snapshot is great but everything else is clunky"*
- Frequent complaints about slow load times
- Cancellation process described as deliberately difficult

**Australian Relevance:** Zero. MLS doesn't exist in Australia. Built entirely around US real estate infrastructure.

---

### 4. REX CRM ⭐ (Most Important Competitor)

**Target:** Australian and UK real estate agencies, solo to mid-size (primary Australian market player)

**Monthly Price:** AUD ~$139–$199/month per agent (enterprise pricing on request for teams). Minimum commitment typically required.

**Core Features:**
- Contact and vendor/buyer management
- Property listing management
- OFI (Open For Inspection) check-in tool (mobile)
- Automated appraisal follow-up sequences
- REA/Domain/Portal integrations
- Email marketing built-in
- Activity feed per contact
- Transaction and settlement tracking
- DocuSign integration
- Reporting dashboards
- Chrome extension for LinkedIn/web capture

**UI Strengths:**
- Actually built for Australian real estate workflows (OFI, vendor/buyer split, appraisal pipeline)
- REA Group integration is genuinely useful
- OFI check-in on mobile is well-executed
- Regular product updates
- Local Australian support team

**UI Weaknesses:**
- Feature bloat — trying to be everything (listing management, CRM, marketing, transactions)
- Onboarding requires agency commitment, not designed for true solo operators
- Pricing is not friendly for a sole practitioner just starting to build habits
- Mobile app is functional but secondary to desktop experience
- Dashboard customisation is limited

**What Users Complain About (G2/Capterra/Product Review AU):**
- *"Way too expensive for a solo agent who doesn't need all the listing management features"*
- *"Onboarding is long — needed their team to help set it up"*
- *"The mobile app works but it's clearly not the priority"*
- *"I use 20% of the features and pay for 100%"*
- *"Feels built for the principal/office manager, not the agent in the field"*
- *"Reporting is powerful but I just want to see what calls I need to make today"*

**Australian Relevance:** High — but overkill and overpriced for solo operators. This is your most direct competitor and your clearest proof that the market gap exists.

---

### 5. AUSTRALIAN-SPECIFIC ALTERNATIVES

#### VaultRE
**Price:** ~AUD $150–250/month per agent (agency-level contracts)
**Target:** Mid to large Australian agencies
**What it does:** Full agency management — listings, buyers, vendors, CRM, portals, trust accounting connections
**Strengths:** Deep REA/Domain integration, widely used in QLD/NSW/VIC agencies, window card and marketing tools
**Weaknesses:** Enterprise software masquerading as an agent tool. Solo agents are not the target market. UI is dense and functional, not beautiful. Requires agency-level onboarding.
**Verdict:** Not competing for solo agents. Too heavy.

#### PropertySuite / AgentPoint
**Price:** Varies, typically agency bundle pricing
**Target:** Agencies needing full website + CRM stack
**What they do:** More about website/portal presence than daily agent workflow
**Verdict:** Not direct competition for the use case described. Website-first, CRM-secondary.

#### AgentBox
**Price:** ~AUD $100–180/month per agent
**Target:** Australian agencies
**What it does:** Similar to VaultRE — listings, portals, CRM all-in-one
**Strengths:** Good portal sync, widely adopted
**Weaknesses:** Same problem — built for agencies, solo agent is a second-class user. Mobile experience rated poorly. UI dated.

**Pattern across all Australian tools:** They are built for the *office* and the *principal*, with the agent as a user inside a larger system. Nobody is building for the *agent* as the primary customer.

---

### 6. SIMPLE SOLUTIONS: HOW AGENTS ACTUALLY COPE TODAY

#### Google Sheets
**Cost:** Free
**What agents actually build:**
- Column headers: Name, Phone, Address, Lead Date, Last Contact, Next Action, Stage, Notes
- Colour-coded rows by pipeline stage
- Simple dropdown for stage tracking
- Conditional formatting for overdue follow-ups

**Why it works:** Zero friction, familiar, flexible, syncs everywhere
**Why it fails:** No reminders/notifications, no mobile-first experience, no conversation history, breaks at scale, no accountability, easy to neglect

#### Notion Templates
**Cost:** Free–$16/month
**What agents actually build:**
- Database with filtered views ("This Week's Follow-ups", "Active Listings", "New Leads")
- Kanban board view for pipeline stages
- Linked databases for properties + contacts
- Templated note pages per client

**Why it works:** Beautiful, flexible, Kanban view is genuinely useful, mobile app is decent
**Why it fails:** Requires significant setup time, no native reminders (must use Notion AI or third-party), overkill to maintain, not purpose-built so agents don't stick with it

**The key insight here:** A meaningful percentage of solo agents are on Sheets or Notion *because nothing purpose-built is appropriately priced and simple enough*. This is not a feature gap — it's a product philosophy gap.

---

## SUMMARY SCORECARD

| Tool | Price AUD/mo | Mobile Quality | Solo-Agent Fit | AU Market Fit | Simplicity |
|------|-------------|---------------|----------------|---------------|------------|
| Follow Up Boss | ~$105 | Good | Medium | Very Low | Medium |
| LionDesk | ~$60 | Poor | Medium | Very Low | Medium |
| Top Producer | ~$165 | Very Poor | Low | Zero | Low |
| Rex CRM | ~$139–199 | Okay | Low | High | Low |
| VaultRE | ~$150–250 | Poor | Very Low | High | Very Low |
| Google Sheets | Free | Poor | High | High | High |
| Notion | Free–$25 | Medium | Medium | High | Medium |

---

## THE #1 GAP IN THE MARKET

### **"The mobile-first, daily-habit CRM built for the Australian agent in the field — not the office."**

Here is the precise gap, broken into three layers:

---

**Layer 1: The Price-Complexity Trap**
Every purpose-built Australian tool (Rex, VaultRE, AgentBox) is priced and designed for *agencies*, not individual agents. They cost $150–250/month, require onboarding, and assume you have an admin. The solo agent either overpays for features they don't use or falls back to Google Sheets. There is **no well-designed tool priced at $29–49/month for the solo Australian agent** that does exactly and only what they need.

**Layer 2: The Mobile-First Gap**
Australian real estate agents spend the majority of their working day in the field — at appraisals, OFIs, driving between properties. Every existing tool is *desktop-first with a mobile app bolted on*. The agent needs to log a note in the carpark immediately after an appraisal. They need to see their three calls for today on their phone before they leave the house. The tool that wins will be **designed phone-first**, with the desktop as secondary.

**Layer 3: The Daily Habit Problem**
The single biggest failure mode of every CRM in this market — confirmed repeatedly in reviews — is that agents stop using it within 60 days because it's too much friction for daily use. Google Sheets wins not because it's good, but because it's *low friction*. The winning product will have a **30-second daily check-in UX** — open app, see today's tasks, log a note, set a reminder, close app. That's it. No configuration. No dashboards they don't need. No features that require training.

---

**The MVP owns this positioning:**
> *"The CRM that fits in your pocket and takes 30 seconds a day — built for Australian real estate agents who are always in the field."*

**Specific feature bets for MVP:**
1. One-tap lead logging with voice-to-text notes (field use case)
2. Daily digest: "You have 4 follow-ups today" — shown on open
3. Pipeline view that fits on a phone screen without scrolling sideways
4. Automatic follow-up nudges: set it and forget it reminders
5. WhatsApp/SMS thread logging (how Australian agents actually communicate)
6. AUD pricing, Australian timezone, Australian number format — baseline table stakes that Rex charges $180/month for

**Who you're stealing from:**
- Rex/VaultRE users who feel overcharged and underserved on mobile
- Google Sheets users who know they need something better but haven't found it
- Agents who trialled a US CRM, got frustrated, and gave up

**Pricing to win:** AUD $39–49/month solo. No setup fee. No contracts. Free trial. This price point doesn't exist in the Australian purpose-built market. It's the gap.

# Real Estate Agent CRM: Feature Analysis for Solo Australian Practitioners

---

## 1. MUST-HAVE Features (MVP Cannot Ship Without These)

### Contact/Lead Record — Exact Fields Required
- **Full name** + **preferred name** (Australians use first names; "Call me Dave" matters)
- **Mobile** (primary) + **home phone** (secondary — older vendors still use these)
- **Property address** — the asset being sold, not just their home address
- **Suburb + postcode** — for quick regional filtering
- **How they found you** (referral name, letterbox drop, open home, online inquiry, etc.)
- **Lead status** — single dropdown: `New Lead → Property Visited → Following Up → Appraisal Given → Listed → Under Contract → Sold → Dead`
- **Lead source** tag (REA, Domain, referral, cold outreach)
- **Estimated property value** — agents need this for prioritization
- **Vendor motivation notes** — "divorcing, must sell by June" is more valuable than any field label
- **Next action date + next action note** — one combined field: "Call Thursday — they're comparing agents"

### Interaction Log — Exactly This
- Timestamped notes per contact (not per "deal" — just chronological against the person)
- Quick-add note from mobile in under 3 taps
- Note types: `Call | Visit | Email | Text | Other` — simple tag, not complex
- The note body: **free text only** — agents write how they think, not in structured fields
- Show full thread view per contact — every interaction in one scroll, newest at top
- Flag a note as "important" — for things like "they mentioned their daughter is pushing them to sell"

### Follow-Up / Reminder System — No Fluff
- Set a reminder from any note: "Remind me in 3 days / 1 week / custom date"
- **Today's task list** as the HOME SCREEN — not a dashboard with graphs, literally "here are your 7 calls today"
- Overdue reminders shown prominently in red — not buried
- One-tap to reschedule from the task: "Not done — push 2 days" without leaving the screen
- Reminder should include: contact name, property suburb, last note summary (1 line), and what action to take
- **No calendar complexity** — not a full calendar, just a date-based task list

### Pipeline View
- Kanban or list view of all active contacts by stage
- **Count + estimated value** per stage — "Following Up: 8 contacts, ~$4.2M in properties"
- Tap any contact from pipeline to open their record
- Visual indicator of "gone cold" — no contact in 14+ days, show a warning flag
- Filter by suburb or estimated value

### Mobile App — Non-Negotiable MVP Requirements
- Native iOS app (iPhone-first — most Australian field agents use iPhones)
- Works **offline** — agents are in rural NSW properties with no signal; notes must save locally and sync later
- Voice-to-text in the notes field — agents dictate after a walk-through while sitting in their car
- One-tap to call a contact directly from their record
- The entire MVP must be operable with one thumb while standing in someone's driveway

---

## 2. HIGH-VALUE Features (Post-MVP — Drive Retention)

### Property Inspection Workflow
- **Pre-visit checklist** per contact: "Confirmed appointment, printed CMA, checked recent sales"
- **Post-visit note template** (optional, not forced): prompts for `Property condition | Vendor motivation | Price expectation | Competition (other agents) | Next step`
- Photo attachment to a note — agents photograph whiteboards, documents, property defects
- **Comparable sales quick-lookup** (link out to CoreLogic or Domain — don't build this, just integrate)

### Smart Reminders & Follow-Up Intelligence
- "You haven't contacted [Name] in 18 days — they were in 'Following Up'" — proactive nudge
- Recurrent reminders: "Check in with past clients every 90 days" (referral pipeline is huge in RE)
- **Reminder templates**: pre-built sequences like "Post-appraisal: Day 3 → Day 7 → Day 14 → Day 30"
- Birthday/anniversary reminders (settlement anniversary is gold for referrals in Australia)

### Communication History Integration
- **SMS log**: send SMS from the app and it auto-logs against the contact
- Email BCC address: agent BCCs a unique address and the email appears in the contact's thread
- WhatsApp note-logging: can't auto-integrate (API restrictions), but one-tap to add "WhatsApp conversation" note
- Call logging: tap "Logged a call" after hanging up → quick note entry → done

### Referral & Source Tracking
- Track which referral sources produce the most listings (not just leads)
- "This referral came from [Past client name]" — link records together
- Simple report: source → leads → listed → sold conversion by source

### Document Basics
- Attach a file to a contact record (agency agreement PDF, council rates notice, etc.)
- **Not** a document management system — just attachment capability

### Pipeline Reporting (Lightweight)
- Weekly summary email to the agent: "You have X contacts going cold, Y follow-ups overdue, Z listings this month"
- Conversion rate by lead source (simple table, not dashboard)
- Monthly "deals closed" summary for their own performance tracking

---

## 3. BLOAT Features — Deliberately Do NOT Build

### Enterprise CRM Garbage
- **Custom field builder** — agents don't configure software, they abandon it
- **Multi-user permissions / roles** — this is a solo tool; teams can come later
- **Workflow automation builder** (Zapier-style if/then logic) — too complex for daily field use
- **Email marketing campaigns / mass email** — not a marketing tool; agents use REA/Domain for that
- **AI lead scoring** — sounds good, adds confusion; agents know their leads
- **Reporting dashboards with 15 charts** — one page of useful numbers, not a BI tool
- **Territory management / geographic routing** — enterprise sales tool, not relevant
- **Commission/split calculators built in** — use a spreadsheet; not a CRM job
- **Integration marketplace** (50+ integrations) — build 3 perfect ones, not 50 mediocre ones
- **Activity feed / team news feed** — Salesforce nonsense; solo agent doesn't need this
- **Contact scoring / lead temperature gauges** — agent knows who's hot; don't gamify their relationships

### Feature Creep That Kills Simplicity
- **Multiple pipelines** — one pipeline with clear stages is enough for MVP and V2
- **Task dependencies** ("Task B cannot start until Task A is complete") — overkill
- **Time tracking** — not relevant
- **Invoice/billing within CRM** — they use Xero or their agency handles this
- **Social media monitoring** — noise
- **Property listing management** — REA and Domain already do this; don't compete
- **Video calling built-in** — they use FaceTime; don't replicate it

### The Golden Rule
> If an agent needs to attend a training session to use a feature, cut it.

---

## 4. Mobile-First Considerations

### What Agents MUST Do On Phone (Field-Critical)
| Action | Design Requirement |
|---|---|
| Add a new lead on the spot | ≤3 taps from app open to saved record |
| Log a call note after hanging up | Voice-to-text + one confirm tap |
| Check today's tasks | First screen on open, no navigation |
| Mark a task done + set next follow-up | Single screen, no modal hell |
| Find a contact's number quickly | Search by name or address, instant |
| View full conversation history | Infinite scroll, newest first |
| Set a reminder while in the car | Natural language: "in 3 days" |
| One-tap call/text from record | Tap number → phone dialer opens |

### What Can Wait for Desktop
- Setting up account, importing contacts (CSV upload)
- Reviewing pipeline performance / monthly reports
- Bulk-updating contact stages after a big week
- Writing longer property appraisal notes (keyboard preferred)
- Managing notification preferences / app settings
- Any admin task that isn't time-sensitive

### Mobile UX Non-Negotiables
- **Bottom navigation bar** — thumb-reachable: Today | Contacts | Pipeline | Add
- **No hamburger menus hiding critical features**
- Large tap targets — agents use phones in gloves or with dirty hands at properties
- Auto-save on every keystroke — never lose a note due to a call interrupting
- **Dark mode** — viewing phone in a bright car at noon is painful
- Push notifications for overdue tasks (not promotional — operational)
- Face ID / fingerprint login — fast access, no password typing in the field

---

## 5. Daily Workflow of a Solo RE Agent

### Morning Routine (7:00–8:30am) — Mostly at Home or Office
**With the tool:**
1. Open app → **Today screen loads immediately** showing 6 follow-up tasks
2. Review each task with one-line context: "Dave Chen — 14 Elm St Parramatta — Last call: They want $1.4M, market says $1.25M. Call to discuss pricing reality."
3. Reprioritize: push 2 non-urgent tasks to tomorrow with one tap
4. Quick scan of **"Going Cold"** alerts — any hot lead not contacted in 10+ days
5. Check if any new leads came in overnight (REA/Domain inquiry that was manually added or auto-logged)

**Total time with tool: 8–12 minutes**

---

### In-Field Usage (9:00am–5:00pm) — Almost Entirely Mobile

**Scenario 1: Just finished a property appraisal visit**
- Sits in car outside property
- Opens contact → taps "Add Note" → hits microphone
- Dictates: "Great property, 4 bed, good condition, motivated seller — wife wants to move to QLD by July. They've spoken to McGrath already. I think we can list at $1.38M. Follow up Friday to get their decision."
- Taps save → immediately sets reminder: "Friday 10am — get listing decision"
- Back on road in 90 seconds

**Scenario 2: Unexpected call from a prospect while driving**
- Pulls over (hands-free, but needs to log after)
- After call: opens app → contact → quick note: "Called re: price concern, reassured with 12 Maple St comparable. Sending info tonight. Call back Monday."
- Sets Monday reminder
- Done in 60 seconds

**Scenario 3: New lead from a sign call (someone calls from a For Sale sign)**
- Pulls over or logs immediately after
- New contact: name, mobile, property address
- One note: "Sign call, interested in selling similar property nearby, says they're 6 months out. Low priority but keep warm."
- Stage: New Lead. Reminder in 6 weeks.

**Scenario 4: Walking into an open home**
- Checks pipeline view for suburb — sees they have 3 other prospects in that area
- Reviews one contact's history in 30 seconds before a meeting — fully briefed

---

### Evening Wrap-Up (6:00–7:30pm) — Home, Possibly Desktop

**With the tool:**
1. Review today's completed/incomplete tasks — close out done items
2. Any incomplete tasks from today: reschedule deliberately (don't just auto-push)
3. Add any notes from the day that weren't logged in the field (rare if mobile UX is good)
4. **Scan tomorrow's task list** — mentally prepare, maybe reorder priorities
5. Check pipeline: anyone move stages today? Update 2–3 records.
6. Look at "Going Cold" list — is there anyone worth a quick text tonight?

**Total time with tool: 10–20 minutes**

---

## Summary: The Product Philosophy

> Build the CRM that a busy agent uses in the **car between appointments**, not at a desk between meetings.

Every feature decision should be tested against: *"Can an agent do this in 60 seconds while sitting in a hot car in Western Sydney with their mind already on the next appointment?"*

If not — cut it, simplify it, or move it to desktop-only.

The agents who love their CRM are the ones who never feel like they're doing data entry — they feel like they're **just remembering things better**.

# CRM Design Analysis & Direction for Australian RE Agent Tool

---

## 1. The 3-4 UI Patterns That Make These Apps "Feel Good" Daily

### Pattern 1: Progressive Disclosure (Notion + Linear)
- Show only what's needed *right now* — hide complexity behind expand/click
- Linear does this brilliantly: a task looks simple until you need depth, then it unfolds
- For RE: lead card shows name, suburb, stage, next action — nothing more until tapped
- **Rule:** Every screen should have one primary action that's obvious without reading

### Pattern 2: The "Inbox Zero" Satisfaction Loop (Follow Up Boss)
- Follow Up Boss built its entire product around the daily call list — agents wake up, see exactly who to call, work through it, feel done
- The emotional reward of clearing a list is addictive and drives daily habit
- **Apply this:** Your home screen IS the task list. Completing a follow-up should feel like ticking off a satisfying checkbox, not filing paperwork
- Linear's "Done" animation, Todoist's confetti — micro-animations matter here

### Pattern 3: Inline Editing & Zero-Friction Data Entry (Streak + Notion)
- Streak wins because it lives inside Gmail — zero context switching
- Notion wins because you click any text and just type — no "edit mode"
- **For field use:** Voice-to-text note entry, one-tap stage changes, swipe gestures
- Every additional tap to log information = data that never gets logged

### Pattern 4: Spatial Memory Through Kanban (Pipedrive)
- Pipedrive's pipeline view works because humans remember *positions* — agents develop spatial memory for where each deal sits
- The act of dragging a card to the next stage is a ritual that creates mental closure
- **Critical insight:** Pipedrive found that users who interact with the pipeline view daily close 28% more deals — the visual accountability drives behaviour

---

## 2. Pipeline View Design: Kanban vs List vs Timeline

### Recommendation: **Kanban Primary, List Secondary, Timeline Hidden**

#### The Kanban Pipeline (Primary View — Desktop/Tablet)
```
[ NEW LEAD ]    [ VISITED ]    [ FOLLOWING UP ]    [ CONTRACT ]    [ CLOSED ]
   Sarah M.        Tom H.          Jenny K.           Mark T.
   Bondi           Manly           Mosman             Neutral Bay
   $1.8M est.      $2.2M est.      $3.1M est.         $4.5M est.
   Call today      Notes due       Check Fri          Sign Thurs
```
- **5 stages maximum** — RE sales cycle doesn't need more
- Each card: Name + Suburb + Estimated property value + Next action due
- Colour-coded urgency indicator (left border stripe): green = on track, amber = due today, red = overdue
- Card count + total estimated value per column (agents love seeing their pipeline value)
- Drag-and-drop stage progression with a satisfying snap animation

#### The List View (Mobile Primary View)
- Sorted by urgency: overdue → due today → due this week → no date
- Swipe right = Mark contacted / Snooze 3 days
- Swipe left = Log note quickly
- This is the **field view** — designed for one thumb, standing at a property

#### Why NOT Timeline as Primary
- RE deals are relationship-driven, not deadline-driven
- Timeline creates anxiety without actionable insight
- Reserve it for a "deal history" view inside the contact page

### Pipeline Stage Design Principles
- Stage names should be **verb-based actions**, not status labels
  - ❌ "Qualification" → ✅ "First Visit Done"
  - ❌ "Negotiation" → ✅ "In Contract"
- Allow custom stages later — but ship with the 5 defaults
- **Stale deal indicator:** Cards that haven't been touched in 7+ days get a subtle amber pulse — silent accountability without nagging

---

## 3. Contact/Lead Detail Page — Above the Fold

### The Golden Zone (What Appears Without Scrolling on Mobile)

```
┌─────────────────────────────────────────────┐
│  ← Back          Sarah Mitchell    [Edit]    │
│                                              │
│  📍 14 Oceanview Tce, Bondi NSW 2026        │
│  💰 Est. Value: $1.8M – $2.1M               │
│  🏷️  [FOLLOWING UP] ←── tap to change stage │
│                                              │
│  📞 0412 345 678    ✉️ sarah@email.com        │
│  [Call Now]  [Send SMS]  [Email]  [WhatsApp] │
│                                              │
│  ┌─────────────────────────────────────────┐ │
│  │ 🔔 NEXT ACTION                          │ │
│  │ Call re: pricing strategy               │ │
│  │ Tomorrow, 10:00am          [Done] [Edit] │ │
│  └─────────────────────────────────────────┘ │
└─────────────────────────────────────────────┘
```

### Below the Fold (Scrollable Sections)
1. **Conversation Thread** — chronological log of all notes, calls, SMSes
   - Each entry: timestamp, type icon, note content
   - Most recent at top
   - "Add Note" button sticky at bottom (always accessible)

2. **Property Details** — bedrooms, condition, motivation to sell, timeline
3. **Upcoming Reminders** — list of all scheduled follow-ups
4. **Documents/Photos** — property inspection images (camera roll integration)
5. **Source/Referral** — how this lead came in (word of mouth, door knock, open house, etc.)

### Above-the-Fold Design Rules
- **One CTA must be dominant** — for most leads it's "Call Now" or "Log Note"
- Property address is more important than email — RE agents think spatially by suburb/street
- Stage change must be one tap — it's the most frequent action
- Never show "created date" above the fold — irrelevant noise

---

## 4. Mobile-First Design Principles for Field Use

### Thumb Zone Architecture
- Primary actions (Call, Log Note, Change Stage) live in bottom 40% of screen
- Top area = information only — no buttons requiring precision at top
- Use iOS/Android native bottom sheet patterns for quick actions
- Minimum tap target: 48x48px — agents use phones with gloves, in cars, standing

### Speed-First Data Entry
- **Quick Log Button** — floating action button always visible, opens a simple note entry:
  - Who did you just talk to? (smart search)
  - What happened? (free text + voice-to-text)
  - Follow up? (3 days / 1 week / custom / none)
  - Done. 4 taps. Under 30 seconds.
- Pre-set follow-up intervals: "3 days", "1 week", "2 weeks", "1 month" — no date picker for common cases
- Template notes: "Left voicemail", "Not ready yet — check back in 30 days", "Very interested — send appraisal"

### Offline Capability
- All data must be readable offline — agents lose signal at properties constantly
- Queue actions locally, sync when connected
- Never show a loading spinner for data the app has already fetched

### Contextual Intelligence
- If it's 9am Monday: show "Today's Calls" first
- If agent is near a lead's property (geolocation opt-in): subtle "You're near Sarah Mitchell's property" nudge
- Calendar integration: surface reminders 1 hour before scheduled calls

### Gestures That Save Time
- Long press on lead card = quick action menu (Call / Log Note / Snooze / Change Stage)
- Pull to refresh feels responsive — <200ms on cached data
- Swipe back gesture always returns to previous screen (never gets stuck)

---

## 5. Colour & Typography Direction

### The Problem With Existing CRMs
- Salesforce: Cold enterprise grey/blue — feels like an IT tool
- HubSpot: Busy orange — high energy but overwhelming
- Most RE platforms: Either dated brown/cream or generic SaaS blue
- **None of them feel like something you'd choose to use**

### Recommended Palette: "Coastal Professional"

```
PRIMARY:
  Warm Slate       #2C3E50  — Primary text, headers (not black — warmer)
  Sandstone        #E8DDD0  — Background (cream-white, not stark white)
  
ACCENT:
  Pacific Blue     #2980B9  — Primary CTAs (blue but warm, not corporate)
  Terracotta       #C0392B  — Urgent/overdue indicators (warmer than red)
  Sage Green       #27AE60  — Completed/done states (fresh, not neon)
  
STAGE COLOURS (Pipeline):
  New Lead:        #8E9BAD  — Cool neutral (unknown potential)
  Visited:         #F39C12  — Warm amber (engaged, in progress)
  Following Up:    #2980B9  — Pacific blue (active relationship)
  Contract:        #8E44AD  — Rich purple (premium, serious)
  Closed:          #27AE60  — Green (victory)
  
BACKGROUND SYSTEM:
  Page BG:         #F7F4F0  — Warm off-white (not blinding white)
  Card BG:         #FFFFFF  — Pure white cards on warm background
  Sidebar/Nav:     #2C3E50  — Dark warm slate
```

### Typography Direction
- **Primary Font:** Inter — clean, modern, exceptional at small sizes on mobile
- **Alternative:** Plus Jakarta Sans — slightly warmer, excellent for Australian market
- **Avoid:** Roboto (too Android-generic), Helvetica Neue (too corporate)
- **Size Scale:**
  - Lead name: 18px semibold
  - Property address: 15px medium (grey)
  - Meta info: 13px regular
  - Notes/body: 15px regular with 1.6 line height (readable while walking)
- **Weight contrast over size contrast** — use regular vs semibold vs bold rather than huge size jumps

### Visual Character
- **Cards with subtle shadow** (not flat, not skeuomorphic) — 0 2px 8px rgba(0,0,0,0.08)
- **8px border radius** on cards — friendly but not playful
- **Generous whitespace** — RE agents deal with stressful situations; the app should feel calm
- Status indicators as **left border stripes** on cards, not full background colours
- **Icons:** Phosphor Icons or Lucide — clean, consistent weight, not cartoon-like

---

## 6. The Dashboard/Home Screen: First Thing Every Morning

### The "Morning Brief" — What Agents Need at 8am

```
┌─────────────────────────────────────────────┐
│  Good morning, James 👋                      │
│  Tuesday, 14 January                        │
│                                              │
│  ┌─── TODAY ────────────────────────────┐   │
│  │  3 calls due today                   │   │
│  │  1 overdue from yesterday ⚠️          │   │
│  │  2 property visits scheduled         │   │
│  └──────────────────────────────────────┘   │
│                                              │
│  OVERDUE                                     │
│  ● Tom Harrison — Manly         Call back    │
│    Was due yesterday                         │
│                                              │
│  DUE TODAY                                   │
│  ● Sarah Mitchell — Bondi       Call re appr │
│    9:00 AM                                   │
│  ● Jenny Kim — Mosman           Send CMA     │
│    11:00 AM                                  │
│  ● Mark Thompson — Neutral Bay  Visit        │
│    2:30 PM                                   │
│                                              │
│  PIPELINE SNAPSHOT            [View Full]    │
│  New: 3  │  Visited: 5  │  Following: 8     │
│  Contract: 2  │  $14.2M total pipeline       │
│                                              │
│  [+ Add New Lead]                           │
└─────────────────────────────────────────────┘
```

### Home Screen Rules
- **No charts on the home screen** — agents don't need analytics at 8am, they need their action list
- Overdue items appear first, always — shame-based accountability is effective
- Pipeline snapshot shows *count* and *total estimated value* — one number that feels meaningful to an agent
- "Add New Lead" button always visible — if they met someone last night, they should be able to add them in 20 seconds
- **No news feed, no activity stream, no "what your pipeline looked like last week"** — that's noise at 8am
- The screen should answer: *"What do I do first today?"* — nothing else

### Notification Strategy
- Daily summary push at 8am: "3 calls due today, 1 overdue"
- Reminder 15 mins before scheduled calls
- **No notification for pipeline movement or "congratulations" messages** — RE agents hate noise
- Weekly digest email Friday 4pm: Deals progressed, deals stalled, new leads added

---

## 7. UI Mistakes That Make CRMs Feel Bloated

### The 7 Deadly Sins of CRM UI

**1. The Empty Fields Problem**
- Showing 15 empty fields on a new lead form destroys motivation to fill anything in
- ❌ Show all fields → ✅ Show 3 required fields, hide the rest behind "Add more details"
- Progressive profiling: capture more data over time, not all at once

**2. Mandatory Fields That Aren't Actually Mandatory**
- Making email required when you only have a phone number = lead never gets logged
- For RE: **only name + phone number should be required to create a lead**
- Everything else is optional and can be added later

**3. Navigation Depth Beyond 3 Levels**
- If an agent needs to tap more than 3 times to log a note, they won't log it
- ❌ Home → Leads → Lead Detail → Activity → Add Activity → Note → Save
- ✅ Any screen → Tap "+" → Type note → Select contact → Done

**4. Confirmation Dialogs for Everything**
- "Are you sure you want to mark this task as done?" — No. Just do it. Offer undo.
- Every unnecessary confirmation dialog erodes trust and creates friction
- Use undo patterns instead of confirm dialogs

**5. Dashboard as Vanity Metrics Theatre**
- Pipeline velocity charts, conversion funnel analytics, lead source pie charts
- A solo agent doesn't need this — it makes the product look complex without delivering value
- **Ship analytics later** — day one value is task management and contact history

**6. Notification Overload**
- HubSpot and Salesforce will notify you when someone opens an email, clicks a link, views a page
- RE agents find this creepy and distracting
- **Default all non-critical notifications to off**

**7. The "Customise Everything" Trap (Notion's dark side)**
- Notion is loved AND abandoned because it requires you to build your own system
- Don't give agents a blank canvas — give them a pre-built workflow they can tweak
- ❌ "Set up your pipeline stages" → ✅ Ship with the 5 RE-specific stages, allow editing later
- **Opinionated defaults > infinite flexibility for first-time setup**

---

## Specific Recommendation: Design Direction for This Product

### Product Name Direction
Consider names in the space of: **Locale**, **Tempo**, **Parcel**, **Stride** — short, memorable, real-estate adjacent without being literal. Avoid "Pro", "Hub", "Suite".

### The Core Design Philosophy: "The Field Agent's Co-Pilot"
This product should feel like a well-organised notebook that got a software upgrade — not like enterprise software that got simplified. It exists in the agent's pocket, opens in under 2 seconds, and gets out of the way.

### Recommended Tech/Design Stack
- **React Native** (Expo) for mobile — single codebase, ships iOS + Android fast
- **Web app** for desktop/tablet with responsive Kanban (agents do admin at home evenings)
- **Supabase**

# Real Estate Agent CRM — MVP Specification

---

## 1. EXACT MVP FEATURE LIST

### Core Principle
One job: **Never lose track of a seller lead.** Everything else is noise.

---

### Screens/Pages (8 total — no more)

**1. Dashboard / Today View**
- List of today's tasks/reminders (sorted by time)
- Count of leads by pipeline stage (visual, not a chart — just numbers)
- Quick-add lead button (always visible)

**2. Lead List**
- All leads, filterable by pipeline stage
- Each row shows: Name, address, pipeline stage, next action date
- Tap/click to open lead
- Search by name or address

**3. Lead Detail Page** *(the most important screen)*
- Contact info block
- Pipeline stage selector (tap to change)
- Activity feed (chronological — notes, calls logged, stage changes)
- Next reminder/task (prominent)
- Add note button
- Add reminder button
- Call/SMS buttons (tap-to-call on mobile)

**4. Add/Edit Lead Form**
- Simple form, one page, no wizard

**5. Add Note Modal** *(quick entry, not a full page)*
- Text area
- Timestamp auto-set
- Optional: mark as "inspection visit" vs "call" vs "general note"

**6. Add Reminder Modal**
- What (free text, e.g. "Call back re: pricing")
- When (date + optional time)
- Linked to lead automatically

**7. Reminders List (optional standalone view)**
- All upcoming reminders across all leads
- Mark complete
- Tap to go to lead

**8. Login / Auth Screen**
- Email + password
- No OAuth in V1 — keep it simple

---

### Data Fields That Must Exist

**Lead/Contact**
- First name, last name
- Phone (mobile — primary)
- Email (optional in V1)
- Property address (text field — not a map API)
- Source (how they found agent — dropdown: referral, signboard, social, open home, other)
- Pipeline stage (enum — see below)
- Estimated property value (optional, free text)
- Created date
- Assigned agent (single user V1 — still store it for V2 multi-user)

**Pipeline Stages (5 — no more)**
- `new_lead` → New Lead
- `visited` → Property Visited
- `following_up` → Following Up
- `contract` → Under Contract
- `closed` → Closed/Won

*Add one more: `lost` — you need to be able to kill leads without deleting them.*

**Activity/Note**
- Lead ID (FK)
- Type (note / inspection / call / stage_change — auto-logged)
- Body text
- Created at (auto)
- Created by (user ID)

**Reminder/Task**
- Lead ID (FK)
- Description
- Due date
- Due time (optional)
- Completed (boolean)
- Completed at (timestamp)
- Created at

**User** *(single user V1)*
- ID, email, password hash, name, created at

---

### Every Action a User Can Take

- Add a new lead
- Edit lead details
- Change pipeline stage (from lead detail)
- Add a note (from lead detail)
- Add a reminder (from lead detail)
- Mark reminder complete (from today view or reminder list)
- View all leads
- Filter leads by pipeline stage
- Search leads by name or address
- Tap phone number to call (mobile)
- Delete a lead (with confirmation)
- Login / logout

**That's it. 14 actions. Ship it.**

---

## 2. DATABASE SCHEMA

```sql
-- Users
CREATE TABLE users (
  id          UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  email       TEXT UNIQUE NOT NULL,
  name        TEXT NOT NULL,
  password_hash TEXT NOT NULL,
  created_at  TIMESTAMPTZ DEFAULT now()
);

-- Leads
CREATE TABLE leads (
  id              UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id         UUID REFERENCES users(id) ON DELETE CASCADE,
  first_name      TEXT NOT NULL,
  last_name       TEXT NOT NULL,
  phone           TEXT NOT NULL,
  email           TEXT,
  property_address TEXT NOT NULL,
  source          TEXT CHECK (source IN (
                    'referral','signboard','social',
                    'open_home','other'
                  )),
  stage           TEXT NOT NULL DEFAULT 'new_lead'
                  CHECK (stage IN (
                    'new_lead','visited','following_up',
                    'contract','closed','lost'
                  )),
  estimated_value TEXT,  -- free text, "~$1.2M" — no need for numeric V1
  notes_summary   TEXT,  -- optional: last note preview for list view
  created_at      TIMESTAMPTZ DEFAULT now(),
  updated_at      TIMESTAMPTZ DEFAULT now()
);

-- Activities (immutable log — never edit, only append)
CREATE TABLE activities (
  id          UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  lead_id     UUID REFERENCES leads(id) ON DELETE CASCADE,
  user_id     UUID REFERENCES users(id),
  type        TEXT NOT NULL CHECK (type IN (
                'note','inspection','call','stage_change'
              )),
  body        TEXT NOT NULL,
  created_at  TIMESTAMPTZ DEFAULT now()
);

-- Reminders
CREATE TABLE reminders (
  id            UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  lead_id       UUID REFERENCES leads(id) ON DELETE CASCADE,
  user_id       UUID REFERENCES users(id),
  description   TEXT NOT NULL,
  due_date      DATE NOT NULL,
  due_time      TIME,              -- nullable
  completed     BOOLEAN DEFAULT false,
  completed_at  TIMESTAMPTZ,
  created_at    TIMESTAMPTZ DEFAULT now()
);

-- Indexes (the ones that matter)
CREATE INDEX idx_leads_user_stage    ON leads(user_id, stage);
CREATE INDEX idx_leads_updated       ON leads(updated_at DESC);
CREATE INDEX idx_reminders_due       ON reminders(user_id, due_date) 
                                     WHERE completed = false;
CREATE INDEX idx_activities_lead     ON activities(lead_id, created_at DESC);
```

**Why this schema works:**
- Activities are append-only — perfect audit trail of every conversation
- Stage changes auto-logged as activity entries (write trigger or app-level)
- No over-engineering: no tags, no custom fields, no relationships tables
- UUID PKs mean future multi-tenancy is trivial to add

---

## 3. TECH STACK RECOMMENDATION

### The Stack: **Next.js + PostgreSQL + Railway (or Hetzner VPS)**

**Frontend: Next.js 14 (App Router)**
- Single codebase for web + mobile (PWA)
- Server components = less client JS = faster on mobile
- API routes built in — no separate backend service to manage
- Tailwind CSS for styling (fast, consistent, mobile-first)
- Shadcn/ui for components (pre-built, looks good, copy-paste)

**Backend: Next.js API Routes + Prisma**
- Prisma ORM maps directly to the schema above
- No separate Express/FastAPI service — one thing to deploy, one thing to break
- Zod for input validation on API routes

**Database: PostgreSQL**
- Hosted on Railway ($5/month) or self-hosted on Hetzner VPS
- Neon.tech is another option (free tier, serverless Postgres)

**Auth: NextAuth.js (credentials provider)**
- Email/password in V1 — 2 hours to implement
- Extend to Google OAuth in V2 with zero schema changes

**Mobile Approach: PWA (Progressive Web App)**
- Do NOT build React Native for MVP. You have 4 weeks.
- PWA on iOS/Android = installable from Safari/Chrome, works offline (cache shell)
- Add `manifest.json` + service worker = installs to home screen
- 95% of what the agent needs works perfectly in mobile Safari
- Tap-to-call works natively via `` links
- **If he hates the mobile experience after 2 weeks → THEN evaluate RN**

**Deployment: Hetzner VPS (€4/month, CX11)**
- Docker Compose: Next.js app + Postgres container
- Caddy as reverse proxy (auto HTTPS, 10-line config)
- Railway is easier but Hetzner is cheaper and you own it
- Daily `pg_dump` to Backblaze B2 ($0.006/GB)

**The full stack in one line:**
> Next.js 14 · Prisma · PostgreSQL · NextAuth · Tailwind · Shadcn · PWA · Hetzner

**Why not:**
- ❌ Supabase — great product but adds complexity; Prisma + plain Postgres is more predictable
- ❌ React Native — 4-week kill. PWA is sufficient.
- ❌ Laravel/Rails — fine stacks but unnecessary context switch if you know JS
- ❌ Firebase — vendor lock-in, painful querying, wrong fit for relational data

---

## 4. FOUR-WEEK BUILD PLAN

### Week 1: Foundation + Data Layer
**Goal: The app boots, auth works, you can create and view leads.**

- [ ] Repo setup, Next.js scaffold, Tailwind + Shadcn configured
- [ ] Hetzner VPS provisioned, Docker Compose running, domain pointed
- [ ] Prisma schema created and migrated (all 4 tables)
- [ ] NextAuth credentials auth (login/logout working)
- [ ] `POST /api/leads` — create lead
- [ ] `GET /api/leads` — list leads with stage filter
- [ ] `GET /api/leads/[id]` — single lead with activities + reminders
- [ ] Lead List page (basic, unstyled is fine)
- [ ] Add Lead form (functional)
- [ ] Lead Detail page (data renders, no actions yet)

**End of Week 1 checkpoint:** You can log in, add a lead, and see it.

---

### Week 2: Core Workflow (Notes + Reminders + Pipeline)
**Goal: The agent can run his entire daily workflow.**

- [ ] Add Note modal (type selector: note/inspection/call)
- [ ] Stage change from Lead Detail (dropdown or button group)
- [ ] Auto-log stage changes as activity entries
- [ ] Add Reminder modal (date picker, description)
- [ ] `GET /api/reminders/today` — reminders due today + overdue
- [ ] Dashboard / Today View (today's reminders, pipeline stage counts)
- [ ] Mark reminder complete (tap, instant, no confirmation needed)
- [ ] Reminders list page (all upcoming)
- [ ] Mobile layout pass — test everything on iPhone Safari
- [ ] Tap-to-call links on phone numbers

**End of Week 2 checkpoint:** The core loop works. Lead → note → reminder → complete.

---

### Week 3: Polish, Mobile UX, and Real-World Hardening
**Goal: It's good enough that a real person won't be frustrated using it.**

- [ ] PWA setup: `manifest.json`, service worker (Next-PWA or manual), install prompt
- [ ] Offline shell caching (app loads without internet — data requires connection)
- [ ] Search leads by name/address (client-side filter on list, fast enough for <500 leads)
- [ ] Lead source tracking (dropdown on add form)
- [ ] Delete lead with confirmation
- [ ] Overdue reminders highlighted in red on dashboard
- [ ] Empty states for all screens ("No leads yet — add your first one")
- [ ] Error handling (form validation messages, failed save feedback)
- [ ] Loading states (skeleton screens on mobile — perceived performance)
- [ ] Test on actual Android + iOS devices
- [ ] Password reset flow (email — use Resend.com, free tier, 10 minutes to set up)

**End of Week 3 checkpoint:** Install the PWA on your own phone. Use it for 2 days. Fix everything that annoys you.

---

### Week 4: Beta Handoff + Real Usage
**Goal: The agent is using it daily. You're watching and fixing.**

- Day 1-2: Set up the agent's account, import his existing leads manually (you do this — takes 1 hour, builds trust)
- Day 2: 30-minute onboarding call. Watch him use it on his phone. Say nothing. Note every hesitation.
- Day 3-4: Fix the top 3 friction points you observed. Ship them.
- Day 5: Check in — "What's broken? What's missing?"
- Day 6-7: Fix. Deploy. Iterate.

**What you're measuring in Week 4:**
- Did he open it every day? (Check server logs — don't rely on him telling you)
- Did he add notes after inspections? (Look at activity table row counts)
- Did he complete reminders? (Check `completed = true` rate)
- Did he text/call you with complaints? (Good — it means he's using it)

---

## 5. WHAT TO CUT FROM V1

These will kill your timeline. Cut them without mercy.

| Feature | Why It's Tempting | Why It's Cut |
|---|---|---|
| **Email integration** (Gmail/Outlook sync) | "Agents live in email" | OAuth scopes, threading logic, 2+ weeks alone. V2. |
| **Document/file uploads** | Contracts, photos | S3 setup, UI complexity. Not the core pain. V2. |
| **Calendar sync** (Google/iCal) | "Reminders should be in my calendar" | OAuth, sync conflicts. Your reminders ARE the calendar. V2. |
| **Team/multi-user** | "What if he has an assistant?" | Schema is ready. Auth isn't. One user ships in 4 weeks. V2. |
| **Reporting/analytics** | "Conversion rate by source" | Meaningless with 20 leads. V2. |
| **Custom pipeline stages** | "Agents work differently" | They don't, not enough to matter in V1. Your 6 stages cover 95%. |
| **SMS/push notifications** | "Remind me on my phone" | Twilio integration, complex. PWA push notifications are flaky on iOS. Badge on app icon is enough. |
| **Map view of listings** | Looks cool in a demo | Google Maps API $$, 0 daily workflow value |
| **Lead scoring/AI** | "Prioritise hot leads" | No data to train on yet. Vanity feature. |
| **Import CSV** | "He has existing data" | You're doing the first import manually. V2 feature. |
| **Dark mode** | Developers love this | Agents don't care. Ship light mode. |
| **Activity editing** | "I made a typo" | Append-only log is a feature, not a bug. Train him on it. |

**Rule:** If it's not in the 14 actions listed in Section 1, it doesn't exist.

---

## 6. GETTING THE FIRST USER ACTUALLY USING IT FROM DAY 1

### The Handoff Protocol

**Before you give him access:**
1. Log into his account yourself
2. Add his top 10-15 current leads manually (ask him for a WhatsApp list, a spreadsheet, whatever he has)
3. Set the correct pipeline stage for each lead
4. Add a reminder for any "call this week" leads
5. When he logs in, he sees a full dashboard, not an empty screen

**Empty screens kill new tools. Never show an empty screen to a first user.**

---

**The 30-minute onboarding session (do this in person or on Zoom with screen share):**

Agenda:
1. Show him the Dashboard — "This is your morning. Every day, you open this."
2. Add a fake lead together — he types, not you
3. Add a note after a "pretend inspection"
4. Set a reminder, then mark it complete
5. Change a pipeline stage
6. Install the PWA on his phone together (Safari → Share → Add to Home Screen)
7. That's it. Stop there.

**Do not show him every feature. Show him the daily loop only.**

---

**The daily habit you're trying to install:**

Morning → open app → check today's reminders → done.

After inspection → open app → find lead → add note → set next reminder → done.

That's