A fixed-price project portfolio review pilot
Review a proposed PortfolioDesk pilot, its published price, and the illustrative sample-data preview. Your agency alone determines its purchasing process, required approvals, security review, and documentation.
A focused project-review scope
An agency's project records, budget information, schedule updates, and leadership reporting may be maintained in separate locations. A proposed pilot can examine one department or capital program, subject to the records the agency authorizes and the scope it approves.
The website currently provides an illustrative preview with fictional project information. It does not represent an operational agency-connected product. See different portfolio review approaches.
Potential pilot steps
Scope
Agree the department, project records, agency reviewers, and authorized pilot objectives.
Review
Define the project-status, budget, and schedule information agency staff would need to assess.
Validate
Separately identify and verify proposed data handling, access control, reporting, and implementation requirements.
Approve
Authorized agency staff retain responsibility for every project decision, reporting output, and purchase.
Your agency determines the purchasing process
The proposed $6,500 fixed-price pilot covers a separately agreed 60-day scope for one department or capital program. Your agency alone determines the purchasing process, applicable rules, required documentation, security review, and approvals.
Any follow-on service requires its own separately verified implementation scope and agency authorization. No purchasing exemption, existing production application, completed security assessment, or available third-party documentation is represented.
Published proposed pricing
The published pilot price and potential follow-on tiers let an agency evaluate a proposed scope against its own requirements and purchasing process. No savings, financial return, customer outcome, or implementation timeline is promised. See the published pricing.
Security requirements come before agency data
Any proposed production access, encryption, hosting, decision record, retention period, or reporting feature must be scoped and independently verified before real agency data is used. No existing security certification or deployed AI implementation is claimed. See the Trust Center.
Potential data sources require separate verification
Project trackers, work records, finance data, and leadership reporting are potential pilot inputs only. Any access, source mapping, connector, and implementation must be separately scoped and approved. Explore proposed capital program review, IT project intake, executive reporting, and existing tracker review scopes.
Common questions
Who decides the purchasing requirements?
Your agency determines its own purchasing process, security review, documentation, and required approvals.
What exists today?
The public website offers an illustrative portfolio preview on fictional sample data and describes a proposed agency pilot. It is not a deployed production application.
Can existing project records be considered?
Any access, field mapping, implementation, and source permissions must be separately scoped, approved, and verified.
Who owns project decisions?
Authorized agency staff retain responsibility for project priorities, source-record review, reporting, and purchasing approval.
Explore a pilot for a portfolio like yours
A short walkthrough of the proposed pilot and sample workflow shaped like your portfolio. No commitment.
Request a demo