A business question connected through analysis to a clear decision.

    Outsourced analytics

    Outsourced analytics: what should your first project deliver?

    Start with one business question your team needs answered. Then agree what a useful answer would let you do.

    By Stephen Flynn

    You know the reporting needs attention. Perhaps the monthly pack takes days to assemble, or three people bring three different revenue figures to the same meeting.

    It is tempting to start by asking for a dashboard. Something clearer, faster and easier to use.

    But before discussing charts, ask a more useful question: what decision are we struggling to make?

    A first outsourced analytics project should have a clear business question, agreed work and an output your team can use. That might include a dashboard. It might begin with a much smaller piece of analysis.

    Choose one question with a real consequence

    “Help us use our data better” is understandable, but it leaves plenty of room for misunderstanding.

    Try making the question specific. For example: which types of sales opportunity are repeatedly slipping beyond their expected close date?

    That gives the project a purpose. The sales leader wants to understand where the forecast is unreliable and decide which opportunities need attention.

    You can then discuss the information needed, the period to examine and how the findings will be used. You also have a reason to leave unrelated work outside the first project.

    A useful starting sentence is: “We need to understand ___ so that we can decide ___.”

    If the second gap is difficult to fill, spend time there before commissioning the output.

    Agree what will be handed over

    An analysis can be thoughtful and still leave the business unsure what to do next. Agree the deliverables before work starts.

    For the sales example, a sensible first brief could ask for:

    • An agreed definition of a slipping opportunity.
    • An assessment of whether the available CRM history supports the question.
    • A clear comparison of the relevant opportunities, with limitations explained.
    • A discussion of the findings and the actions the sales leader wants to take.
    • A record of the definitions and method, so the work can be understood later.

    These are illustrative deliverables, not a package every business needs. The right scope depends on the question and the condition of the information.

    Be clear about the practical handover too. Who receives it? Where will the files live? Will someone need to refresh it? What support, if any, is included after delivery?

    Find out early whether the information is good enough

    Suppose your CRM stores today’s close date but has no history of earlier dates. That limits what an analyst can say about past changes.

    It is better to discover that near the start than after agreeing a polished report built around information you do not have.

    Ask the analyst to identify the relevant sources and explain material gaps. Some can be resolved within the project. Others may require a change to how information is collected, followed by time to build a usable history.

    The result should distinguish what the records show, what remains uncertain and what would improve the answer. An unsupported conclusion becomes no more useful because it appears in an attractive chart.

    Keep someone inside the business responsible for the decision

    An external analyst brings time and analytical expertise. Your team still brings the context: what the sales stages mean, why a large order moved, and which changes are realistic.

    Give the project a named business owner who can answer questions and bring the right colleagues into the conversation. Agree when they will review definitions and early findings.

    That does not mean attending constant meetings. It means avoiding a situation where the analyst finishes work only to discover that a key term meant something different to the people using it.

    Judge the first project by whether you can use it

    Before starting, agree how you will recognise completion. For example: the sales leader can identify the opportunities behind the forecast changes, understand the gaps in the evidence and decide what to review with the team.

    That is more concrete than “a better dashboard”. It also makes the next decision easier. You can decide whether to repeat the analysis, improve the records, extend the work or bring the task into the team.

    Outsourcing can suit a defined project or ongoing support. An internal hire may suit a continuing role that needs someone embedded in the business. Your first brief should help clarify the work you need, rather than assume one arrangement is always best.

    Write the brief before choosing the chart

    Start with the question, the decision, the available information and the handover. Agree scope, responsibilities, access and costs before work begins.

    You do not need to solve every reporting problem in the first engagement. Choose a useful piece of work your team can understand and act on.

    Data Compass provides outsourced data analytics through focused projects and ongoing support, working directly with Stephen Flynn. To discuss the first question you want answered, .