KnownShift Platform
Project OS
Turn project requirements into a delivery-ready plan.
Move from requirements and assumptions to backlog, estimation, delivery planning, commercials and client-ready project artifacts through one governed workflow.
One user, up to three active projects, billed monthly.
Project OS converts project requirements into an approved backlog, defensible estimate, executable delivery plan, commercial model and professional project documentation.
How it works
The connected workflow
Each stage consumes the approved output of the one before it, which is what makes a commercial position traceable back to a requirement.
Requirements & Discovery
Understand what is being asked for, and what has not been said.
- Requirements capture and analysis
- Scope understanding
- Assumptions
- Clarification questions
- Requirement structuring
- Dependencies
Estimation
Size the work in the unit your organisation actually estimates in.
- Story Points
- Person-Days
- Assumptions
- Transparent estimation basis
- Estimation scenarios
Backlog
Structure the work so every item traces to an approved requirement.
- Epics
- Features
- User stories
- Acceptance criteria
- Dependency awareness
- Structured backlog
- Traceability
Execution Plan
Turn the sized backlog into a team, a sequence and a timeline.
- Team model
- Resource planning
- Timeline
- Milestones
- Phases
- Capacity
- Sequencing
- Delivery assumptions
Commercial Setup
Configure how the engagement is costed before anything is priced.
- Delivery model
- Locations
- Roles
- Rate cards
- Costing assumptions
- Commercial configuration
Commercials
Produce a client price you can defend line by line.
- Project cost
- Client price
- Time and Materials
- Fixed Price
- Margin
- Markup
- Contingency
- Commercial scenarios
Artifacts
Generate project documentation from approved data, not from a blank template.
- Proposal
- Kickoff deck
- Project initiation and governance documents
- Team structure and RACI
- Definition of Done
- Test strategy and approval records
How KnownShift uses AI
- 1KnownShift proposes.
- 2You review.
- 3You edit.
- 4You approve.
- 5Approved information becomes a governed project baseline.
What Project OS is not
Project OS prepares and governs the project. Day-to-day execution can continue in Jira, Azure DevOps, Microsoft Project or the organisation's preferred delivery platform.
- Issue-level execution tracking
- Source control
- Timesheet management
- Actual-cost accounting
- Earned-value tracking
- Benefits-realisation tracking
Project OS pricing
Three plans, priced on the size of the team and the number of projects it runs at once. Every plan includes the full requirements to artifacts workflow; what changes is scale.
Project OS Individual
For individual project managers, consultants and delivery professionals.
- 1 user
- Up to 3 active projects
- 120 Analysis Units included each month
- Full requirements to artifacts workflow
Project OS Professional
RecommendedFor small delivery teams running several engagements at once.
- Up to 3 users
- Up to 10 active projects
- 400 shared Analysis Units each month
- Full requirements to artifacts workflow
Project OS Team / Organisation
For larger teams that need configurable usage, onboarding and organisation-level support.
Configured around your team size, project volume, usage and support requirements.
- Seats and active projects agreed with you
- Analysis Unit allocation sized to your delivery volume
- Onboarding for the team, run with your own projects
- A named point of contact at KnownShift
Individual and Professional are bought here and start straight away. Team and Organisation plans are configured with you.
How the analysis allowance works
An Analysis Unit is one piece of interpretive work, weighted by how much reading the task actually requires. Structuring a short requirement list costs less than reading a full requirement document and producing a backlog from it.
Every plan includes an allowance that resets each month. Deterministic work, such as recalculating a commercial model or regenerating a document from information you have already approved, consumes nothing.
Analysis Units are a KnownShift measure of work. They are not a resale of any provider's tokens, and no provider account, key or balance is ever required of a customer.
From one project to enterprise governance
The KnownShift platform family
Project OS prepares and governs one project. Program OS does the same for several interdependent ones. Portfolio OS reconciles competing investments. PMO OS governs how delivery itself is run. Each answers a question the layer below it cannot, which is why Project OS is where it starts.
- 1One project
Project OS
This pageIs this project defined well enough to start executing?
- Requirements
- Backlog
- Estimation
- Execution Planning
- Commercial Baseline
- Delivery Artifacts
Takes one project from a raw requirement to an execution-ready baseline.
- 2Several interdependent projects
Program OS
Do these initiatives hold together as one commitment we can approve?
- Program Objectives
- Constituent Projects
- Cross-Project Dependencies
- Integrated Roadmap
- Shared Resource Demand
- Program Commercials
Turns related initiatives into one sequenced, execution-ready program.
Explore Program OS - 3Competing investments
Portfolio OS
Are we funding the right initiatives, in the right order, within our capacity?
- Initiative Intake
- Prioritisation
- Investment Scenarios
- Demand versus Capacity
- Budget Allocation
- Portfolio Roadmap
Supports investment, prioritisation and capacity decisions across initiatives.
Explore Portfolio OS - 4The organisation
PMO OS
Do projects and programs here run to a consistent, governed standard?
- Lifecycle Standards
- Governance Framework
- Stage and Quality Gates
- Reporting Standards
- RAID and Estimating Standards
- PMO Operating Model
Defines how projects and programs are governed across the organisation.
Explore PMO OS
Common principles
- Structured decisions
- Traceable assumptions
- Human oversight
- Professional outputs
- Explainable intelligence
See Project OS against your own project
The fastest way to judge Project OS is to run it against a project you already know. Tell us about one and we will walk it through with you.
One project is defined. What about the five that depend on each other?
Project OS prepares one project for execution. Program OS works on the space between several: the dependency that sets the program date, the architect two workstreams both assumed they had, and the estimate that double counts the overlap. One baseline a sponsor can approve, rather than five that do not reconcile.
Evaluating this for a team? Discuss team or enterprise use with the KnownShift team.