Executive dashboard
Revenue, margin, cash and orders on one screen — assembled around your KPI definitions, not a template's.
ÆTHER Pulse is a business intelligence portal that builds itself around your company. The AI interviews you, drafts your connectors and dashboards; an ÆTHER engineer checks the assembly and connects live data before you see a single number.
Orders sit in the CRM, stock and cost in the ERP, money in the bank portal, ad spend in three ad cabinets, marketplace sales in seller dashboards, and margin — in someone's spreadsheet. Getting one honest picture means a person copying numbers by hand every Monday.
Discovery workshops, requirement documents, integration estimates. Many die in meetings before a single dashboard ships.
Templates assume your business looks like everyone else's. Your margin logic, your order flow, your KPI definitions — they never quite do.
An LLM wired straight to your data will confidently chart the wrong column. Numbers you act on need a human sign-off.
A scripted onboarding session. On the left — the AI interview. On the right — the client's workspace being drafted in real time from the answers. All figures are demo data.
You sign up on the portal. No sales calls, no discovery workshops — the account exists in a minute and the interview starts when you're ready.
You describe your business in plain language, and the AI asks the questions an analyst would: what you sell, where orders live, which systems you run — CRM, ERP and accounting, payments and banking, ad platforms, e-commerce, spreadsheets, telephony — and which KPIs actually matter to you.
From the interview, the AI drafts your personal workspace: which API connectors to attach, how the dashboard is laid out, how each KPI is defined, and which alert rules to set. It is a proposal, not a product — nothing is live yet.
The draft lands in an ÆTHER engineer's queue. A human reviews how the AI assembled the dashboard, checks every data mapping, connects real credentials and validates live numbers against source systems. AI is a tool under human control here — computation is separated from interpretation, and no client sees a figure an engineer hasn't verified.
You get a production workspace: BI dashboards on live data, AI Q&A over your own numbers, alerts to your messengers, and role-based access for your team. From then on, the workspace grows with you — new sources go through the same review loop.
Revenue, margin, cash and orders on one screen — assembled around your KPI definitions, not a template's.
Thresholds you define, checked continuously. When orders dip or spend spikes, the alert reaches Telegram or Slack — not a report nobody opens.
Ask "why did margin drop in March?" in plain language. Answers come from your verified data model — with the query shown, so you can check the work.
Owner sees everything; a sales lead sees the funnel; an accountant sees payments. Access is scoped per role, per source.
Every source — CRM, ERP, bank, ads, marketplaces — connected in one place, refreshed on schedule, with connector health visible at a glance.
Scheduled PDF and spreadsheet exports for the board, investors or the bank — generated from the same verified numbers as the dashboard.
Each new client deployment that needs a source we haven't wired yet adds it to the library — for everyone after. Custom REST and webhooks cover the rest on day one.
HubSpot · Salesforce · Pipedrive
QuickBooks · Xero · NetSuite · Odoo
Stripe · PayPal · Plaid bank feeds
Google Ads · Meta · TikTok
Shopify · WooCommerce · Amazon
Google Sheets · Excel files · CSV drops
Twilio · Aircall · call logs
any system with an API — wired by our engineers
Pulse follows the house principle behind every ÆTHER system: AI does the assembly and the arithmetic; humans own the interpretation and the keys.
Each workspace keeps its own encrypted credential vault. No shared keys, no cross-tenant access.
Connectors request the minimum: read access to reports and records. Pulse observes your systems; it does not write to them.
An engineer reconciles dashboard figures against source systems before access is granted. If the numbers don't match, the workspace doesn't ship.
Where regulation or policy requires it, the data layer deploys inside the client's own infrastructure — the portal connects to it, not the other way around.
We onboard a small number of companies at a time — every workspace gets a named ÆTHER engineer, and engineers don't scale like servers do.