Back to Thinking
Nov 17, 2026|5 min read

From your lab to something customers use

Teams can build their own tools now. The question we hear in every company is how to do that without breaking the systems everyone already relies on. Build in one place and use in another, with someone who checks each tool before it moves across.

Your team can build its own tools now. The worry we hear in every company is how to do that without breaking the systems everyone already relies on. The answer is to build in one place and use in another, with someone who checks each tool before it moves across.

The four places a tool lives

Two places to build and try things, then one check and the live system. A tool only ever moves left to right.

The four places a tool lives

My lab

your own computer, only you

Team lab

shared, inside the organisation

The check

signed off by IT, or by us

Live

customers, colleagues, real work

A change to a live tool goes back through the team lab and the check. Nobody edits the live version directly.

The words we use, and IT's words

Engineers say development and production. Most of the people building tools now aren't engineers, so we use plain names. We call the first two a lab, the way R&D teams and the AI labs do: a place to experiment. Keep this list for when you talk to IT or a supplier.

  • My lab is what IT calls local development: folders on your computer where you try things with Claude.
  • Team lab is a development or staging server: a shared copy the whole team can open, use and test, inside the company.
  • The check is review, QA or release approval: someone who didn't build the tool looks at it and signs it off.
  • Live is production: the version customers and colleagues rely on every day, with real information in it.

What happens in each place

The further right, the more people depend on it, so the more care it gets.

  • In your lab you use samples and the documents you're allowed to use. If it breaks you start again and nobody notices. The work is a folder on your computer and you look after it.
  • In the team lab real documents can be used, and they stay inside the organisation. Nothing is public. If it breaks the team waits while it's fixed. The work is kept in a GitHub repository in your organisation's account, and each tool has one named owner.
  • Live has real customers, real workflows and real information. If it breaks, customers notice. It runs the signed-off version from that same repository, and your IT team looks after it, or we do until you have someone.

Where the team lab runs

As soon as a tool is for more than one person, it needs somewhere shared to run. There are two ways to do it, and the code lives in your GitHub organisation either way.

A private server online

A server rented in Europe, only reachable with your team's logins, paid monthly. It works from home, other offices and on the road, and there's nothing to buy. Your documents sit with a hosting company, so it goes in your data records.

A machine in the office

A box such as an NVIDIA DGX Spark or a Mac Studio, on your own network. It can run AI models itself and it's bought once. Sensitive documents never leave the building and the whole team shares one machine. You have hardware to buy and a cupboard to lock.

The check before anything goes live

Five questions. A tool goes live when all five have a yes and someone has signed for it.

  1. Data. What does it read, where does that go and who can see it? Does it match your AI charter?
  2. Security. Logins for each person, no passwords or keys inside the code, and only the right people can change it.
  3. Connections. If it touches an older system (accounts, stock, the CRM), it has been tested on a copy first and it reads before it ever writes.
  4. It does the job. It passes its scorecard on real examples, checked by the people who'll use it.
  5. An owner and a way back. One named person looks after it, and if something goes wrong we can switch back to the last good version in minutes.

Who signs it off

If you have an IT team, they sign. We prepare the sign-off pack with your team (what the tool does, the five answers, the test results) so IT can review it quickly and say yes or ask for changes.

If you don't, I take responsibility for the sign-off. When a tool needs more than I can check, I bring in a specialist in security or data protection, or someone who knows your older systems inside out.

The person who signs is never someone who built the tool. They come to it fresh from outside the team and check what it does with real information before your customers see it.

Step by step, from idea to live

Step 1 is what we do in the Praxis programme. Steps 2 to 6 are where you might want a hand.

Step by step, from idea to live

  1. 1

    Build in your own lab

    Your folders, your rules file and Claude on your computer.

    In the programme
  2. 2

    Set up the team lab

    GitHub organisation, shared server or office machine, a login each, data rules.

    Set-up, quoted once
  3. 3

    Build and test together

    One repository. The people who'll use it try it on real examples and score it.

    Your team, with support
  4. 4

    The check

    The sign-off pack, five questions, a specialist if needed, a signature.

    Quoted per tool
  5. 5

    Go live

    The signed-off version moves across. We watch the first week closely.

    Part of the check
  6. 6

    Look after it

    Every change goes back to step 3. A short monthly look at what's live.

    Monthly, if you want it

Why it's worth setting up

Building on laptops is where every team starts, and it works for one person. The moment a tool is shared without a team lab, it runs on one laptop and stops when that person is away. Copies get emailed round and nobody knows which one is right. A quick fix goes straight to the people using it, and IT finds out last and says no.

With a team lab and a check, everyone uses the same version from wherever they work. Every change has a name, a reason and a way back. Testing happens where customers can't see it, and IT gets a pack they can say yes to.

We set up the team lab with you, run the check and the move to live for each tool, find specialists when you need them and look after it monthly if you want. The first step is to pick the one tool your team most wants to share. We look at it together for an hour, and I come back with a quote for the team lab and its first sign-off. Get in touch.