See the whole business
Connect your sources, monitor what matters and dig into what changed and why. Every result traces back to the query that produced it.
Perimeter automates the routine work in finance, operations and sales: reports, reconciliations, follow-ups and alerts. You stay in charge: every number shows where it came from, so your team can focus on what matters.
select channel, sum(net) as sales
from sales where week = 35
group by 1 order by 2 desc
Trusted by leading teams








Connect your sources, monitor what matters and dig into what changed and why. Every result traces back to the query that produced it.
Model scenarios, challenge assumptions and keep the tradeoffs in plain sight. The plan stays current as conditions change.
It runs workflows inside the controls you set, with visibility into every step. When human judgment is needed, it stops and asks you.
Everyday exploratory questions move to agents you can verify, and the data team focuses on what actually needs human judgment.
The question that used to go into the data team’s ticket queue now gets answered in the same meeting where it came up.
Every figure comes with the query that produced it. If the number matters, anyone can check where it came from before deciding.
Five layers that connect AI to the context and data it needs to do reliable operational work.
Secure, permissioned access to your systems, enforced read-only, and your business definitions encoded. Deploy in our cloud or yours: your data stays yours.
The rules, exceptions and definitions for every table live with the agent. It knows what “active customer” means to your team, which sales count and which suppliers are excluded.
The model, the tools and the reasoning approach are chosen per task. When a cheaper model answers better, we use it.
Before answering, the agent checks its figures against control sources and runs the evals your team wrote. If something doesn’t add up, it says so instead of making things up.
Roles, per-source permissions, per-user scope and a log of who asked what and when. Any connection can be revoked in one click without affecting the rest.
Load the rules, definitions and exceptions for every table, so the agent knows exactly what “active customer” means to your team.
Tell it something once in chat—like “exclude non-compliant suppliers”—and it’s saved and applied automatically from then on.
Write the questions whose answers you already know. The agent goes into production when it passes them, not before.
Describe what you want to monitor. Charts are chosen, wired to live data and laid out on a dashboard, or a full data site with a shareable link.
The same dashboard lives where your team already works: a link, the intranet or an iframe in an internal tool. You decide which filters viewers control and whether the page requires a signed token before it loads.
Every chart comes with a summary of what changed: which segment moved, by how much, and what it means if the trend holds.
Describe the report once. It runs on your schedule and arrives already written to the right people.
Every run is recorded: when it fired, what each step returned and why, without digging through logs.
Add an analysis step inside the workflow and define when it should stop for approval. If the number falls outside the range you set, it waits for a person before sending anything.
Wherever there’s a question nobody got around to answering, Perimeter goes to work. Here’s how each team’s day changes.
The forecast corrects itself when the month shifts, and tells you which account moved it.
See the use caseThe close explained line by line, with the margin variance attributed before anyone opens Excel.
See the use caseStockouts caught before the store reports them, with the SKU, the warehouse and the likely cause.
See the use caseWhere to put the next dollar, matching what was spent against the sales that actually happened.
See the use caseWhat to restock, what to clear and when, using real sell-through by store instead of the national average.
See the use caseThe forecast lives in the same conversation where it gets discussed. Every figure comes with the account, the date and the movement behind it, so the committee debates the decision, not the data.
The margin variance arrives attributed by product line, channel and customer, checked against the accounting close. When a source is missing, the agent flags it instead of filling the gap.
Perimeter matches inventory, sales and shipments at the SKU and warehouse level. When a pattern goes out of range, it alerts you with the likely cause and the history of every time the same thing happened.
Each platform’s spend is matched against the sales that actually happened in your own systems, not the number the platform reports about itself.
The national average hides the decision. Perimeter goes down to the store and SKU level to tell you what to restock, what to move between stores and what to clear before price decides for you.
A tool that lets hundreds of people look at the company’s data needs more governance, not less.
Perimeter can only read. Any attempt to modify or delete information is blocked before it reaches your data.
Connection keys travel encrypted, are isolated per account and are never shown or stored in the browser.
Your data is used only to answer your questions: it doesn’t train models and isn’t shared with anyone. On Enterprise plans, processing can stay in your cloud and your region.
Roles, per-source permissions and a log of everything that was queried, who asked for it and when.
Each person sees only the data meant for them, including when dashboards are shown inside your own application.
Every connection has the minimum permissions it needs and can be revoked in one click, without affecting the rest of the team.
Databases, warehouses, spreadsheets and business apps, all queryable from a single conversation in plain language. No exporting, no copy-pasting by hand.
Ask about a connector
BsaleHow Perimeter compares with traditional BI tools and generic AI assistants.
| Feature | Perimeter | Traditional BI | Generic AI assistants |
|---|---|---|---|
| Implementation time | Days | Weeks or months | Immediate |
| Agent with business context | Trained on your rules | — Not available | Generic, no context |
| Natural-language answers | Accurate and governed | — Not available | Frequent hallucinations |
| Dashboards | One prompt, real time | Built by hand | Static, one-off |
| Alerts and reports | Included, one prompt | Manual setup or add-on | — Not available |
| Governance (roles, audit) | Built in | Enterprise plan only | — Not available |
| Data sources | Databases, apps and spreadsheets | Depends on connector licenses | Manual upload, no large data |
| Verifiability | SQL visible in every answer | Technical users only | — Not available |
What data teams ask before trying it, answered straight.
Not to replace your dashboards. A dashboard answers a question someone planned for, and that’s still useful. Perimeter exists for the other questions: the ones that come up on a Tuesday, matter for an hour and never justified opening a ticket.
That’s where analysis backlogs come from, and where most teams give up and export to a spreadsheet. Perimeter doesn’t replace your reporting layer: it removes the queue in front of the questions that never warranted building one.
No. It takes the repetitive work off their plate: the same five queries they get asked for every week on Slack. Your team goes from answering questions to defining what the numbers mean, and those definitions are exactly what makes the agent answer well.
You see it. Every answer shows the query that produced it, so the error is visible instead of hidden in a number. And you only fix it once: tell the agent what was wrong, it’s saved as a rule and applied from then on.
No. It connects to your data as it is, with no cleanup project first. What you do need is to write down your definitions—what an active customer is, which sales count—and that happens during implementation, in hours, not months.
The first results come out the same day we connect your sources. What takes a bit longer is loading your business context and testing the agents with questions whose answers you already know, before opening it up to the rest of the team.
That’s the normal case, not the exception. Databases, spreadsheets and business apps are queried from the same conversation, so a question that mixes ERP sales with ad spend gets answered without anyone exporting anything.
The price doesn’t spike when you add people who only ask questions. That’s the difference from traditional BI, where every new license pushes people back to asking a coworker for screenshots.
Bad data still produces bad answers, now faster and more confidently, which is worse. That’s why Perimeter’s agents load your definitions before answering, and why every answer shows its query.
Governance matters more, not less: a tool that lets hundreds of people look at the company’s data needs enforced read-only access, per-person permissions and a log of who asked what. Someone still owns what the numbers mean; what changes is that they write it down once, as rules the agent applies, instead of re-encoding them in every report.
Most trials fail because they test the wrong question. Ask any tool something that already has a report and it will look good, because the answer is a lookup.
Test the questions that never became a report, and hold us to the same checks as anyone else: can you see the query? What happens with the second question? How do you correct it? What does it cost as usage grows? Does it reach your data as it is?
Tell us what you want to answer and we’ll show you Perimeter on your own sources.
Thanks for reaching out. We read every message and reply within one business day.
Perimeter is implemented together with your team: we connect your sources, load your business context and test the agents with questions whose answers you already know before putting them to work.
Let’s talk about your data. We reply within one business day.