Get started
A few thousand rows is enough. The data map opens next: every column, drag each onto its level, preview, then check the roll-up. Nothing leaves your browser.
Excel, CSV or JSON. Up to 50,000 rows are read, then the data map opens. Names can be replaced with IDs before you upload.
Share the sheet as “anyone with the link can view”, paste the link, and we read the tab it points at. No sign-in to Google, nothing stored.
The same file, posted to the API or dropped in an S3, Azure or SFTP location you own. Same checks, same report. Included on Business.
Start with a file or a sheet, because every system you run already exports one. From there the same data can arrive on a schedule, or be read from the system it lives in. What is offered depends on the plan: files and sheets now, scheduled delivery on Business, and connections to your systems built with your team on Enterprise.
Now, in your browser. Excel (.xlsx, .xls), CSV, TSV, JSON; Parquet and XML on request.
Any column names, any order. You map them once and the mapping is reused.
Now, in your browser. Google Sheets today; Excel Online, OneDrive and SharePoint, Airtable and Smartsheet on request.
Share the sheet as “anyone with the link can view” and we read the tab it points at.
Business. REST API, Amazon S3, Azure Blob Storage, Google Cloud Storage, SFTP, email attachment.
The same file, nightly or hourly, with the same checks and the same report every time.
Enterprise. SQL Server, PostgreSQL, MySQL, Oracle, Snowflake, BigQuery, Redshift, Databricks, Azure Synapse.
A view your DBA owns, read on a schedule. No write access, ever.
Enterprise. Salesforce, HubSpot, Microsoft Dynamics 365, Pipedrive, Zoho CRM.
Accounts, opportunities, activities and targets, by rep and by region.
Enterprise. SAP, Oracle NetSuite, Dynamics 365 Business Central, Sage, Xero, QuickBooks, Workday.
Actuals by cost centre and account, budgets and forecasts, purchase orders and commitments.
Enterprise. Anaplan, Workday Adaptive Planning, Board, Vena, Planful.
Budget and forecast versions, phased by month, beside the actuals they are compared with.
Enterprise. Oracle Primavera, Microsoft Project, Procore, Jira, Smartsheet.
Work packages, milestones, change requests and rate cards for cost control.
Enterprise. NielsenIQ, Circana, Kantar, retailer portals and EPOS extracts.
Market share, distribution and price beside your own shipments.
Enterprise. Power BI datasets, Tableau extracts, Looker, Qlik.
When the clean table already lives in your BI layer, we read it from there.
Enterprise. Core banking exports (Temenos, Finacle, FIS), general ledger feeds, trade and revenue attribution systems.
Balances, rates, fees and client revenue by desk, product and region.
Tell us. If your source is not listed, it almost certainly exports a file already.
A connection is usually the export your IT team already schedules, pointed at us.
Because every system you run already exports one, and it lets you see the result on your own data in minutes, free, with no account and nothing leaving your browser. Once the mapping and the checks are right, the same file can arrive on a schedule, or a connection can be built to the source.
Yes, on Enterprise. An engineer builds the connection with your team, on your side, reading a view or an export your IT owns. We never hold credentials to your systems, and we never write to them.
As fresh as the delivery. Nightly is usual, hourly if you want it. Coverage and cost figures do not move by the minute, and a scheduled file is easier to audit than a live query.
Tell us what it is. Almost every system exports Excel, CSV or JSON, and the scheduled delivery and API routes take any of them. The connections above are the ones we have built most often, not a limit.