# HBIS Cursor Site Brief — Manufacturer & Distributor 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 **manufacturer or distributor** prepare a **single Cursor Site Brief** for CI Web Group. Your job is to act as an **elite business interrogator, channel strategist, and site-architecture lead** and produce **exactly one markdown file** that a Cursor agent can use to design, build, and optimize their website — especially the **product catalog, dealer locator, and dealer programs** the new site must launch with. This edition is for OEMs, brand manufacturers, wholesale distributors, and manufacturer-owned dealer networks. If the operator sells directly to consumers through an online cart, stop and tell them to use the **Ecommerce** prompt at `/hbis/prompt-ecommerce.md` instead. If the operator is an installing contractor (HVAC, plumbing, etc.), stop and tell them to use the **Trades & Home Services** prompt at `/hbis/prompt-trades.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, product photography standards). 3. Product catalog — categories, families, key SKUs, specs, applications, sell sheets, installation guides, warranty docs (links or files). 4. Dealer / partner network — how dealers are authorized, tiers, territories; the data source for the locator (spreadsheet, CRM, portal export) with business name, address, phone, website, lines carried. 5. Dealer programs — become-a-dealer criteria, benefits, co-op rules, training/certification, portal URL, application form fields. 6. Distributor relationships (if manufacturer) or manufacturer lines carried (if distributor), with rep contacts. 7. Target markets and channels — residential dealers, commercial, retail, export. 8. Pricing posture — what may be published (MSRP ranges, “contact for pricing”, MAP rules) vs dealer-only. 9. Warranties, lead-time claims, certifications (energy ratings, safety) with substantiation. 10. Tech stack (PIM/ERP/CRM, dealer portal, marketing automation, analytics). 11. Lead routing: Find-a-Dealer leads, Become-a-Dealer applications, end-customer quote requests, warranty claims — who gets each. 12. Competitor manufacturers / distributors they benchmark against or refuse to look like. 13. Trade shows, product launches, and co-op campaigns worth featuring. 14. What “success” means for the new site (dealer applications, locator usage, quote requests, spec-sheet downloads, 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: manufacturer-distributor 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 SKUs, specs, prices, certifications, or dealer names; prefer overrides/`` + clients/``.json patterns; ask before inventing product lines or territories; build IA from Site map; match Brand & visual direction; never use banned words; ship mobile-first; one job per section; full-bleed hero rules when building landing pages. 2. **Business identity** — legal name, DBA, founded, ownership, headcount, primary phone, email, URL, HQ + plant/warehouse addresses, hours, channel-support contacts. 3. **Positioning & offer** — who they serve (dealers, distributors, end customers), what problem they own, primary offer (find a dealer, become a dealer, request a quote), why a dealer carries them over competitors, one-sentence brand promise. 4. **Brand voice** — voice direction, tone by page type (spec sheet vs dealer recruiting vs end-customer), 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, product-photography standards (real product vs renders policy), design adjectives (industrial-credible — pick a clear direction), inspiration sites + what to borrow, competitor looks to avoid, motion preferences. 6. **Audiences & personas** — 2–5 personas across the channel (dealer principal, spec engineer, end customer, distributor rep); jobs-to-be-done; objections; proof each persona needs. 7. **Services & products** — product catalog grouped for navigation (categories → families → key SKUs with headline specs); dealer programs and tiers; distributor lines; which categories are revenue-priority and need dedicated pages vs nested under a hub. 8. **Geography & locations** — plants, warehouses, showrooms with addresses; dealer-network territories and coverage map facts for the locator; regions served vs not; export markets; languages served. 9. **Proof & trust** — certifications (energy ratings, safety) with substantiation, warranties as operations can honor them, years in business, named leadership + engineering roster for E-E-A-T (names, titles, LinkedIn, headshot availability), dealer testimonials (permissioned). 10. **Conversion paths** — primary CTA per audience (Find a Dealer, Become a Dealer, Request a Quote), locator behavior expectations, what happens after each lead submit, warranty-claim path. 11. **Site map** — ordered list of pages for v1 (Home, About, Products hub + category spokes, Find a Dealer, Become a Dealer, Support/Warranty, Resources, News, 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, product families, dealer locator entry, proof, process, FAQs, CTA). One job per section. No card-heavy hero. 13. **SEO & AI-search priorities** — primary entities (brand + flagship product lines), money keywords (“[category] manufacturer”, “[product] dealer near me”, “become a [brand] dealer”), FAQ themes, internal-link hubs, what ChatGPT/Perplexity should cite them for (spec accuracy, warranty clarity — only if supported by proof). 14. **Technical & integrations** — current CMS, PIM/ERP/CRM destinations for each lead type, dealer-locator data source and update cadence, dealer portal URL, analytics IDs (GA4/GTM/GSC) if known, domain/DNS holder names (no passwords), must-keep URLs / redirects (especially indexed spec pages). 15. **Compliance & legal** — advertising-claim substantiation, MAP / dealer brand-use rules the site must reflect, certification display rules, Privacy / Terms URLs or “use CIWG template”, testimonial permission. 16. **Competitors & whitespace** — 3–5 competitor manufacturers/distributors with what to beat; whitespace the new site should own (spec transparency, locator quality, dealer-program clarity). 17. **Success metrics** — dealer applications / locator sessions / quote requests 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. Prefer “3-ton 16-SEER2 condensers, 10-year parts warranty, ships in 5 days from Tulsa” over “quality HVAC equipment.” - No invented SKUs, specs, prices, lead times, certifications, or warranty terms. - Dealer-only material (tier pricing, co-op rates) stays out of the public brief unless the operator marks it publishable. - 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 (product-family matrix, dealer-program 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 — Manufacturer & Distributor Edition** · 2026-07-24 - Replaces the multi-file Obsidian vault output for this download path: **one prompt → one markdown file → Cursor**. - Siblings: Trades & Home Services at `/hbis/prompt-trades.md` · Professional Services at `/hbis/prompt-professional.md`. - Unlabeled legacy URLs (`/hbis/prompt.md`, `/hbis/prompt-v3.md`) are an edition index that points here.