Runpoint ships systems that keep running after the first launch. Someone has to own the afterlife.
This role manages the ongoing maintenance layer across client contracts. Bugs, minor feature requests, model changes, workflow drift, documentation gaps, recurring reports, access issues, stakeholder check-ins, and the quiet pile of small fixes that can either preserve trust or erode it.
The job is not to be a meeting scheduler. It is to keep a portfolio of live systems healthy and make sure the right person is working on the right thing before the client has to ask twice.
What you will do
- Run the maintenance cadence across multiple client accounts.
- Triage requests, clarify requirements, assign specialists, and track follow-through.
- Maintain visibility into system health, open bugs, recurring issues, and client satisfaction.
- Write clean scopes for small improvements and make sure they actually ship.
- Keep documentation, handoff notes, and maintenance playbooks current enough to be useful.
What we need
- You have managed delivery, support, implementation, client success, or technical programs across multiple accounts.
- You can separate urgent from loud, and important from merely annoying.
- You are comfortable with technical systems even if you are not the person writing most of the code.
- You communicate clearly in writing. Clients should never wonder what is happening.
- You like making messy operating loops boring. Boring is underrated.
Strong signals
If any of these describe you, the conversation will move quickly.
- You have owned a portfolio of client work where context switching was part of the job.
- You can create lightweight process without turning the company into a process museum.
- You know how to protect builder time while still serving clients well.
- You notice stale tickets, recurring defects, and vague ownership before they become drama.