Start with what you're trying to find out.
These pages say what Overscore does and where each part is, in the words the app uses. Describe what you need in plain words; the app, or your agent, picks the right door. Everything in the app is the map of every screen.
Ask a question
Plain words in. You get the number, the table it came from, and the SQL folded underneath if you want it. The answer reads what it knows about your business before it reads the data.
Connect a source
Shopify, Stripe and QuickBooks take a pasted key. Your own Postgres links live. Spreadsheets and files drop in. Everything syncs on its own and tells you when something's off, with the fix ready.
The inbox
What broke, what moved, and what it heard you say that needs a yes, one row per thing. Click a row for what it asks and its buttons; your answer becomes something it keeps.
Your fields on any table
A checkbox, an owner or a note on a Shopify order or an invoice, saved against the row beside the source's own columns. It survives every resync, and the next report knows.
Dashboards
Built by you or your agent, in your company's theme, on a phone. Every number on it carries the definition it used.
Context and definitions
What you say becomes a fact it keeps. A number computed in two places becomes one definition with an owner. When it gets something wrong and you correct it, that correction is kept too. Every answer, every dashboard and every agent reads these first.
Your first ten minutes
A new company starts with a sample store already in it, a made-up leather goods shop with an online store and two shops, a year and a half of orders, a cost sheet and a Sales page. It sits in a dataset of its own, sample, apart from anything of yours, and its page says it is from the sample.
Home has a checklist of seven things to do on it. Each one ticks when the app sees it done, never from a button.
- Ask a question about the sample, in the chat beside its Sales page.
- Say yes to a number, the sample's gross margin, waiting in your Inbox.
- Change the page by asking for the Sales page by store.
- Make something new, product margin as a metric from the cost sheet.
- Connect your Claude Code with two commands on your laptop.
- Build a page from Claude Code and publish it.
- Your own data, a connected system or a file.
Show me on the next step takes you where it happens and points at the spot. The chat beside the sample's page offers three messages written for these steps, and the first three messages you send are on us, on Free as on Self-serve. The box on Home and the chat's box say how many are left. After them your own Claude Code is how you keep asking and building, at no cost with us (Use with Claude Code).
When you're done with it, Remove the sample takes all of it, and what you made on it, after one confirm that names each thing. It is on the checklist and in Settings, Company, a chat does it on your yes, and so does ovs sample remove. The checklist keeps its last three steps.
Playbooks
Worked paths through the app for jobs people have, like a report that arrives by email, lead scoring sent back to HubSpot, offline conversions to your ad platforms and sales against goal across companies. Each step says where in the app it is done. What a playbook is.
For whoever's technical
Nothing above needs this section. It's here for the person on your team, or the consultant, who wants to see under the hood.
The warehouse. Every table by dataset, the one you pick with its rows first and what people know about it a click away; a query editor with history and saved queries. Ask, and it writes the query.
Models. SQL kept under a name, as a view or as a table built after what it reads lands, with tests. Download the lot as a dbt project from Settings, Company.
Agents and keys. One address for Claude, Cursor or any agent. A key names the datasets it may use, each at Add rows only, Read, or Read and write, and can be masked (names and emails replaced). Everything an agent does is logged like a colleague's work.
The Postgres door. A Postgres login for a BI tool. Not open yet; its page says what to use meanwhile.
The CLI and the API. ovs on your laptop does what the app does, and the HTTP API does the same for scripts: the CLI reference and the API reference have every command and door, and ovs --help lists every command.