Fractional technical project management
A fractional technical project manager owns delivery for an agency that sells technical work but has no dedicated PM layer. Kodelytics runs sprint planning, estimation, scope and change control, QA, and client-facing communication on a monthly retainer — typically two to four days a week across several client accounts.
Most agencies under sixty people don't have a delivery function. Account managers sell the work, developers build it, and the space between them — estimation, sequencing, acceptance, the awkward conversation about scope — is nobody's job. It gets absorbed by whoever has the least billable pressure that week. That works until two projects run concurrently, and then margin quietly disappears into rework.
The cost is invisible because it never appears as a line item. It shows up as senior developers doing coordination at developer rates, as a client escalation that took three weeks to surface, and as the fourth project this year that shipped two months late for reasons everyone can describe and nobody wrote down.
A fractional project manager owns delivery for an organization part-time on an ongoing basis — typically two to four days a week — rather than as a full-time employee or a fixed-length consulting engagement. The word fractional describes the time commitment, not the scope of responsibility.
What's actually wrong
These are the symptoms buyers of this service recognize before they can name the problem.
- Developers ask what to work on next, and the answer depends on who asked most recently.
- Projects are quoted by the person who sold them, not the person who has to build them.
- Jira or Asana exists, but the real status lives in a Slack thread and a spreadsheet.
- Scope changes are agreed verbally on client calls and never re-priced.
- QA happens when the client finds something.
- Retrospectives don't happen, so the same estimate is wrong the same way twice.
What the engagement includes
- Sprint planning and a running backlog with real acceptance criteria, not one-line tickets.
- Effort estimation using Fibonacci story points, calibrated against your team's actual velocity rather than an industry benchmark.
- Jira or Atlassian setup, workflow design, and ongoing board hygiene — including the reporting configuration that makes velocity meaningful.
- Scope and change control: a written change record, a re-estimate, and a client-facing decision instead of silent absorption.
- QA methodology — test cases tied to acceptance criteria, staging sign-off, and a defect triage process with severity definitions.
- Developer and vendor coordination, including subcontractors and the client's own IT.
- Client-facing status communication: a weekly written update the client can forward to their own stakeholders.
- Escalation handling — the call where a deadline moves, made early and with options attached.
What the first thirty days look like
Week one is inventory, not change. Every active project, its commercial model, what was promised in writing, what has been promised since, and where each one actually stands versus where it's reported to stand. That inventory is usually the first document of its kind the agency has had, and it is frequently uncomfortable.
Week two establishes cadence: a sprint boundary, a backlog with acceptance criteria on the next two weeks of work, and a weekly written client update in a format you can white-label. Weeks three and four run that cadence once and fix what breaks in it — usually estimation, because the first velocity measurement is always a surprise.
Process changes land in that order deliberately. Tooling migrations, new templates, and ceremony redesigns before there's a measured baseline are how process work becomes theatre.
How this works alongside your account managers
The division that works: account managers own the client relationship and the commercial conversation; delivery owns the estimate, the sequence, and the acceptance. The friction point is always the scope conversation, and the resolution is that delivery supplies the number and the account manager delivers it.
That split also protects the relationship. An account manager who has to invent an estimate on a call is exposed twice — once when it's wrong, and once when the developer says so.
Fractional PM, delivery agency, or full-time hire
| Fractional PM | Delivery agency | Full-time hire | |
|---|---|---|---|
| Time to effective | Days | Weeks | 3–6 months |
| Cost structure | Variable retainer | Marked-up project or retainer | Salary + benefits |
| Availability | Defined days per week | Team-dependent | Full-time |
| Process | Brings one | Brings theirs | Learns yours |
| Best when | 2–5 concurrent technical projects | Whole function outsourced | Sustained internal pipeline |
How it's scoped and priced
Engaged as a monthly retainer with a defined baseline of hours plus ad hoc capacity. The baseline covers sprint cadence, ceremonies, and standing client communication; ad hoc covers escalations and new scoping work. Most agency engagements sit between two and four days a week.
Retainers are quoted after a discovery call and a look at the current delivery process. Where the situation is unclear — or the agency wants to test the working relationship first — the entry point is a fixed-fee Delivery & Scoping Review, which is credited against the first month if a retainer follows.
Kodelytics does not publish rates. Every engagement is quoted after a discovery call, because the same service name covers materially different amounts of work.Ask for a quote.
What you get at the end
- A configured project management instance your team keeps using after the engagement.
- An estimation model calibrated to your team's velocity.
- A written change control process and a change log per project.
- A QA methodology document with test case templates.
- Weekly client-facing status reports, in a format you can white-label.
Questions
How much does a fractional technical project manager cost?
Kodelytics quotes fractional PM work as a monthly retainer with a defined baseline of hours. Price depends on the number of concurrent client accounts, the cadence, and how much scoping work is included. Ranges are quoted on a discovery call rather than published, because a two-account engagement and a six-account engagement are not the same job.
What's the difference between a fractional PM and a full-time hire?
A full-time PM costs a salary, benefits, and three to six months of ramp, and the agency carries the risk if pipeline dips. A fractional PM starts inside a week, is priced as a variable cost, and brings a delivery process rather than learning one. The trade-off is availability: a fractional PM is not in every internal meeting.
Do you manage our developers directly?
Yes, on the delivery side — assignment, sequencing, unblocking, and acceptance. Employment matters stay with you: performance management, compensation, and hiring decisions are not part of the engagement, though technical hiring assessments can be scoped separately.
Which tools do you work in?
Jira and the Atlassian suite by preference, and Asana, Linear, ClickUp, Monday, or Azure DevOps where that's what the team already uses. Kodelytics will not migrate you to a new tool in the first month; process comes first, tooling follows.
Can you work with our existing project manager?
Yes. A common arrangement is Kodelytics owning the technical accounts — builds, migrations, tracking work — while the in-house PM keeps the creative and retainer accounts.
Do you sign an NDA and work under our brand?
Yes to both. Most of this work is white-labelled: Kodelytics appears to your client as part of your delivery team, and client names are never published.