PRODUCT // EXECUTIVE BRIEFING
Every conclusion has a threshold. Every metric has a source.
CEO Brief pulls from Stripe, SAP, Salesforce, GitHub and official data sources, reduces them to one dictionary of 64 canonical metrics, and generates a briefing every morning across finance, engineering and geopolitics. It is a rules engine: every sentence shows which metric and which source triggered it — and a metric without a working source is reported as “no data”, never as zero.
Why CEO Brief
Most executive dashboards share one flaw: when a source goes quiet they draw a zero, and a zero looks exactly like a real zero. CEO Brief is built around the opposite rule — missing data is information, and it has to be shown.
A metric with no working source is reported as “no data” and lands on the gap list along with the reason and the timestamp of the last successful sync. Nothing is guessed and nothing is interpolated. An empty sales section tells you Salesforce is returning a 401 — not that your pipeline is zero.
The briefing is a rules engine, not a model writing prose. The sentence “runway fell to 14.2 months” carries the rule that fired it, the metric it rests on, and the source of that metric. You do not have to trust the narrative — you can check it.
Every value is labelled with a confidence level: verified (straight from a system of record), calculated (derived, like ARR from MRR) or declared (a manual entry or an aggregator). Fact and noise are never merged into one number — the armed-event registry from ACLED and reporting intensity from GDELT sit beside each other, not on top of each other.
Connectors map their fields onto canonical metrics, and widgets read only those metrics. Swapping Stripe for SAP, migrating off Salesforce, or adding your own HTTP source changes no widget — and does not invalidate the history you have already collected.
Capabilities
Six metric domains, a configurable dashboard, and a daily report that delivers itself — without an analyst team maintaining spreadsheets.
01
Five standing sections — Executive Summary, Finance, DORA Engineering, Global context and Geopolitics — generated daily at 05:00 UTC, before you open your laptop. One-click Markdown export, and `/api/briefing?format=md` is ready to wire into Slack or email.
02
Finance, sales, product, engineering, market and geopolitics in one contract: definition, unit, direction (“higher is better”), source and confidence. Derived metrics — ARR from MRR, runway from cash and burn rate, Net New MRR — compute themselves and know what they came from.
03
Stripe, SAP S/4HANA, Salesforce, GitHub and Statuspage as systems of record; ECB, FRED, Stooq, ACLED and IMF PortWatch as official sources; GDELT as an aggregator. Plus any HTTP source and manual entries for the numbers nobody exposes over an API yet.
04
Field path, transforms, filter, aggregation and time dimension — configured in a form generated from the connector’s own specification. Connection test and a raw sample preview before anything is saved, so you validate a mapping against real records rather than documentation.
05
Fifteen presentation types — KPI tiles, line, area and bar charts, donut, meter with a goal line, table, briefing, news, incidents, markets, chokepoints. Every widget gets its own metrics, width, time range and target. The layout builder belongs to the CEO, not to IT.
06
AI model launches, agentic AI news, and the three fastest-growing GitHub repositories — switched on deliberately in the company profile, because what is critical for one company is noise for another. Every item carries its justification: the detected model name, the agentic term, or the matched keyword from your profile.
07
An event counts toward the risk index only when it touches a region, a trade route or a dependency named in your company profile. Transits through Hormuz, Bab al-Mandab, Suez, the Taiwan Strait and Malacca are tracked as facts from IMF PortWatch — separately from how much is being written about them.
08
The code asks for a permission, not a role, so the permission matrix in the admin panel is generated from the code itself and cannot drift from actual behaviour. API keys are encrypted with AES-256-GCM and never return to the browser in the clear. An instance administrator manages access — they do not read other people’s briefings.
Screenshots
Captures of the running application, not mockups. The finance sections deliberately read “no data” — no financial source is connected in the demo environment, and a gap is information here, not a zero. The interface currently ships in Polish.
Morning briefing
Five standing sections plus the modules you switch on. Under every conclusion sits the rule that fired it and the source of the metric — including the gap, when a source goes quiet.
Integrations and mappings
The source catalogue with confidence level and last sync, a raw sample preview, and the mapping editor: path, transform, filter, aggregation.
Canonical metric dictionary
The contract the whole system rests on: definition, value, day-over-day change, source, confidence and freshness — with gaps marked explicitly.
Dashboard layout
The widget builder: presentation type, the metrics behind it, tile width, time range and an optional goal line. The layout belongs to the CEO, not to IT.
Rollout
01
The app lands on your Vercel account from your repository, with your Redis store and three keys generated on your side. Your data and secrets never pass through our infrastructure — there is no server of ours for them to land on.
02
We configure connectors with least-privilege credentials — read-only Stripe, a SAP communication user, a Salesforce Connected App, a GitHub PAT — and map fields onto canonical metrics. Your company profile (industry, markets, competitors, tickers, North Star) decides what is signal and what is noise.
03
A cron at 05:00 UTC, Monday to Friday, syncs the sources and generates the report before you open your laptop. You shape the dashboard, switch modules on and off, and wire `/api/briefing?format=md` into Slack or email.
Specs
FAQ
No. CEO Brief is deployed to your Vercel account, with your data store and your encryption keys. We supply the code and the rollout; the data goes straight from your systems into your instance. There is no intermediary server of ours, because the architecture does not have one.
BI tools draw whatever you feed them. CEO Brief adds two things they do not have: a canonical metric dictionary, which means swapping a source breaks no widget, and a rules engine that turns numbers into sentences with a threshold and a source. And it says outright when it does not know something, instead of drawing a zero.
Every source is optional. You can start with GitHub and manual entries, add any HTTP source through a form, and connect your systems of record later — the canonical metrics do not change, so the history survives. The market and geopolitical sections need no keys at all: ECB, Stooq, ACLED and IMF PortWatch are public.
No. The briefing is generated by a rules engine, which is why every sentence can be traced to a threshold, a metric and a source. That is deliberate: a report you cannot verify is not fit for financial decisions. The AI radar modules read public feeds and likewise show which signal let each item through.
Polish today, including the briefing text. An English interface and report is one of the things we deliver as part of the rollout if you need it — describe it in the form and we will include it in the quote.
A company licence plus a fixed-scope rollout: source configuration, mappings against your chart of accounts and pipeline, the company profile, and the dashboard layout. Describe your systems in the form and we will send a specific quote — usually within two business days.
Order
Tell us which systems you run and which decisions you want to make in the morning. We will show a live demo and prepare a rollout quote — from the engineer who built the product, not from a sales queue.
Prefer email?hello@pixelofsoftware.com