The lab works with people who carry a question about what AI means for their work. We were running experiments inside real companies before CAPSLOCK had a name, so we start from the work you already do.

who it's for

  • Founders and innovation leaders. You have a question about how intelligence is changing your business, and room to try something real.
  • Marketing teams. Bring the content and the channels you already run; we look for the repetitive part a system can carry.
  • Regulated organisations, like banks. Bring the rules you work under; we treat them as part of the brief.
  • Researchers and universities. Bring a question worth studying; we bring prototypes and a lab that writes down what it finds.
  • Students. Bring curiosity and something you're building; a working session is a good place to start.

two ways in

1 · the core

Our main way of working: three months, give or take for heavy builds.

  1. Month 1, discovery. We learn how your work runs today and where a system would change it. It ends in a workshop and a game plan.
  2. Month 2, prototype. We build the smallest version that works inside your real work.
  3. Month 3, delivery. Something you can show, or the start of a heavier system.

what a project looks like: 2fifty texas bbq's newsletter →

2 · a working session

"Show me what you're building with AI." About two hours with us, on something you're already building with AI. You leave with something concrete: a quick prototype, a sharper prompt, or better questions.

how it starts

We keep only a few collaborations running at a time, so each one gets the lab's full attention. That's also why there's no form here.

  1. You write. The question, where it lives in your business, and what you've already tried. The link below starts the email for you.
  2. We read it properly. A person on the team reads every note and answers it, even when the answer is "not right now".
  3. We talk. If there's a fit, we set up a call to dig into the question together.
  4. A first small step. A working session, or the first month of the core, inside your real work, before anyone commits to more.
flow of four steps: you write the question, where it lives and what you’ve tried; a person on the team reads every note; if there is no fit right now you still get an answer, “not right now”; if there is a fit, we talk on a call to dig into the question together, then run a first small experiment inside your real work. anything more comes only after that, if anyone commits
fig. every note gets a human answer; a fit leads to a call, then one small experiment before anyone commits

who owns the code

You own the code you pay for. If you'd rather not run it yourself, we can host and maintain it for you, and you can take it over whenever you want. We keep the general methods and tools we bring to every project, and we publish lessons, never your name, your data or your code.

We also give talks and workshops.