What Marque means for the CRO

Chief Revenue Officer

Live pipeline with the why behind each stage move, and quote-ready pricing from the contracts we actually signed.

  • pipeline generation and forecast
  • enterprise deals and renewals
  • CRM hygiene
  • partner channel
  • pricing execution
  • sales enablement

Key takeaways

The takeaways, starters and worked examples for this seat quote real company figures, so they are shown to signed-in colleagues only. Sign in to read them.

What to ask

Starters for this seat

The same starters the Ask screen offers you, from the seat's own list and its home department. Each one is answerable from connected sources today.

Sign in to see the starters for this seat.

Runs for you

Routines for this seat

Enable any of these on the Routines page. Defaults run at 06:00 UTC; change the day and time, choose whether actions ask first, and pick email, in-app or both.

  • Daily Salesperson Summary

    Daily

    One personalised email per salesperson, deals that matter most first: pipeline, hot deals, stuck in stage, company signals, CRM contacts (shadow contacts). UK reps at 07:00 UTC, USA reps set their instance to 13:00 UTC. Replaces the mc-stats daily summary.

    Delivered by email and in-app notification.

  • Weekly Pipeline Review

    Weekly

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

    Delivered by email and in-app notification.

  • Unanswered inquiries (weekly)

    Weekly

    Every external inquiry to api@ and info@ that nobody answered: this week's rows get a Marque draft and a Copper follow-up task for Lisa; older ones are listed.

    Delivered by email and in-app notification.

  • Sales Weekly Executive Report

    Weekly

    The flagship summary of the sales week (Monday to Sunday just ended) for the executive list. Salesperson-driven activity is kept separate from self-signup API subscriptions throughout. Replaces the mc-stats weekly executive report.

    Delivered by email and in-app notification.

  • Sales Monthly Executive Report

    Monthly

    Same partitioning as the weekly report with longer horizons: month and year to date, quarterly cumulative revenue, revenue quality, six-month trend, team performance for the month, month and YTD self-signup segment tables. Replaces the mc-stats monthly executive report.

    Delivered by email and in-app notification, PDF attached.

  • Lost Deal Reasons (monthly)

    Monthly

    Analysis of the lost-deal survey responses and Copper loss reasons for the month: losses by rep-verified reason with counts, values and survey coverage, free-text themes with verbatim quotes, contradictions between the ticked reason and what the rep wrote, actionable signals, re-engagement note, per-rep survey completion. Alastair: the one report we must keep.

    Delivered by email and in-app notification.

  • CRO Weekly Notes (Jim)

    Weekly

    CRO-focused highlights for Jim's Monday meeting: a headline sentence plus grouped bullets (wins, risks, movement) from the deterministic weekly metrics, with the pipeline tables attached as a workbook (stages and summary views, UK and USA merged, USD). Replaces the mc-stats Jim weekly notes.

    Delivered by email and in-app notification, XLSX attached.

  • Weekly Deal Data Quality

    Weekly

    Per rep, Enterprise Sales only, read-only: open deals with data-quality problems (missing close dates, values, sources or companies, close dates passed, stages out of date) and deals closed in the last 90 days that still need data (loss reason, value, close date, source, close dates left in the future), each with the fields to fix and a Copper link, the rep's DQ score (share of those deals with nothing to fix) and two or three tips. Only a rep with an open deal missing data gets the note (closed-deal gaps ride along); everyone else gets nothing (the run is silent). Replaces the mc-stats weekly DQ reports.

    Delivered by email.

  • Lost-deal survey invitations

    Daily

    Builder routine: when an Enterprise deal is marked Lost or Abandoned the owner gets a short survey link (confirm or correct the Copper loss reason, then a few questions); reminders every 3 days, two at most, then the survey lapses. Completed answers are appended to the Copper opportunity as a note. Review mode sends the invitations to the review recipients in config/sales-routines.json until deliverToOwners is on.

    Delivered by a thread.

  • Won touch-point reminders

    Daily

    Builder routine: 30, 90, 120 and 180 days after an Enterprise win, checks Copper for evidence of client contact since the previous checkpoint (activities, captured meetings). No evidence produces one reminder email to the owner with Copper links; an inconclusive check never sends. Review mode sends to the review recipients in config/sales-routines.json until deliverToOwners is on.

    Delivered by a thread.

  • Sales calendar review (monthly)

    Monthly

    Builder routine: on the first of the month Marque reviews how the sales and account people spent their external meeting time in the month just ended against the month before and the year to date (meetings, hours, prospects met, first meetings, Copper note and Gemini coverage, per-person table with an activity indicator, deals created, won and lost on the companies they met, watch list), and mails it to the executive team (review recipients until calendarReview.deliverToExecs is on).

    Delivered by a thread.

  • Quiet pipeline nudge (monthly)

    Monthly

    Builder routine: on the second of the month every deal owner gets one mail listing only their own open counted deals on companies nobody on the sales or account roster has met for 60 days (deal, company, stage, value, last meeting date, days since, largest value first). An owner with no such deals is sent nothing. Review mode delivers every owner mail as one combined message to the review recipients until quietPipeline.deliverToOwners is on.

    Delivered by a thread.

Worked examples

Real questions, this week's real answers

These answers quote real company data, so they are shown to signed-in colleagues only. Sign in to read them.

Boundaries

What protects you

The rules are code, not prompt. They apply the same way to every seat.

Every department brain, tiers T0 to T3
A CXO seat reads the org brain and all eleven department brains at tiers T0 to T3. Tier T4 (executive-explicit) is deliberately excluded: those files need a named grant, seat or not.
The lens frames, it never grants
Pick your seat lens on the Ask screen and answers lead with your KPIs and end with one recommended action. Access comes from grants.json and your principal record; the lens is appended after the ACL filter.
Actions wait for your click
Jira issues and comments, Copper tasks and notes, and delegated email are actions. Each shows an approval card with its consequence before it runs, is always a create or an append, and lands in the audit log with your name.
Everything is audited
Every ask records the sources and tools it used; every denial records its reason. Unreadable grants deny, missing secrets 401, and the actions kill switch stops every write.

Internal preview for MarketCheck staff. Not for customers.

Prepared by Marque at MarketCheckversion f422dbb