Meet Marque(say "mark")

Cited answers over everything you are allowed to see. Ask in plain English and get an answer with numbered sources, a table when the data is tabular, and contact details masked unless your role may see them.

Try asking

• ›
  Which enterprise contracts renew in the next 90 days, and what do they commit us to?
• ›
  What are the top support ticket drivers this month?
• ›
  Give me a 360 on Cox Automotive: contracts, open pipeline, support history, billing.

Switch the composer to Agent and Marque plans its own steps: search, the change log, live consults (BigQuery, Jira, Zendesk, Stripe, Drive), document generation, up to 50 tool calls per run. Anything that writes outside Marque (Jira, Copper, email) pauses for your approval unless the thread is set to auto-approve.

Try asking

• ›
  Query BigQuery for auction listing counts by state, top 5.

  writes and runs the SQL, returns a table

• ›
  Create a Jira issue in project MIT titled "Brain UI smoke test", due 2026-09-30.

  shows the approval card; deny it and the run records the denial

• ›
  Make me a branded PDF summarizing the Cox NeoVIN evaluation agreement.

  two tool calls: search, then generate

Scheduled briefs Marque runs for you: daily, weekly or monthly at a time you pick, delivered by email and as an in-app notification, with an optional Word, Excel or PDF attachment. Enable one from the catalog, adjust the cadence, and choose whether actions ask first or run automatically.

From the catalog

1. Weekly Pipeline Review

   Pipeline movement, commit vs forecast, and at-risk deals with citations. Weekly, for sales.

2. AR Aging Watch

   Open A/R aging, dunning status, and the top overdue accounts. Weekly, for the CFO seat.

3. Exec Weekly Brief

   Releases, pipeline, quality deltas and the action-item scorecard, under 400 words. Weekly, for the CEO seat.

Marque watches shared inboxes. In assistant mode it drafts the reply inside the mailbox and notifies the reps in the thread; in responder mode it may answer external senders itself, with an AI disclosure and the reps copied. Reply to the notice to change the draft; start with "always" and it becomes a standing instruction for every future draft.

What happens on api@, end to end

1. A prospect writes to api@

   Every 5 minutes Marque reads new mail, skips automation and internal threads, and classifies the rest: intent, needs a reply, sensitive.

2. It drafts and assigns

   It gathers facts from the knowledge base and live sources, drafts six sentences at most with prices only as retrieved, saves the draft in the mailbox and notifies the reps in the thread.

3. Follow-up steps run

   For external, non-sensitive senders it finds or creates the Copper lead, attaches the draft as a note, opens a two-day follow-up task, opens a Qualified opportunity for sales intents, and labels the thread Marque/Drafted.

Teach Marque without leaving your inbox. Send, forward or CC marque@marketcheck.com and the thread joins the knowledge base, attachments included (PDF, Word, Excel, PowerPoint, text). A short directive in the subject decides where it lands.

Subject lines that route

• ›
  [sales] Cox renewal call notes

  lands in the sales brain, tagged dept:sales

• ›
  [org] [tag: pricing, neovin] Updated rate card for 2027

  org brain, tagged pricing and neovin

• ›
  Fwd: Feed spec for Ethos #feeds

  no bracket directive: an org-domain sender to marque@ shares with everyone; the hashtag becomes a topic tag

Ask for a document and get a file: Word, Excel, PowerPoint or PDF, MarketCheck-branded by default (logo, blue rule, Inter body, page numbers and a Prepared by Marque footer), stored under Artifacts and linked from the answer. Private to you unless you publish it.

Try asking

• ›
  Make me a branded PDF summarizing the Cox NeoVIN evaluation agreement term and renewal.
• ›
  Put our API pricing tiers and per-call rates in a one-page Word summary for a dealer-group prospect.
• ›
  Build an Excel register of our data license agreements with renewal term and notice period per client.

Marque is private: nothing outside Google can reach it, so it pulls changes instead of receiving webhooks. Copper, Jira and Stripe changes are polled every 5 to 15 minutes, and every source also re-syncs on its schedule: a nightly pass at 00:00 UTC for daily sources and a 30-minute tick for hourly ones.

In practice

1. Copper within minutes

   New leads, people and companies are picked up every 5 minutes and enriched; the full Copper source re-syncs hourly.

2. Freshness you can check

   Every source row shows its last sync; the admin sources page adds a fresh or stale verdict against each source's SLO.

Marque is one system with many brains. Everyone gets the org brain; your department brain comes with your department; CXO seats read across departments; anything beyond that is an explicit, admin-controlled, version-controlled grant. Sources are filtered before the model sees them, contact details are masked for most roles, and every ask, tool call and denial is audited.

In plain words

1. Department brains

   Sales sees sales, engineering sees engineering. Finance and legal documents carry tier T3 and stay with those teams.

2. CXO seats

   A seat (CEO, CFO, CRO, CTO and the rest) reads every department at tiers T0 to T3, with a lens that frames the answer for that job. A lens never grants access.

3. Masking and audit

   Emails and phone numbers are masked unless you are finance, people, a CXO seat or an admin. Denials are logged with the reason; asks are logged with every source and tool used.

What you will not see: documents outside your brains, tier T4 files unless you are named on them, other people's personal brains, and contact details your role is not entitled to. If an answer seems thin, that is usually why. Ask an admin for a grant rather than a workaround.