USNW AI Estimate Platform — Product Blueprint Package (V1)
1. Executive Summary
The USNW AI Estimate Platform is an AI-assisted exterior property intelligence and estimate automation platform designed to dramatically reduce estimate creation time while increasing estimate quality, operational consistency, upsells, and recurring service opportunities.
The platform will act as an intelligent estimating layer that sits in front of Jobber. Instead of replacing operational systems, the platform will accelerate and standardize the estimate creation workflow.
The system combines:
- Property intelligence
- Measurement workflows
- Human-guided map verification
- AI-assisted estimate generation
- Pricing intelligence
- Good / Better / Best package generation
- Automated Jobber quote injection
The platform’s primary goal is to reduce estimate creation time from 30–60 minutes to under 5 minutes while increasing average ticket value and improving estimate consistency.
2. Core Product Vision
Vision Statement
An AI-assisted exterior property intelligence and estimate automation platform that transforms property measurements, aerial imagery, and estimator inputs into high-quality customer-ready estimates in minutes.
Core Philosophy
The system is NOT intended to fully replace estimators.
Instead, the platform acts as an intelligent estimating copilot that:
- Guides estimators
- Accelerates measurements
- Recommends services
- Builds estimate packages
- Generates professional scopes
- Pushes estimates into Jobber automatically
Human verification and approval remain critical components of the workflow.
3. Core Business Goals
Primary Goals
- Reduce estimate build time to under 5 minutes
- Eliminate repetitive manual estimate creation
- Standardize estimate quality across estimators
- Increase Good / Better / Best package adoption
- Increase recurring maintenance revenue
- Improve upsell conversion rates
- Improve estimate presentation quality
- Reduce estimator training complexity
- Automatically generate Jobber-ready estimates
Secondary Goals
- Build long-term property intelligence profiles
- Reuse measurements for future services
- Create recurring maintenance opportunities
- Improve operational consistency
- Create scalable multi-division workflows
4. End-To-End Workflow
Master Workflow
Lead Intake
↓
Property Lookup
↓
Property Intelligence Loads
↓
Aerial Imagery Loads
↓
AI Attempts Measurement Detection
↓
Human Verification / Redrawing
↓
Dynamic Smart Questions
↓
Service Selection
↓
Pricing Engine Runs
↓
Good / Better / Best Package Generation
↓
AI Scope Generation
↓
Human Review & Approval
↓
Push To Jobber
↓
Quote Ready To Send
5. Core User Roles
Office Admin
- Full access
- Manage pricing
- Manage templates
- Approve estimates
- Configure integrations
Estimator
- Create estimates
- Draw measurements
- Review AI suggestions
- Push approved estimates to Jobber
Sales Manager
- Review pricing
- Approve large estimates
- Review estimate quality
- Track conversion metrics
Branch Manager
- Region-specific pricing oversight
- Crew production oversight
- Estimate approval authority
Reviewer / QA
- Verify measurements
- Verify AI confidence
- Review scopes
6. Core Product Modules
1. Property Intelligence Engine
Stores:
- Property data
- Measurements
- Service history
- Photos
- AI observations
- Recurring opportunities
2. Measurement Engine
Supports:
- AI detection
- Human drawing
- Polygon editing
- Line measurements
- Zone management
- Overlay management
3. Service Recommendation Engine
Automatically suggests:
- Relevant services
- Upsells
- Seasonal recommendations
- Maintenance opportunities
4. Pricing Engine
Handles:
- Base pricing
- Production rates
- Difficulty modifiers
- Margin protection
- Market intelligence adjustments
5. AI Estimate Engine
Generates:
- Customer-facing scopes
- Internal notes
- Good / Better / Best packages
- Service recommendations
6. Jobber Sync Engine
Pushes:
- Customers
- Properties
- Line items
- Quotes
- Notes
- Service mappings
7. Core Data Objects
Property
Stores:
- Address
- Parcel data
- Property type
- Measurements
- Images
- Service history
- AI observations
Customer
Stores:
- Name
- Phone
- Email
- Jobber reference
- Service history
Measurement Object
Stores:
- Type
- Geometry
- Area/length
- Confidence score
- Notes
- Service compatibility
Service Template
Stores:
- Pricing rules
- Measurement type
- Production rates
- Labor assumptions
- Jobber mappings
- Upsells
Estimate
Stores:
- Line items
- Packages
- Pricing
- AI outputs
- Revision history
AI Recommendation
Stores:
- Recommended services
- Confidence
- Suggested upsells
- Suggested packages
8. Service Categories
Lawn & Landscape
- Lawn mowing
- Edging
- Weed control
- Fertilizer
- Aeration
- Overseeding
- Mulch installation
- Shrub trimming
Exterior Cleaning
- Roof cleaning
- Gutter cleaning
- Pressure washing
- House washing
- Concrete cleaning
- Window cleaning
Tree Services
- Tree trimming
- Tree removal
- Stump grinding
- Hazard tree assessments
- Emergency cleanup
Seasonal Services
- Christmas lighting
- Snow removal
- Fall cleanup
- Spring cleanup
Exterior Maintenance
- HOA maintenance
- Parking lot cleanup
- Property cleanup
- Commercial maintenance
9. Measurement Types
| Measurement Type | Used For |
|---|
| Turf Square Footage | Lawn services |
| Roof Square Footage | Roof cleaning |
| Concrete Square Footage | Pressure washing |
| Mulch Bed Square Footage | Mulch installation |
| Gutter Linear Footage | Gutter cleaning |
| Roofline Linear Footage | Christmas lighting |
| Fence Linear Footage | Fence cleaning/staining |
| Tree Count | Tree services |
| Shrub Count | Landscape maintenance |
| Property Acreage | Commercial maintenance |
10. Human Verification Workflow
AI-generated measurements are treated as suggested values only.
Human estimators must be able to:
- Approve measurements
- Edit polygons
- Redraw zones
- Adjust measurements
- Add missing zones
- Reject AI suggestions
Confidence Rules
Low-confidence measurements should trigger:
- Visual warnings
- Manual verification prompts
- Review workflows
Example:
- Turf area confidence: 96%
- Roof pitch confidence: 62%
11. Dynamic Question Engine
The platform should dynamically ask contextual questions based on:
- Property type
- Selected services
- Measurements
- AI observations
Example — Roof Cleaning
Questions:
- Roof pitch?
- Heavy moss?
- Number of stories?
- Access limitations?
- Roof type?
Example — Lawn Services
Questions:
- Gates?
- Irrigation?
- Obstacles?
- Slope?
- Frequency?
Example — Tree Services
Questions:
- Crane required?
- Power lines?
- Haul away?
- Access width?
- Stump grinding?
12. Good / Better / Best Package Engine
The platform automatically builds service packages.
Example — Pressure Washing
Good
Better
Best
- Full exterior cleaning package
Example — Lawn Maintenance
Good
Better
Best
13. Pricing Engine Architecture
Layer 1 — Internal Base Pricing
USNW-controlled pricing rules.
Layer 2 — Production Logic
Includes:
- Labor assumptions
- Crew production rates
- Equipment costs
- Difficulty modifiers
Layer 3 — Market Intelligence
N8N orchestrates:
- Regional pricing research
- Competitive positioning
- Market adjustment recommendations
The system should NEVER blindly use internet pricing.
The platform must protect:
- Margins
- Labor burden
- Overhead
- Equipment costs
- Profitability
14. AI Responsibilities
AI SHOULD:
- Generate scopes
- Suggest upsells
- Recommend packages
- Generate internal notes
- Suggest services
- Assist measurements
AI SHOULD NOT:
- Finalize pricing autonomously
- Send estimates automatically
- Replace human review
- Override business rules
15. UX Philosophy
The platform should feel:
- Fast
- Guided
- Minimal
- Premium
- AI-assisted
- Map-centric
- Touch-friendly
- Dark-mode-first
Estimators should feel:
"I am being intelligently guided."
NOT:
"I am filling out forms."
16. Primary Screens
Dashboard
- Recent estimates
- Pipeline
- AI recommendations
- Quick actions
Property Profile
- Measurements
- History
- Photos
- Recommendations
Map Measurement Screen
- Aerial map
- Drawing tools
- AI overlays
- Polygon editing
Service Selection Screen
- Service cards
- Recommendations
- Package builder
AI Estimate Review Screen
- Line items
- Scope generation
- Good / Better / Best comparison
- Pricing review
Jobber Sync Screen
- Sync status
- Validation
- Push to Jobber
17. Technical Architecture
Frontend
- Next.js
- Tailwind
- shadcn/ui
- Dark mode first
Backend
- PostgreSQL
- Supabase or custom backend
Automation Layer
AI Providers
Integrations
- Jobber API
- Map providers
- Aerial imagery providers
- SMS/email systems
18. Source Of Truth Architecture
| System | Responsibility |
|---|
| USNW Estimate Platform | Property intelligence + estimate generation |
| Jobber | Operational execution |
| N8N | Automation/orchestration |
| AI Providers | Recommendations + language |
| Database | Measurements/history |
19. Future Expansion Opportunities
Future Features
- AI image analysis
- Commercial property mode
- Route intelligence
- Crew production forecasting
- Recurring maintenance engine
- Automated renewal generation
- Seasonal recommendation engine
- Mobile estimator mode
- Offline field support
20. Immediate Next Steps
Phase 1
- Finalize product blueprint
Phase 2
- Create detailed screen inventory
Phase 3
- Build low-fidelity wireframes
Phase 4
- Create Claude implementation package
Phase 5
21. Detailed Screen Inventory
1. Login / Authentication
Purpose:
- Secure access
- Role-based permissions
- Branch/division selection
Key Components:
- Email/password login
- SSO support (future)
- Branch selector
- Remember session
2. Main Dashboard
Purpose:
- Daily operational hub
- Quick estimate access
- Pipeline overview
Key Components:
- Recent estimates
- Estimates awaiting approval
- AI recommendations
- Recurring opportunities
- Recently viewed properties
- Quick create estimate button
- Activity feed
3. New Estimate Intake Screen
Purpose:
- Start estimate workflow quickly
Key Components:
- Customer search/create
- Address lookup
- Property autocomplete
- Property type selector
- Service category quick-select
- Import previous measurements
Workflow Goal:
Under 30 seconds to begin estimate.
4. Property Intelligence Screen
Purpose:
- Central property overview
Key Components:
- Property map
- Property imagery
- Measurements summary
- Previous services
- Photos timeline
- AI recommendations
- Service opportunities
- Recurring maintenance suggestions
5. Measurement Workspace
Purpose:
Layout:
LEFT PANEL
- Service workflow
- Smart questions
- Selected services
- AI recommendations
CENTER PANEL
- Interactive aerial map
- Polygon drawing tools
- Line measurement tools
- AI overlays
- Editable zones
RIGHT PANEL
- Live estimate preview
- Measurement totals
- Pricing preview
- Confidence warnings
Core Features:
- Draw polygons
- Draw line measurements
- Approve AI zones
- Edit overlays
- Snap-to-edge support
- Undo/redo
- Measurement labels
- Zone naming
- Save reusable measurements
6. Dynamic Question Screen
Purpose:
- Collect estimator-specific information
Behavior:
Questions dynamically generated based on:
- Selected services
- Property type
- AI observations
- Measurements
Examples:
- Roof pitch
- Heavy moss?
- Irrigation?
- Access limitations?
- Gate width?
- Power lines?
UX Goals:
- Minimal typing
- Mostly toggle/select inputs
- Fast guided workflow
7. Service Recommendation Screen
Purpose:
- Present upsell opportunities
- Build estimate scope
Key Components:
- Recommended services
- Seasonal recommendations
- Suggested bundles
- AI reasoning
- Quick add/remove actions
Examples:
- Gutter cleaning recommended due to roof tree coverage
- Pressure washing recommended due to moss/shade conditions
8. Good / Better / Best Builder
Purpose:
- Automatically package estimate options
Layout:
Three-column comparison layout
GOOD
BETTER
BEST
Features:
- Drag/drop services
- Pricing comparison
- Margin preview
- Highlight recommended option
- Optional upgrades
9. AI Estimate Review Screen
Purpose:
- Human approval before Jobber sync
Key Components:
- Generated line items
- Customer-facing scopes
- Internal crew notes
- AI confidence indicators
- Margin indicators
- Pricing overrides
- Optional line items
- Revision tracking
Approval Features:
- Approve estimate
- Request changes
- Save draft
- Escalate for manager review
10. Jobber Sync Screen
Purpose:
- Push finalized estimate into Jobber
Key Components:
- Customer sync validation
- Property sync validation
- Service mappings
- Line item preview
- Sync status
- Error handling
Workflow:
- Create/update customer
- Create/update property
- Create Jobber quote
- Push line items
- Attach notes
- Return Jobber quote reference
11. Estimate History Screen
Purpose:
- Track revisions and historical estimates
Key Components:
- Estimate versions
- Revision timeline
- Previous pricing
- Approval history
- Service changes
- Customer decisions
12. Service Catalog Management
Purpose:
- Admin management of services
Key Components:
- Service templates
- Pricing rules
- Measurement types
- Production rates
- Jobber mappings
- Upsell relationships
- AI prompt context
13. Pricing Engine Management
Purpose:
Key Components:
- Base pricing
- Regional pricing
- Difficulty modifiers
- Margin thresholds
- Labor assumptions
- Equipment costs
- Seasonal adjustments
14. AI Configuration Screen
Purpose:
Key Components:
- AI provider selection
- Prompt templates
- Scope tone settings
- Upsell behavior
- Recommendation rules
- Confidence thresholds
15. Reporting Dashboard (Future)
Purpose:
Key Components:
- Estimate conversion rates
- Average ticket size
- Upsell conversion
- Estimator efficiency
- AI usage metrics
- Margin reporting
22. Low-Fidelity Wireframe Planning
Wireframe Philosophy
Initial wireframes should prioritize:
- Workflow clarity
- Speed
- Minimal clicks
- Information hierarchy
- Estimator usability
NOT:
- Branding
- Final visual design
- Animations
- Polish
Primary Wireframes To Build First
Wireframe 1 — Dashboard
Focus:
- Daily workflow
- Estimate queue
- Quick actions
Wireframe 2 — Property Intake
Focus:
- Fast customer/address entry
- Property lookup
- Service selection
Wireframe 3 — Measurement Workspace
Focus:
- Map-centric workflow
- Drawing tools
- AI overlays
- Live estimate panel
Wireframe 4 — Good / Better / Best Builder
Focus:
- Package comparison
- Upsells
- Pricing visibility
Wireframe 5 — AI Estimate Review
Focus:
- Human approval
- Scope review
- Margin protection
- Confidence review
Wireframe 6 — Jobber Sync Confirmation
Focus:
- Sync validation
- Final quote push
- Error handling
23. MVP Scope Definition
MUST HAVE (MVP)
- Address lookup
- Property profiles
- Manual drawing tools
- Measurement storage
- Service catalog
- Dynamic question engine
- Pricing engine
- Good / Better / Best generation
- AI scope generation
- Human review workflow
- Jobber integration
- Estimate versioning
NICE TO HAVE
- AI measurement detection
- AI image analysis
- Market pricing intelligence
- Seasonal recommendation engine
- Advanced reporting
- Route intelligence
FUTURE FEATURES
- Drone imagery support
- Commercial property mode
- Mobile offline mode
- Crew forecasting
- Predictive maintenance engine
- Automated renewals
- Multi-branch analytics
24. Claude Implementation Preparation
Claude Build Inputs Will Include:
- Product blueprint
- Screen inventory
- Wireframes
- UX philosophy
- Database architecture
- Service catalog structure
- AI responsibilities
- API architecture
- Technical stack
- Integration requirements
Development Philosophy
Claude should build:
- Modular architecture
- Reusable components
- Clean workflows
- Fast interfaces
- Scalable systems
Claude should avoid:
- Overengineering
- Excessive animations
- CRM replacement behavior
- Complex accounting features
- Operational bloat
25. Low-Fidelity Wireframes
Wireframe 1 — Main Dashboard
Primary Goal
Allow estimators and office staff to:
- Quickly resume work
- Start estimates rapidly
- View pipeline activity
- See AI recommendations
- Access recent properties
Layout Structure
Code:
┌──────────────────────────────────────────────────────────────┐
│ TOP NAV │
│ Logo | Search | Notifications | User | Branch Selector │
├───────────────┬──────────────────────────────────────────────┤
│ LEFT SIDEBAR │ MAIN CONTENT │
│ │ │
│ Dashboard │ Quick Actions │
│ Estimates │ [+ New Estimate] │
│ Properties │ [Resume Estimate] │
│ Customers │ [Search Property] │
│ Reports │ │
│ Settings │ Estimate Pipeline │
│ │ - Draft Estimates │
│ │ - Pending Approval │
│ │ - Synced To Jobber │
│ │ │
│ │ AI Recommendations │
│ │ - Recurring opportunities │
│ │ - Suggested follow-ups │
│ │ │
│ │ Recently Viewed Properties │
│ │ │
└───────────────┴──────────────────────────────────────────────┘
UX Priorities
- Minimal clutter
- Fast access to estimate creation
- AI insights visible immediately
- Mobile/tablet friendly
Wireframe 2 — Property Intake Screen
Primary Goal
Begin estimate workflow in under 30 seconds.
Layout Structure
Code:
┌──────────────────────────────────────────────────────────────┐
│ NEW ESTIMATE │
├──────────────────────────────────────────────────────────────┤
│ Customer Search/Create │
│ [ Search Customer __________________________ ] │
│ │
│ Property Address │
│ [ Enter Address ___________________________ ] │
│ │
│ Suggested Property Results │
│ ---------------------------------------------------------- │
│ 123 Main St │
│ 456 Oak Ave │
│ │
│ Property Type │
│ ( ) Residential ( ) Commercial ( ) HOA │
│ │
│ Initial Services Needed │
│ [ ] Lawn │
│ [ ] Roof Cleaning │
│ [ ] Pressure Washing │
│ [ ] Tree Service │
│ │
│ [ Continue To Property Intelligence ] │
└──────────────────────────────────────────────────────────────┘
UX Priorities
- Very few required fields
- Smart autocomplete
- Minimal typing
- Fast estimate initiation
Wireframe 3 — Measurement Workspace
Primary Goal
Create the central intelligent estimating workspace.
Layout Structure
Code:
┌────────────────────────────────────────────────────────────────────────────┐
│ PROPERTY: 123 Main St │
├────────────────┬─────────────────────────────────────┬────────────────────┤
│ LEFT PANEL │ CENTER MAP WORKSPACE │ RIGHT PANEL │
│ │ │ │
│ SERVICES │ AERIAL MAP │ LIVE ESTIMATE │
│ ☑ Lawn │ │ │
│ ☑ Roof Clean │ [Editable AI Overlays] │ Turf: 4,200 SF │
│ ☑ Gutters │ │ Roof: 2,100 SF │
│ │ │ Gutters: 180 LF │
│ QUESTIONS │ Polygon Tools │ │
│ - Irrigation? │ Line Tools │ Estimated Total │
│ - Gates? │ Zone Labels │ $4,850 │
│ - Roof Pitch? │ AI Confidence │ │
│ │ │ GOOD / BETTER / │
│ RECOMMENDED │ │ BEST PREVIEW │
│ + Aeration │ │ │
│ + Pressure │ │ │
│ │ │ [Review Estimate] │
└────────────────┴─────────────────────────────────────┴────────────────────┘
Core UX Concepts
- Map is the centerpiece
- Estimator always sees live pricing
- AI suggestions remain editable
- Minimal screen switching
Critical Features
- Polygon editing
- Snap-to-edge
- Undo/redo
- AI overlay confidence
- Quick service toggles
- Real-time estimate updates
Wireframe 4 — Good / Better / Best Builder
Primary Goal
Increase average ticket size and upsell conversion.
Layout Structure
Code:
┌──────────────────────────────────────────────────────────────────────────┐
│ GOOD / BETTER / BEST BUILDER │
├────────────────────┬────────────────────┬───────────────────────────────┤
│ GOOD │ BETTER │ BEST │
│ │ │ │
│ Driveway Cleaning │ Driveway + Walks │ Full Exterior Cleaning │
│ Basic Lawn Mow │ Lawn + Edging │ Premium Maintenance Package │
│ │ │ │
│ Total: $299 │ Total: $699 │ Total: $1,299 │
│ │ │ │
│ [Select] │ [Recommended] │ [Premium] │
│ │ │ │
├────────────────────┴────────────────────┴───────────────────────────────┤
│ Optional Add-ons [+] │
│ - Gutter Cleaning │
│ - Aeration │
│ - Moss Treatment │
└──────────────────────────────────────────────────────────────────────────┘
UX Priorities
- Clear comparison
- Easy upsells
- Recommended package emphasis
- Visual simplicity
Wireframe 5 — AI Estimate Review Screen
Primary Goal
Human approval before Jobber sync.
Layout Structure
Code:
┌──────────────────────────────────────────────────────────────────────────┐
│ AI ESTIMATE REVIEW │
├──────────────────────────────────────────────────────────────────────────┤
│ CUSTOMER-FACING SCOPE │
│ ---------------------------------------------------------------------- │
│ We will carefully clean all identified roof surfaces... │
│ │
├──────────────────────────────────────────────────────────────────────────┤
│ LINE ITEMS │
│ ---------------------------------------------------------------------- │
│ Roof Cleaning .............................................. $1,250 │
│ Gutter Cleaning .............................................. $350 │
│ Pressure Washing ............................................. $799 │
│ │
├──────────────────────────────────────────────────────────────────────────┤
│ INTERNAL NOTES │
│ ---------------------------------------------------------------------- │
│ - Steep rear access │
│ - Bring ladder stabilizer │
│ - Heavy moss buildup │
│ │
├──────────────────────────────────────────────────────────────────────────┤
│ AI CONFIDENCE │
│ Roof Area: 92% │
│ Roof Pitch: 61% ⚠ Verify │
│ │
├──────────────────────────────────────────────────────────────────────────┤
│ [Save Draft] [Request Review] [Approve & Push To Jobber] │
└──────────────────────────────────────────────────────────────────────────┘
UX Priorities
- Trustworthy review process
- Human control
- Margin visibility
- Clear AI confidence indicators
Wireframe 6 — Jobber Sync Screen
Primary Goal
Finalize operational handoff cleanly.
Layout Structure
Code:
┌──────────────────────────────────────────────────────────────────────────┐
│ JOBBER SYNC │
├──────────────────────────────────────────────────────────────────────────┤
│ Customer Match │
│ ☑ Existing Customer Found │
│ │
│ Property Match │
│ ☑ Existing Property Found │
│ │
│ Services Mapped │
│ ☑ Roof Cleaning → Jobber Service │
│ ☑ Gutter Cleaning → Jobber Service │
│ ☑ Pressure Washing → Jobber Service │
│ │
│ Sync Status │
│ Ready To Push │
│ │
│ [Push To Jobber] │
│ │
│ SUCCESS │
│ Quote Created Successfully │
│ Jobber Quote #: Q-10294 │
│ │
│ [Open In Jobber] │
└──────────────────────────────────────────────────────────────────────────┘
UX Priorities
- Clear validation
- Low friction
- Operational confidence
- Easy error resolution
26. UX Design Direction
Visual Style
Recommended visual direction:
- Modern SaaS aesthetic
- Dark-mode-first
- Minimal distractions
- High readability
- Clean typography
- Soft panel contrast
- Map-centric layouts
Inspiration References
Recommended inspiration:
- Linear
- Arc Browser
- Notion
- Tesla UI
- Stripe Dashboard
Design Principles
- Fast interactions
- Minimal clicks
- Large touch targets
- AI guidance without clutter
- Context-aware interfaces
- Real-time updates
27. MVP Development Order
Phase 1 — Core Infrastructure
- Authentication
- Database
- Property objects
- Service catalog
- Jobber integration
Phase 2 — Estimating Workflow
- Property intake
- Measurement workspace
- Drawing tools
- Dynamic questions
Phase 3 — Estimate Generation
- Pricing engine
- Good / Better / Best
- AI scope generation
- Review workflow
Phase 4 — Automation & Intelligence
- AI recommendations
- Measurement suggestions
- N8N orchestration
- Market intelligence
Phase 5 — Advanced Features
- AI image analysis
- Recurring maintenance engine
- Reporting
- Commercial workflows
28. Database Architecture & Core Data Model
Core Database Philosophy
The platform should be:
- Property-centric
- Measurement-centric
- Service-template-driven
- Revision-safe
- AI-assisted but human-controlled
The database must support:
- Reusable measurements
- Multi-service workflows
- Historical estimates
- AI recommendations
- Jobber synchronization
- Future recurring maintenance
Core Tables / Objects
1. users
Purpose:
Authentication and permissions.
Core Fields:
- id
- first_name
- last_name
- email
- role
- branch_id
- permissions
- created_at
2. branches
Purpose:
Multi-branch support.
Core Fields:
- id
- branch_name
- region
- pricing_profile_id
- created_at
3. customers
Purpose:
Customer management.
Core Fields:
- id
- first_name
- last_name
- email
- phone
- jobber_customer_id
- notes
- created_at
4. properties
Purpose:
Main property intelligence object.
Core Fields:
- id
- customer_id
- property_address
- city
- state
- zip
- latitude
- longitude
- parcel_id
- property_type
- lot_size
- notes
- created_at
5. measurements
Purpose:
Store reusable property measurements.
Core Fields:
- id
- property_id
- measurement_type
- geometry_data
- measured_value
- unit
- ai_generated
- ai_confidence
- verified_by_user
- created_by
- created_at
Examples:
- Turf polygon
- Roof polygon
- Fence line
- Driveway polygon
6. property_images
Purpose:
Store imagery and uploads.
Core Fields:
- id
- property_id
- image_url
- image_type
- uploaded_by
- ai_processed
- ai_tags
- created_at
7. service_templates
Purpose:
Master service catalog.
Core Fields:
- id
- service_name
- service_category
- measurement_type
- pricing_model
- base_price
- production_rate
- jobber_service_id
- active
- created_at
Examples:
- Roof Cleaning
- Lawn Mowing
- Gutter Cleaning
- Pressure Washing
8. service_modifiers
Purpose:
Difficulty adjustments.
Core Fields:
- id
- service_template_id
- modifier_name
- modifier_type
- modifier_value
- created_at
Examples:
- Steep pitch
- Heavy moss
- Limited access
- Two-story home
9. estimates
Purpose:
Main estimate object.
Core Fields:
- id
- customer_id
- property_id
- estimate_status
- estimate_total
- estimate_version
- ai_generated
- ai_confidence
- approved_by
- created_by
- created_at
10. estimate_line_items
Purpose:
Store estimate services and customer-facing premium line item presentation.
Core Fields:
- id
- estimate_id
- service_template_id
- line_item_name
- customer_friendly_title
- luxury_description
- measurement_type
- quantity
- unit
- unit_price
- total_price
- package_type
- optional_item
- ai_generated_description
- created_at
Package Types:
Estimate Line Item Philosophy
Every line item pushed into Jobber should feel:
- premium
- detailed
- professional
- trustworthy
- luxurious
- highly intentional
The estimate should NEVER feel like:
- a generic contractor invoice
- rushed
- vague
- low-effort
- templated spam
Each line item should include:
- service title
- measurement type
- quantity
- unit pricing
- total pricing
- professionally written customer-facing description
Example — Roof Cleaning Line Item
Service Title
Roof Cleaning Service
Quantity Structure
2,100 Square Feet @ $0.42/SF
Customer-Facing Description
"Our team will carefully perform a comprehensive roof cleaning service across all identified roof surfaces to remove moss, organic buildup, debris, and environmental staining. Special care will be taken to protect surrounding landscaping, gutters, and exterior surfaces throughout the cleaning process. This service is designed to improve curb appeal, extend roof longevity, and restore the overall appearance of the property."
Example — Gutter Cleaning Line Item
Service Title
Full Gutter Cleaning Service
Quantity Structure
180 Linear Feet @ $2.75/LF
Customer-Facing Description
"Our team will thoroughly clean and clear all accessible gutter systems and downspouts to restore proper water flow and drainage performance. Debris, organic buildup, and obstructions will be safely removed to help prevent overflow, water intrusion, and long-term drainage-related issues around the property."
Example — Lawn Maintenance Line Item
Service Title
Premium Lawn Maintenance Service
Quantity Structure
4,200 Square Feet @ $0.08/SF
Customer-Facing Description
"Our team will provide routine lawn maintenance services across all identified turf areas, including precision mowing, trimming, and surface cleanup to maintain a clean, healthy, and professionally maintained exterior appearance. Care will be taken around landscape features, irrigation systems, and property access points throughout service completion."
AI Line Item Generation Rules
AI-generated line items must:
- sound professional and premium
- clearly explain the service value
- avoid sounding robotic
- avoid vague contractor wording
- maintain consistent tone across all services
- include service-specific details
- reinforce professionalism and care
The estimate presentation layer should feel comparable to:
- luxury home service brands
- premium design-build firms
- high-end property maintenance providers
NOT:
- low-cost handyman estimates
- generic invoice systems
- rushed contractor proposals
11. ai_outputs
Purpose:
Store AI-generated content.
Core Fields:
- id
- estimate_id
- output_type
- output_text
- ai_provider
- ai_confidence
- created_at
Examples:
- Customer scope
- Internal notes
- Upsell recommendations
12. estimate_revisions
Purpose:
Track estimate changes.
Core Fields:
- id
- estimate_id
- revision_number
- revision_notes
- revised_by
- created_at
13. jobber_sync_logs
Purpose:
Track Jobber synchronization.
Core Fields:
- id
- estimate_id
- jobber_quote_id
- sync_status
- sync_payload
- sync_response
- synced_at
29. API & Integration Architecture
Integration Philosophy
The platform should:
- integrate deeply
- remain modular
- avoid vendor lock-in
- separate responsibilities cleanly
Core Integrations
1. Jobber API Integration
Purpose:
Operational execution.
Responsibilities:
- Customer sync
- Property sync
- Quote creation
- Line item creation
- Quote updates
- Estimate status tracking
Important:
Jobber remains the operational system of record.
2. N8N Orchestration Layer
Purpose:
Automation and workflow coordination.
Responsibilities:
- AI workflow orchestration
- Market pricing checks
- Notification workflows
- Data enrichment
- Scheduled tasks
- Webhook handling
- Multi-system automations
Examples:
- Estimate approval notifications
- AI processing chains
- Follow-up reminders
- Market pricing enrichment
3. AI Provider Integrations
Recommended Providers:
Responsibilities:
- Scope writing
- Internal note generation
- Service recommendations
- Upsell suggestions
- Package generation
- AI assistance
Important:
AI must remain constrained by:
- business rules
- pricing engine
- service templates
- approval workflows
4. Mapping & Imagery APIs
Potential Providers:
- Google Maps
- Mapbox
- Nearmap
- EagleView
- Roofr APIs
Responsibilities:
- Property lookup
- Aerial imagery
- Parcel overlays
- Measurement assistance
- Geolocation
5. Authentication Layer
Recommended:
Responsibilities:
- User authentication
- Permissions
- Session management
- Branch access
30. API Workflow Architecture
Estimate Generation Workflow
Code:
User Creates Estimate
↓
Property Lookup API
↓
Map & Imagery APIs
↓
AI Measurement Suggestions
↓
Human Verification
↓
Dynamic Questions
↓
Pricing Engine
↓
AI Scope Generation
↓
Estimate Review
↓
Jobber API Sync
↓
Quote Created
31. Pricing Engine Logic Flow
Pricing Pipeline
Code:
Measurement Data
↓
Service Template Rules
↓
Production Rates
↓
Difficulty Modifiers
↓
Margin Protection
↓
Market Intelligence Adjustments
↓
Good / Better / Best Packaging
↓
Final Human Review
32. AI Workflow Architecture
AI Agent Philosophy
Avoid one giant AI prompt.
Instead:
- specialized AI tasks
- modular AI workflows
- controlled context
- isolated responsibilities
AI Task Modules
1. Scope Writer Agent
Generates:
- Customer-facing scopes
- Professional language
- Service explanations
2. Internal Notes Agent
Generates:
- Crew notes
- Access concerns
- Equipment notes
- Safety notes
3. Recommendation Agent
Generates:
- Upsells
- Service recommendations
- Seasonal opportunities
4. Packaging Agent
Generates:
- Good / Better / Best structures
- Optional upgrades
- Recommended bundles
5. Market Intelligence Agent
Generates:
- Regional pricing comparisons
- Competitive positioning
- Pricing suggestions
33. Security & Approval Rules
Estimate Approval Rules
Examples:
- Estimates over $15,000 require manager approval
- AI confidence below 70% requires manual verification
- Pricing overrides require admin permissions
Security Priorities
- Role-based permissions
- Audit logs
- Revision tracking
- API key isolation
- Branch-based visibility
- Secure webhook handling
34. Claude Master Build Prompt Preparation
Claude Development Goals
Claude should build:
- Fast workflows
- Clean architecture
- Reusable components
- Mobile-friendly interfaces
- Map-centric layouts
- AI-assisted UX
Claude should prioritize:
- Speed
- Scalability
- Modularity
- Estimator efficiency
- Operational simplicity
Claude Technical Targets
Frontend
- Next.js
- TypeScript
- Tailwind
- shadcn/ui
Backend
- PostgreSQL
- Supabase
- API-first architecture
Infrastructure
- Docker
- Cloudflare
- VPS or self-hosted deployment
Claude UX Targets
The application should feel:
- premium
- intelligent
- fast
- modern
- estimator-friendly
- operationally efficient
NOT:
- cluttered
- enterprise-heavy
- spreadsheet-like
- form-heavy
35. Next Product Design Steps
Immediate Next Actions
Step 1
Create higher-fidelity UI mockups.
Step 2
Create actual component architecture.
Step 3
Create database schema diagrams.
Step 4
Create API endpoint definitions.
Step 5
Build Claude implementation prompt package.
Step 6
Begin MVP frontend development.
36. Frontend Component Architecture
Frontend Philosophy
The frontend should be:
- component-driven
- modular
- reusable
- fast-loading
- mobile-friendly
- map-centric
- optimized for estimator speed
Recommended Stack:
- Next.js
- TypeScript
- Tailwind
- shadcn/ui
- React Query
- Zustand (lightweight state)
Global Layout Components
AppShell
Purpose:
Main application wrapper.
Contains:
- Top navigation
- Left sidebar
- Main content area
- Responsive layout logic
TopNavigation
Contains:
- Search
- Notifications
- Branch selector
- User profile
- Quick actions
SidebarNavigation
Contains:
- Dashboard
- Estimates
- Properties
- Customers
- Reports
- Settings
Dashboard Components
DashboardOverviewCards
Displays:
- Draft estimates
- Pending approvals
- Jobber sync status
- Revenue metrics
RecentPropertiesList
Displays:
- Recently viewed properties
- Recent estimate activity
- Quick resume actions
AIRecommendationsPanel
Displays:
- Upsell opportunities
- Follow-up reminders
- Recurring maintenance suggestions
Property Components
PropertyHeader
Displays:
- Address
- Property type
- Customer info
- Property tags
PropertySummaryCards
Displays:
- Turf square footage
- Roof square footage
- Gutter footage
- Service history
PropertyTimeline
Displays:
- Estimate history
- Previous services
- Uploaded images
- AI observations
Measurement Workspace Components
MapWorkspace
Core estimating workspace.
Contains:
- Interactive map
- Polygon overlays
- Drawing controls
- AI overlays
- Zone labels
DrawingToolbar
Contains:
- Polygon tool
- Line tool
- Edit tool
- Delete tool
- Undo/redo
- Snap controls
MeasurementSidebar
Displays:
- Selected services
- Measurement totals
- Smart questions
- AI recommendations
LiveEstimatePanel
Displays:
- Live estimate totals
- Good / Better / Best preview
- Margin indicators
- Confidence alerts
Estimate Components
ServiceSelectionGrid
Displays:
- Service cards
- Categories
- Recommended services
- Quick add/remove
PackageComparisonCards
Displays:
- Good package
- Better package
- Best package
- Pricing comparison
- Optional upgrades
EstimateLineItemTable
Displays:
- Line items
- Pricing
- Quantities
- Optional items
- Editable totals
AIScopePreview
Displays:
- Customer-facing scope
- Internal notes
- AI-generated recommendations
ConfidenceWarnings
Displays:
- Low-confidence measurements
- Required manual reviews
- Manager approval warnings
Jobber Integration Components
JobberSyncStatus
Displays:
- Sync validation
- Customer matching
- Property matching
- Service mapping status
JobberPushModal
Handles:
- Final sync confirmation
- Error handling
- Sync progress
- Success states
37. Backend Service Architecture
Backend Philosophy
Backend should be:
- API-first
- modular
- scalable
- event-driven where possible
- integration-friendly
Core Backend Services
Authentication Service
Responsibilities:
- User login
- Permissions
- Sessions
- Branch access
Property Service
Responsibilities:
- Property storage
- Measurement storage
- Property intelligence
- Image management
Measurement Service
Responsibilities:
- Polygon storage
- Geometry calculations
- Measurement validation
- AI measurement ingestion
Pricing Service
Responsibilities:
- Pricing calculations
- Modifiers
- Margin rules
- Market adjustments
- Package pricing
AI Orchestration Service
Responsibilities:
- AI prompt management
- AI task routing
- AI output validation
- Confidence scoring
Estimate Service
Responsibilities:
- Estimate generation
- Line item management
- Revision tracking
- Approval workflows
Jobber Sync Service
Responsibilities:
- Quote creation
- Customer sync
- Property sync
- Error handling
- Sync logging
38. Suggested API Endpoints
Authentication
Code:
POST /api/auth/login
POST /api/auth/logout
GET /api/auth/me
Customers
Code:
GET /api/customers
POST /api/customers
GET /api/customers/:id
Properties
Code:
GET /api/properties
POST /api/properties
GET /api/properties/:id
PUT /api/properties/:id
Measurements
Code:
POST /api/measurements
PUT /api/measurements/:id
DELETE /api/measurements/:id
Estimates
Code:
POST /api/estimates
GET /api/estimates/:id
PUT /api/estimates/:id
POST /api/estimates/:id/review
POST /api/estimates/:id/approve
AI Workflows
Code:
POST /api/ai/generate-scope
POST /api/ai/recommend-services
POST /api/ai/generate-packages
POST /api/ai/internal-notes
Jobber Integration
Code:
POST /api/jobber/sync-estimate
GET /api/jobber/sync-status/:id
39. Higher-Fidelity UI Direction
Visual Identity Goals
The application should visually communicate:
- intelligence
- speed
- professionalism
- operational clarity
- premium service quality
Color Direction
Primary Themes:
- Dark charcoal backgrounds
- Deep forest green accents
- White/light gray typography
- Subtle blue highlights
- Soft borders and shadows
Typography Direction
Recommended:
- Inter
OR
- Geist
OR
- SF Pro-style typography
Typography Goals:
- High readability
- Modern SaaS appearance
- Clean spacing
- Strong hierarchy
UI Design Style
Recommended:
- Rounded cards
- Soft shadows
- Minimal borders
- Dense but readable information
- Smooth transitions
- Large touch targets
Avoid:
- Heavy gradients
- Skeuomorphic design
- Busy dashboards
- Overly corporate enterprise UI
40. Claude Master Implementation Prompt (Draft)
Product Summary
Build a modern AI-assisted exterior property estimate platform that accelerates estimate creation for exterior service companies.
The platform should:
- Load property intelligence
- Support map-based measurement workflows
- Allow human-guided polygon drawing
- Generate Good / Better / Best estimate packages
- Use AI for scopes and recommendations
- Push finalized estimates into Jobber
The platform is NOT intended to:
- Replace Jobber
- Handle accounting
- Replace CRM workflows
- Manage payroll
Core UX Requirements
The application should feel:
- Fast
- Premium
- Intelligent
- Guided
- Minimal
- Map-centric
- Estimator-friendly
The application should NOT feel:
- Spreadsheet-heavy
- Form-heavy
- Enterprise-bloated
- Slow
Core Technical Requirements
Use:
- Next.js
- TypeScript
- Tailwind
- shadcn/ui
- PostgreSQL
- Supabase
- API-first architecture
Prioritize:
- Component reusability
- Fast interactions
- Modular architecture
- Responsive layouts
- Touch-friendly workflows
Core Product Workflows
Workflow:
Address Lookup
↓
Property Intelligence
↓
AI Measurement Suggestions
↓
Human Verification
↓
Dynamic Questions
↓
Pricing Engine
↓
Good / Better / Best
↓
AI Scope Generation
↓
Human Review
↓
Push To Jobber
Key Product Features
- Property-centric architecture
- Reusable measurements
- Polygon-based map drawing
- AI-assisted recommendations
- Dynamic contextual questions
- Pricing engine with modifiers
- Good / Better / Best packaging
- Jobber quote synchronization
- Human approval workflows
Initial MVP Priority
Build first:
- Authentication
- Dashboard
- Property intake
- Map measurement workspace
- Estimate builder
- AI review screen
- Jobber integration
Do NOT overbuild advanced features initially.
Focus on:
- estimator speed
- workflow simplicity
- operational clarity
- scalable architecture
41. Phase 2 — Implementation Blueprint
MVP Build Strategy
The MVP should prioritize:
- speed-to-market
- workflow validation
- estimator usability
- operational efficiency
- stable integrations
The goal is NOT perfection.
The goal is:
- rapid estimating
- clean Jobber quote creation
- repeatable workflows
- scalable architecture
Recommended Development Order
Sprint 1 — Core Foundation
Goals:
- Project setup
- Authentication
- Database setup
- UI framework
- Navigation
- Property objects
Deliverables:
- Working login
- Dashboard shell
- Sidebar navigation
- Property creation
- Customer creation
Sprint 2 — Property Intelligence
Goals:
- Property lookup
- Address autocomplete
- Map integration
- Imagery loading
- Property profile pages
Deliverables:
- Interactive map
- Address search
- Property pages
- Property history
- Basic measurements
Sprint 3 — Measurement Workspace
Goals:
- Polygon drawing
- Line measurements
- Zone editing
- Overlay system
- Measurement storage
Deliverables:
- Turf polygons
- Roof polygons
- Gutter measurements
- Editable overlays
- Saved measurements
Critical:
This is the heart of the platform.
Sprint 4 — Service & Pricing Engine
Goals:
- Service catalog
- Pricing rules
- Modifiers
- Dynamic questions
- Package builder
Deliverables:
- Service selection
- Pricing engine
- Good / Better / Best
- Difficulty modifiers
- Dynamic workflow questions
Sprint 5 — AI Integration
Goals:
- AI scopes
- AI internal notes
- Recommendation engine
- Upsell generation
Deliverables:
- Customer-facing descriptions
- Internal crew notes
- AI recommendations
- Package recommendations
Important:
AI must remain constrained by:
- service templates
- pricing rules
- approval workflows
Sprint 6 — Jobber Integration
Goals:
- Customer sync
- Property sync
- Quote creation
- Line item generation
Deliverables:
- Jobber quote sync
- Jobber line item formatting
- Premium estimate formatting
- Sync logging
- Error handling
Critical:
Jobber estimates must feel:
- premium
- polished
- luxurious
- professional
Sprint 7 — Workflow Refinement
Goals:
- Speed optimization
- Mobile responsiveness
- Estimator testing
- UX refinement
Deliverables:
- Faster workflows
- Better touch interactions
- Reduced clicks
- Cleaner interfaces
- Better AI confidence flows
42. Estimator Workflow Optimization Philosophy
Every Screen Must Ask:
"Does this reduce estimate creation time?"
If the answer is no:
- simplify it
- automate it
- remove it
Workflow Goals
Target Metrics
| Goal | Target |
|---|
| Estimate creation time | Under 5 minutes |
| Property lookup | Under 10 seconds |
| Map load speed | Under 3 seconds |
| Jobber sync | Under 5 seconds |
| Estimate approval flow | Under 1 minute |
Estimator Experience Goals
The estimator should feel:
- guided
- confident
- fast
- intelligent
- professional
The workflow should feel like:
- using a premium SaaS platform
NOT
- filling out contractor forms
43. Mobile & Tablet Workflow Strategy
Primary Device Assumption
Estimators will commonly use:
- iPads
- tablets
- laptops in truck
- mobile phones onsite
Mobile UX Priorities
Touch Optimization
Must support:
- touch drawing
- polygon editing
- quick toggles
- swipe interactions
- camera uploads
- one-handed navigation where possible
Responsive Layout Strategy
Desktop
Three-panel estimating workspace.
Tablet
Collapsible side panels.
Mobile
Stacked workflow with bottom action tray.
Offline Considerations (Future)
Future support for:
- temporary offline measurements
- queued uploads
- delayed Jobber sync
- cached property data
44. N8N Workflow Architecture
N8N Philosophy
N8N acts as:
- orchestration engine
- automation engine
- integration router
- AI workflow coordinator
NOT:
- primary application backend
Core N8N Workflows
Workflow 1 — AI Scope Generation
Trigger:
Estimate ready for AI generation.
Workflow:
- Gather measurements
- Gather selected services
- Gather package structure
- Send to AI provider
- Return formatted scope
- Save to estimate
Workflow 2 — Market Pricing Intelligence
Trigger:
Estimate pricing review.
Workflow:
- Check regional market data
- Compare pricing targets
- Suggest adjustment ranges
- Return pricing guidance
Important:
Never directly overwrite pricing.
Workflow 3 — Jobber Sync Workflow
Trigger:
Estimate approved.
Workflow:
- Validate customer
- Validate property
- Build line items
- Push quote to Jobber
- Store sync logs
- Notify estimator
Workflow 4 — Follow-Up Automation
Trigger:
Estimate not accepted.
Workflow:
- Send reminders
- Create follow-up tasks
- Recommend upsells
- Track customer engagement
45. High-Fidelity Mockup Direction
Visual Design Direction
The UI should resemble:
- premium SaaS products
- modern operational software
- clean design systems
- intelligent dashboards
Recommended inspiration:
- Linear
- Vercel
- Stripe
- Arc Browser
- Notion
Layout Personality
The interface should feel:
- calm
- intelligent
- fast
- uncluttered
- operationally powerful
UI Density Strategy
Avoid:
- giant empty spaces
- oversized cards
- excessive animations
Prefer:
- dense but readable layouts
- fast scanning
- compact operational UI
- contextual information panels
46. Final Product Positioning
Product Positioning Statement
USNW Estimate Platform is an AI-assisted exterior property intelligence and estimate acceleration platform that transforms aerial imagery, measurements, and estimator workflows into premium customer-ready Jobber estimates in minutes.
Core Differentiators
1. Property Intelligence Layer
Reusable measurements and property history.
2. Human-Guided AI
AI-assisted, not AI-dependent.
3. Premium Estimate Presentation
Luxury-quality line item descriptions.
4. Good / Better / Best Automation
Built-in upsell workflows.
5. Jobber Acceleration
Operational workflows remain inside Jobber.
Final Product Philosophy
The platform exists to:
- reduce estimate creation time
- improve estimate quality
- increase upsells
- improve operational consistency
- accelerate sales workflows
- create reusable property intelligence
The platform should always prioritize:
- speed
- clarity
- professionalism
- estimator usability
- scalable architecture
47. Visual Design System Direction Package
Design Philosophy
The application should visually feel like:
- a premium operational platform
- a modern AI-assisted SaaS product
- a luxury service business command center
- a high-speed estimator workspace
The interface should NOT feel like:
- old contractor software
- spreadsheet software
- generic CRM systems
- enterprise accounting tools
The visual system should communicate:
- intelligence
- trust
- speed
- professionalism
- operational precision
Visual Personality
Desired Feelings
The estimator should feel:
- confident
- fast
- guided
- efficient
- technologically empowered
The customer-facing estimate should feel:
- luxurious
- polished
- premium
- trustworthy
- intentional
UI Inspiration References
Recommended inspiration:
Operational UX
- Linear
- Stripe Dashboard
- Vercel
- Arc Browser
Visual Simplicity
- Notion
- Raycast
- Superhuman
Map & Workspace Feel
- Figma
- Google Maps
- Nearmap
Color Palette Direction
Base Colors
Primary Background
Deep charcoal / near-black
Example:
Secondary Panels
Soft elevated dark panels
Example:
Accent Color
Deep forest green
Example:
Purpose:
- buttons
- active states
- recommendations
- success indicators
Secondary Accent
Subtle modern blue
Example:
Purpose:
- AI actions
- overlays
- helper states
- active measurements
Warning Color
Soft amber/orange
Purpose:
- low AI confidence
- review required
- sync warnings
Typography Direction
Recommended Fonts
Typography Philosophy
Typography should feel:
- clean
- highly readable
- modern
- operationally dense
- premium
Avoid:
- playful typography
- oversized headings
- excessive weight variation
Layout Philosophy
Core Layout Structure
The app should use:
Left Sidebar
Persistent navigation.
Top Bar
Quick actions + global controls.
Main Workspace
Primary operational area.
Context Panels
Right-side contextual workflows.
Workspace Philosophy
The map workspace is the centerpiece.
The estimating workflow should feel like:
- Figma
- modern GIS tools
- operational command center
NOT:
- form filling
- spreadsheet entry
Panel Design Philosophy
Panels should:
- float subtly above background
- use soft borders
- use layered depth
- remain compact and readable
Avoid:
- thick borders
- harsh shadows
- cluttered cards
Button Philosophy
Buttons should feel:
- clean
- intentional
- premium
- minimal
Primary CTA buttons:
- slightly larger
- green accent
- high visibility
Examples:
- Push To Jobber
- Review Estimate
- Generate Packages
Form Philosophy
Forms should:
- minimize typing
- maximize selections/toggles
- use autocomplete heavily
- support keyboard shortcuts
- support touch workflows
Avoid:
- giant forms
- excessive dropdown nesting
- repetitive manual entry
Data Density Philosophy
The platform should support:
- dense operational information
- fast scanning
- compact workflows
Avoid:
- oversized widgets
- excessive whitespace
- giant enterprise cards
Animation Philosophy
Animations should:
- feel subtle
- improve usability
- reinforce speed
Avoid:
- flashy transitions
- excessive motion
- gimmicky effects
Recommended:
- subtle fades
- panel slides
- smooth hover states
- micro-interactions only
Measurement Workspace Visual Direction
Core Principle
The map is the hero.
Everything else supports the map.
Workspace Layout
Left Panel
Operational workflow.
Contains:
- services
- questions
- recommendations
- workflow progress
Center Workspace
Interactive aerial map.
Contains:
- polygons
- overlays
- measurements
- AI detection zones
- drawing tools
Right Panel
Live estimate intelligence.
Contains:
- pricing
- package preview
- AI confidence
- upsells
- estimate totals
Good / Better / Best Visual Philosophy
This screen should feel:
- premium
- sales-oriented
- visually persuasive
- easy to compare
The “Better” package should usually appear visually emphasized.
Recommended:
- subtle glow
- highlighted border
- recommendation badge
Estimate Presentation Philosophy
Customer-facing estimates should feel:
- luxurious
- premium
- trustworthy
- thoughtfully prepared
The customer should feel:
"This company is highly organized and professional."
NOT:
"This is a generic contractor quote."
Jobber Sync UX Philosophy
The sync process should feel:
- safe
- validated
- operationally reliable
Avoid:
- confusing sync states
- technical API language
- unclear failures
48. High-Fidelity Mockup Plan
Initial Mockups To Create
Mockup 1 — Main Dashboard
Goals:
- premium command center feel
- operational clarity
- fast estimate access
Mockup 2 — Property Intake
Goals:
- rapid estimate initiation
- minimal typing
- intelligent suggestions
Mockup 3 — Measurement Workspace
Goals:
- map-first estimating workflow
- AI-assisted measurements
- live estimate updates
Critical:
This is the flagship screen.
Mockup 4 — Good / Better / Best Builder
Goals:
- premium sales presentation
- easy package comparison
- upsell visibility
Mockup 5 — AI Estimate Review
Goals:
- premium line item presentation
- confidence visibility
- approval workflows
Mockup 6 — Jobber Sync Screen
Goals:
- operational trust
- clean validation
- simple workflow completion
49. Mockup Execution Strategy
Mockup Priorities
The mockups should prioritize:
- layout hierarchy
- workflow clarity
- interaction flow
- operational speed
- visual polish direction
The mockups do NOT need:
- production-perfect visuals
- advanced animations
- final branding assets
- marketing graphics
Mockup Creation Workflow
Step 1
Establish layout structure.
Step 2
Establish spacing system.
Step 3
Apply dark-theme visual system.
Step 4
Apply operational hierarchy.
Step 5
Validate estimating workflow speed.
Step 6
Convert into Claude implementation prompts.
50. Immediate Next Build Phase
Current Status
The product is now:
- architected
- scoped
- workflow-defined
- visually directed
- implementation-ready
Immediate Next Phase
The next step is:
creating visual mockups for the core workflow screens.
Priority order:
- Measurement Workspace
- Dashboard
- Good / Better / Best Builder
- AI Estimate Review
- Property Intake
- Jobber Sync
Post-Mockup Workflow
Once mockups are complete:
Step 1
Create screen-specific Claude prompts.
Step 2
Begin frontend scaffolding.
Step 3
Build Supabase schema.
Step 4
Build map measurement workflows.
Step 5
Build AI orchestration.
Step 6
Build Jobber synchronization.
Final Recommendation
The Measurement Workspace should become the flagship screen and defining UX experience of the entire platform.
If that screen feels:
- intelligent
- fast
- premium
- guided
- operationally powerful
then the rest of the platform will naturally feel valuable and differentiated.
51. Flagship Screen — Measurement Workspace Mockup Specification
Purpose
The Measurement Workspace is the heart of the platform.
This screen should:
- dramatically reduce estimate creation time
- guide estimators intelligently
- provide live pricing feedback
- create reusable property intelligence
- generate premium Jobber-ready estimates
This screen is the platform’s:
- operational center
- AI collaboration layer
- estimating engine
- sales acceleration workspace
Screen Goals
The estimator should be able to:
- load a property
- draw or verify measurements
- answer contextual questions
- build Good / Better / Best packages
- generate estimate scopes
- push into Jobber
all from a single workflow-oriented workspace.
Core Layout Structure
Code:
┌──────────────────────────────────────────────────────────────────────────────┐
│ TOP NAV │
│ Logo | Search | Global Actions | Notifications | User | Branch │
├────────────────┬─────────────────────────────────────┬──────────────────────┤
│ LEFT PANEL │ CENTER MAP WORKSPACE │ RIGHT PANEL │
│ │ │ │
│ Workflow Steps │ Interactive Aerial Map │ Live Estimate │
│ │ │ │
│ Services │ AI Overlay Zones │ Estimate Total │
│ Questions │ Polygon Drawing │ Package Preview │
│ Recommendations│ Line Measurement │ Line Items │
│ Progress │ Measurement Labels │ AI Confidence │
│ │ │ Push To Jobber CTA │
└────────────────┴─────────────────────────────────────┴──────────────────────┘
LEFT PANEL SPECIFICATION
Purpose
Guide the estimator through the workflow.
This panel acts like:
- intelligent copilot
- workflow navigator
- contextual assistant
Section 1 — Workflow Progress
Displays:
Code:
1. Property Loaded ✓
2. Measurements In Progress
3. Questions Pending
4. Packages Generated
5. Estimate Review
6. Ready For Jobber
Purpose:
- reduce confusion
- reinforce workflow completion
- guide estimators step-by-step
Section 2 — Selected Services
Displays active services.
Example:
Code:
☑ Roof Cleaning
☑ Gutter Cleaning
☑ Pressure Washing
☐ Lawn Maintenance
Features:
- toggle on/off
- quick add services
- AI-recommended badges
Section 3 — Dynamic Questions
Questions dynamically generated.
Examples:
Code:
Roof Pitch?
( ) Low
( ) Medium
( ) Steep
Heavy Moss?
[ Yes / No ]
Stories?
[ 1 ] [ 2 ] [ 3+ ]
UX Goals:
- no typing when possible
- fast interactions
- touch-friendly
Section 4 — AI Recommendations
Displays:
- upsells
- service recommendations
- recurring opportunities
Example:
Code:
Recommended:
+ Moss Treatment
+ Concrete Cleaning
+ Aeration Package
Purpose:
- increase average ticket size
- surface hidden opportunities
CENTER MAP WORKSPACE SPECIFICATION
Purpose
This is the visual estimating engine.
The map is the centerpiece of the product.
Core Features
Aerial Imagery
Supports:
- satellite imagery
- parcel overlays
- seasonal imagery (future)
- property outlines
Polygon Drawing
Supports:
- turf areas
- roof sections
- mulch beds
- concrete zones
Features:
- drag handles
- editable vertices
- snap-to-edge
- duplicate zone
- rename zones
Line Measurement Tools
Supports:
- gutters
- fence lines
- rooflines
- edging
Features:
- snap measurement
- linear labels
- live footage updates
AI Overlay Suggestions
AI attempts to identify:
- roof sections
- concrete
- turf
- driveways
- gutters
- mulch areas
These appear as:
- translucent overlay zones
- confidence-labeled suggestions
Example:
Code:
AI Turf Detection
Confidence: 94%
Important:
AI overlays are suggestions only.
Humans always remain in control.
Visual Overlay System
Suggested Color Logic
Green:
Blue:
Amber:
Gray:
RIGHT PANEL SPECIFICATION
Purpose
Provide live operational estimate intelligence.
The estimator should always see:
- pricing
- package structure
- estimate totals
- AI confidence
- Jobber readiness
without changing screens.
Section 1 — Measurement Summary
Example:
Code:
Roof Area: 2,100 SF
Concrete: 850 SF
Gutters: 180 LF
Purpose:
- quick validation
- operational clarity
Section 2 — Live Pricing Preview
Example:
Code:
Roof Cleaning
2,100 SF @ $0.42/SF
= $882
Gutter Cleaning
180 LF @ $2.75/LF
= $495
Purpose:
- real-time estimate feedback
- transparent pricing
Section 3 — Good / Better / Best Preview
Compact package comparison.
Example:
Code:
GOOD — $899
BETTER — $1,499 ⭐
BEST — $2,250
Features:
- highlight recommended package
- quick toggles
- expandable details
Section 4 — AI Confidence & Warnings
Example:
Code:
Roof Pitch Confidence: 62%
⚠ Manual Review Recommended
Purpose:
- operational trust
- human validation
- estimate safety
Section 5 — Primary Actions
Primary CTA:
Secondary CTAs:
- Save Draft
- Request Approval
- Push To Jobber
Measurement Workspace Interaction Philosophy
Core UX Principle
The estimator should:
- rarely leave this screen
- rarely type manually
- always feel guided
- always understand estimate status
Workflow Philosophy
The screen should feel like:
- a modern GIS tool
- AI-assisted estimating workspace
- operational command center
NOT:
- a form
- spreadsheet software
- legacy contractor software
Performance Targets
Interaction Targets
| Action | Target |
|---|
| Polygon drag | Instant |
| Measurement update | Real-time |
| Package update | Under 1 second |
| AI suggestions | Under 5 seconds |
| Map load | Under 3 seconds |
Mobile & Tablet Adaptation
Desktop
Three-panel layout.
Tablet
Collapsible side panels.
Mobile
Map-first stacked workflow.
Priority:
Map interaction remains primary.
52. High-Fidelity Dashboard Mockup Specification
Dashboard Goals
The dashboard should feel like:
- an operational command center
- a premium SaaS platform
- a productivity accelerator
NOT:
- a cluttered CRM homepage
- an accounting dashboard
Dashboard Layout
Code:
┌────────────────────────────────────────────────────────────┐
│ TOP NAV │
├──────────────┬─────────────────────────────────────────────┤
│ LEFT SIDEBAR │ MAIN DASHBOARD │
│ │ │
│ Dashboard │ KPI Overview Cards │
│ Estimates │ Recent Estimate Activity │
│ Properties │ AI Recommendations │
│ Customers │ Quick Actions │
│ Reports │ Recurring Revenue Opportunities │
│ Settings │ Recent Properties │
└──────────────┴─────────────────────────────────────────────┘
KPI Overview Cards
Examples:
Code:
Estimates Created Today
Pending Approval
Average Ticket Size
Recurring Opportunities
Jobber Sync Queue
Design Goals:
- compact
- highly scannable
- operationally useful
AI Recommendations Panel
Examples:
Code:
3 Properties Due For Follow-Up
5 Recurring Lawn Renewals Available
2 Roof Cleaning Upsells Detected
Purpose:
- revenue acceleration
- proactive sales workflows
Quick Actions
Primary CTAs:
- New Estimate
- Resume Estimate
- Search Property
- Review Approvals
53. High-Fidelity Estimate Review Mockup Specification
Screen Goals
This screen should:
- build trust
- validate AI outputs
- present premium estimates
- prepare Jobber-ready line items
Core Layout
Code:
┌────────────────────────────────────────────────────────────┐
│ Estimate Summary │
├────────────────────────────────────────────────────────────┤
│ Customer Scope │
├────────────────────────────────────────────────────────────┤
│ Premium Line Items │
├────────────────────────────────────────────────────────────┤
│ Internal Notes │
├────────────────────────────────────────────────────────────┤
│ AI Confidence & Warnings │
├────────────────────────────────────────────────────────────┤
│ Approval Actions │
└────────────────────────────────────────────────────────────┘
Premium Line Item Presentation
Each line item should visually include:
- service title
- quantity
- measurement type
- unit pricing
- total pricing
- premium customer-facing description
Example:
Code:
Roof Cleaning Service
2,100 SF @ $0.42/SF
Total: $882
Our team will carefully perform a comprehensive roof cleaning service across all identified roof surfaces to remove moss, organic buildup, debris, and environmental staining...
Approval Workflow
Primary Actions:
- Approve Estimate
- Save Draft
- Request Manager Review
- Push To Jobber
Important:
This screen should reinforce:
- professionalism
- estimate quality
- operational confidence
54. Screen-By-Screen Claude Build Prompt Package
Purpose
The following prompts are intended to be used directly with Claude to begin frontend implementation.
Each prompt is:
- modular
- screen-specific
- workflow-focused
- architecture-aligned
This prevents:
- inconsistent UI
- architectural drift
- random workflows
- poor component reuse
Claude Prompt 1 — Global App Shell
Objective
Build the global application shell for the USNW Estimate Platform.
Requirements:
- Next.js App Router
- TypeScript
- Tailwind
- shadcn/ui
- Dark-mode-first
- Responsive layout
Build:
- Left sidebar navigation
- Top navigation bar
- Global search
- Notification area
- User profile dropdown
- Branch selector
- Main content layout system
Visual style:
- premium SaaS
- modern operational dashboard
- compact but readable
- deep charcoal backgrounds
- forest green accents
The application should resemble:
Avoid:
- enterprise bloat
- spreadsheet aesthetics
- oversized cards
- excessive whitespace
Claude Prompt 2 — Dashboard Screen
Objective
Build the Main Dashboard screen.
Requirements:
- KPI cards
- Recent estimates list
- AI recommendations panel
- Quick action buttons
- Recent properties panel
- Responsive layout
The dashboard should feel:
- operationally powerful
- fast
- uncluttered
- estimator-focused
Add:
- compact KPI cards
- hover interactions
- quick estimate creation CTA
- subtle panel elevation
Include example AI recommendations:
- recurring opportunities
- follow-up reminders
- upsell opportunities
Design goals:
- dense operational UI
- modern SaaS feel
- minimal clicks
Claude Prompt 3 — Property Intake Screen
Objective
Build the Property Intake screen.
Requirements:
- customer search/create
- address autocomplete
- property type selector
- initial service selector
- continue workflow CTA
The screen should:
- minimize typing
- prioritize speed
- feel intelligent
- guide the estimator naturally
Use:
- autocomplete inputs
- service cards
- quick selection toggles
- modern form styling
Target:
An estimator should begin an estimate in under 30 seconds.
Claude Prompt 4 — Measurement Workspace (Flagship Screen)
Objective
Build the flagship Measurement Workspace screen.
This is the most important screen in the platform.
Layout:
- Left workflow panel
- Center map workspace
- Right live estimate panel
The map must remain the centerpiece.
Left Panel Requirements
Include:
- workflow progress
- selected services
- dynamic questions
- AI recommendations
- workflow completion states
Questions should use:
- toggles
- segmented controls
- dropdown chips
Avoid large forms.
Center Workspace Requirements
Include:
- interactive map container
- polygon overlays
- line measurement tools
- editable zones
- AI suggestion overlays
- measurement labels
- drawing toolbar
The workspace should feel like:
- Figma
- modern GIS tools
- operational software
NOT:
- legacy contractor software
Right Panel Requirements
Include:
- measurement summaries
- live pricing preview
- Good / Better / Best preview
- AI confidence warnings
- estimate totals
- review CTA
Live pricing updates should feel instant.
Visual Direction
The screen should feel:
- intelligent
- premium
- operationally fast
- AI-assisted
- visually calm
Use:
- subtle panel elevation
- layered dark surfaces
- compact operational density
- smooth hover states
Avoid:
- clutter
- giant cards
- excessive whitespace
Claude Prompt 5 — Good / Better / Best Builder
Objective
Build the Good / Better / Best package builder.
Requirements:
- three-column comparison layout
- pricing comparison
- recommended package highlighting
- optional add-ons
- expandable package details
The “Better” package should usually appear visually emphasized.
This screen should feel:
- sales-oriented
- premium
- visually persuasive
- easy to compare
Include:
- recommendation badges
- package total summaries
- optional upgrades
- add/remove interactions
Claude Prompt 6 — AI Estimate Review Screen
Objective
Build the AI Estimate Review screen.
Requirements:
- customer-facing scope section
- premium line item presentation
- internal notes panel
- AI confidence warnings
- approval actions
Line items MUST include:
- service title
- quantity
- unit measurement
- unit pricing
- total pricing
- premium customer-facing description
Example:
Roof Cleaning Service
2,100 SF @ $0.42/SF
The estimate should feel:
- luxurious
- highly professional
- thoughtfully prepared
- premium-quality
Avoid:
- generic contractor estimate styling
- spreadsheet appearance
- low-detail line items
Claude Prompt 7 — Jobber Sync Screen
Objective
Build the Jobber Sync confirmation workflow.
Requirements:
- customer validation
- property validation
- service mapping review
- sync status display
- success/failure states
- push confirmation CTA
The sync workflow should feel:
- operationally reliable
- validated
- trustworthy
- clean and simple
Avoid:
- technical API language
- cluttered sync states
- confusing errors
55. Frontend Development Standards
Component Standards
All components should:
- be reusable
- use TypeScript
- use consistent spacing
- support responsive layouts
- support dark mode
- follow accessibility best practices
State Management Philosophy
Use:
- lightweight state
- localized state where possible
- React Query for server state
- Zustand for app state if needed
Avoid:
- overly complex global state
- Redux unless truly necessary
Styling Standards
Use:
- Tailwind utility classes
- shadcn/ui components
- consistent spacing scale
- soft border system
- compact operational density
Avoid:
- inline styles
- inconsistent spacing
- excessive custom CSS
Animation Standards
Animations should:
- improve usability
- feel subtle
- reinforce responsiveness
Use:
- micro-interactions
- subtle fades
- panel transitions
- hover feedback
Avoid:
- flashy motion
- large transitions
- unnecessary animation
56. Recommended Initial Technical Stack
Frontend
Recommended:
- Next.js 15+
- TypeScript
- Tailwind CSS
- shadcn/ui
- React Query
- Zustand
Backend
Recommended:
- Supabase
- PostgreSQL
- Edge Functions where needed
Infrastructure
Recommended:
- Docker
- Cloudflare
- VPS deployment initially
AI Stack
Recommended:
- Claude for scopes/descriptions
- OpenAI for embeddings/search
- N8N for orchestration
Mapping Stack
Potential options:
- Google Maps
- Mapbox
- Nearmap
- EagleView
57. Immediate Build Execution Plan
Immediate Next Actions
Action 1
Feed the Global App Shell prompt into Claude.
Action 2
Build the Dashboard screen.
Action 3
Build the Property Intake screen.
Action 4
Build the Measurement Workspace screen.
Action 5
Refine UX interactions.
Action 6
Connect Supabase backend.
Action 7
Implement Jobber integration.
Final Build Philosophy
The platform should always optimize for:
- estimate speed
- estimator confidence
- premium presentation
- operational consistency
- scalable architecture
- reusable property intelligence
The Measurement Workspace remains the flagship experience and core differentiator of the platform.
