How we work

Put how your business works in a place your team owns.

A Company OS starts as a shared folder your team owns. It holds short files that explain the work, point to the records people and AI can use, and name who makes decisions.

Start with the business

Understand how the work really happens.

We usually start with two conversations. First, we learn how people work, where teams get stuck, and what they want to change. Then we look at the tools, systems, and records behind the work.

With your permission, we record and transcribe the conversations. We use them to write down how the business works today, where you want to go, and what to tackle first. Your team checks what we capture.

Work alongside the team

Build it. Teach it. Check that it helped.

  1. Build your Company OS. Write down how the business works, which records to trust, and who makes the call when something doesn’t fit.
  2. Coach people on their actual work. Work one-on-one with the people doing the job and the leaders responsible for it.
  3. Help more of the team use AI well. Teach people when it helps, what to check, and how to run the work themselves.
  4. Automate work worth automating. Agree what would improve, measure how it works today, and check again after the change.

How the context works

Give AI the context it needs to do useful work.

We agree which records to trust, which rules to follow, and who decides when something doesn’t fit. Your team tests the work, practices handling an exception, and makes a change on its own. That is how we check that the team can keep using what we build.

We start with the systems you already use when they can provide reliable answers. If several teams repeatedly need the same answer from different systems, we work out what needs to be joined and whether a shared data model or warehouse would help.

Fictional example

What your team keeps after a billing handoff.

Finance keeps asking sales for the billing start date. Sales and finance can write one short file for the handoff. Here’s what it contains.

Source to use
The approved signed agreement.
AI can help
Draft the handoff and show where the terms came from.
Rule
Hold the handoff if the billing start date is missing.
Who decides
Finance approves the handoff. Sales confirms commercial terms when records disagree.
What we test
A complete deal, one with a missing date, and one with conflicting terms.
What the team practices
Run a fresh case, handle an exception, and update one rule when the process changes.

To see if it helped, compare the share of handoffs finance had to chase before and after.

How to start

Bring the business problem.

Tell us what your people are trying to do, where they get stuck, and what you want to be different. We’ll work out what the team needs to learn, what to build first, and how to check the result.