Both. The architecture supports individual enrolments and sessions alongside cohorts, group sessions and attendance.
Operations setup
Your clients know their next step. So do you.
A connected delivery workspace for coaches and consultants, bringing onboarding, sessions, participant actions and follow-ups into one clear operational view.
The coordination problem
The session is only one part of the work.
A participant books, but their intake still needs checking. Preparation requests sit apart from the calendar. Agreed actions disappear into session notes, and rescheduling creates another trail of reminders to inspect.
Each task is small. Together, they create a delivery process that needs constant attention—especially when individual participants, cohorts and changing schedules all need to stay aligned.
The Client Delivery Hub gives that work a shared structure, so the next action is visible without reconstructing the participant journey from separate tools.
The delivery flow
From confirmed engagement to programme completion.
The system follows the delivery journey while keeping approvals, exceptions and professional judgement with the people responsible.
Activate the engagement
Connect the programme, organisation and participants, giving the work a clear operational starting point.
Coordinate onboarding
Track intake requirements and prompt only the participants whose information is incomplete.
Keep sessions connected
Link individual bookings and cohort sessions to the correct programme, participant and delivery context.
Prepare for delivery
Coordinate preparation requests and show the facilitator what is ready and what still needs attention.
Record outcomes and actions
Capture attendance, outcomes and agreed actions with a clear owner, status and due date.
Coordinate follow-through
Prepare session follow-ups and action check-ins, holding messages for review where approval is required.
Surface exceptions
Make booking gaps, outstanding actions, pauses, withdrawals and approaching completions visible.
Close and review
Coordinate completion and feedback, then provide a practical view of upcoming work and unresolved items.
One participant, start to finish
A connected journey, not another disconnected list.
A participant can move from enrolment to completion with their intake, bookings, session context and agreed actions attached to the same delivery record.
- Before the session
- Onboarding, intake and preparation stay visible together.
- During delivery
- Attendance, outcomes and agreed actions gain clear context.
- After the session
- Approved follow-ups and action check-ins move forward.
- At programme level
- Progress, exceptions and completion remain easy to review.
This is an illustrative demonstration using sample records. It shows the intended system behaviour rather than claiming a client result.
Inside the build
The workspace and the coordination behind it.
A tailored implementation uses the parts your delivery model actually needs rather than copying the demonstration wholesale.
- Linked records for organisations, contacts, programmes, engagements, enrolments, cohorts and sessions.
- Supporting records for attendance, actions, resources, follow-ups, operational tasks and feedback.
- Operational views for upcoming sessions, incomplete preparation and outstanding work.
- Workflows for onboarding, session coordination, follow-through, completion and reporting.
- Approval points for communications that require a person to review them.
- Dispatch, monitoring and reconciliation workflows for routine operations.
- Testing across missing information, reschedules, pauses and withdrawals before live messages are enabled.
Architecture
A clear role for each part of the system.
The demonstration uses this stack. A client implementation starts with the tools already in place and the delivery process they need to support.
- Notion
- The delivery workspace where programme, participant, session and action information is organised.
- n8n
- The workflow layer coordinating events, checks, updates, reminders and approved follow-ups.
- Supabase / PostgreSQL
- The operational layer for workflow state, planned operations and activity tracking.
- Connected tools
- Calendly, Google Calendar, Tally, Gmail and Google Drive support booking, intake, communication and resources.
Human responsibility
Keep the relationship personal.
The Hub supports the work around delivery. Coaches and consultants still own the conversations, interpret participant needs, agree actions and decide when a situation requires a different response.
Messages that need judgement wait for approval. Participants who pause, withdraw or need personal attention are surfaced for review instead of being pushed through a rigid sequence.
Questions, answered plainly.
No. The demonstration uses Notion as the delivery workspace, but an implementation begins by reviewing what your existing systems already handle well.
Yes. Follow-ups that require judgement can be prepared and held until the responsible person approves them.
Their status informs which delivery actions should continue, stop or return to a person for review.
No. The core build relies on connected records and workflow rules. AI is not required to coordinate onboarding, sessions, actions and reminders.