See when enrolment opens

Step back from delivery

For agency founders who still run delivery themselves. 8 live sessions on Claude Code put clients, calls and tasks in one place, and nothing sends without your OK.

See when enrolment opens
See the 8 sessions

From working in your agency to running it

  • Your team runs delivery from one folder, so you can step back and the agency keeps moving.

  • A fact lives in one place. A client looks the same everywhere, and the glue between 5 tools goes away.

  • You see a client's status, hours against budget and what's next, at a glance.

  • Calls, emails and messages get sorted into information, action or decision, and the client record updates itself.

  • You edit your own system with Claude Code, inside guardrails that keep it consistent.

The bootcamp, session by session

Tuesdays and Thursdays at 18:00 CET, from Tue, Nov 10. 3 hours live and about 2 hours rebuilding, each week.

  1. Before week 1

    Start here

    Optional and free to watch. Skip it if Claude Code is already open on your machine.

    • Install Claude Code and open it in a folder
    • Make a git repo and commit once
    • Ask Claude a question about a file and have it show its source

  2. Tue, Nov 10

    Facts live in one place

    The same client looks different in Airtable, Notion, Drive and a Google Sheet.

    Session 1 finds what your agency repeats, from your calendar, your board and your last 5 calls. Then it builds one folder where a fact lives once, with an index at every level. One Claude Code project reads it, so you stop running one project per client.

    12 repeated tasks listed, and the top 3 are delivery work.

    Adds to your repo: wiki/repeated-work.md

    wiki/repeated-work.md Example

  3. Thu, Nov 12

    Calls update the client record

    What you learn on a call never reaches the record, the tasks or the process.

    You process one call by hand with Claude watching, then turn it into a skill. Points from the call land as information for the track record, an action that becomes a task, or a decision about scope.

    It runs on 2 different calls and the records have the same shape.

    Adds to your repo: skills/process-call/SKILL.md

  4. Tue, Nov 17

    See where every client stands

    You can't tell which clients are urgent, or what each one costs you.

    A client folder opens the day the deal is won. It holds the open tasks, the urgent items, the hours against budget and what's next, and it updates after each call.

    You ask what you promised in June and what shipped, and get an answer with sources.

    Adds to your repo: clients/<slug>/ledger.md

    clients/<slug>/ledger.md Example

  5. Thu, Nov 19

    Q&A: get your own folder unstuck

  6. Tue, Nov 24

    Check your inbox only where the AI has a doubt

    You don't trust the AI to send anything, so you check everything.

    Skills end in a proposal that spells out what will change. You approve, modify or reject. A hook blocks anything going out under your name before you do, so a doubt reaches you and nothing else does.

    You tell it to email a client and watch it get stopped.

    Adds to your repo: hooks/block-send.sh

    hooks/block-send.sh Example

  7. Thu, Nov 26

    Drop the Make and Zapier bill

    You pay for automations that only move data between tools that don't agree.

    Once the facts live in one folder, a schedule can do the work those zaps did. Before anything runs unattended, you answer one question: how will you know it worked? We run one at the wrong tier on purpose, let it fail, then fix it.

    One recurring job runs on its own, and its file says why you can trust it.

    Adds to your repo: schedules/weekly-update.yaml

    schedules/weekly-update.yaml Example

  8. Tue, Dec 1

    Deliver more with the same team

    You can't hire or take on more, because you can't see where capacity runs out.

    Hand the agent an overloaded board and get back a week that fits. It works in one-week batches, with points per task and a cap per person. Anything that doesn't fit is listed with the reason. Then you can tell what to stop before you hire.

    The cap holds for each person, and a reason sits beside each bumped task.

    Adds to your repo: rules/capacity.yaml

    rules/capacity.yaml Example

  9. Thu, Dec 3

    Q&A: edit your own system with Claude Code, inside guardrails

One call updates the client record

After a call

  1. Call ends, transcript lands in clients/<slug>/raw/

  2. Skill reads the client's record, then the transcript

  3. The skill sorts every point: information, action or decision

  4. Unsure which, or no date given?

    Yes
    It asks you. It doesn't guess.
    No
    The record and the tasks update

  5. A follow-up draft is written into decisions/

  6. You read it and decide

  7. The send hook holds it until you do.

skills/process-call/SKILL.md 
---
name: process-call
description: Sort a client call into information, actions and decisions, and update the client record. Use when a new transcript lands in clients/<slug>/raw/.
---

# Process a client call

1. Read clients/<slug>/dossier.md first, so you know the history.
2. Read the transcript in clients/<slug>/raw/.
3. Sort each point into one of 3 kinds:
   - Information: add it to the track record in the dossier.
   - Action: write a task with an owner and a date. If the call gave no date, ask. Don't guess.
   - Decision: a change of scope or price. Put it in decisions/ and flag it for the founder.
4. Update clients/<slug>/ledger.md with the new tasks.
5. Write a follow-up email into decisions/. Use company/voice.md.

## Rules
- Never send anything. Step 5 ends in a file. It never ends in an email.
- Never invent a date or a number the call didn't contain.
- Cite the transcript line behind each item.

Free videos show the result. The bootcamp builds it on your agency.

The weekly rhythm

  1. Watch

    Join the live session and see the system built from an empty file.

  2. Understand

    Ask why, while it's on screen. The answer shapes the next step.

  3. Redo

    Rebuild it on your own clients before the next session.

Tools the sessions use: Claude Code, ClickUp, Gmail, Google Calendar.

What's included

Live sessions
8 sessions, with your questions answered in the room.
Chaptered replay
Cut into chapters, so you can jump to the step you need.
The blueprint
The folder map and the order to build it in.
The template repo
All the skills, rules and hooks from the sessions, ready to copy.
The community
A room for the cohort, so a stuck step doesn't wait for Thursday.

Your host

Ramzi Tabka, UpSys founder

Ramzi Tabka

Founder, UpSys

Ramzi runs UpSys, an agency that builds delivery systems for other agencies. The folder in this bootcamp is the one UpSys runs on, so he teaches what he uses on Monday morning.

Since 2021: 30+ ClickUp workspaces configured, 1,500+ people trained.

What clients say about working with UpSys

Melanie Das CEO, BrainWaves Consulting

The team went above and beyond, from automations to SOPs and walk-through videos. It really felt like white-glove service, and I've already saved hours getting new hires up to speed.

Mark Robinson CEO, Brandtegic (Video Agency)

UpSys helped us improve our system and actually make the transition to ClickUp, which we had been trying to do for a long time. They delivered what we were looking for, were flexible and supportive, and fixed a lot of problems and complexities from previous...

Fabien CLEMENT Managing Director, Ecobird

We were looking for a powerful tool to plan our teams and monitor our activity that was user-friendly, dynamic, and easy to use. Our objective and the challenge we faced was to get our staff to adopt a new business management method in which they would become active...

Guillaume Raullin UX Designer, Rossignol

I got in touch with Ramzi for some automation stuff, and his coaching really opened my eyes, especially about ClickUp's limits. He came up with a Make solution, and honestly, we're super happy: everything's running smoothly.

Pascal Bénard Smart Global

I took time to step back before writing this to fully assess both the solution and how it was implemented. Today, I can say I'm very satisfied. The solution clearly meets our needs. It removed several bottlenecks for our teams. ClickUp is now part of our daily routines.

Valentin Video Editor, Socialsky

UpSys helped us transition from our previous project management tool, which wasn't fulfilling our video editing tracking needs, to ClickUp. The changeover was smooth and efficient, and the team quickly adapted to the new tool.

Enrolment opens soon

Prices and payment links go live the day enrolment opens. Book a call if you want to ask something first.

Book a call

Questions

Who is this not for?
You want someone to do it for you: that's the OS Install, a different offer. You're hoping for a prompt pack: this teaches a folder, not prompts. You won't open your terminal, where Claude Code lives. Or you have no clients yet: win some first, then build the system.
I'm not technical. Can I follow?
If you can open a folder and read a file, yes. There's no code to write. The work is plain-English instructions and reading what comes back. The optional start-here videos get you to the first session.
Do I need a team?
The pains come from a 3-person agency, and the sessions fit that size and up. A solo operator can follow along, but the approval inbox and the capacity week assume several people.
I don't use ClickUp. Does that matter?
No. The method is software-agnostic. Your clients, calls and rules live in the folder, and ClickUp, Airtable, Notion or a sheet only feeds tasks in.
Does my client data go to Anthropic?
Claude Code reads the files you point it at, and what it reads is processed under your own plan's terms. Check your plan's data settings. In week 1 you write a rule listing the folders it never opens.
Where do my files live?
In a repo on your own machine. UpSys never sees your folder.
What if I miss a session?
The replay is chaptered and goes online after each session. You can rebuild from it before the next one.
What if my build breaks between sessions?
Ask in the community. Anything it can't settle goes into the next Q&A session.
Ask Claude, ChatGPT or Gemini if this is for you

Step back from delivery

You finish on Dec 3 with every client, call and task in one folder.

See when enrolment opens

Privacy Cookies