Applied AI lab

We build AI applications that take the busywork out of enterprise operations.

We're starting with the work that quietly eats enterprise time. Reading and re-keying documents, chasing approvals, and hunting for answers that already exist somewhere. Our first product, Proba, is in development.

Products

Products

Software we build in the lab and share with the community.

View all products

Problem areas

Three problem areas we're exploring.

Beyond Proba, these are the problems we're looking at next, and how far along each one is.

  • Stage: Prototyping

    Document-heavy operations

    Contracts, policies, forms and reports that people read, check and re-key by hand.

    Our angleAI that extracts, cross-checks and summarises, with a person approving anything that matters.

  • Stage: Exploring

    Workflow & approvals

    Requests that sit in inboxes and spreadsheets while someone chases the next sign-off.

    Our angleRouting, reminders and draft decisions that fit the approval rules a team already follows.

  • Stage: Exploring

    Knowledge retrieval

    Answers buried across wikis, shared drives and old tickets that take hours to find.

    Our angleSearch that cites its sources and respects who is allowed to see what.

Problem areas may change as we learn. The Discord hears about it first.

Living with one of these problems?

Tell us how it shows up in your organisation. Real examples shape what we prototype next.

Why "small seed"

Small ideas, tested before they grow.

Every product here starts as a small, testable idea. Most won't make it past the prototype. The ones that prove useful get the time and engineering to grow into software an enterprise can rely on.

Our approach

From seed to scale.

A deliberate, four-stage process decides which ideas earn more investment. Community feedback is part of every stage.

  1. Discover

    Pick a specific, recurring piece of busywork and agree how we'll measure whether it got better.

  2. Prototype

    Build a small working version against realistic documents and workflows to test quality and cost.

  3. Validate

    Put it in front of community members, collect honest feedback, and stop if it isn't useful.

  4. Scale

    Harden what works with security, integration and monitoring, then keep improving it with users.

Principles

What we design for.

Commitments we hold ourselves to from the first prototype onwards.

  1. Your data stays yours

    We design for least-privilege access and audit trails. Customer data will never be used to train models without explicit opt-in.

  2. People stay in control

    For decisions that matter, AI drafts and a person decides. We'll publish how we evaluate quality and failure cases.

  3. Fits what you already run

    We design for single sign-on, standard APIs and existing data stores. No new silo.

  4. Measured, not hyped

    We agree the measure of value before writing code, and report against it honestly, including when something didn't work.

Community

Follow the work as it grows.

Join to see build notes as they happen, try prototypes early and tell us where they fall short.

Main community

Discord

Our main home for the lab. Engineers, operations people and anyone tired of enterprise busywork are welcome.

What's inside

  • #build-notesShort updates on what we're building and what we learned, planned roughly every two weeks.
  • #early-accessFree preview access to prototypes as they become usable, in exchange for honest feedback.
  • #problem-spacesShare the busywork you see at work. The best examples shape what we build next.
Join the Discord (opens external site)

Also on