Project Proposal

AI Lead Assistant

AI-powered chat widget that qualifies leads, generates estimates, and creates jobs in Jobber - built for Kemp Concrete Group
Prepared by James Douglas K Camanse | Lonely Pine AI | March 2026

The Problem We're Solving

Every lead that hits your website and doesn't get a fast, intelligent response is revenue walking away. The AI Lead Assistant captures, qualifies, and routes leads automatically - 24/7.

24/7
Lead Capture Coverage
<60s
Response Time to Visitors
0
Leads Lost to Voicemail

Website Visitor

Chat widget on WordPress

Claude AI

Qualifies, quotes, answers

n8n Orchestration

Routes data, triggers actions

Jobber + Twilio

Creates leads, sends alerts

Why This Approach Works

The conversation layer (Claude) is separated from the business logic layer (n8n). This means you can update pricing rules, add services, or change routing logic without touching the AI conversation design. Your rates live in an external config - not buried in code.

System Architecture

Four layers, cleanly separated. Each one does one job well.

UI

Frontend - Chat Widget

Lightweight widget embedded on your WordPress site.

  • Clean, branded UI matching Kemp Concrete's look
  • Mobile-responsive
  • Loads fast, no page-speed impact
  • Conversation history per visitor
AI

AI Engine - Claude API

Handles natural conversation and lead qualification.

  • Understands concrete services and terminology
  • Asks qualifying questions (project type, size, timeline)
  • Generates rough estimates using your pricing rules
  • Knows when to escalate to a human
n8n

Orchestration - n8n

The brain that connects everything together.

  • Routes qualified leads to Jobber
  • Triggers Twilio SMS/call alerts
  • Pulls pricing rules from your config
  • Logs every interaction for your records
API

Integrations - Jobber + Twilio

Your existing tools, connected automatically.

  • Creates leads/requests in Jobber via GraphQL API
  • Updates job records with conversation context
  • SMS notifications for hot leads
  • Call escalation for urgent requests

Two-Week Build Timeline

From kickoff to live on your WordPress site in 14 days.

1
Days 1-2

Jobber API + Pricing Config

Map out Jobber's GraphQL schema, build the lead creation and job update mutations, and set up your pricing rules in an external config file you can edit anytime.

Jobber API Integration Pricing Config (Editable) API Authentication
2
Days 3-5

Claude Conversation Engine

Build the AI conversation layer - trained on your services, pricing, and qualification criteria. Claude handles the dialogue; pricing rules are pulled from your config at runtime.

Claude API Integration Service Knowledge Base Lead Qualification Logic Estimate Generation
3
Days 6-8

n8n Workflows + Twilio

Wire up the orchestration layer - every qualified lead flows into Jobber automatically, SMS alerts fire for hot leads, and call escalation routes to your team.

n8n Workflow Engine Twilio SMS/Call Lead Routing Logic Notification Rules
4
Days 9-10

WordPress Widget + Integration Testing

Embed the chat widget on kempconcretegroup.com, style it to match your brand, and run end-to-end testing across the full pipeline - from visitor question to Jobber lead.

WordPress Chat Widget Brand Styling End-to-End Testing
5
Days 11-14

Edge Cases, Client Testing + Handoff

You test it live. We refine conversation flows, handle edge cases, tune the estimate accuracy, and document everything for your team. You go live with confidence.

Client UAT Edge Case Handling Documentation Handoff + Training

What You Own at Handoff

Everything is yours. No vendor lock-in. Full source code and documentation.

UI

Chat Widget

Branded, mobile-responsive widget live on your WordPress site

AI

AI Conversation Engine

Claude-powered assistant trained on your services and pricing

$

Editable Pricing Config

Update rates and services yourself - no developer needed

n8n

n8n Workflow Suite

Lead routing, notifications, and Jobber sync - all automated

API

Jobber Integration

Leads and job records created automatically via GraphQL API

SMS

Twilio Alerts

SMS notifications and call escalation for priority leads

DOC

Full Documentation

System docs, architecture diagrams, and admin guide

</>

Source Code

Complete codebase - backend, widget, workflows, configs

Post-Launch Support Included

After handoff, I remain available for four weeks during your testing period. Bug fixes, conversation tuning, Jobber workflow adjustments - whatever comes up as your team puts it through real-world use.

Onboarding Checklist

Everything I need from you to hit the ground running on Day 1. Most of this takes 15-20 minutes to gather.

A

Access and Credentials

Jobber API Key

API key or OAuth credentials from your Jobber account. I'll need permission to create leads/requests and read job records.

Twilio Account

Account SID and Auth Token. If you don't have Twilio yet, I can help set it up - takes about 10 minutes.

WordPress Admin Login

Admin access to kempconcretegroup.com for installing the chat widget and matching your site's styling.

Notification Phone Numbers

Which phone numbers should receive SMS alerts when a hot lead comes in? Can be one person or multiple.

B

Business Rules and Pricing

Pricing / Rate Card

Your current rates - per square foot, per cubic yard, by service type, minimum job sizes. Whatever format you have is fine; I'll structure it.

Service Area Boundaries

Which cities, counties, or zip codes do you serve? Any areas you don't cover? This keeps the assistant from booking out-of-range work.

Service List

Full list of services you want the assistant to quote on: driveways, patios, foundations, sidewalks, stamped concrete, repairs, etc.

Qualification Criteria

What makes a lead worth pursuing? Minimum project size, residential vs. commercial, timeline requirements, any deal-breakers.

C

Conversation and Workflow Preferences

Escalation Rules

When should the assistant hand off to a human? Examples: commercial projects over a certain size, urgent timelines, repeat customers, complaints.

Brand Voice Notes

How should the assistant sound? Professional and formal, or friendly and direct? Any phrases you use or avoid? "Doing It Right" tone guidance.

Common Customer Questions

The top 10-15 questions your office handles repeatedly. Turnaround times, warranty info, seasonal availability, payment terms, etc.

Jobber Workflow Preferences

How do you currently organize leads in Jobber? Any tags, custom fields, or assignment rules you want the assistant to follow?

Ready to Build?

14 days from kickoff to a live AI lead assistant on your website, creating qualified leads in Jobber automatically.

Schedule Onboarding