Job It Ready

The front desk for trades that don't have one. A customer photographs a problem, Job It Ready prices it off the business's own price sheet, and books the job onto their calendar — no receptionist, no waiting for a callback.

Product

A web platform for independent service businesses (plumbers, electricians, detailers, and any trade that prices jobs from a photo) to run an AI-powered quote intake: customers send a photo and a couple of sentences, get an instant priced estimate, and book directly. The business gets a lead inbox, a branded proposal generator, and an embeddable widget + shareable link for their own site and socials.

Target user: someone newer to running a service business — solo or small-crew, any trade, checking this on a phone between jobs — not a power user of software. Even more so if you've never had to build a proposal, invoice, or receipt before: the AI gives you a starting point instead of a blank page.

Stack

• React 19 + TanStack Start (file-based routing, SSR) + Vite
• Tailwind CSS 4
• Radix UI primitives
• Claude (Anthropic) for photo diagnosis and pricing — see src/lib/estimate-server.ts
• Supabase for auth — see src/integrations/supabase/

Local development

Requires Bun.

bun install
cp .env.example .env   # fill in the values below
bun run dev

You need two things in .env:

1. ANTHROPIC_API_KEY — from console.anthropic.com. The /demo route exercises the real estimate flow against a sample price sheet without this returns an honest error instead of a real diagnosis.

2. A Supabase project — create a new one at supabase.com/dashboard (don't reuse a project from another app — Job It Ready's users should be their own, not shared with anything else). Settings → API on that project gives you the URL, anon/publishable key, and service role key. Without this, /login and /signup will throw on submit.

   Then run the schema: open the SQL editor on that project and paste in supabase/migrations/0001_init.sql (or supabase db push if you're using the Supabase CLI locally). It creates tenants, price_sheet_items, leads, lead_line_items, and lead_messages, all RLS-scoped so a user can only ever see their own tenant's rows, plus a trigger that gives every new signup a tenant row automatically — no manual setup step needed to get the dashboard reading/writing real data.

3. Stripe — API keys from dashboard.stripe.com/apikeys (use the test keys while developing). For the webhook secret, either create a webhook endpoint at dashboard.stripe.com/webhooks pointed at <your-deployed-url>/api/stripe/webhook once deployed, or run stripe listen --forward-to localhost:8080/api/stripe/webhook locally, which prints a temporary signing secret. Without this, the "Switch to Solo/Crew" buttons on the billing page fail with a clear error instead of starting checkout.

Checkout itself never asks for an email — it's pulled server-side from the already-authenticated Supabase session (see src/lib/stripe-server.ts), so there's no separate email field to keep in sync with the account someone actually logged in with.

Design direction

Built to read as a real business tool for tradespeople, not a startup demo: a grounded charcoal/navy palette with one confident accent color, real job-site photography instead of stock or illustration, plainspoken copy, and deliberately none of the purple-gradient/glassmorphism/sparkle-icon look that's become the default "AI-generated" aesthetic.

SEO / AI discoverability

Same tech as caboshandyman.com, for the same reason: public/llms.txt (an AI-crawler-readable summary of the product), public/sitemap.xml (generated via npm run generate-sitemap, listing only real marketing pages — not /dashboard/* or /api/*), a Sitemap: line in robots.txt, and SoftwareApplication JSON-LD structured data on the homepage. All of this points at www.jobitready.com, the real registered domain, matching the one used in src/lib/mock-data.ts's widget/quote-link helpers.

Scope

Out of scope for v1: SMS/Instagram DM intake, two-way calendar sync (a pasted Cal.com/Calendly link is enough for now), a support ticket inbox, multi-language, and a /dashboard/settings/team multi-user flow — real value, but not needed to prove the core loop works.