Business context
Connect objectives, signals, use cases and the everyday business files teams already use, including PowerPoint, Word, Excel, email and PDF sources.
MAYSANO PORTFOLIO STUDIO
Turn the PowerPoint decks, Word documents, Excel sheets, emails, PDFs, objectives, signals and use cases your teams already have into a structured data product portfolio for review, prioritization and delivery. Portfolio Studio keeps the business context connected throughout the process.
Built on open data product standards developed under the Linux Foundation.
Time saved
Use existing source material and written guidance to prepare the first structured package for review.
Estimate covers preparation of the first structured draft and shareable package. Review, approval, procurement, and implementation are excluded.
AI runtime cost
Portfolio Studio is designed for evidence-handling and structured-output workloads that do not require frontier models by default. Suitable local and economical online models can keep generation costs low while the review stays with people. When local models are preferred, Studio can work with LM Studio and Ollama-based runtimes.
Demo
Watch a short walkthrough of the main Portfolio Studio workflow, from business inputs to a decision-ready portfolio.
See how Studio supports the full path from portfolio creation to approval and delivery.
See how Studio turns business inputs into a structured data product portfolio with objectives, use cases, signals, and product needs connected.
Watch video
See the Assistant answer business questions using portfolio context, with a focus on decision support rather than generic chat.
Watch video
See how Studio turns the portfolio into an approval-ready package with priorities, expected outcomes, risks, assumptions, readiness, and decision material.
Watch video
See the handoff into delivery, including Epic and Feature creation, retained business context, and progress monitoring back in Studio.
Watch videoProduct value
Connect objectives, signals, use cases and the everyday business files teams already use, including PowerPoint, Word, Excel, email and PDF sources.
Generate consistent product definitions, relationships and portfolio packages from material the organization already has.
Review priorities, assumptions and recommendations before moving selected products toward delivery.
Business value
Portfolio Studio helps teams move faster, improve decision quality, and create a clearer basis for delivery.
Business teams structure objectives, needs, signals, and use cases before technical design begins.
Goals, evidence, use cases, and proposed data products stay connected for review.
Teams assess candidate data products before investing in delivery, procurement, or automation.
Source files, generated outputs, versions, and portfolio decisions remain traceable and shareable.
How it works
PowerPoint decks, Word documents, Excel sheets, emails, PDFs, objectives, product needs, signals and use cases.
Define scope, language and portfolio-specific instructions.
Portfolio Studio structures the information into connected products and business context.
Leadership and teams review the portfolio, assumptions and recommendations.
Selected products move into integrated delivery workflows, for example Jira, while Studio keeps decision context and delivery progress visible.
Business context
Portfolio Studio keeps each data product connected to the business reason behind it. Objectives, signals, needs and use cases remain connected through portfolio review and into delivery. This gives decision-makers more context than a list of technical assets.
This connected context makes portfolios easier to review, explain, hand over and evolve.
Workflow as product
Portfolio Studio does more than generate product definitions. It supports the workflow around them, from business material and portfolio generation through review, decisions, versioning and delivery handoff into tools such as Jira.
Delivery progress can be monitored from Studio so the original business context stays connected to execution.
Portfolio Assistant
The Assistant grounds its answers in your objectives, signals, use cases, products and decision history. Teams can explore priorities and rationale without reducing the experience to generic chat.
Answers remain transparent and traceable, helping teams reach aligned decisions faster.
Business to delivery
Approved portfolio items become Jira Epics and Features while the objectives, use cases and data product context stay connected.
Delivery status flows back into Studio, giving decision-makers a clear view from original intent to execution.
Open standards
Portfolio Studio uses the Open Data Product Specification family developed under the Linux Foundation. This gives the generated portfolio a structured and portable foundation rather than locking its meaning inside the application.
Learn about the open standards



Learn Data Products
Studio helps you apply data product practices. These courses teach the methods, standards and operating models behind them.
Build the fundamentals of designing, managing and scaling data products.
View course (opens in a new tab)
Build AI-ready data product portfolios using the ODPS standards family, SDK and agent workflows.
View course (opens in a new tab)
Learn ODPS and create machine-readable data product specifications with AI support.
View course (opens in a new tab)
Create lightweight governance that makes data products trusted without slowing delivery.
View course (opens in a new tab)
Learn how to define value, pricing and monetization models for data products.
View course (opens in a new tab)Enterprise deployment
Portfolio Studio is intended for organizations that need portfolio decisions, data product context and delivery handoff to sit inside their own governance model.
The architecture direction supports controlled deployments and integration patterns without presenting every enterprise capability as already production-ready.
Portfolio Studio is available as a guided SaaS trial and can also be deployed for customer-controlled environments when governance requires it.
Keep decision context, data products and delivery information connected.
Studio includes an AI gateway layer for controlled model access, workload routing, guardrails, policies, budgeting and provider governance. Local AI-ready, with Qwen3 32B-compatible runtime recommended as the strong baseline for suitable evidence-handling and structured-output workloads. As an online option, GPT-4o mini has performed well for many Studio workloads, showing that frontier models are not required by default.
Architecture designed for identity, permissions, auditability and delivery integrations such as Jira, with progress visible back in Studio.
Security & control
Deploy Studio with the privacy, model and review controls your organization requires.
PII masking and prompt-injection guardrails for sensitive source material.
Self-hosted with no product telemetry, so your data never leaves your infrastructure.
Route work through the integrated AI gateway to approved local or online model providers.
Keep people in control of generated portfolios before approval or delivery.
Fit identity, permissions, usage controls and budget policies to your operating model.
Retain the source context behind generated products and portfolio decisions.
Pricing
$25,000one-time
For early customers who want a deployed solution and direct product collaboration.
$53,000one-time
For organizations that want Portfolio Studio deployed in their own environment.
From $65,000one-time
For large organizations that need stronger support, governance or custom needs.
All plans include the first year of software license. SaaS trial access is available for evaluation. Customer-environment deployment requires a separate integration project to set up access, configuration, delivery workflows, and operational readiness.
Frequently asked questions
Portfolio Studio turns existing business material into a structured data product portfolio for review, prioritization, approval and delivery.
Teams can work from the material they already have, including PowerPoint presentations, Word documents, Excel sheets, emails, PDFs, objectives, signals and use cases.
The Assistant can answer portfolio questions through different personas, respond in different languages, and accept either typed questions or speech input when voice is enabled.
No. Studio prepares a structured first draft and keeps people in control of review, prioritization, approval and delivery decisions.
No. Studio is designed for evidence-handling and structured-output workloads that can run with suitable local models or economical approved online models.
Yes. If you have a suitable local LLM running and available to Studio, it can be used for supported workloads through local runtimes such as LM Studio or Ollama.
Yes. Portfolio Studio can be used through a guided SaaS trial and can also be deployed into customer-managed environments when infrastructure and governance require it.
Deployments can route AI work through the integrated gateway and apply PII masking, prompt-injection guardrails, controlled model access, workload-level policies and budgeting to sensitive source material.
Yes. Approved portfolio items can become Jira Epics and Features while their business context stays connected, with delivery progress visible back in Studio.
Depending on the selected plan, the engagement can include deployment, configuration, onboarding, administrator guidance and preparation of the first portfolio.
Next step
See how Portfolio Studio works with the material and processes your organization already has.