Onboarding Project Manager

About the Role

When a property management company decides to move to Rentvine, you're the person who gets them there. You'll run a full slate of implementations at once, and every one of them landing on time — with clean data and a client who actually knows how to use the platform — is on you.

This is a project management job first. You'll own the plan, keep everyone honest about their commitments, spot trouble before it turns into a missed date, and stay the one accountable person from kickoff to handoff. You'll scope work up front as needed and write the SOWs that define it — sometimes for your own projects, sometimes for a teammate's — and those calls are yours.

You won't be purely managing from a distance, either. You'll get into the data — building migration files, checking balances — working alongside our accounting and data specialists. Most of your time goes to running the project, but this isn't a role where you hand off a plan and watch.

• Run a portfolio of client implementations end to end, from kickoff through go-live and the weeks after
• Build project plans that actually hold up — sequencing discovery, data migration, configuration, training, and financial cut-over with realistic timelines
• Confirm scope at kickoff and make sure the client knows what they owe you and when
• Handle scope changes head‑on: figure out the impact, walk the client through the tradeoff, get agreement. Don't just absorb it
• Keep project status current and clear enough that a colleague could pick up your project cold

• Scope incoming accounts — sometimes ones you'll run yourself, sometimes ones that go to a teammate. You're scoping for the team, not just your own slate
• Get on the phone with people you've never met to do it. Often you'll be calling a prospect or a new client cold, with no relationship to lean on, and you'll need to pull real answers out of them fast
• Size up the account: how much data, what condition it's in, what they're coming from, how complex their portfolio is, and how ready they actually are
• Turn that into an estimate of effort and timeline you can stand behind — including when someone else will be the one delivering against it
• Write SOWs that spell out what's included, what isn't, what we're assuming, what the client needs to do, and what "done" looks like — clear enough to settle an argument three months later
• Write change orders when scope moves, with the timeline and effort impact quantified and the client signed off before the work starts
• Make these calls yourself within your thresholds. Escalate when the commercial terms warrant it, not by default
• Get involved with Sales on the complicated deals so we scope them right before signing, not after
• Help build the templates and estimating standards so this gets more consistent over time

• Catch risks and slippage early, raise them, and fix them before a date slips
• Hold internal teams and integration partners to their dates. These are dependencies, not favors
• Run go‑live readiness reviews against real exit criteria, and make the call on whether a client is ready
• Close projects out properly and hand off to Customer Success with the context, open risks, and configuration decisions they need

• Be the client's person throughout — one point of accountability, start to finish
• Run the rhythm: kickoff, regular check‑ins, milestone reviews, close‑out
• Chase what you need from the client side. Data, decisions, people's time. Escalate on their end when their delays put the date at risk
• Say the hard things early. Timeline problems, scope creep, readiness gaps

• Work with our accounting and data specialists on migration, validation, and financial cut‑over, splitting the work based on how complex the project is and who's got capacity
• Build migration files yourself when that's faster — mapping fields, cleaning up legacy exports, prepping data for load
• Own the quality bar no matter who did the work. Review it closely enough to find the problems before the client does
• Push what you learn back into the process, so we're not solving the same problem from scratch on every project