OS-06 · Core · v1.0

systems &
tools.

OS-06 · the lean stack

every tool we use has earned its place.

how the stack fits together

four tools.
one ecosystem.

Zeal runs on a deliberately lean stack. Most of these tools connect to each other. That’s the point.

The Portal is our staff-facing front door, and where the OS and the playbooks live. Projects live in the portal: the projects dashboard, and each project’s plan and finance tabs. Microsoft 365 handles communication and scheduling, and Teams is where we talk, project conversations included. CurrentRMS is the commercial truth: opportunities, equipment, crew. Dropbox is where files live. Each one has a job. Each one stays in its lane.

Departments have their own specialist systems beneath this layer. Those live in the relevant playbook. AI (primarily Claude) extends what a small team can do across the whole picture.

first principle · 01

earned its place.

Every tool integrates with the others, and has someone at Zeal who owns its standards. “Can an existing tool do this?” before “what new tool do we need?”

first principle · 02

stays in its lane.

Files in Dropbox. Projects in the portal. Commercial truth in CurrentRMS. Comms in Teams. If it’s not in the right system, it isn’t being managed.

the diagram · November 2026

the stack,
top to bottom.

Read top-down. The Portal sits at the surface; the AI layer wraps everything; specialist tools sit beneath. Lines aren’t rigid: most of these systems talk to each other where it earns its place.

surfacewhere staff land first coreeveryone touches it extensionAI across the stack specialistper department, see playbook
the core four

tools that
earn their place.

The cross-cutting layer everyone at Zeal touches. Each one has a Head who owns its standards, and a clear job that doesn’t overlap with the others.

01
tool · 01 · staff hub

zeal portal.

Where Zeal lives internally.

portal.wearezeal.co

What it’s for: the staff-facing home. Where this OS is published, where company-wide tools live (Studio Bookings, Label Maker, dashboards, and a growing list), and where information from every other system gets surfaced in one place. Projects live in the portal: the projects dashboard, and each project’s plan and finance tabs, beside CurrentRMS opportunities and Dropbox project folders.

How it stays current: Steve owns the architecture, with Claude Code building features against agreed plans and Claude Design owning the visual treatment. The OS and the playbooks live in the portal, and the portal is their source of truth. To suggest a change, press the thought bubble at the top of any page.

What’s on your plate is self-managed for now. Tasks are starting to appear in the portal, and Zeal PA comes to everyone towards the end of the year.

Owner
Steveportal architecture · publishing
Detail
how the portal fits together →/os/systems/portal/
02
tool · 02 · productivity

microsoft 365.

Email, calendar, Teams. The glue.

Business Premium

What it’s for: Outlook handles email, Teams handles general company communication, the calendar is where meetings and availability live, OneDrive sits in the background for some Microsoft-native file work. The portal can read calendar and email data where useful (for instance, surfacing your day on the portal home), but Dropbox is where most files actually live.

Where we talk: Teams is where we talk, project conversations included.

Owner
OperationsIT & infrastructure
Detail
PB-04 · Operations →
03
tool · 03 · commercial

currentRMS.

The commercial truth. Always.

zeal.current-rms.com

What it’s for: the commercial reality of every project (the opportunity, the kit list, the crew bookings). When the portal shows commercial information, CurrentRMS is the source it’s pulling from.

Why it matters: CurrentRMS is the system that turns “we’re doing this project” into “here’s what it costs, here’s what we need, here’s who’s on it.”

Owner
Projects · Operationscommercial · equipment usage
Detail
PB-01 · PB-04 →/os/systems/currentrms/ coming
04
tool · 04 · files

dropbox.

Files. Source of truth.

Dropbox Business Advanced

What it’s for: where Zeal’s files live (projects, OS, brand assets, finance documents). Projects follow a Client > Year > Project structure with a standard template (_ClientFolder and _CrewFolder for portal-linked client and crew folders, plus numbered subfolders 01–06).

The four root folders: Projects · Team · Finance · People. If you’re looking for a file, this is where it is. The portal links into Dropbox folders where useful, but Dropbox itself is the file system.

Owner
Operationsfolder structure · access control
Detail
PB-04 · Operations →
how we work with AI

a tool. like any other.

AI is a thinking partner, not a replacement for craft, judgement, or voice. The final shape, the final decision, and the final voice are still ours.

principle 01 · craft

shaped by a person.

Anything that goes out under our name has been shaped by a person, not generated by a machine. Authentic human voice is non-negotiable, especially client-facing.

principle 02 · use

where it earns its place.

Synthesis, structure, drafting, research, automation of repetitive work. We use AI tools because they make us better, not because they’re trendy.

principle 03 · growth

make yourself redundant.

You’ll have a job for life. Let AI take the parts of your work that drain you, and free yourself for the bit you actually love. Resisting AI to protect your job is the surest way to make your job harder, not safer.

Claude · the surfaces we use

surface 01

chat.

Iterative thinking, drafting, exploring ideas. The everyday surface.

surface 02

projects.

Ongoing work that benefits from persistent context, like Zeal HQ, where this OS is being shaped.

surface 03

cowork.

Agentic, outcome-oriented tasks. Including scheduled, recurring work that runs on its own.

surface 04

code.

Repo-based development on the portal and other code projects. Steve owns plans; Claude builds.

the line that matters: AI extends what a small team can do. It doesn’t replace what makes us, us.

A fuller treatment lives at /os/systems/ai/: prompting, when to use which surface, principles for AI-assisted work, and worked examples. Sub-page coming.

specialist tooling

beyond the
core four.

Each department has its own specialist tools beneath the cross-cutting layer. If you’re looking for guidance on a tool that isn’t on this page, the relevant playbook is the place to start.

PB-07

finance.

  • Xero
  • The portal
  • Dext (until December, then our own agent)
  • Capital on Tap
PB-07 · finance →
PB-04

operations.

  • Warehouse tools
  • Equipment maintenance
  • IT infrastructure
PB-04 · operations →
PB-06

marketing.

  • Publishing platforms
  • Analytics
  • Content tools
PB-06 · marketing →
PB-03

technical.

  • Design & drafting
  • Technical paperwork
PB-03 · technical →
PB-02

creative.

  • Design tools
  • Visualisation tools
PB-02 · creative →
the principle worth holding
a lean stack. by design. not by accident.

Every tool we use has earned its place, integrates with the others, and has someone at Zeal who owns its standards. When a new need surfaces, the first question is “can an existing tool do this?” before “what new tool do we need?” That’s the discipline. It compounds.