# HBIS Cursor Site Brief — Professional 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 **professional services** firm 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 firms such as: legal, accounting / CPA, bookkeeping, IT / MSP, insurance agencies, financial advisory, architecture / engineering (non-trades install), and similar knowledge / advisory businesses. If the operator is a **consulting or marketing agency** (branding, digital marketing, PR, fractional CMO, creative), stop and tell them to use the **Consulting & Marketing** Master Document at `/hbis/prompt-v4-consulting-marketing.md` instead. If the operator is a home-service trades contractor (HVAC, plumbing, electrical, roofing, 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 (plus practice-area microsites or landing pages). 2. Brand assets (logo, colors, brand guide, partner / attorney headshots). 3. SOPs, intake scripts, engagement letters / proposal templates. 4. Origin story, mission, values, pro-bono / community history, press. 5. Reviews, testimonials, case studies (with publish permission), awards, credentials. 6. Practice areas / service lines, ideal client niches, geography. 7. Pricing models (hourly, flat, retainer, contingency, package, subscription) — publishable ranges only. 8. Tech stack (CRM / practice management, phone, marketing, client portal). 9. Lead routing: phone, forms, calendar / booking, chat, after-hours. 10. Compliance constraints (attorney advertising rules, disclaimers, regulated claims). 11. Competitor sites they admire or refuse to look like. 12. What “success” means for the new site (leads, retainers, booking rate, talent recruiting, 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: professional-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 credentials or prices; prefer overrides/`` + clients/``.json patterns; ask before inventing practice areas; 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, entity type, founded, ownership, headcount, primary phone, email, URL, HQ address, hours, after-hours policy. 3. **Positioning & offer** — who they serve, what problem they own, primary offer, why a client picks them over alternatives, one-sentence brand promise. 4. **Brand voice** — voice direction, tone by page type, humor level, writing mechanics, 3 “sounds like us” lines, 3 “never sounds like us” lines, banned words / claims. 5. **Brand & visual direction** — logo variants available, colors (hex if known), typography cues, photography style, design adjectives (pick a 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 client personas + referral-source personas; jobs-to-be-done; objections; proof each persona needs. 7. **Practice areas & services** — full service catalog grouped for navigation; which are revenue-priority; which need dedicated pages vs nested under a hub. 8. **Geography & locations** — offices, service footprint, geo pages needed (city / region), languages served. 9. **Proof & trust** — credentials, licenses, awards, case studies (permissioned), review scores + platforms, team E-E-A-T roster (names, titles, LinkedIn, headshot availability). 10. **Conversion paths** — primary CTA, secondary CTA, phone vs form vs calendar, consultation / intake fee rules, what happens after lead submit, emergency / urgent path if any. 11. **Site map** — ordered list of pages to build for v1 (Home, About, Services hub + spokes, Locations, Team, Insights/Blog, 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. 13. **SEO & AI-search priorities** — primary entities, money keywords, local modifiers, FAQ themes, internal-link hubs, what ChatGPT/Perplexity should cite them for. 14. **Technical & integrations** — current CMS, CRM destination for leads, booking/calendar vendor, chat, analytics IDs (GA4/GTM/GSC) if known, domain/DNS holder names (no passwords), must-keep URLs / redirects. 15. **Compliance & legal** — required disclaimers, advertising ethics constraints, Privacy / Terms URLs or “use CIWG template”, testimonials permission rules. 16. **Competitors & whitespace** — 3–5 competitors with what to beat; whitespace opportunities on the new site. 17. **Success metrics** — lead / booking / retainer 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 “family-law retainers for Collin County parents” over “quality legal services.” - No invented prices, credentials, case results, or guarantees. - When a trades-shaped concept does not apply (truck rolls, manufacturer rebates, etc.), omit it — do not pad. - 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 — Professional Services Edition** · 2026-07-20 - Replaces the multi-file Obsidian vault output for this download path: **one prompt → one markdown file → Cursor**. - Sibling: Trades & Home Services edition at `/hbis/prompt-trades.md`. - Unlabeled legacy URLs (`/hbis/prompt.md`, `/hbis/prompt-v3.md`) are an edition index that points here.