For purpose-driven organisations

Your team is already using AI. Now it’s time to lean in.

Get in touch

Common problems

Problems worth solving

The same problems surface in almost every purpose-driven organisation. Solved well, they return hours to the mission and increase impact without increasing headcount.

  1. Every funder wants the same story in a different shape. Drafting support tuned to your voice and your evidence cuts the rewriting, so the saved hours go back into delivery.

  2. Requests for help arrive by email and wait in a queue nobody can see. Intake and triage automations sort, route and acknowledge them, so people get answers sooner and nothing slips.

  3. Some of the team use AI daily, others avoid it entirely. Training grounded in your real work levels that out, so the whole organisation gets the benefit, not just the early adopters.

  4. Boards and funders now ask how AI is governed. A working policy and governance framework, written in language they can read, turns that question into a strength.

  5. Someone senior rebuilds the same pack every quarter out of exports and copy-paste. Automating the assembly frees that time and makes the numbers consistent between meetings.

  6. Turnover and volunteer churn take the precedent and the ‘how we handle this’ with them. A searchable layer over your own policies and records keeps the answers in the organisation, so new staff get up to speed without shadowing someone for a month.

  7. Retention is slipping while acquisition gets more expensive. Segmentation and tailored engagement built on your existing donor data lift the return on the list you already have, without adding headcount.

The practice

What this looks like for a mission

The same three practice areas and the data work behind them, framed here for organisations that answer to a mission, a board and a funder.

  1. AI Governance

    Rules that protect the mission without slowing it.

    Policies, decision rights and oversight written for the realities of purpose-driven work: client records, counselling notes, volunteer data, funder reporting. The result reads less like a compliance document and more like an agreement. What we use, how we use it safely, who to ask.

  2. AI Capability

    The judgement to use AI well, grown with the people already using it.

    Working sessions for boards, executives and programme staff: practice at weighing a use case, spotting a risk, and knowing when an output should not be trusted. The people already using these tools help shape the rules, so the training lands as recognition rather than correction. Nobody is punished for having been early.

  3. AI Enablement

    Working systems, fitted to the mission and its budget.

    Assistants and automations where the case is proven: intake, reporting, the paperwork that sits between people and the mission. Built small, governed from the first day, and owned by the organisation’s own team when the engagement ends.

Also in the practice

Data Analysis and Visualisation

The mission’s evidence, made legible.

Analysis that shows what the mission is actually producing: honest baselines, measures a funder can trust, charts a board can read without a translator. Often the understated second half of another engagement, and available on its own.

Safety-critical AI work is the strictest training ground for the questions boards and funders are now asking.

Orsana was founded by Monty Daley, who built and governed AI systems at Netsafe, New Zealand’s independent online safety organisation, protecting the people other organisations exist to serve. Read about the practice.

Get in touch to see how Orsana can help your organisation.

A short conversation, no obligation. Monty replies personally.