Do it yourself

From an everyday computer to a workspace for AI.

Ten stages from an ordinary Windows or Mac computer to a workspace where an AI works with your files, with every command and every check.

To the first stage Get the pack by email

What this is about

What ends up on your computer.

A setup is not a single program but a small order of four parts. Know them and every stage of this guide makes sense, and later you know where to look when something sticks.

The vault: your working folder
The vault is one person’s folder on their computer: projects, notes, documents and the instructions for recurring tasks in one organised place. We organise it by PARA, into projects, areas, resources and archives. It opens in Obsidian by default; other tools work too, because the files stay plain text in Markdown.
The AI harness: where the AI works
An AI harness is the workspace in which the AI reads your files and carries out agreed steps: creating files, drafting texts, writing small programs. The choice is yours; we recommend Claude Code, and this guide sets it up. Claude Code starts in one folder and works there: before it reads or changes files outside that folder, it asks you.
Project repositories: each project on its own
Each project gets its own folder with its own history, a Git repository. It keeps every saved version, including every change the AI makes, and each one can be undone. What a team shares lives in the shared project repository that you control, for example on GitHub or on your own Git server.
Where things run
What you set up with this guide runs on your computer, and only while it is switched on. Your working files stay in the vault on your computer. The AI itself, the language model, runs at the AI provider: what you show the AI goes there to be processed.

The tools underneath, and what each is for

Terminal: The window where you type commands. You install and check the other tools in it, and Claude Code runs in it.
Git: Keeps every version of your files. You see what changed and undo a change that does not fit.
GitHub: Keeps your project repositories off your computer: as a backup, and as the shared place for a team.
Node.js: Many extensions for AI tools run on it, for example an MCP server, through which the AI harness reaches other programs.
Python: The language of many small helper programs for spreadsheets, documents and data. When the AI writes a script for your workflow, it is often Python.

Three rules that apply from the start

Credentials never belong in a chat, not even the one with the AI. Keep them in a password manager.
Work with sample files instead of real client data for the first weeks.
Let the AI prepare, not finish: you check every draft before anything leaves your computer.

The guide

Ten stages, in this order.

Each stage builds on the one before and says what it is for, which commands to type, how to tell it worked, and what to do when it did not. You need no prior knowledge, just some patience and a task you would like to get rid of. Windows comes first each time, macOS second; copy the commands with the button next to them and paste them into the terminal. Every stage ends with a check, and you can stop after any of them and carry on later.

The commands are as of October 2026. If a maker’s page says otherwise, the maker’s page wins; the links are at every stage.

Stage 01

Prepare the computer

Before anything is installed, settle three things: whether your system is recent enough, whether you may install software, and whether your important files are backed up. It takes ten minutes and saves you the evening when the permissions suddenly turn out to be missing.

On both systems

At least 4 GB of memory and an internet connection; Claude Code needs both.
Administrator rights on the computer. If an IT company looks after it, ask them first; some companies block installing software on purpose.
A current backup of your important files before any program may write in your folders.
A password manager and two-factor authentication for the new accounts you create in the next stages.

Windows

You need Windows 10 version 1809 or later, or Windows 11. The window the command below opens shows the version.
On Windows this guide installs with winget, Microsoft’s package manager. It comes with Windows 11 and current versions of Windows 10; if it is missing, install “App Installer” from the Microsoft Store.

macOS

You need macOS 13 (Ventura) or later. The version is in the Apple menu under “About This Mac”, or the command below shows it.

How to check

You know your system version, and on Windows winget reports a version number. You type the commands in the terminal; the next stage shows how to open it.

Windows

```
winver
```
Opens a window with the Windows version, for example “Version 22H2”.
```
winget --version
```
Shows a version number like “v1.9…”.

macOS

```
sw_vers
```
Shows the macOS version under “ProductVersion”, for example 14.6.

If it sticks

Windows says “winget” is not recognised.: Install or update “App Installer” from the Microsoft Store, then open a new terminal window.
Installing shows a block, or a window asks for an administrator password you do not have.: This is where self-help ends. Ask your IT company; do not work around the block.

In the Setup We check the computer before installing and set up the software on Windows and macOS, with your IT partner’s approval where needed.

The makers’ pages

Stage 02

Open the terminal

The terminal is the window where you type commands instead of clicking. All further stages work in it, and Claude Code runs in it. A command is one line of text; you confirm it with Enter. After each installation open a new window, because one that is already open does not know the new programs yet.

Windows

Open the Start menu, type “Terminal” and open the program. On Windows 10 it is called “Windows PowerShell”; the newer “Windows Terminal” is free in the Microsoft Store.
The line starts with “PS C:\Users\…>”. The “PS” tells you that you are in PowerShell. If it is missing, you are in the old Command Prompt (CMD); open PowerShell, because the commands in this guide are written for PowerShell.
To paste: Ctrl + V or a right-click in the window.

macOS

Open “Terminal” under Applications › Utilities, or press Cmd + Space and type “Terminal”.
Then install Homebrew, the package manager this guide uses on the Mac. The installer asks for your Mac password (no characters appear as you type, which is normal) and installs Apple’s command line tools along with it if needed.
At the end Homebrew shows one or two commands under “Next steps” that add Homebrew to the terminal’s search path. Copy those lines from your terminal and run them; they depend on your Mac.

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Installs Homebrew (the command from brew.sh).

How to check

The terminal answers a command, and on the Mac Homebrew reports ready.

Windows

```
$PSVersionTable.PSVersion
```
Shows the PowerShell version, for example 5.1 or 7.x.

macOS

```
brew --version
```
Shows a line like “Homebrew 4.…”.
```
brew doctor
```
At best says “Your system is ready to brew.”; otherwise it names what to fix.

If it sticks

Mac: “command not found: brew” right after the installation.: The lines under “Next steps” were not run. Scroll back in the terminal, run them and open a new window.
Windows: a line with “&&” reports an error.: You are in PowerShell and the command is meant for CMD, or the other way round. Use the commands in this guide in PowerShell.

In the Setup You do not need to know the terminal then: you start your workflows with short commands we set up, and check the results wherever suits you.

The makers’ pages

Stage 03

Install Git

Git keeps every version of your files that you save. Later you see what changed and undo any change, including one the AI made. On Windows, Anthropic also recommends Git for Windows so that Claude Code can use Bash; without Git, Claude Code falls back to PowerShell.

Windows

Install “Git for Windows” with winget. It brings Git Bash and the Git Credential Manager, which later handles signing in to GitHub.

```
winget install --id Git.Git -e --source winget
```
Installs Git for Windows (the command from git-scm.com).

macOS

Install Git with Homebrew. An older version from Apple is often already there; the one from Homebrew is more recent.

```
brew install git
```
Installs Git.

Then, on both systems

Open a new terminal window and record your name and email address once. Git writes both into every saved version. Use the address you will create your GitHub account with in the next stage.
The third line names the first branch of every new project “main”, as GitHub does.

```
git config --global user.name "First Last"
```
Your name, as it should appear in every version.

git config --global user.email "name@company.com"

Your email address.

git config --global init.defaultBranch main

The first branch is called “main”.

How to check

Git reports its version and shows your name and address.

Windows

```
git --version
```
Shows a line like “git version 2.…windows…”.
```
git config --global --list
```
Shows user.name, user.email and init.defaultbranch.

macOS

```
git --version
```
Shows a line like “git version 2.…”.
```
git config --global --list
```
Shows user.name, user.email and init.defaultbranch.

If it sticks

“git” is not recognised although the installation finished.: Close all terminal windows and open a new one. An open window does not know newly installed programs.
Later Git says “Please tell me who you are”.: Name and address are missing. Run the two “git config” lines above.

In the Setup In the Pro Setup we create a structure for your project files; Git is among the software we install for it.

The makers’ pages

Stage 04

Create a GitHub account

GitHub keeps your project repositories off your computer. That is your backup if the computer fails, and the shared place when a team later works on the same project. Only the people you invite see a private repository. A free account is enough to begin with.

On both systems

Create an account at github.com, with an address you will keep using.
Turn on two-factor authentication straight away (Settings › Password and authentication). GitHub requires it for many accounts anyway.
Then install GitHub CLI, the program “gh”. It signs Git in to GitHub and creates your first repository in stage 9. At “gh auth login”, choose GitHub.com, HTTPS and signing in with the browser, and confirm that Git may use your GitHub sign-in.
Individual projects go on GitHub, not your whole vault: the vault is your personal folder.

Windows

```
winget install --id GitHub.cli
```
Installs GitHub CLI.
```
gh auth login
```
Signs you in to GitHub in the browser (in a new terminal window).

macOS

```
brew install gh
```
Installs GitHub CLI.
```
gh auth login
```
Signs you in to GitHub in the browser.

How to check

GitHub CLI reports that you are signed in, with your user name.

```
gh auth status
```
Shows “Logged in to github.com account …”.

If it sticks

When uploading, Git asks for a password and rejects your GitHub password.: GitHub does not accept an account password for Git. Sign in with “gh auth login” and confirm that Git may use that sign-in.
“gh” is not recognised.: Open a new terminal window after the installation.

In the Setup What your team shares we put in the shared project repository that you control: on GitHub, on your own Git server or wherever you prefer.

The makers’ pages

Stage 05

Install Node.js

Many extensions for AI tools run on Node.js, for example an MCP server, through which Claude Code reaches other programs such as your calendar or a database. The helper from the starter pack (stage 10) runs on it too. Claude Code itself does not need Node.js when you install it as in stage 7. Choose the “LTS” version: it is maintained the longest.

Windows

Open nodejs.org, choose the LTS version and download the “Windows Installer (.msi)”. Run it with the suggested settings.

macOS

Open nodejs.org, choose the LTS version and download the “macOS Installer (.pkg)”. Run it with the suggested settings.

How to check

Node.js and its package program npm each report a version number (in a new terminal window).

```
node -v
```
Shows a version number starting with “v”; the number depends on the current LTS version.
```
npm -v
```
Shows a version number.

If it sticks

Windows: “npm” says running scripts is disabled on this system.: That is PowerShell’s execution policy. The usual setting for your own user account allows local scripts and requires a signature for downloaded ones. If an IT company looks after your computer, ask them first.
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
Applies to your user account only.

In the Setup We install the software your setup needs; which depends on your workflows.

The makers’ pages

Stage 06

Install Python

Python is the language of many small helper programs for spreadsheets, documents and data. When the AI writes a script that, say, copies details from PDF files into a spreadsheet, it is often Python, and it only runs if Python is installed.

Windows

On Windows you install the “Python install manager”, which the Python documentation recommends. It manages the Python versions for you.
Then open a new terminal window. The first time you run “python”, the manager installs the current Python version.

winget install 9NQ7512CXL7T -e --accept-package-agreements --disable-interactivity

Installs the Python install manager (the command from the Python documentation).

macOS

On python.org, under Downloads › macOS, download the installer of the current version and run it. On the Mac the command is then “python3”.

How to check

Python reports its version.

Windows

```
python --version
```
Shows a line like “Python 3.…”; the first time, the manager installs the current version first.
```
py list
```
Lists the installed Python versions.

macOS

```
python3 --version
```
Shows a line like “Python 3.…”.

If it sticks

Mac: “command not found: python”.: On the Mac the command is “python3”.
Windows: a different Python version starts than you expected.: The manager prefers the versions it manages itself. “py list” shows them; “py install” installs the one you want.
Windows: “python” is not found or behaves oddly.: Click Start, open “Manage app execution aliases” and check that the aliases for “Python (default)” are on. If they already are, switch them off and on again; that is what the Python documentation recommends.

In the Setup We install the software your workflows need; Python is often part of it.

The makers’ pages

Stage 07

Set up the AI harness: Claude Code

Claude Code is the workspace in which the AI works with your files. You start it in a folder; it reads the files in it, suggests steps and carries out what you allow. It runs in the terminal and connects to your account with Anthropic.

On both systems

You need an account with Anthropic: a Claude subscription (Pro, Max, Team or Enterprise; Anthropic recommends these) or a Claude Console account with pre-paid credit. Usage costs depend on the plan; Anthropic lists the current prices. You open the account yourself, in your own name.
Install Claude Code with the official installer. It shows no progress until it is done; wait for the prompt to come back. After that, Claude Code updates itself in the background.

Windows

You enter the command in PowerShell. With Git for Windows from stage 3, Claude Code uses Bash.

```
irm https://claude.ai/install.ps1 | iex
```
Installs Claude Code (Anthropic’s command for PowerShell).

macOS

You enter the command in the terminal.

```
curl -fsSL https://claude.ai/install.sh | bash
```
Installs Claude Code (Anthropic’s command for macOS).

Then, on both systems

Open a new terminal window and start Claude Code. On first start it signs in to your account in the browser; after that the sign-in is kept. “/exit” ends the session again.
For real work, always start Claude Code in a project’s folder, not in your user folder. That comes in stage 9.

```
claude
```
Starts Claude Code and walks you through signing in the first time.

How to check

Claude Code reports its version, and the diagnosis finds no problems. In a running session, “/doctor” checks the same and fixes what it can.

```
claude --version
```
Shows a version number followed by “(Claude Code)”.
```
claude doctor
```
Checks the installation without changing anything.

If it sticks

Windows: “claude” is not recognised.: The install folder is missing from the search path. These two lines add it for your user account (from Anthropic’s guide); then close PowerShell and open a new window.
$currentPath = [Environment]::GetEnvironmentVariable('PATH', 'User')
Reads your search path.
[Environment]::SetEnvironmentVariable('PATH', "$currentPath;$env:USERPROFILE\.local\bin", 'User')
Adds Claude Code’s folder.
Mac: “command not found: claude”.: The install folder is missing from the search path. These two lines add it (from Anthropic’s guide).
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
Adds Claude Code’s folder.
source ~/.zshrc
Reloads the setting.
Windows: “'irm' is not recognized”.: You are in the Command Prompt (CMD), not in PowerShell. Open PowerShell and try there.
The installation stops with “403” or another message.: Anthropic’s “Troubleshoot installation” page matches each message to a fix; Claude Code is also only available in the countries Anthropic supports.

In the Setup We install the chosen AI harness; Claude Code is one option. We keep credentials out of chats, for example in 1Password.

The makers’ pages

Stage 08

Create the vault

The vault is your working folder for everything to do with the AI: projects, notes, documents and the instructions for recurring tasks. Organise it by PARA from the start: projects have a goal and an end, areas run continuously, resources are reference material, and the archive takes what is done. That way you and the AI later find what goes where.

On both systems

Create a folder “Vault” with four subfolders in your user folder; the commands below do it in one step. You may choose the place freely; the guide assumes your user folder.
Optional: install Obsidian and open the folder there with “Open folder as vault”. Obsidian shows your notes linked; the files stay ordinary text files that Claude Code reads too.
If the vault sits in a folder synced to a cloud (OneDrive, iCloud), make sure projects under Git are not changed from two sides at once.

Windows

mkdir $HOME\Vault\1-Projects, $HOME\Vault\2-Areas, $HOME\Vault\3-Resources, $HOME\Vault\4-Archive

Creates the vault with the four PARA folders.

macOS

mkdir -p ~/Vault/{1-Projects,2-Areas,3-Resources,4-Archive}

Creates the vault with the four PARA folders.

How to check

The vault holds the four folders.

Windows

```
Get-ChildItem $HOME\Vault
```
Lists 1-Projects, 2-Areas, 3-Resources and 4-Archive.

macOS

```
ls ~/Vault
```
Lists 1-Projects, 2-Areas, 3-Resources and 4-Archive.

If it sticks

You cannot find the vault in File Explorer or the Finder.: It sits directly in your user folder, not under “Documents”. Windows: type %USERPROFILE% into File Explorer’s address bar. Mac: in the Finder, Shift + Cmd + H opens your user folder.

In the Setup The Basic Installation gives you a vault template; in the Pro Setup we set up your vault as your working folder, and our platform with it. Local, our local app, connects it to the platform.

We are still matching the names of the four folders with our vault template.

The makers’ pages

Download Obsidian

Stage 09

Create the first project

Now everything comes together: a project folder in the vault with the templates from the starter pack, its own Git repository, a private copy on GitHub, and Claude Code starting in that folder. Claude Code then works in exactly this project and reads the instructions in the file “CLAUDE.md” when it starts.

On both systems

Request the starter pack at the bottom of this page and download it through the link in the email.
Unpack it into the “1-Projects” folder of your vault and rename the folder “jules-starter-pack” after your first workflow, for example “first-workflow”.
Copy the instructions file from “templates” into the project folder as “CLAUDE.md”. Claude Code reads this file every time it starts in this folder.
Make the folder a Git repository, save the first version and create a private copy on GitHub with GitHub CLI.
Start Claude Code in the project folder and enter the first prompt: “Read the file 02-quick-setup.md. Then ask me at most five questions before you suggest anything.”

Windows

cd $HOME\Vault\1-Projects\first-workflow

Changes to the project folder.

Copy-Item templates\instructions.md CLAUDE.md

Creates the instructions for Claude Code.

```
git init
```
Makes the folder a Git repository.
```
git add .
```
Stages all files for the first version.
```
git commit -m "First version"
```
Saves the first version.
```
gh repo create first-workflow --private --source . --push
```
Creates a private repository on GitHub and uploads the version.
```
claude
```
Starts Claude Code in this project.

macOS

```
cd ~/Vault/1-Projects/first-workflow
```
Changes to the project folder.
```
cp templates/instructions.md CLAUDE.md
```
Creates the instructions for Claude Code.
```
git init
```
Makes the folder a Git repository.
```
git add .
```
Stages all files for the first version.
```
git commit -m "First version"
```
Saves the first version.
```
gh repo create first-workflow --private --source . --push
```
Creates a private repository on GitHub and uploads the version.
```
claude
```
Starts Claude Code in this project.

How to check

Git shows the first version, GitHub shows the private repository, and Claude Code knows your instructions: ask it “What is in CLAUDE.md?”.

```
git log --oneline
```
Shows a line with “First version”.
```
gh repo view --web
```
Opens the repository in the browser.

If it sticks

Claude Code does not know your instructions.: The file must be called “CLAUDE.md” and sit in the folder where you start “claude”. Quit Claude Code, change to the project folder with “cd” and start it again.
“gh repo create” says the repository already exists.: Choose another name, or upload into the existing repository.
Claude Code wants to run a command you do not understand.: Decline and ask what the command does. You decide what runs.

In the Setup In the Pro Setup we set up three to five commands that start your workflows, and in an introduction session you practise with your own documents how to start them and check the results.

The makers’ pages

Claude Code quickstart (Anthropic)

Stage 10

Set up the helper, and keep going

The starter pack holds a small, optional helper for Claude Code: when Claude runs into a problem or you ask for debugging, Claude suggests once per session, politely, that you give Jules a call to have it built properly. The helper sends nothing and keeps nothing of yours. After that you keep working with the templates and prompts, step by step.

On both systems

The helper’s instructions are in the pack under “claude-code-helper/README.md”: copy one file into the folder “.claude/hooks” in your user folder, add two entries to the file “.claude/settings.json” next to it and restart Claude Code. Removing it means deleting both again.
Then work through the templates: the quick setup first, then the deeper interview that Claude Code holds with you. The prompts for it are further down.
After each step of work, save a version with “git add .” and “git commit”, and upload it to GitHub with “git push”.

How to check

In Claude Code, the command “/hooks” shows the helper’s two entries.

```
/hooks
```
Type it in Claude Code, not in the terminal.

If it sticks

The helper never says anything.: It only speaks up after a problem or a request for debugging, and only once per session. Check with “/hooks” that the entries are there.

In the Setup When you reach a part you would rather hand over: the Basic Installation is a fixed CHF 490.–, the Pro Setup CHF 1'490.–.

The makers’ pages

Hooks in Claude Code (Anthropic)

The Setup

Where the Setup takes over.

The Setup is the same route, done by us, plus what a guide cannot do: connect your systems, tailor the workflows to your work and show you how to work with them. This is how we go about it:

The computer first, then the installation
We look at your computer before we change anything, and set up the software on Windows or macOS. If an IT company looks after your computer, we install with their approval.
Installation by package
Depending on the package, we install the chosen AI harness and the software your setup needs. We keep credentials out of chats, for example in 1Password or a designated local file.
Vault, platform and workflows
The Basic Installation gives you a vault template and one or two basic workflows. In the Pro Setup we set up your vault, our platform and workflows with AI agents, connect your first existing systems and create three to five commands that start your workflows.
Remote access only with your consent
We work on your device on site or by remote access, and we only carry out remote access from Switzerland. We have no standing access: every remote session needs your consent. At handover we remove our access.
A handover that lasts
A handover document records what we set up. After the Basic Installation we check in after two weeks on how the workflows are running; the Pro Setup includes 30 days of follow-up support and an introduction session.

We will describe here exactly how we check the computer before the installation.

We will record here where we put the software, the vault and the projects on your computer.

The Basic Installation is a fixed CHF 490.–; the Pro Setup for CHF 1'490.– also connects your first existing systems.

See the Setup and packages Write to us

In the pack

Fill-in templates, not a course.

The pack is a ZIP of Markdown files: plain text that any editor opens and any AI assistant can read. In stage 9 it becomes your first project. The pattern comes from practice: a short setup first, a thorough conversation later.

00 Start: The ten stages of this page with every command, to tick off.
01 Prerequisites: The list from stage 1, with room for your notes.
02 Quick setup: Ten questions about your business, your workflow and what the AI may and may not do.
03 Deeper interview: An interview your AI assistant holds with you. Questions about the work only, nothing private.
04 Prompts: The prompts from below, ready to copy.
Templates: A workflow map, a profile of the expected result, an instructions file for the AI harness (your later CLAUDE.md) and a sheet for the next step.
05 When to get help: The honest list from below.
Claude Code helper: Optional: a small hook. When Claude runs into a problem or starts debugging, it suggests once per session, politely, that you give Jules a call to have it built properly. It sends nothing and keeps nothing; how to set it up and remove it again comes with it.

The pack carries our watermark: every file starts with a line naming the starter pack and its version, and ends with our contact address; the logo sits in the folder “_jules-solutions”. You may use and adapt the templates freely. Keep the lines and our contact details are at hand when something sticks.

Everyday prompts

Four sentences that take work off your plate.

Enter them in Claude Code once the project from stage 9 is in place. They work in any other common AI program too.

Understand first

Read the file 02-quick-setup.md. Then ask me at most five questions before you suggest anything.

Interview

Run the interview in 03-deeper-interview.md with me. Ask one question at a time and wait for my answer each time. At the end, summarise everything in templates/profile.md.

Break the workflow down

Describe the workflow in templates/workflow.md as numbered steps. Mark which steps follow a fixed rule and which need my judgement.

The smallest solution

Suggest the simplest solution that works for the first step. If it works without AI, say so. Give a short reason and list what you need for it.

The pack

The pack by email.

We email a link to your address. One click confirms it and downloads the pack. Free, no subscription and no sales call you did not ask for.

The form needs JavaScript. Write to info@jules.solutions instead and we will send you the pack.

When to get help

Doing it yourself has limits. Here they are.

We do not make the guide hard on purpose so that you call us. But at these points a second person is worth it:

Client data, personal data or credentials are involved, and you are unsure who may see what.
An IT company looks after your computer. Then ask them first, before you install anything.
The workflow should connect other systems: the accounting, a CRM or the team’s shared mailbox.
Several people should work with the same setup.
On the second evening you are still chasing installation errors instead of saving work.

Then we take over. The Basic Installation is a fixed CHF 490.–; the Pro Setup for CHF 1'490.– also connects your first existing systems.

Compare the packages Write to us

Not sure where you stand? The questions on the home page show you, free. To the questions

FAQ

Questions about doing it yourself

Do I need to know how AI works?

No. The interview asks about your work, not about AI. Every answer is saved the moment you give it, so you can stop any time and continue later, on another device too. You can also answer the first questions in conversation with our AI assistant.

Will AI providers use our inputs to train their models?

That depends on the provider and your account. Under the terms available in October 2026, OpenAI, Anthropic and Google say they do not use inputs through paid API access for training by default. Anthropic says the same for business accounts such as Claude for Work. Free and personal accounts may have different terms. Check the terms for the account you will use.

If the chosen provider offers terms that exclude training on your inputs, we set up your access on those terms and show you the relevant clause before work begins.

If the model runs on your own hardware, your inputs are not sent to a model provider.

Must we use Claude Code or a particular provider?

No. The choice of AI harness, model and provider remains yours. Claude Code is an option, not a requirement. Your working files are in the installed vault on your machine. If you use a cloud model, we discuss what content goes to its provider.

Our IT partner manages our devices. How do you involve them?

Installation on your device requires admin rights. Depending on the package, we install the chosen AI harness and other tools. We discuss with you which tools your IT team needs to approve.

The interview asks who looks after your IT and who else needs to be involved, such as an IT partner. If your IT partner handles installations, we send them the list of required tools and agree the approach with them.

How do the packages differ?

Basic Installation gives you an installed AI harness, a vault template for working files on your machine, one or two basic workflows and a handover document.

With the recommended Pro Setup, we install additional software on your device and set up the vault and platform. We build multi-step workflows, initial connections to your systems and three to five commands to run them. We show you how to use the setup, provide 30 days of follow-up support and include three months of platform access through a Business seat for one person.

Operator System is for businesses with their own team, existing systems or more complex integrations. In a free call with Jules, you can discuss which package fits your work. For everything each package includes, see ‘What the setup price covers’.

Read all the answers

Start with the interview

Find the work your team keeps doing by hand.

The free interview asks about your work, one question at a time. Your report shows where your time goes and where it pays to start.

No technical knowledge needed, no account. You can stop any time and continue later.

Start the interview Contact us

From an everyday computer to a workspace for AI.

What ends up on your computer.

The vault: your working folder

The AI harness: where the AI works

Project repositories: each project on its own

Where things run

The tools underneath, and what each is for

Three rules that apply from the start

Ten stages, in this order.

On both systems

Windows

macOS

How to check

If it sticks

The makers’ pages

Windows

macOS

How to check

If it sticks

The makers’ pages

Windows

macOS

Then, on both systems

How to check

If it sticks

The makers’ pages

On both systems

Windows

macOS

How to check

If it sticks

The makers’ pages

Windows

macOS

How to check

If it sticks

The makers’ pages

Windows

macOS

How to check

If it sticks

The makers’ pages

On both systems

Windows

macOS

Then, on both systems

How to check

If it sticks

The makers’ pages

On both systems

Windows

macOS

How to check

If it sticks

The makers’ pages

On both systems

Windows

macOS

How to check

If it sticks

The makers’ pages

On both systems

How to check

If it sticks

The makers’ pages

Where the Setup takes over.

The computer first, then the installation

Installation by package

Vault, platform and workflows

Remote access only with your consent

A handover that lasts

Fill-in templates, not a course.

Four sentences that take work off your plate.

Understand first

Interview

Break the workflow down

The smallest solution

The pack by email.

Doing it yourself has limits. Here they are.

Questions about doing it yourself