Client Success Representative

Remote
R25K+

per year

Job Description

ABOUT MOONWARD Moonward is a Brisbane-based software development company building custom software, mobile apps and web applications for businesses across Australia and New Zealand. The company has delivered 120 products, with every client passing through a Discovery Phase before development starts so scope is clear before a single ticket is written. THE ROLE This is a relationship and growth role, not a delivery or technical role.

The Client Success Rep does not write tickets, allocate sprint work, or make technical calls — that responsibility stays with the Project Coordinator, the developers, and Moonward’s AI ticket system. The role exists to make sure every client always understands what’s happening, always feels heard, and hears about new value from Moonward before they have to ask for it. The Client Success Rep owns the client relationship end to end.

Once a project is quoted and approved, they become the client’s one consistent point of contact for the life of that relationship — running daily communication, translating technical work into plain language, surfacing new opportunities, and ensuring every client is fully across what’s happening on their project. This role is being built by repositioning Moonward’s current Project Manager into it. Everything technical they previously owned has moved to the Project Coordinator, the developers and Moonward’s AI ticket system.

What carries forward is the growth and relationship mandate, drawing directly on the client relationships already built. WHAT YOU'LL OWN, DAY TO DAY CLIENT COMMUNICATION & INBOX DISCIPLINE (DAILY)

Clear every client Slack channel, email inbox and support request queue daily — nothing sits unread or unanswered overnight.

Act as the daily, primary point of contact in every client Slack channel for timelines, deadlines, scope questions and anything else the client raises.

Own the relational side of client onboarding: introduce yourself and set expectations for cadence and communication, while the Project Coordinator handles systems setup (Jira, Forecast, Slack) in parallel.

Respond to non-technical requests the same day; route anything technical to the Project Coordinator for status or the dev team for judgment calls.

Monitor relationship health signals across all accounts — a slow reply, a flat tone — and act the same day rather than letting it sit. CLIENT MEETINGS & VISIBILITY (FORTNIGHTLY, WEEKLY SLACK MINIMUM)

Attend a fortnightly check-in meeting with every active client.

In any week without a scheduled meeting, send a substantive Slack update instead — every client hears from you at least once a week, no exceptions.

Own the standard behind both: clients should never have to ask what’s happening on their project. Full visibility on progress is a gap you close, not one you wait out. PROJECT KNOWLEDGE & CONTEXT (ONGOING)

Interpret the UI/UX designs and tickets for every active project owned — not just the summary — to speak to the work with confidence.

Answer scope and “why” questions directly, without chasing Dev or the Project Coordinator for an explanation every time.

Act as the communication bridge between the dev team and the client: translate technical detail into plain language outbound, and translate client asks into something Dev can action inbound. IDEATION & NEW REQUIREMENTS (ONGOING)

Strategise with clients to build out new requirements, drawing on business context, Discovery insights and the Coordinator’s reporting to identify what they need next before they ask.

Build out and present new ideas to clients proactively, without waiting for them to ask.

Own the upsell conversation and pipeline, working toward an agreed sales upsell target set with Leadership.

Treat Moonward Autopilot as a standing upsell: as a project stabilises post-launch, pitch the ongoing support package proactively. QUOTE REQUESTS (AS THEY ARISE)

Document what’s being asked for and map out roughly what it involves whenever a client wants something new.

Pass new technical requirements to the dev team for quoting and estimating — the translator role, not the estimator.

Package the estimate into a quote and secure Leadership sign-off before it goes to the client, protecting margin the same way the original quote does. CLIENT REPORTING (WEEKLY, EVERY PROJECT)

Turn the Project Coordinator’s draft sprint report into a client-ready update, adding narrative and business framing.

Fold release notes and the forward release schedule into that update so clients see both what shipped and what’s coming next.

Attend sprint reviews alongside a developer where scheduled — leading the relationship and framing while the developer demos the work. SALES & OPPORTUNITY REPORTING (WEEKLY, INTERNAL)

Compile and send Leadership a weekly report of new sales and extension opportunities across the account book.

Move at least one ideation or upsell conversation forward per active account each week. CUSTOMER EXPERIENCE (ONGOING)

Own how the relationship feels, distinct from whether the work ships on time.

Request reviews and testimonials at natural high-satisfaction moments — a strong sprint, a project completion, a milestone win.

Flag CX concerns — a client who seems disengaged or frustrated even if delivery is on track — the same way you’d flag a churn risk. TIMELINE & RISK CONVERSATIONS (AS NEEDED)

Own the conversation with the client when the Project Coordinator flags a project trending behind its quoted timeline.

Loop in Leadership on the actual options rather than renegotiating the commitment alone, while owning delivery of the message to the client. RETENTION (ONGOING)

Track the health of every relationship owned — raise a slow response, frustrated tone or declining engagement early rather than waiting for a churn signal.

Work toward an agreed client longevity target (average tenure or renewal rate) set with Leadership, alongside the upsell target. WHAT THIS ROLE DOESN'T OWN Set clearly so the role stays useful and doesn’t drift into decisions that belong elsewhere.

Ticket authorship, technical scope, or sprint and pointing decisions — these stay with developers, the Project Coordinator’s AI-ticket accuracy checks, and the Designer’s approved scope.

Technical or architectural decisions — reading tickets and designs is for context and communication, not to make the call.

Final sign-off on quotes — documenting the request and getting it estimated is owned; Leadership signs off before it’s sent.

Resource allocation, staffing, or performance management.

Jira and Forecast administration — the Project Coordinator owns that system’s hygiene. WEEKLY CADENCE

Daily: every client Slack channel, email inbox and support queue cleared; primary point of contact for timelines, deadlines and scope questions; same-day responses on non-technical requests.

Weekly: client report sent by the agreed deadline; a substantive Slack touchpoint with every client at minimum; sales and extension opportunities report sent to Leadership; at least one ideation or upsell conversation moved forward per active account.

Fortnightly: check-in meeting attended with every active client.

Per sprint: sprint review attended alongside a developer where scheduled. WHAT WE'RE LOOKING FOR

Client-facing experience in a software agency, professional services, account management or customer success role — ideally 2 years.

Comfortable reading a ticket or a UI/UX design well enough to explain it in plain language, without needing to write code.

Confident owning a revenue number — measured on upsell and retention targets, not just relationship warmth.

Clear, persuasive written and verbal communication — daily Slack, meetings and client-facing reports are the job.

Comfortable translating between technical and non-technical people in both directions.

Able to run several concurrent client relationships without losing context on any of them.

Comfortable in a fast-moving, remote-friendly, Slack-heavy environment. NICE TO HAVE

Experience in a software development agency or client-services environment.

Background in UX, product or a technical discipline, enough to read design and tickets with real fluency.

A track record of growing accounts: upsells, renewals or expansion revenue.

Familiarity with Jira and Forecast, even at a read-only level. WHAT GOOD LOOKS LIKE IN 90 DAYS

Every active account has a single, clearly communicated point of contact and same-day responses on non-technical requests.

Every client Slack channel treats you as the fast, reliable first response on timelines, deadlines and scope questions.

A track record of proactive ideas, upsell conversations and quote requests raised across the account book, not just client-initiated ones.

At least one Moonward Autopilot conversation underway on a stabilised project.

The first reviews or testimonials collected off the back of a strong sprint or milestone.

Client reporting goes out on time, every time, built on the Coordinator’s data.

Apply for Client Success Representative

Submit your application for this position at VA Connect Ltd

Add a few notes about your experience first for a more personal draft. You can edit the draft before submitting.

PDF, DOC, or DOCX (max 5MB)

Ready to Apply?

Submit your application for this position