Sidekick for operations and finance leaders: business answers in plain English

The everyday problem

For the people actually running operations, finance, or supply chain, the data conversation usually has nothing to do with platforms or ontologies. It has to do with a much smaller question, asked dozens of times a week: can I get a straight answer to this question without raising a ticket?

Most of the time, the honest answer is no. The data exists somewhere. The dashboard probably has it, or could be built to have it, but the dashboard was designed for a different question. The BI team is two weeks out. The person who knows where the relevant field actually lives is on leave. So the question either gets shelved or gets answered with a guess.

This is the layer Sidekick fixes for non-technical users — not by adding another dashboard, but by removing the need to wait for one.

The core insight: For operations and finance leaders, the value of a data platform is measured in the number of questions that get answered today rather than next sprint. Sidekick is designed to move that number significantly.

How it works for a non-technical user

Sidekick exposes the data estate to authorised users through Microsoft Teams. The interface is conversational. A user asks a question in plain English, and Sidekick assembles the answer from the relevant fields across the systems it is connected to.

The questions can cross systems without the user needing to know that they do. A supply chain lead asking about delivery exceptions does not need to know that the answer involves joining records from the warehouse management system, the carrier integration, and the customer record in the CRM. The ontology Sidekick has built handles that. The user just asks.

Three properties matter for the non-technical user.

The answers come back with provenance. Sidekick can show which fields, in which systems, were used to produce the answer. The user does not have to take it on trust.

The answers respect access controls. A user asking a question only sees data they are authorised to see. Restricted fields are masked. The conversation through Teams inherits the same role-based access that controls every other part of the system.

The answers are current. Sidekick is not querying a stale snapshot. The view of the estate is continuously updated, so the answer reflects the current state of the underlying systems.

What Sidekick Pulse adds

Alongside the Teams interface, end users have access to Sidekick Pulse — the client-facing intelligence dashboard. Pulse is what users tend to mean when they talk about Sidekick day-to-day. Let me pull up Pulse becomes a normal part of the conversation.

Pulse gives a non-technical user four things in one place:

• The data dictionary. Plain-English descriptions, quality scores, and sensitivity classifications for every field across the estate. Useful when a user wants to understand what a field actually means before relying on it.
• The enterprise ontology. A visual map of the business entities — customers, orders, products, suppliers — and how they relate across systems. Useful for understanding what is connected to what.
• Natural language query. The same conversational interface available in Teams, accessible directly through Pulse. Useful for ad-hoc questions where the user wants to dig into the answer.
• The governance dashboard. Sensitivity heatmaps, quality scoring, completeness metrics, and risk visibility. Useful for users who own a process and want to understand the data underneath it.

The combination is less about giving a non-technical user new powers and more about removing the friction between having a question and getting an answer.

Who actually uses this

The user profile here is straightforward. Operations managers running daily exception reports. Finance managers chasing reconciliation between systems. Supply chain leads tracking commitments against actuals. Procurement specialists looking at supplier performance. None of these users are technical in the traditional sense, but all of them spend a meaningful part of their week trying to get a clear answer out of the systems the business depends on.

For these users, Sidekick is not a strategic capability. It is a way of getting their job done with less waiting.

Why this drives adoption

Most data platforms fail at the adoption stage, not the deployment stage. The technology works, the dashboards exist, but nobody uses them and the platform quietly fades into background noise.

The reason Sidekick tends to land differently is that the daily-use barrier is genuinely low. The interface is Teams — a tool the user already lives in. The question is asked in the language the user already speaks. The answer arrives in the same conversation, with the relevant fields cited. There is no new application to learn, no new login to remember, no new mental model to adopt.

The compounding effect of this is significant. As more users start asking questions through Sidekick, the platform learns more about how the business actually uses its data, and the answers get sharper. The flywheel is not artificial — it is simply what happens when a useful tool is genuinely embedded in the way people already work.

What this means for the wider business

For the leaders accountable for the data investment, the adoption story matters because it is the difference between a platform that gets justified once and a platform that becomes part of how decisions get made.

The signal to look for is the question that previously required a ticket and now does not. Multiply that signal across an organisation and the cumulative effect is meaningful: faster decisions, fewer reconciliation cycles, fewer hours spent on questions that should have taken minutes, and an organisation that learns to operate on evidence rather than guesswork.

The takeaway

The strategic case for Sidekick lives in the office of the CIO and the partner conversation. The daily case for Sidekick lives in a Teams window, where an operations manager asks a question about exceptions and gets a clear answer in the time it would normally take to write the ticket.

Both layers matter. The strategic case is what gets the platform deployed. The daily case is what makes it stick.