Project Manager

Aviso de fuente externaen Revflow Growth Partners

Why we existOwners of growth-stage companies do not get stuck because they lack ambition. They get stuck because the work only moves when they touch it. The owner becomes the bottleneck....

Fuente externa - sin verificarhace 8 díasVigente hasta: 23 oct 2026

Salario

No especificado

Ubicación

Quito, Ecuador

Tipo de empleo

Tiempo completo

Modalidad

No especificado

Project Manager

Quito, Ecuador

Descripción del empleo

Why we existOwners of growth-stage companies do not get stuck because they lack ambition. They get stuck because the work only moves when they touch it. The owner becomes the bottleneck. We call it Owners Living Like Operators, and it is the problem we were built to solve.
What we doAt Revflow we design and install operating systems for growth-stage companies between $10M and $100M in revenue: how opportunities enter and close, and how work moves from intake through delivery to payment. One system, both halves. We design the system first, then choose the tools that serve it. Our method is Diagnose, Design, Deploy.
Why this role existsRevflow is a small, remote team. Today every client build runs through our Operations Director. That has worked. It does not scale, and it keeps him in coordination instead of the work that grows the firm.This is our first dedicated project management hire. You will own the delivery of client builds end to end: the plan, the cadence, the client relationship, and the standard the work gets held to.
You are not stepping into a machine someone else built. You are building the delivery function, then running it. That is the honest tradeoff of this role. Less structure handed to you, more of it authored by you.
What this role is notNot a development role. You coordinate developers and subcontractors. You do not build the software.Not a note taker. You hold people to commitments. Ours, the client’s, and your own.Not a middle layer. The client hears the schedule, the risk, and the tradeoff from you.
What you will ownRun the delivery cadence. Sprint planning, standups, backlog refinement, reviews, retrospectives. You set the cadence a build actually needs, and you hold it.Own the client relationship through delivery. You are the person the client calls. You run the meetings, set expectations, and give the hard update early rather than the comfortable one late.Coordinate the build. Keep our developers, any subcontractors, and the client moving against agreed scope. Hold each side to what they committed to.Protect scope. Name the change, price the tradeoff, get the decision made and recorded. Never absorb scope silently.Clear blockers. Find what is slowing the work and remove it. Escalate to the Operations Director when a blocker needs a technical or commercial decision above your line.Keep delivery visible. Progress, risk, tradeoffs, and delivery health, in a form the client and the Operations Director can read in two minutes.Measure what matters. Track delivery health: milestone attainment, cycle time, predictability. Track adoption: whether the client’s team is actually using what we built. Adoption is the one that counts. Metrics improve the system. They are never used to grade people.Improve the process itself. Bring your continuous improvement discipline to how Revflow itself delivers. Find the waste in our workflow and take it out. This is not a side project here. It is part of the job.Keep good records. Project documentation, decision logs, milestone plans, status reporting. If a decision is not written down, it did not happen.
What we are looking forRequiredYou have run projects, not only tracked them. Scope, timeline, risk, and stakeholders, owned end to end.Agile in practice. You have run iterative delivery in a real sprint cycle. You know when to hold the ceremony and when to bend it.A structured approach to process improvement, Lean Six Sigma or similar, backed by real work applying it. We care more about the process you fixed than the belt you hold.You have owned client relationships. You have been the face of the work, run the meetings, and delivered bad news well.Enough technical fluency to coordinate a build. Credible with developers, clear with non-technical stakeholders. You do not need to write code. You do need to know when an estimate is fiction.Excellent written and spoken English, in professional, client-facing work.Organized, with follow-through. Structure holds when you are in the room.
What will make you stand outExperience in manufacturing, building trades, or field service. That is where our clients live.You have built a delivery process from nothing and gotten a team to adopt it.You have worked inside a company running EOS. Many of our clients do. We build the operational layer underneath it, so knowing the language helps.You treat automation and AI as capacity on the team, tied to a human outcome, rather than as novelty.
Whether this is the right fitWe would rather be clear now than have you find out in month three.You will like this ifYou believe process is a form of care, not bureaucracy.You would rather own an outcome than administer a task list.You want your improvement work to be the product, not something you defend at budget time.You want direct access to the people making decisions. We are four people. There is no layer between you and the founder.You want to see the whole arc: a company that could not scale, and the system that let it.
You will not like this ifYou need an established playbook on day one. You will be writing large parts of it.You want one account and a predictable rhythm. You will hold several builds across different industries.You want to be measured on velocity. We measure whether the client’s business runs better.
Your first 90 daysDays 1 to 30. Learn the method and the accounts. Sit inside active builds. Meet every client. Read every project record we have and tell us where it is thin.Days 31 to 60. Take delivery ownership of a live build. Run the cadence. Own the client conversation. Escalate early and often while you are calibrating.Days 61 to 90. Give us your read: where our delivery process leaks, what you would standardize, what you would measure. Then start installing it.
At 90 days we should be able to say the delivery function has an owner, and the Operations Director is no longer the single point of coordination.
How we workRemote. We are based in Colorado Springs and work remotely distributed.Small team. Drew (Founder and CEO), Jen (Co-Owner and Chief Experience Officer), Jorge (Operations Director), Andrés (Creative Director). Abigail & Alejandra (Implementation Specialists)Partner, not vendor. We work with client teams, not to them. That standard applies inside the company too.Reporting line. You report to the Operations Director.Full-time contract. We hire on a long-term, full-time contract basis. Compensation (in USD) & benefits are discussed openly on the first call. We would rather find out in twenty minutes whether we are in the same range than spend three weeks discovering we are not.

¿Es tuya esta vacante?

Reclámala gratis y recibe candidatos con video en CazVid.

Empleos similares