Skip to content
HORQUVA

Before you change something important, know what it will affect.

OBA Core is the product we're building at Horquva. It shows how an organisation's people, AI, systems, processes, knowledge and vendors are connected, and what happens when something changes.

Talk to us about OBA CoreSee how it works

  1. Connect

    Plug into what you already use.

    Read-only links to your HR system, project tools and code. Nothing to migrate, nothing to type in twice.

  2. Map

    See it all in one place.

    People, processes, systems, vendors and AI agents, pulled together into one picture you can trust.

  3. Understand

    Find where it would break.

    Spot the work that rests on one person, the systems with no backup and the links nobody wrote down.

  4. Simulate

    Try the change first.

    See what happens if someone leaves, a vendor changes or a model is swapped, before it happens for real.

  5. Act

    Fix it, and show your working.

    Clear, ranked next steps, with the evidence behind each one ready for your leadership team.

Someone leaves, a vendor changes, a model is swapped out. Most teams find out what that affected afterwards.

The information to see it coming usually exists. It's spread across HR systems, project tools, documents and people's heads, and nothing joins it up.

Scattered
How work really gets done is spread across HR systems, project tools, documents and people's heads. No one place shows the whole picture.
Resting on one person
Critical work often sits with one specialist or one system, with no backup, and nobody notices until they're gone.
Found out too late
When someone leaves, a vendor changes or a model is replaced, the knock-on effects usually surface after the fact.

One picture of everything important work depends on.

  • People

    Who owns what, who backs them up, and who is carrying too much.

  • AI agents and models

    Which agents run where, who owns them, and what relies on them.

  • Systems

    The software the organisation runs on, and how hard each one is to replace.

  • Processes

    The workflows that matter, and every person and system each one touches.

  • Knowledge

    Where know-how lives, and where it would be lost if someone left.

  • Vendors

    Outside providers, and what depends on them staying.

Three questions, answered with evidence.

  1. What changed?

    OBA Core builds a live picture from the systems you already use, so a change to a person, an agent, a system or a vendor shows up as it happens, with the evidence behind it.

  2. What does it affect?

    It follows the change through every dependency: the processes, agents and people downstream, where there's no backup, and how the organisation's health score moves.

  3. What should we do?

    Test the options before acting. Ask “what if?”, compare scenarios safely, and get ranked recommendations with the reasoning shown, not just a verdict.

Where it's going

OBA Core is being built in five stages, each one useful on its own.

  1. Build the picture

    Connect the systems the organisation already uses.

  2. Find weak points

    One person owning too much, no backup, systems that are hard to replace.

  3. See change effects

    When something changes, show what else is affected.

  4. Test before acting

    Ask “what if?” and compare options safely.

  5. Learn from results

    Record decisions and what actually happened.

Where it helps

Technology companies

Tech teams run on people, software, AI agents, models, vendors and workflows. When an engineer leaves or a model is replaced, the effects are often discovered late. OBA Core shows what that person owns, which agents and workflows depend on them, where there is no backup, and what happens if someone else, or another model, takes over.

A company wants to replace an AI model. OBA Core shows which agents and workflows use it and what is exposed, and lets the team test another model first.

Fewer surprises, safer changes, clearer planning.

Healthcare

Hospitals depend on doctors, nurses, administrators, software, medical systems and vendors, and critical work often sits with one person or one system. OBA Core shows which processes depend on a single specialist, which systems support critical work, and what is affected if a person leaves or a system is replaced.

A hospital plans to replace a system used by several departments. OBA Core shows which teams and processes depend on it and lets leadership test the change first.

Better preparation and continuity. OBA Core supports operations; it does not make medical decisions.

Education and beyond

The same approach works anywhere important work depends on people, systems and vendors that can change: universities, government, banking, manufacturing, energy and large enterprises.

A university finds which courses depend on a single specialist, and plans cover before anyone leaves.

Continuity that doesn't rest on one person.