Ryz Labs/Guides/Group assistant program
Guides

An assistant program for your whole group: seats by function, not by site

One assistant per leader works until you have ten sites or ten partners. Here's how groups design an assistant program that scales across every location.

A single executive assistant changes one leader's week. A group with many locations, portfolio companies or partners needs something different: a program, with seats designed by function, one playbook, and a way to plug in each new site or acquisition. This guide is for operators, COOs and managing partners of multi-location businesses who are past the one-assistant stage. We're Ryz Labs. We place dedicated executive and virtual assistants, and multi-seat programs are a large part of what we do, so we're an interested party. The design principles hold whoever provides the seats.

Why per-person assistants stop scaling

The design principle: seats by function

Instead of one assistant per site, give each seat one function across every site. Functions that work well as group seats:

Function seatCovers across the groupMeasured by
Leadership EACEO or COO calendar, board and investor prep, group-wide meetingsLeader hours returned, meeting prep on time
Scheduling and intakeAppointments, call-backs, new-customer intake for all sitesResponse time, booked appointments
Receivables follow-upInvoice reminders and collections cadence for every locationDays sales outstanding, aged balance
Vendors and renewalsSupplier follow-up, licences, insurance and certificate trackingLapsed renewals (target zero)
Recruiting coordinationJob posts, interview scheduling, offer paperwork logisticsTime from post to start date
ReportingWeekly site scorecards compiled from each location's systemsScorecard out on time, every week

Not every group needs every seat. Most start with two or three and add as volume shows where the next one is needed. A useful rule: when one function seat is consistently behind on its response-time standard for a month, split it by region or by site cluster rather than handing the overflow back to site managers. Splitting keeps the playbook intact; handing work back undoes the program.

How it looks by industry

The functions stay the same; the work inside them changes. We've written detailed guides for the groups we see most:

One playbook for every seat

A program works because every seat runs from the same written playbook. Each function gets a short document covering:

  1. The processes it owns, with triggers and steps.
  2. The tools and the access level for each.
  3. Response-time standards and escalation rules.
  4. Who approves what, especially anything involving money or customers.
  5. The weekly report the seat sends, and to whom.

With the playbook in place, a new seat can be trained in days, and coverage during time off is a matter of handing the playbook to a colleague.

Rolling it out

  1. Pilot one function at two or three sites. Pick the function with the most visible pain, often scheduling or receivables.
  2. Write the playbook from the pilot. The first month surfaces every exception the playbook needs to cover.
  3. Extend that function to every site. Same seat, more volume, until the numbers say a second seat is needed.
  4. Add the next function. Repeat the pilot, playbook and extend sequence.
  5. Plug in new sites from day one. Acquisitions or openings join the existing seats rather than building their own admin.

Who runs the program

Seats should report to one operations lead, not to each site manager. Site managers request work through a shared queue or channel; the operations lead sets priorities when requests compete. That keeps standards consistent and stops any one location from absorbing a shared seat.

Measuring the program

Report monthly on three levels: per seat (its function metric from the table above), per site (hours of admin removed from the site manager), and for the group (cost per seat against the in-house alternative). For the in-house benchmark, the May 2025 BLS median for executive administrative assistants was $76,590 a year before benefits; our cost guide works through the full comparison.

Setting up a group program with Ryz Labs

Ryz builds assistant programs for groups seat by seat: dedicated executive assistants start at $3,000 a month and dedicated virtual assistants at $2,000 a month, each month to month, so you can add seats as sites open and scale down if a function shrinks. Assistants can cover any US time zone, which lets a group spread across regions keep each queue staffed during local business hours. Every assistant writes and speaks fluent English and works on your team, reporting to your operations lead.

We start with a named shortlist, a plan and a price for the pilot seats. Access to each system is vaulted and revocable, so you control it seat by seat. Groups that also need projects delivered across sites can add a dedicated project manager, and an operations coordinator can own the recurring admin. Ready to plan a pilot? Contact us.

FAQ

How many seats does a group assistant program start with?

Usually two or three: a leadership EA and one or two function seats such as scheduling or receivables. Seats are added as the numbers show where volume is.

Should each location have its own assistant?

Generally no. Seats organised by function across all sites are easier to measure, cover each other during time off and absorb new locations without rework.

Who should the assistants report to?

One operations lead. Site managers send requests through a shared queue, and the operations lead resolves competing priorities.

How do new acquisitions join the program?

They plug into the existing seats and playbooks from their first week, instead of keeping their own admin setup.

Can one seat cover sites in different time zones?

Yes, if the work is mostly asynchronous. For live phone queues, staff each region during its own business hours.

Sources

Checked November 15, 2026. General guidance for multi-location operators.

Questions we didn't answer? Email info@ryzlabs.com.

Thanks — your message has been sent. We’ll get back to you soon.

Something went wrong while sending your message. Please try again or email info@ryzlabs.com.

Explore Ryz Labs

Software development servicesAI development teamsIndustriesStaff augmentationAI pod teamsNearshore software developmentHire engineers by roleEngineer ratesGuidesBuyer guidesCase studiesHow we vet engineers

Ryz Labs

Senior engineers on your team. AI pod teams that ship.

Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.

  • Only the top 1% of tens of thousands interviewed make it
  • On US business hours, including New York hours
  • Trusted by Fortune 500 engineering teams

Tell us who you need

A Ryz partner replies with a scoped team plan.

Start a conversation →

Prefer to talk? Book a 15-min call →