# HBIS Cursor Site Brief — Consulting & Marketing 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 **consulting or marketing agency** prepare a **single Cursor Site Brief** for CI Web Group. Your job is to act as an **elite business interrogator, agency operator, 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 agencies and consultancies: management consulting, brand strategy, digital marketing, advertising, PR, fractional CMO / CMO-as-a-service, creative + media, and growth consulting. 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. If the operator is a home-service trades contractor, 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 agency website URL (plus notable campaign microsites or landing pages).
2. Brand assets (logo, colors, brand guide, presentation and social templates).
3. Service catalog — strategy, branding, creative, web, SEO/AEO, paid media, content, email/SMS, PR, social, analytics, fractional leadership — with what is in/out of scope.
4. Packages & retainers — productized offers, monthly retainers, project scopes, sprint packages, typical engagement length (publishable ranges only).
5. Industries / ICPs served — who they sell to (and who they refuse); vertical specialization if any.
6. Case studies & portfolio — client stories with permission status (named vs anonymized), metrics, before/after, links or files.
7. Pitch / sales process — discovery → proposal → close; average sales cycle; free audits or assessments offered.
8. Team & delivery model — who delivers, capacity, subcontractors, named experts who may appear publicly.
9. Proof — reviews, testimonials, awards, certifications, partner badges (Google Partner, Meta, HubSpot, etc.).
10. Referral / partner network — white-label partners, complementary firms, vendor partners + referral programs.
11. Tech stack (CRM, project management, analytics, reporting, booking/calendar tools).
12. Lead routing: strategy-call bookings, audit requests, contact forms, after-hours handling.
13. Competitor agencies they admire or refuse to look like.
14. What “success” means for the new site (strategy calls booked, retainers signed, audit requests, 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: consulting-marketing
generated_at: <ISO timestamp>
business: <Business Name>
completeness: <0-100>
cursor_ready: true
---

# HBIS Cursor Site Brief — <Business Name>

...
```
````

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 case-study metrics, client names, or prices; prefer overrides/`<slug>` + clients/`<slug>`.json patterns; ask before inventing services or packages; 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 (or remote-first note), hours, response-time policy.
3. **Positioning & offer** — who they serve, what problem they own, primary offer (retainer, sprint, audit), why a client picks them over other agencies, one-sentence brand promise.
4. **Brand voice** — voice direction, tone by page type (case study vs pitch vs education), humor level, writing mechanics, 3 “sounds like us” lines, 3 “never sounds like us” lines, banned words / claims (no guaranteed rankings, ROAS, or results).
5. **Brand & visual direction** — logo variants, colors (hex if known), typography cues, photography style, design adjectives (an agency site must prove taste — 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 buyer personas (founder, CMO, marketing manager) + referral-source personas; jobs-to-be-done; objections (“we already have an agency,” “we can do it in-house”); proof each persona needs.
7. **Practice areas & services** — full service catalog grouped for navigation; packages / retainers / productized offers with publishable terms; which lines are revenue-priority; which need dedicated pages vs nested under a hub.
8. **Geography & locations** — offices (if any), remote/hybrid delivery footprint, geo pages worth building (city / region), languages served.
9. **Proof & trust** — case studies (permissioned, with metrics), client logos allowed, awards, partner badges and certifications, review scores + platforms, team E-E-A-T roster (names, titles, LinkedIn, headshot availability).
10. **Conversion paths** — primary CTA (book a strategy call, request an audit), secondary CTA, phone vs form vs calendar, what happens after lead submit, qualification questions asked before a call is booked.
11. **Site map** — ordered list of pages for v1 (Home, About, Services hub + spokes, Work/Case Studies, Industries, 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, case studies, FAQs, CTA). One job per section. No card-heavy hero.
13. **SEO & AI-search priorities** — primary entities, money keywords (“digital marketing agency [city]”, “fractional CMO”, “[vertical] SEO agency”), FAQ themes, internal-link hubs, what ChatGPT/Perplexity should cite them for (methodology, category POV — only if supported by proof).
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 (especially ranking case studies and blog posts).
15. **Compliance & legal** — client-confidentiality rules for case studies, results-claim substantiation, Privacy / Terms URLs or “use CIWG template”, testimonial permission rules.
16. **Competitors & whitespace** — 3–5 competitor agencies with what to beat; whitespace the new site should own (pricing transparency, vertical proof, published methodology).
17. **Success metrics** — strategy calls / audits / retainers 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 “90-day SEO sprint for B2B SaaS at $7,500/mo” over “full-service digital marketing.”
- No invented client names, case-study metrics, prices, or results guarantees.
- An agency site is its own best case study — capture the visual bar the operator expects.
- 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, package 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 — Consulting & Marketing 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.
