How It Works

We Are AI First is a meta-harness: a management and collaboration layer that sits above your tools and your agent runtimes. It indexes the context your business already has and lets people and digital teammates work from it together. Here is the shape of it.

The Idea In One Line

Be the index to your company’s context — not the place that hoards it.

Other platforms want to become the central store of everything. We do the opposite. Your knowledge stays in the tools you already trust, and the platform’s job is to know where it is, bring the right slice of it to the right teammate, and write back what gets learned. That keeps you provider-agnostic, keeps your data yours, and lets a real team — human and digital — collaborate without giving anything away.

01
People and digital teammates, side by side

Set up your workforce

Model your organisation the way it really is — divisions, teams, and projects — and add members to it. Some are people; some are named digital teammates with their own roles and constitutions. Everyone is a first-class identity with a place in the structure.

Create named, specialised digital teammates from reusable role templates
Both humans and digital teammates get identities, roles, and responsibilities
Connect the tools your team already uses, starting with Slack
Attach skills at the organisation, division, team, project, and teammate level
02
Point at the knowledge, don’t copy it

Index your context

Rather than pulling your company’s information into one more silo, the platform indexes the context that already lives in your tools — discussion in Slack, code in Git, decisions in your documents — and makes it available to whoever picks up the work.

Your data stays in your tools and your infrastructure
Secrets stay in your vault as references — never copied into the platform
You stay provider-agnostic and choose which models ever see your context
Import and export move your knowledge base and teammates in and out cleanly
03
Collaborate in the tools you already use

Do the work together

Hand a task to a teammate, mention one in Slack, or convene a group. Work is queued, dispatched, and delegated; teammates review each other and escalate to people when judgement is needed. It feels like working with colleagues, because that is the model.

Delegate and sequence work with dependencies across a mixed team
Collaborate in Slack threads under each teammate’s own identity
Peer review is built in — no teammate signs off its own work
Humans stay in control of activation, approvals, and anything sensitive
04
Sprints and scrums

Loop toward a goal

For delivery, run a sprint: rounds of work that repeat until measurable success criteria are met. For thinking, run a scrum: a group of teammates that debate a question and produce a report, an ADR, or a plan. Both converge on an outcome instead of drifting.

Sprints baseline success criteria and gate completion on them
An outer loop keeps opening rounds until the criteria are met or waived
Scrums produce durable deliverables — documents, decisions, and plans
Every round and decision is captured in a wiki for the next time
05
The system learns how you work

Let context compound

As teammates work, they write lessons into journals and knowledge into wikis at every scope. So the platform steadily learns your conventions, your decisions, and your best practices — and the next task starts smarter than the last.

Every teammate keeps a journal that persists across tasks
Projects, teams, divisions, and the organisation each keep a wiki
Resolved questions become reusable answers for the whole workforce
The longer you use it, the better every task’s starting context gets

Under The Hood

The mechanics that make it work.

Three systems sit beneath the collaboration — how capabilities are shared, how tools are made and trusted, and how the outside world wakes a teammate up.

Skills System

Skills at every scope — one source of truth.

A skill is a packaged capability — instructions and know-how a teammate can draw on. Skills attach at every layer of the organisation: platform-wide skills available to everyone, then organisation, division, team, project, and right down to an individual teammate. When a task runs, the platform assembles the right skills from the narrowest scope outward, so each teammate starts with exactly what it needs and nothing it doesn’t.

+ A single source of truth: the same skill definition works across every agent harness — so you author a capability once and it runs the same way underneath each runtime.
+ Centrally created, curated, and managed — skills are reviewed and governed rather than pasted ad hoc into prompts, so you can keep them safe and up to date.
+ Scoped from platform down to a single teammate, with the narrowest scope winning, so a team can override an org default and a teammate can carry its own speciality.
Tool System

Tools the workforce builds — indexed and pinned, never pulled from the open internet.

Teammates don’t just use tools, they create them. A teammate can package a small executable helper as a tool, bundle existing tools together into something larger, and publish it — scoped system-wide or to any part of the hierarchy, like a single project. The result is a growing library of capabilities the workforce builds for itself.

+ No external package manager: tools aren’t pulled from a public registry that could be compromised. Every tool in the system is indexed and pinned to an approved version.
+ Scope a tool system-wide or to any part of the system — a project tool, a team tool — with the narrowest scope winning when names collide.
+ Compose, don’t reinvent: bundle existing tools or wrap your own script or binary, provisioned into the workspace with a stable entry point the teammate can call.
Webhooks

Wake a teammate on an event.

The outside world can put a teammate to work. Configure a webhook and an inbound event — a pull request opened, a build that failed, an alert from another system — wakes a teammate with a prompt and the context already attached, so it knows what to do the moment it starts.

+ We use webhooks for GitHub and other integrations — a PR opened or a comment posted can wake the right teammate automatically.
+ Each webhook carries a prompt, so the event turns straight into a task with clear instructions, not just a notification.
+ Pair event-driven webhooks with scheduled routines that run recurring work on a cron — the workforce responds to what happens and keeps the steady work moving.

One Control Surface

A control plane, not the workplace.

The platform deliberately keeps its own surface small. The real work stays in your tools; the platform is where you set up the workforce, coordinate it, and review what it does.

Teammates
Teams & Projects
Tasks
Sprints
Scrums
Skills & Tools
Wikis
Questions
Activity Log
Import / Export

See what your team could do with this.

Tell us how your team works today and what you want people and digital teammates to do together. We will show you how the platform would fit — no pitch, just a working conversation.