Operations & Delivery Manager (Client Systems)

About Us
Bolder Digital is an Australian-based recruitment agency committed to connecting top Filipino talent with leading businesses globally. We are looking for an individual to join our team and work remotely from the Philippines as we are based in Australia (Remote, based in the Philippines, working on Australian Eastern Time Zone 8/9 AM – 5 PM).

Job Type
Full-Time – Long term/Gig

Start Date:
ASAP

Compensation:
Negotiable — based on proven expertise

1. Purpose of the Role
The Operations & Delivery Manager is responsible for turning The Event Engineer methodology into working systems inside client accounts, and for keeping those systems running through every event cycle.

This role owns the build, the delivery and the client relationship at an operational level. It is the bridge between what is sold on a strategy call and what actually exists inside GoHighLevel on event day. When a client's funnel, automation, portal or event works, this role built it. When it breaks, this role fixes it.

The role is accountable for client outcomes at the delivery layer: events that launch on time, funnels that convert, automations that fire correctly, and clients who feel supported without the Founder having to intervene.


2. Scope
Client portfolio: Full operational responsibility for all active equity and retained client accounts, plus incoming Event Engineer beta clients. Typical portfolio size is three to six concurrent accounts, each running its own event cycle.

Event volume: Multiple live client events per quarter, each on a recurring turnover cycle of roughly four to six weeks, plus The Event Engineer's own events.

Systems: GoHighLevel (all client sub-accounts and the master account), ClickUp, the Event Engineer Studio platform, Canva, Zoom, Facebook Groups, Skool, Circle, Stripe payment configuration within GHL, Replit, and Loom.


3. Key Responsibility Areas
3.1 Client Delivery Management
Own the day to day operational relationship with each assigned client.

Act as the primary operational point of contact for clients in their dedicated channels, responding to build requests, technical questions and delivery issues.
Translate client requests into scoped, prioritised tasks, and push back or escalate where a request falls outside agreed scope.
Maintain a prioritised task list per client and keep the client visible on status, blockers and timelines.
Run proactive check-ins on an agreed cadence: more frequently in the lead up to an event, weekly at baseline.
Send pre-event support messages, event turnover checklists and event reflection forms, and chase the inputs needed to close each cycle.
Record walkthrough videos and short training clips so clients can self-serve on recurring tasks.
Attend client calls where technical input is required, and convert call outcomes into actioned tasks.
Flag client risk early: unmet expectations, scope creep, delivery slippage, or a client going quiet.
3.2 GoHighLevel Build & Automation
Design, build, test and maintain the full technical stack inside client sub-accounts.

Build and maintain workflows, triggers, conditions, tags, dynamic tags and custom values.
Build and maintain email and SMS sequences across every funnel phase: registration, launch, nurture, stick, live day, replay, VIP upsell, retargeting, sales and onboarding.
Build funnel pages: landing, registration, thank you, VIP upsell, order, sales, sign in, event portal, replay, waitlist and feedback pages, including mobile views.
Configure products, pricing, payment plans, coupons, order bumps and refund processes.
Configure calendars, booking flows, forms, surveys and pre-session intake.
Manage domains, sub-domains, email deliverability, sender reputation, phone number provisioning and A2P registration.
Build and maintain pipelines, opportunity stages and follow-up automations.
Set up communities and course delivery inside GHL, and build integrations to external platforms such as Skool and Circle where required.
Own snapshot management: creation, versioning, cleanup and deployment across client accounts.
Test everything end to end before it goes live. No sequence, page or automation goes to a client without a full test pass.
3.3 Event Delivery Lifecycle
Run the full operational cycle for every client event, from set up through to turnover.

Pre-event set up

Branding board, domain, email, phone integration and account configuration.
Build or update the event funnel, portal, community group and all supporting assets.
Configure the event calendar invite builder, timezone handling and countdown timers.
Schedule the pre-event social, email and SMS sequences.

Live event

Monitor systems throughout the event and resolve faults in real time.
Confirm Zoom links, sign in flows, attendance tracking and portal access are live across all comms before day one.
Update replay pages, post daily group content and manage attendance workflows day by day.

Post-event turnover

Run the standard turnover checklist against every client account: dates in email and SMS copy, automation date triggers, tag names, workflow triggers and conditions, product prices, money-off codes, email and SMS links, pipelines, registration and sign in pages, waitlist updates.
Manage refunds, group closure, member removal and the reset of social assets.
Set up the next event cycle and confirm the new dates are live everywhere.
Progressively automate steps of the turnover so the cycle gets faster each time.
3.4 Gamification & Interactive Builds
Design and build instant-feedback gamification systems layered on top of GHL event portals, including chains, hearts, badges, progress trackers and unlockable rewards.
Produce the supporting graphics, unlock logic, webhooks and external services required.
Build the client-facing explanation assets: how-to-play videos, onboarding emails and walkthrough recordings.
Test gamification against real audience conditions and resolve display or trigger failures.
3.5 Event Engineer Product & Systems Support
Work alongside the development team on the Event Engineer Studio platform: custom fields, login and access automation, onboarding webhooks, snapshot logic and sub-account provisioning.
Participate in structured platform testing cycles and report defects with clear reproduction steps.
Maintain the master Event Engineer GHL account: whitelabelling, branding consistency, disclaimers, workflow hygiene and removal of unused sub-accounts.
Build internal tools that reduce manual delivery load, including reporting and analysis applications.
Confirm build logic with developers where the platform and the delivery methodology intersect.
3.6 Systems Integrity, Documentation & SOPs
Run a regular systems health check across GoHighLevel and ClickUp, and report anything breaking or at risk of breaking.
Maintain and improve delivery SOPs: event turnover, Zoom configuration, testing checklists, backend event running, gamification builds and client change requests.
Document every build so another tea ---------- mber can pick it up. Nothing critical sits only in one person's head.
Maintain credential and access hygiene across all platforms, including rotation when a tea ---------- mber or contractor exits.
Build and maintain the client change-request process so scope is captured, priced and tracked.
3.7 Delivery Coordination
Maintain the ClickUp structure for delivery: lists, statuses, deadlines and priorities across all client accounts.
Add realistic duration estimates to build tasks and hold the delivery timeline.
Coordinate contractors and developers assigned to delivery work, including briefing, handover and quality review of their output.
Schedule client calls and delivery meetings, and manage the meeting cadence per client.
Report weekly on delivery status, blockers and upcoming event dates.


4. Success Measures
Performance in this role is assessed against:

Measure
Target
On-time event delivery
100% of client events launch on their agreed date with all funnels, automations and portals live and tested
Live event fault rate
Zero critical faults during a live event. Any fault resolved within the session it occurs in
Event turnover completion
Full turnover checklist closed within five business days of an event ending
Client responsiveness
Client operational requests acknowledged same business day, with a clear timeline given
Build quality
No client-facing build goes live without a documented end to end test pass
Documentation coverage
Every recurring delivery process has a current SOP that another tea ---------- mber can execute
Founder escalation rate
Declining volume of delivery issues requiring Founder intervention
Continuity
A named, briefed backup exists for every client account and every critical system



5. Skills & Experience Required
Essential

Advanced, hands-on GoHighLevel expertise across workflows, funnels, custom values, snapshots, products, calendars, communities and deliverability. This is the single most important technical requirement.
Demonstrated experience building and running online event funnels end to end.
Strong automation logic: able to reason about triggers, conditions, tags, timing and re-entry, and to debug why something did not fire.
Comfortable with HTML, CSS and JavaScript at the level needed for custom page elements and embedded widgets.
Experience with webhooks, APIs and connecting third-party services.
Confident client-facing written communication. Able to explain a technical problem to a non-technical business owner without jargon or defensiveness.
Project management discipline: able to hold multiple client accounts, multiple event cycles and competing deadlines at once without dropping items.
High standard of testing and quality assurance. Checks work before it ships.

Desirable

Experience with Zapier, Make or n8n.
Experience with Skool, Circle, Zoom configuration and Facebook Group management at scale.
Experience building lightweight internal tools or apps.
Canva and basic design capability for event assets.
Prior exposure to equity or revenue-share client models where delivery quality directly drives the fee.


6. Attributes
Ownership. Takes a problem to resolution rather than reporting it and waiting.
Integrity. Says what is actually true about status and timelines, including when something has slipped.
Calm under event pressure. Live events do not allow for panic. Faults get diagnosed and fixed.
Systems thinking. Solves the class of problem, not just the instance. Automates repeated work.
Boundaried. Supports clients generously without letting client urgency override agreed priorities and scope.
Documents by default. Builds so that someone else could take over tomorrow.


7. Working Arrangements
Full time, remote, with core overlap to Melbourne business hours.
Availability outside standard hours during live client event windows, with time back in lieu. Event weeks are known and blocked in advance.
Planned leave to be flagged at least two weeks ahead where possible, with handover notes and a named cover for each active client.
Weekly one to one with the Founder, plus participation in team check-ins.


8. Continuity Requirement
Because this role holds the technical and operational knowledge for every client account, continuity is a formal part of the job, not an optional extra. The incumbent is required to:

Maintain current written SOPs for all recurring delivery processes.
Record walkthrough videos for any build that is non-obvious.
Keep a live handover document per client covering status, credentials location, open items and known quirks.
Brief a nominated backup before any planned absence.

How to Apply

Submit the following:
- Resume
- Short cover letter explaining how you are fit to work in this role mentioning the experience you have and how it would help you complete this role at a high level.
- A portfolio with any examples
- Use the application code WOWZA so we know you’ve read the full role description.

IMPORTANT: This is an expert-only position. You will be skills-tested.
If you’re not proven, not fast, or not world-class — this isn’t for you.