Any type of work, planned and delivered in one place
One platform for product work and customer projects
ServiceNow Strategic Portfolio Management (SPM) gives you one platform for the two kinds of work that matter most: the products your teams build and the projects your customers pay for. Capture an idea or a signed order, plan it, staff it with the right people, track the time and watch the margin while the work runs. Software teams work in sprints, delivery teams work in phases, and leadership sees one view of all of it. Whether you run Jira, a project tool or spreadsheets today, this is the version where sales, delivery and finance work from the same record.
About ServiceNow SPM›
ServiceNow SPM brings ideas, demand, roadmaps, resource plans, projects, timesheets and project financials onto the ServiceNow AI Platform. It began as a tool for managing internal portfolios. We implement it for two models of work: software development teams taking ideas to product, and professional services businesses delivering the projects they have sold.
Your projects sit on the same platform as your sales, orders and customer service. A signed order in Sales CRM becomes the project. A customer request becomes work in the backlog. The commercial context travels with the work, so the delivery team starts from what was sold, not from a retyped summary.
Bring us the way work arrives in your business today, and we will show you both paths running on the platform.
What changes when all your work runs on one platform
Product work and customer projects draw on the same people, so portfolio reporting shows both, and leadership stops assembling the real picture by hand after the fact.
Capacity by skill and role is visible before anyone promises a start date, so work is approved against the people who will actually do it.
Time, cost and budget are attached to delivery as it happens, so a project drifting off plan shows up in the current month, not three months later.
Sprints, phases and hybrid projects run side by side, and stories and project tasks roll up to one status.
Idea lists, roadmap slides, resource spreadsheets, timesheet tools and project cost workbooks come together in one application on a platform you may already run. Security, compliance and access controls are inherited from ServiceNow rather than added on.
Those are the gains worth measuring, and they get measured on your own numbers, in your own business.
Idea to product and project execution, running side by side
SPM runs two models of work on one platform. Idea to product serves software development, from the first idea to a deployed product. Project execution serves professional services, from a signed order to a delivered project. Both draw on the same resource management, timesheets, financials and portfolio reporting.
Two intakes, one platform: an idea or a signed order.
Hybrid projects run agile phases inside the work breakdown structure.
Stories and project tasks roll up to one status.
Defects and requests re-enter the backlog.
Built for businesses that sell their people's time
For a consultancy, an IT service provider or a system house, SPM is the delivery core of professional services automation (PSA): selling the work, staffing it, tracking the time and watching the margin. PSA is the industry name for that category. On ServiceNow you build it from SPM and the commercial applications around it: projects, capacity planning, resource management, time capture, rate models and project financials.
because you see the demand on your people first.
not after month-end.
with the commercial context attached.
We map every requirement to the system that should own it, including utilization targets, bench visibility, revenue forecasting, invoicing and revenue recognition: SPM, your finance system or a specialist platform. You see where each capability lives, and why, before you commit.
Related: Technology Service Providers & IT System Houses.
The handover from signed order to project that arrives intact
When sales and delivery run on the same platform, a signed order is never retyped into a project tool. The customer never has to explain it twice.
A qualifying order in Sales CRM creates the project workspace, with the work breakdown, milestones, tasks and financials set up from what was sold. An AI handover summary gives the project manager what was promised, to whom and on what terms, before the kickoff.
The platform makes it possible, the process makes it work, and five answers get you there:
We settle those with you in a workshop, then the platform enforces what you agreed.
Related: what happens before the order is signed → ServiceNow Sales CRM and CPQ.
Products, customer projects or both?
Bring us how work arrives, gets staffed and gets delivered today.
From idea to deployed product, with the reason it was funded attached
SPM keeps the chain from idea to product in one place: an idea arrives, becomes demand with a business case, gets scored and placed on the roadmap, then runs through sprints and release. Anyone can trace a shipped feature back to the objective it was funded for, and the roadmap stays true because it reads from the work itself.
That chain gives you a decision layer between an idea appearing and delivery capacity being committed to it. Not every idea should become a project, and the layer is where you decide which ones do.
It matters more each year. AI-assisted development makes building faster, which makes deciding what is worth building the harder problem. SPM holds the requirements and planned work upstream, while your engineers use the AI development tools that suit them.
Teams already in Jira or Azure DevOps keep working there: ServiceNow documents two-way integrations with both, so the portfolio view stays connected. When a sprint slips, the roadmap updates itself. Defects and new requests flow back into the backlog through Release and Change.
AI that takes the admin off your project managers
AI in SPM drafts the work around the work. It writes user story drafts for product teams, a handover summary for the project manager when an order is signed, and status summaries while the project runs. It summarizes incoming requests and spots similar ones already in the pipeline, flags work that looks at risk, and helps match people and skills to what a project needs.
The output is only as good as the portfolio data underneath it: complete skills data makes resource recommendations sharper, and consistent project data makes status predictions reliable. So we establish the naming, the request model and the people data first, then switch on AI where it improves real work.
ServiceNow runs the workflow and the governance, and Claude brings the intelligence.
We work in a multi-model architecture with Claude as our preferred model, choosing the model that fits the task.
Related: ServiceNow AI · AI Control Tower.
The groundwork that makes SPM deliver
SPM delivers when the decisions around the work are clear, and making them clear is a large part of the value of the project. Who can submit work, who prioritizes it, who owns the funding, what counts as strategic and when a project gets stopped: we settle those with you as part of the work.
And by the end, someone in the business owning the operating process, because that is what keeps it working after go-live.
We start with a focused first phase that people use every day, then extend it.
We implement the systems your projects have to connect to
Project delivery succeeds or fails at the seams: the signed order, the people plan and the cost. That is the work we do.
We implement the systems SPM has to connect to, on the same platform: sales and orders, quoting, customer service and marketing. When we design your project model and your handover, we already know what the sending end looks like.
We are a professional services business ourselves, so capacity, time and margin are questions we answer every week, not concepts from a slide.
We design the operating model, not only the configuration, and we tell you what works out of the box and what needs configuration. Our independence is written into our contracts: we document the recommended system of record and the integration boundary for each capability, including where another product is the better answer for you.
The senior practitioners who design your solution are the same people you work with from first workshop through go-live. No account layer, no handover to a bench.
See all your work in one place.
SPM pays off when the idea, the order, the people and the margin live on one platform. Bring us how work arrives, gets staffed and gets delivered today, and we will show you what it looks like on ServiceNow.
- Professional services automation (PSA)
- The industry name for software that helps a services business sell, staff, track and bill project work.
- RICE scoring
- Ranking ideas by reach, impact, confidence and effort.
- Work breakdown structure (WBS)
- A project divided into phases, deliverables and tasks.
- RIDAC
- Risks, issues, decisions, actions and changes, tracked on the project.
- Hybrid project
- A project that runs agile sprints inside a phased plan.
- Planning interval
- A fixed period in which several agile teams plan and deliver together.
- Rate model
- How you set what a role costs internally and what you bill for it.
The questions buyers ask us.
What is ServiceNow SPM?
›
Strategic Portfolio Management connects business strategy to delivery on the ServiceNow AI Platform. It covers ideas and incoming demand, portfolio planning, roadmaps, capacity and people, project and agile delivery, time, project costs and value tracking. We implement it for software development teams and for professional services businesses delivering customer projects.
What is the difference between SPM and PPM?
›
Project Portfolio Management, or PPM, is the narrower part inside the SPM family. PPM manages projects, programs, people and financial plans. SPM adds strategy, incoming demand, portfolio planning, roadmaps, sprint planning and investment decisions.
Is SPM only for internal IT portfolios?
›
It started there. What makes it valuable for product teams and services businesses is what sits on the same platform: sales, orders and customer service share one customer record with your projects, so customer work and product work are planned, staffed and measured together.
Can we run a professional services business on it?
›
Yes. SPM provides the delivery core of professional services automation: projects, resource management, time capture, rate models and project financials, connected to Sales CRM for the order. We map requirements such as utilization targets, bench visibility, revenue forecasting and invoicing to SPM, your finance system or a specialist platform, and document the system of record for each.
Do we have to replace Jira, Asana or Monday?
›
Not necessarily. Teams in Jira or Azure DevOps can keep working there, because ServiceNow documents two-way integrations with both. If a team only needs task boards, it can keep the tool it likes. SPM earns its place when capacity, time and project cost need to connect to what you sold and what you are building.
Does it support agile and hybrid teams?
›
Yes, through Enterprise Agile Planning. You can run sprint-based, phased and hybrid delivery side by side, with planning intervals for teams that plan together and one status above all of it.
Is SPM the right fit for us?
›
It fits best where projects are how you deliver revenue or products, resource planning happens in spreadsheets, work gets committed before capacity is checked, project cost arrives late, or many initiatives compete for the same people. If your need today is task boards for a few teams, we will tell you, and plan SPM for when that changes.
How is AI used here?
›
For user story drafts, sales-to-project handover summaries, project status summaries, summarizing incoming requests, flagging risk and matching people to what a project needs. The value depends on the quality of your portfolio and people data, which is why we establish that first.
What do we need to license?
›
ServiceNow publishes editions and lists several components separately, so the answer depends on your existing estate. We establish the entitlements that apply to your organization and map them against the capabilities you actually need, before scoping what to switch on. How licensing fits your wider plan is covered in Roadmapping.