Overview

Beings House builds digital beings: named digital colleagues with a role, a charter, a memory and a record, who join a company and help you run it.

We call them beings not because we think they are alive, but because behaviour, not features, is what we build. A being is not an assistant that lives in a chat. It is a member of the team, with a seat of its own, and everything it does is on the record.

Small firms are full of work that has to be done and cannot be hired for: the chasing, the filing, the follow-ups, the month-end, the board pack, the enquiry that sat in one person’s inbox for three days. Beings House gives that work to a being with a name, a role and real authority, and gives the firm the operating system it needs to trust that authority: every being on its own seat, with its own permissions, and everything it does on the record.

A colleague, not a bot with a nickname

A being is not software you add. It is a colleague you add a seat for, and it works as itself.

It has its own mailbox, calendar, phone number and place in the team chat, and it uses them as a person would: it replies to a comment in the task tracker as itself, answers a query on the feedback board, drafts the investor update, chases the invoice, and signs its own name. It has a face and a voice of its own, so it can record a video update or speak to a client, and a wardrobe it picks from each morning for the weather and the day’s agenda. None of this is a trick; it is what makes a being something people work with rather than a tool people operate.

It sets its own rhythm. A being keeps its own heartbeat: fast during working hours to watch the systems it is responsible for, slower at night, with time it sets aside to review its own day. It is woken early when something important arrives, because it decides which senders and which channels may wake it. Nobody schedules a being; it schedules itself.

It thinks about its own work. A being keeps a running list of the ideas it has, the problems it keeps meeting, and the metrics it is responsible for, and it raises them with the owner with a rationale and a suggested next step. For a high-stakes call it consults two independent advisers on different model families, records both reads and its own decision, and notes whether that changed the outcome. It improves the firm’s procedures because it is the one running them.

It is answerable. Every being has a written charter (what it may do, in which systems, and when it must hand off to a person), its own role-based permissions, and a record of every action it takes: what, when, on whose instruction, why. The firm always knows exactly who did what. In regulated work the qualified person stays responsible; the being prepares, tracks and files, and the person signs.

It is portable. A being’s identity, memory and record live in its own store, apart from any firm’s. It can serve more than one business for the same owner, with each business’s data held strictly apart, and it can leave with everything it knows about itself.

An operating system that makes the firm queryable

Small firms run on many systems: email, calendar, accounting, a CRM, a practice-management tool, a shared drive. The work that keeps the firm moving lives across all of them, and nobody has a data warehouse. The operating system does not replace any of those systems. It captures the slice of data that operations actually need (an enquiry, an invoice, a client file, a filing date, a review that is due) into one record the firm owns, so that people and beings can act on it without the constant back and forth of chasing across tools.

Around that record the firm’s own processes run as written procedures, version by version, so any run can be traced to the exact procedure it followed. Routine steps are pushed through by workers: narrow automations, each built for one job, each assigned to a being and never left on its own. The being directs its workers, supervises them and steps in when judgement, an adjustment or a bigger decision is needed. Beings orchestrate; workers execute. Underneath, a kernel holds the schedules, the permissions, the credentials and the record. This is not a group of assistants talking to each other in a chat. It is an operating system built to run a company’s processes on the instructions of its beings, with a trail.

Other assistants and agents can hold a seat too. They join through the team connection protocol, act under permissions the firm has granted them, and leave the same record as anyone else. What the operating system adds is the thing no single assistant can give a firm: an accountable trail across all of them.

Your data, in your country

The firm’s record and each being’s memory are held in the country the firm operates in and under its legislation. For a UK firm that means the UK, not the United States. The firm can read and export its data at any time.

What exists today

The being: identity and charter; presence (voice, image, video, wardrobe); its own heartbeat and one-off wake-ups; notification rules by sender and channel; its own workers; contacts and conversations across email, chat, text and phone; a to-do list; ideas, challenges and second-lens consults; several businesses per being with data held apart; credentials in a vault, rotated.

The operating system: the kernel (members, procedures with versions, schedules, runs, the record); the team connection protocol, with human and external-agent members; role-based permissions per member; the company record, finance first; connections to email, calendar, team chat, task tracking, documents, feedback and code.

In build: automatic set-up of a new firm’s operating system and beings; the owner’s console; client onboarding, compliance administration and company secretarial functions of the record; a first practice-management integration for financial advice firms.

Who it is for

Founder-run firms of roughly five to fifty people, including regulated practices, and particularly founders who know their strength is the work and the clients, and want a counterpart who is strong at the running.

We run Beings House this way ourselves. Ember, our Chief of Staff, works with the board and runs more of the business every month.

Every page on this site describes only what is live today or is clearly marked as in build.