Website

Where the public site is, and what comes next.

Homepage, About, how-it-works, practice areas, and contact now sell the same Civil / AEC company brain: specs, RFIs, submittals, SOPs, as-builts, and project docs — one Corpusmith AI engine, their documents behind hard tenant walls, answers with receipts, Discover → Ingest → Private brain → Ask with receipts → Expand. White + deep navy chrome. Vertical is locked — no longer TBD. This page is the short website roadmap — not a product backlog, and not a promise of a community app.

Book a demo

Done

  • Homepage + About

    White + deep navy north star. Civil / AEC locked (no longer TBD). One Corpusmith AI engine, tenant walls, private brain, receipts. Discover → Ingest → Private brain → Ask with receipts → Expand.

  • How it works

    Full Civil / AEC motion: document types (specs, RFIs, submittals, SOPs, as-builts), example questions, human sign-off, Discover → Ingest → Private brain → Ask with receipts → Expand.

  • Practice Areas

    Every civil discipline the engine already runs on — land development, structures, transportation, water resources, geotechnical, and field — not a rate card, not fake metrics.

  • Contact

    Bring us one project. Specs / RFIs / submittals / SOPs / as-builts prep list. No calendar auto-booking — a person replies.

  • Book a demo CTA

    One CTA, everywhere: Book a demo → /contact. Replaced the old placeholder-tenant demo push.

  • Collide-level polish

    Collide structure without holograms: numbered 01–04 stack, Civil Engineering workflow cards (Specs & Submittals, RFI Workflow, SOP / Tribal Knowledge), dark knowledge layers, big CTA band. 3D floating charts (bars/nodes) instead of document schematics. Terracotta on the wordmark only. Glow accents stay navy / cyan.

Near-term

  • Citations to real files

    Receipts are the promise. Point answers at real files and chunks when that ships. Do not invent a citations UI in a website PR.

  • Environmental beachhead

    Later. Civil / AEC is first. Do not pitch environmental as the current vertical.

  • Real case study

    Only after a paying client. No invented logos, names, or metrics.

  • Contact intake

    A form or calendar only if discovery volume needs it. Until then, the prep list on /contact is enough.

Not now

Out of scope for the marketing site

  • Community app, social layer, or “AI marketplace”
  • Marketing pages that require Supabase, LLM, or embedding keys
  • Fake social proof, fake citations UI, or certification claims
  • Oil and gas positioning
  • Ingest / chat / embeddings / tenant status UI — do not change them in a website PR

The same list, with page map and collaboration notes, lives in docs/SITE_PLAN.md. Product rules stay in About and docs/PRODUCT.md.

Find your first workflow.

The placeholder tenant is the public preview. A real Civil / AEC corpus starts with one project.

Book a demo