# HBIS Cursor Site Brief — Technology · Integrations · APIs 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 **technology company** prepare a **single Cursor Site Brief** for CI Web Group. Your job is to act as an **elite business interrogator, product marketer, 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 SaaS, software platforms, developer tools, API / integrations companies, app marketplaces, and B2B tech products. If the operator is a consulting or marketing agency, stop and tell them to use the **Consulting & Marketing** prompt at `/hbis/prompt-consulting-marketing.md` instead. 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, API secrets, or recovery codes. --- ## 🛑 Intake phase: what the operator will provide 1. Current website URL (plus docs site, status page, and community links). 2. Brand assets (logo, colors, brand guide, product screenshots with usage rights). 3. Product catalog — products, plans, modules; what each does; who each is for; public vs gated features. 4. Pricing & packaging — free / trial / paid tiers, seat vs usage pricing — publishable figures only. 5. Integrations catalog — named integrations (native + partner), category, status (GA / beta / deprecated), docs URLs, logo permission. 6. API & developer platform — public API surfaces, auth model (API key / OAuth), SDKs, webhooks, sandbox, changelog policy. Never invent endpoints or SLAs. 7. Marketplace / partner ecosystem (if any) — listing criteria, featured apps, reseller and referral programs, or `[Not applicable]`. 8. ICPs & verticals — who they sell to (and refuse); buyer roles (CTO, RevOps, developer). 9. Case studies & proof — customer stories with permission, metrics allowed, logos, G2/Capterra/TrustRadius scores. 10. Sales motion — PLG / sales-assisted / enterprise; demo → trial → close; security review packet availability. 11. Tech stack for the site itself (current CMS, CRM destination, demo-booking vendor, chat, analytics). 12. Lead routing: demo requests, trial signups, sales@ / partnerships@ / support@ destinations. 13. Competitor products they benchmark against or refuse to look like. 14. What “success” means for the new site (demos booked, trials started, docs adoption, partner applications, 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: technology 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 endpoints, SLAs, uptime claims, or prices; prefer overrides/`` + clients/``.json patterns; ask before inventing products or integrations; 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 address (or remote-first note), support hours, status-page URL. 3. **Positioning & offer** — who they serve, what problem the product owns, primary offer (trial, demo, free tier), why a buyer picks them over incumbents, one-sentence brand promise. 4. **Brand voice** — voice direction, tone by page type (developer docs vs marketing vs pricing), humor level, writing mechanics, 3 “sounds like us” lines, 3 “never sounds like us” lines, banned words / claims (no invented uptime or benchmark numbers). 5. **Brand & visual direction** — logo variants, colors (hex if known), typography cues, screenshot / illustration policy, design adjectives (pick a clear direction — avoid the generic purple SaaS cliché unless the brand truly is that), inspiration sites + what to borrow, competitor looks to avoid, motion preferences. 6. **Audiences & personas** — 2–5 buyer + user personas (economic buyer, champion, developer); jobs-to-be-done; objections (security, migration cost, lock-in); proof each persona needs. 7. **Services & products** — product / plan catalog grouped for navigation; integrations catalog (named, categorized, with status); API & developer platform surface (public docs, SDKs, sandbox); marketplace or partner program if any; publishable pricing tiers. 8. **Geography & locations** — HQ + offices, market regions served, data-residency regions worth stating publicly, languages served, geo pages only if genuinely relevant. 9. **Proof & trust** — customer logos allowed, case studies (permissioned, with metrics), review-platform scores (G2/Capterra), security & compliance badges (SOC 2, GDPR — only if held), team E-E-A-T roster (founders + key engineers: names, titles, LinkedIn, headshot availability). 10. **Conversion paths** — primary CTA (start trial, book demo), secondary CTA (docs, pricing), PLG vs sales-assisted path split, what happens after signup/demo request, partner/integration inquiry path. 11. **Site map** — ordered list of pages for v1 (Home, Product(s), Pricing, Integrations hub + spokes, Developers/Docs entry, Customers, About, Blog/Changelog, 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, product tour, integrations wall, pricing teaser, FAQs, CTA). One job per section. No card-heavy hero. 13. **SEO & AI-search priorities** — primary entities, money keywords (“[category] software”, “[competitor] alternative”, “API for [use case]”, “[product] integration”), FAQ themes, internal-link hubs, what ChatGPT/Perplexity should cite them for (integration breadth, docs quality — only if supported by proof). 14. **Technical & integrations** — current CMS, CRM destination for leads, demo-booking vendor, chat, analytics IDs (GA4/GTM/GSC) if known, docs platform, domain/DNS holder names (no passwords), must-keep URLs / redirects (especially docs and changelog paths). 15. **Compliance & legal** — security/compliance claims that may be published (with proof), data-processing facts, Privacy / Terms URLs or “use CIWG template”, customer-logo and testimonial permission rules. 16. **Competitors & whitespace** — 3–5 competitor products with what to beat; whitespace the new site should own (pricing transparency, integration proof, migration guides). 17. **Success metrics** — trials / demos / partner applications 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 “native Salesforce sync with 2-way field mapping, GA” over “powerful integrations.” - No invented endpoints, SLAs, uptime figures, benchmark numbers, or prices. - When a trades-shaped concept does not apply (truck rolls, service areas), 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 (plan matrix, integrations 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 — Technology · Integrations · APIs 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.