engagement-models - AGH Teams

A decision framework, not a pricing table

One operating model does not fit every business.

Some businesses need infrastructure before people. Others need one ongoing role, several complementary roles, a defined project, or a technology layer that improves structure and management visibility.

AGH Engagement Models explain how those requirements can be structured commercially and operationally. They are not fixed-price packages and they do not replace the seven AGH Services.

Five ways to work with AGH

Choose the structure that matches the requirement — not a pre-built package.

The five models answer one practical question: does the business need infrastructure, one role, several roles, a defined project, technology, or a combination?

Setup & Systems

Build or clarify the operating structure before ongoing support begins.
Best fit when workflow, SOPs, systems, reporting or role structure needs attention first.
Dedicated Managed Support

One primary defined role operating inside an agreed scope and client environment.
Best fit when one ongoing business function needs structured support.
Managed Team

Several complementary roles working within one coordinated support structure.
Best fit when connected functions need shared workflow and management visibility.
Project-Based Support

Defined work with agreed deliverables, responsibilities and a completion point.
Best fit when the requirement is a specific project or implementation.
Technology

Relevant AGH technology or dashboard systems used where they support the operating requirement.
Best fit when technology should improve structure, execution, reporting or visibility.

The five engagement models

Different structures for different operational requirements.

Each model has a defined commercial purpose. The detail is configured around the agreed scope rather than a universal package.

Setup & Systems

Build the structure before running the operation.

For businesses that need clearer operational infrastructure before adding ongoing support.

Depending on scope, AGH can help establish or clarify the working structure behind a business function without implying that a dedicated team member is automatically included.

Workflow
SOP
Dashboard
Templates
Systems
Role Definition

Clarify the process

Define responsibilities, statuses, follow-up, reporting and escalation around the actual workflow.

Prepare the environment

Structure relevant documents, templates, dashboards or system configuration where they form part of the approved scope.

Dedicated Managed Support

One defined role around a clear operating scope.

For an ongoing primary function that benefits from one clearly structured AGH-supported role.

The engagement defines responsibilities, working hours where relevant, client systems, workflow, communication, reporting, escalation and KPIs where applicable. The role is not an undefined extra resource.

Remote Coordinator

Coordination, follow-ups, schedules, communication, tasks and reporting within the agreed process.

Recruitment Support

Recruitment operations and relevant recruitment infrastructure within the approved scope.

Sales Assistant

Lead follow-up, CRM activity, appointments, sales administration and reporting.

Project Coordinator

Project coordination, tasks, meetings, documentation, follow-up and reporting.

Data Support

Agreed data operations, reporting and operational information management.

Management visibility

Use client systems, reporting, tasks, dashboards, relevant KPIs or AGH technology where configured.

Managed Team

Several roles. One coordinated support structure.

For businesses that need complementary functions connected through clear role boundaries, workflow and management visibility.

A Managed Team can connect several AGH-supported roles around shared systems and operating requirements without turning them into unrelated remote workers.

Illustrative team configuration

Remote CoordinatorSales AssistantData Support

Define ownership

Clarify who owns each activity, how information moves and where responsibilities intersect.

Coordinate visibility

Use agreed client systems, reporting and escalation so management can review connected activity.

Project-Based Support

Defined work with a defined project scope.

For a specific outcome that can be structured around agreed responsibilities, deliverables, review and completion.

Project-Based Support does not automatically require an ongoing dedicated role. Once the agreed deliverables are complete, the project can conclude or move into separately scoped ongoing support where relevant.

Website
Dashboard
Recruitment System Setup
CRM Setup
Workflow Setup

Defined deliverables

Agree what the project is expected to produce before delivery begins.

Defined completion point

Keep the project distinct from ongoing managed support unless a separate requirement is later agreed.

Technology

Technology where the operation needs it.

For requirements where technology improves structure, execution, reporting or management visibility.

Technology may be the main defined requirement or a supporting layer within another engagement. AGH remains Human-led. Technology-enabled.

AGH Workforce Management Platform

Configurable workforce-management visibility where the agreed engagement requires it.

AGH CRM

May support relevant Sales engagements where appropriate; existing client CRM systems can remain in use.

Dashboard Systems

Operational, sales, recruitment, project, HR or performance visibility based on available data and agreed metrics.

Existing technology stays valid

AGH technology is not automatically required and does not force unnecessary system replacement.

One model — or a combination

Combine the components that make operational sense.

Some businesses begin with one model and later add another. Others combine relevant components from the beginning. These are conceptual scope-led structures, not fixed pathways or bundles.

Connected AGH engagement-model components illustrating setup, people, managed activity, technology and reporting around one operating structure.

Setup & SystemsDedicated Managed Support

Build the workflow, reporting structure and role definition first; then operate the defined role inside that structure where required.

Dedicated Managed SupportManaged Team

Begin with one primary role and review complementary roles only when the operational requirement expands.

Project-Based SupportOngoing Managed Support

Complete the defined project first. Ongoing support can be scoped separately if the business later needs it.

TechnologyManaged Support

Add relevant technology where it supports the agreed operating structure or management visibility.

People + Process + Technology

The engagement model determines the right combination — not the other way around.

Not every engagement requires the same mix. The operating requirement determines whether people, process, technology, or a combination should form part of the agreed scope.

P

People

Relevant AGH-managed professionals where people form part of the engagement.

P

Process

Responsibilities, workflow, SOPs, reporting, communication, escalation and KPIs where relevant.

T

Technology

Client systems first, with AGH technology added where it supports the agreed requirement.

Work with your existing systems

Keep the systems that already work.

Choosing an AGH Engagement Model does not automatically require replacing the tools or processes already embedded in your operation. Where appropriate, AGH can work inside the client's existing environment.

CRM
Project Systems
Home Care Software
Task Systems
Spreadsheets
Reporting Systems
Communication Tools
Internal Software
SOPs & Workflows

Use what already works. Add what the operation needs.

AGH technology can be introduced where relevant, but it is not automatically mandatory.

How we identify the right model

The model follows the requirement.

AGH first needs enough operational context to understand what the business is trying to build, operate, manage or improve. The engagement structure follows that requirement.

Requirement

Nature of requirement + scope

What needs support, what is included and what remains outside the agreed scope.

Capacity

Workload + working hours

The recurring or project workload and relevant coverage requirements.

People

Roles + existing team

Whether the requirement needs no new role, one role, several roles or support around an internal team.

Environment

Systems + infrastructure

What technology, workflows, SOPs, dashboards or operating structures already exist.

Outputs

Deliverables + reporting

What the engagement must produce and what management needs to review.

Context

Management + technology + complexity

The management structure, technology requirement and wider operational complexity.

Custom proposal

No fixed package. A proposal based on the actual scope.

Custom proposal based on your operational requirements. Different engagements can require materially different combinations of people, time, systems, reporting and management support.

No public hourly, monthly, per-seat or package pricing is published on this page.

See How AGH Works

ScopeThe amount and type of work required.

Working HoursCoverage requirements where ongoing managed support is involved.

Team SizeOne role and a coordinated multi-role team have different operating requirements.

ExperienceRelevant professional experience required for the agreed role or project.

EquipmentManaged work setup where equipment forms part of the engagement.

SoftwareRelevant technology requirements without assuming third-party licence costs are included.

Management LevelThe level of coordination, oversight, setup or ongoing service management required.

Reporting RequirementsThe level, frequency and complexity of agreed management reporting.

01Consultation

02Understand requirement

03Define scope

04Identify model

05Prepare proposal

Client control

Flexible support. Clear responsibility.

The engagement model can change the shape of the support. It does not transfer strategic control of the client's business to AGH.

The client retains

Business direction and final management authority.

Business direction and operational priorities
Final approvals and relevant commercial decisions
Relevant system-access decisions
Role requirements and relevant KPI approval
Final management decisions

AGH supports

The agreed operating structure.

Depending on the model and scope, AGH may support setup, people, projects, systems, technology, reporting and relevant service management within the agreed boundaries.

Flexibility does not mean undefined support.

Responsibility, approval and escalation boundaries should be clear before normal operation begins.

Start with what you need now

You do not need to build the final model on day one.

Begin with the requirement the business has today. If the operation changes later, the scope can be reviewed rather than assuming automatic expansion.

01Setup

02One role

03Several roles

04One project

05Technology

Frequently asked questions

Questions about structuring an AGH engagement.

Practical answers about scope, people, projects, technology and proposal structure.

Does AGH offer fixed packages?

Can we start with Setup & Systems before adding a team member?

Can we work with one dedicated AGH team member?

What is the difference between Dedicated Managed Support and a Managed Team?

Can AGH support a one-off project?

Do we have to use AGH technology?

Can different Engagement Models be combined?

Can the engagement change later?

What determines our proposal?

Define the requirement first

Build the right engagement around what the operation actually needs.

The Consultation is designed to understand the business requirement, current workload, existing team, current systems and required support before the appropriate engagement structure and custom proposal are defined.

Book a Consultation

The right support model starts with what your business actually needs.

One operating model does not fit every business.

Choose the structure that matches the requirement — not a pre-built package.

Setup & Systems

Dedicated Managed Support

Managed Team

Project-Based Support

Technology

Different structures for different operational requirements.

Build the structure before running the operation.

One defined role around a clear operating scope.

Several roles. One coordinated support structure.

Defined work with a defined project scope.

Technology where the operation needs it.

Combine the components that make operational sense.

The engagement model determines the right combination — not the other way around.

People

Process

Technology

Keep the systems that already work.

The model follows the requirement.

Nature of requirement + scope

Workload + working hours

Roles + existing team

Systems + infrastructure

Deliverables + reporting

Management + technology + complexity

No fixed package. A proposal based on the actual scope.

Flexible support. Clear responsibility.

Business direction and final management authority.

The agreed operating structure.

You do not need to build the final model on day one.

Questions about structuring an AGH engagement.

Build the right engagement around what the operation actually needs.