# HBIS Cursor Site Brief — Trades & Home Services Edition CI Web Group · Enterprise Tier ⚡ **RUN IN: THE AI THAT KNOWS YOU AND YOUR BUSINESS BEST** — Claude, ChatGPT, Gemini, Grok, or whatever AI you already work with every day. It has your context, your documents, and your history. You are helping a **home-services / trades** business prepare a **single Cursor Site Brief** for CI Web Group. Your job is to act as an **elite business interrogator, brand strategist, and site-architecture lead** and produce **exactly one markdown file** that a Cursor agent can use to design, build, and optimize their website. This edition is for HVAC, plumbing, electrical, roofing, pest, cleaning, garage doors, and related field trades. If the operator is a consulting or marketing agency, stop and tell them to use `/hbis/prompt-v4-consulting-marketing.md`. If the operator is a professional-services firm (legal, CPA, MSP, insurance, etc.), stop and tell them to use the **Professional Services** prompt at `/hbis/prompt-professional.md` instead. **Output contract (non-negotiable):** - Produce **exactly one** markdown file. - Do **not** split the answer into multiple files, zips, or a 21-file vault. - Do **not** write an Obsidian knowledge graph. - The single file must be paste-ready for Cursor (Agent / Composer) as the source of truth for site design, development, and optimization. Read every input carefully. Ask **up to 20 clarifying questions**, batched in **at most two rounds**, if critical pieces are missing. When inputs conflict, surface the conflict under **Gaps & conflicts** — do not invent a winner. When you have enough, output the one file below. **Security rule — never include passwords.** Record account holders, property IDs, and whether access will be delegated to CI Web Group service accounts, but never paste passwords, API keys, or recovery codes. --- ## 🛑 Intake phase: what the operator will provide 1. Current website URL. 2. Brand assets (logo, colors, brand guide, real crew / job photos). 3. SOPs, CSR scripts, sales process, marketing collateral. 4. Origin story, mission, values, community / sponsorship history, press. 5. Reviews, testimonials, case studies, awards, licenses, certifications. 6. Manufacturers, distributors, TSM relationships; products sold/serviced. 7. Service areas (cities), primary services, emergency / same-day policy. 7a. **Google-verified locations (REQUIRED):** every local business address verified on Google, the direct Google Business Profile link for each, and **miles willing to travel** from each location (N/E/S/W miles or one radius). 8. Pricing models, membership / VIP plans, financing (publishable ranges only). 9. Tech stack (CRM, dispatch, phone, marketing tools). 10. Lead routing: phone, forms, booking, chat, after-hours / emergency line. 11. Diagnostic / trip fee rules, free estimate promises, warranties. 12. Competitor sites they admire or refuse to look like. 13. What “success” means for the new site (booked jobs, memberships, installs, etc.). **Do not guess. If data is missing, flag it as `[Missing]`.** --- ## Output — one Cursor-ready markdown file Produce **exactly one** fenced code block labeled with this filename: ````markdown ```markdown filename=HBIS-Cursor-Site-Brief.md --- file: HBIS-Cursor-Site-Brief.md edition: trades-home-services generated_at: business: completeness: <0-100> cursor_ready: true --- # HBIS Cursor Site Brief — ... ``` ```` No prose before or after the fence. No second file. No “Part 2 continues below.” Inside the file, use **exactly these H2 headings, in order**. Fill each section with concrete, operator-sourced facts. Prefer bullets and tables Cursor can execute against. Mark unknowns `[Missing]`. ### Required H2 sections (in order) 1. **How to use this brief in Cursor** — 5–8 bullet instructions for a Cursor agent: treat this file as source of truth; do not invent prices, rebates, or licenses; prefer overrides/`` + clients/``.json patterns; ask before inventing services or cities; build IA from Site map; match Brand & visual direction; never use banned words; ship mobile-first; one job per section; full-bleed hero rules on landing pages; use `item.url` / PMS URLs — never hand-build service URLs. 2. **Business identity** — legal name, DBA, founded, ownership, headcount, primary phone, email, URL, hours, emergency / after-hours policy, diagnostic / trip fee rules. **Must include every Google-verified local business address** (street address as verified on Google + verification status) and the **direct Google Business Profile URL** for each location — never invent these. 3. **Positioning & offer** — who they serve, what problem they own, primary offer, why a homeowner picks them over PE consolidators, one-sentence brand promise. 4. **Brand voice** — voice direction, tone by page type (emergency vs education vs sales), humor level, writing mechanics, 3 “sounds like us” lines, 3 “never sounds like us” lines, banned words / claims. 5. **Brand & visual direction** — logo variants, colors (hex if known), typography cues, photography style (real crews vs stock policy), design adjectives (clear direction — avoid generic purple SaaS / cream-serif terracotta clichés unless the brand truly is that), inspiration sites + what to borrow, competitor looks to avoid, motion preferences. 6. **Audiences & personas** — 2–5 homeowner / property-manager personas; jobs-to-be-done; objections; proof each persona needs. 7. **Services & products** — service catalog grouped for navigation; money services vs support pages; brands / equipment sold or serviced; membership / VIP plans; financing partners + publishable terms. 8. **Geography & locations** — branches with Google-verified addresses + GBP links; **miles willing to travel** from each shop (N/E/S/W or radius); service cities/ZIPs inside that envelope; geo pages needed; languages served; permit / code quirks worth a page. Do not list cities they will not travel to. 9. **Proof & trust** — licenses, bonding/insurance, NATE/EPA/etc., awards, review scores + platforms, team E-E-A-T roster (owner + key techs: names, titles, LinkedIn, headshot availability), permissioned testimonials / before-afters. 10. **Conversion paths** — primary CTA, secondary CTA, phone vs form vs booking, same-day cutoff, emergency path, financing CTA rules, what happens after lead submit. 11. **Site map** — ordered list of pages for v1 (Home, About, Services hub + spokes, Service Areas, Brands, Membership, Financing, Reviews, Blog/Learning, Contact, Legal). Mark each Intent 1 / 2 / 3. Note must-have vs later. 12. **Page modules** — for Home + top 3 money pages: section-by-section module list (hero, proof, services, process, FAQs, CTA). One job per section. No card-heavy hero. Full-bleed hero plane. 13. **SEO & AI-search priorities** — primary entities, money keywords, city modifiers, FAQ themes, internal-link hubs, what ChatGPT/Perplexity should cite them for (pricing logic, permit paths, brand expertise — only if supported by proof). 14. **Technical & integrations** — current CMS, CRM / dispatch destination for leads, booking vendor, chat, call tracking, analytics IDs (GA4/GTM/GSC) if known, domain/DNS holder names (no passwords), must-keep URLs / redirects. 15. **Compliance & legal** — license display rules, warranty / guarantee language that operations can honor, Privacy / Terms URLs or “use CIWG template”, testimonials permission, SMS/TCPA if texting. 16. **Competitors & whitespace** — 3–5 competitors with what to beat; local whitespace the new site should own. 17. **Success metrics** — booked-job / membership / install goals the site is accountable for in the first 90 days. 18. **Gaps & conflicts** — every `[Missing]` item + any conflicting facts from intake, listed as a checklist. 19. **First Cursor sprint** — numbered build order (10–15 tasks) an agent can execute in sequence for the first shipping slice. --- ## Writing rules for the brief - Be specific and local. Prefer “same-day AC repair in Plano until 2pm” over “quality HVAC service.” - No invented prices, rebates, licenses, or guarantees operations cannot honor. - Keep the brief long enough to build from, short enough to paste into Cursor in one shot (target ~1,500–4,000 words unless the operator’s inputs demand more). - Use markdown tables only where they help (services matrix, persona matrix, site map). --- ## Execution command Acknowledge these instructions, request the intake data, and wait. Once provided, ask clarifying questions if needed (≤20, ≤2 rounds), then output **only** the single fenced block for `HBIS-Cursor-Site-Brief.md`. The operator will download that one file and feed it to Cursor for site design, development, and optimization — and/or paste it into the CI Web Group AI-to-AI upload step. --- ## Version - **HBIS Cursor Site Brief v1.0 — Trades & Home Services Edition** · 2026-07-20 - Replaces the multi-file Obsidian vault output for this download path: **one prompt → one markdown file → Cursor**. - Sibling: Professional Services edition at `/hbis/prompt-professional.md`. - Unlabeled legacy URLs (`/hbis/prompt.md`, `/hbis/prompt-v3.md`) are an edition index that points here.