If you can export it, Aptic can read it.
Connections exist for one reason: a conclusion is only as good as the number of systems it was checked against. Below is what Aptic reads, what each source unlocks, and the limits every connection is under.
Eight kinds of source, and what each one makes possible.
Every business connects a different subset. One source is enough to start; the cross-system conclusions begin at three.
Sales and point of sale
Orders, transactions, product mix, discounts, refunds.
What is actually selling, at what price after discount, and which lines carry the margin.
Advertising and marketing
Spend, campaigns, audiences, email and campaign performance.
What each channel earns after the orders it double-counted, rather than what it reports about itself.
Web and product analytics
Traffic, conversion, activation and the events that precede retention.
Where demand is lost between arriving and paying, and which behaviours predict churn.
Accounting and finance
Revenue, costs, invoices, budgets, aged receivables.
Contribution rather than revenue - and the runway figure that decides how much risk you can take.
Operations and fulfilment
Stock, suppliers, delivery times, returns, service and queue times.
Whether the business can serve the demand it is buying, and what each fulfilled order really costs.
Customers and support
CRM records, pipeline, tickets and their topics, reviews.
Early warning: support volume and review language move weeks before revenue does.
Work and scheduling
Projects, tasks, time entries, rotas, diaries.
Where the hours actually go, what each client or session costs to serve, and which work overruns.
Files, exports and spreadsheets
CSV and spreadsheet exports, statements, documents you upload.
Everything above, for any system with no connector - which is why nothing is blocked on our roadmap.
What a connection grants, and what it never does.
A connection is permission to read, not permission to act. Acting is a separate decision you make separately, per action type.
- Read-only by default. Write access is granted per action type, by you, and never assumed.
- Aptic asks for the narrowest access a source offers. Where a system only offers broad access, the page in your workspace says so plainly.
- Revoking is one click here, and it also works from the other system - nothing keeps working after you cut it off.
- Nothing you connect is pooled with another client.
- Finance is advisory: Aptic never holds a payment credential and never moves money.
A missing integration is a delay, not a wall.
Aptic is in private beta and supports fewer connectors than it intends to. That is a real limitation and there is no point dressing it up - but it is rarely a blocker, because the analysis runs on the data, not on the pipe it arrived through.
Export and upload
A CSV or spreadsheet export gets read the same way a live connection is. Most engagements start with at least one source arriving this way.
Tell us what you use
Connector work is prioritised by what beta clients actually run, so the systems you name genuinely move up the list.
Thin data is stated, not hidden
When a conclusion rests on one source rather than four, Aptic says so and marks its confidence down instead of sounding certain.
Tell us what you run, and we will tell you what it unlocks.
Aptic is in private beta. Send us the list of systems you use and we will say plainly what connects today, what needs an export, and what is not ready.