AI connected to your business data
Ask questions about your business. Get answers from your own data.
We build custom AI assistants that connect to your business database. Your team can ask about orders, stock, schedules and other agreed records in plain language, with access controlled by staff role.
The answer is in the system. Finding it takes too many steps.
A simple question can mean opening several screens, filtering a report or waiting for someone who knows where to look. An assistant gives your team a more direct way to find the information they are allowed to see.
Ask the questions your team already asks.
| Team | Example question | Useful answer format |
|---|---|---|
| Sales | Which of my orders are still pending this week? | Order list, status and next recorded milestone |
| Operations | Which jobs are waiting for a quality check? | Job list and current stage |
| Inventory | Which items are below their reorder level? | Item, available quantity and recorded threshold |
| Finance | Which invoices are overdue by more than 30 days? | Invoice list, age and outstanding amount |
| Management | How do this month's confirmed orders compare with last month? | Comparison using an agreed definition of confirmed orders |
Illustrative examples. Available answers depend on your records, data quality and the scope we agree.
A direct answer, with the relevant records beside it.
Which packing materials are below reorder level?
Two packing materials are below their recorded reorder level.
| Material | Available | Reorder level |
|---|---|---|
| A4 cartons | 12 | 30 |
| Shipping labels | 6 rolls | 20 rolls |
Which of these has an open purchase order?
A4 cartons have one open purchase order. I found no open purchase order for shipping labels in the connected records.
The answer should respect the person's access.
We define which records each role can access before connecting the assistant. A salesperson may see assigned customer orders. An inventory manager may see stock across agreed locations. Financial records can remain restricted to the people authorised to view them.
These permissions must be enforced by the connected system, not left to instructions in a chat prompt.
Built around your database and your business terms.
- 01
Understand your records
We review the databases, relationships and definitions behind the questions you want answered.
- 02
Define access
We agree staff roles, permitted records and which information is outside the assistant's scope.
- 03
Connect and build
We create the assistant and connect it to the approved data sources.
- 04
Test real questions
We check results against known records, including missing data, ambiguous wording and attempts to access restricted information.
- 05
Launch and review
Your team starts with an agreed set of questions, and we review how the assistant performs in use.
You may be ready if…
If your records are scattered or inconsistent, the first step may be connecting and organising them. We can scope that work before adding an assistant.
- Your business already keeps useful records in a database or business application.
- Staff repeatedly ask for the same operational information.
- Reports require a small number of people to retrieve them.
- You can define who should see which information.
What clients say.
“From migrating more than 20 million records to building sign detection from roadway video, Brown Button has taken on some of our hardest technical work. They ask the right questions, they're honest about trade-offs, and they deliver.”
Manoj RavichandranProject Head, Rieker Inc.“We needed one system for our office, our carers and our patients, and Brown Button understood home care as well as the software. Today our team plans over 2,000 hours of care a week on it. They felt like part of our team, not a vendor.”
Sajeesh KesavanFounder, Link Healthcare
Questions, answered.
Can it work with our existing database?
We review the database, available interfaces and access arrangements first. We then confirm which sources can be connected and what preparation is needed.
Do we need to replace our current software?
Not necessarily. The assistant can be scoped as an additional way to access information in an existing system, where a suitable connection is available.
Can every employee see every answer?
No. The agreed role and record permissions determine the information a person can access. We test those boundaries as part of delivery.
How current are the answers?
That depends on how the source is connected and updated. We agree the refresh behaviour and explain it to users before launch.
What happens if there isn't enough information?
We design for the assistant to ask a clarifying question or explain that it cannot answer from the available records. Important answers should be checked against the underlying records.
Can it update our database or send messages?
This service focuses on retrieving information and answering questions. Any ability to change records or take actions would need a separate scope and controls.
Where does our data go?
The proposal identifies the hosting arrangement, AI providers, information sent for processing and retention settings. These details depend on the agreed implementation.
What costs continue after launch?
Hosting, model usage, connected services and support may carry ongoing costs. We separate these from the initial build in your proposal.
What would you ask your business data?
Bring three questions your team regularly needs answered and a brief description of where those records live. We'll help you assess what an assistant could do.
Discuss your data