On-prem deployment option for enterprise
Do not prioritize. Present the pipeline evidence (SSO is the actual blocker) to leadership and revisit if enterprise demand shifts.E-05E-11
Five stages, in the order they ran: what Juno planned to find out, what it retrieved, what it concluded, what it checked before showing you anything, and only then the recommendation itself.
- Identify customer evidence
1 customer interviews retrieved and read.
- Review support trends
No support tickets matched this theme.
- Review sales feedback
No sales note references this theme.
- Review engineering feasibility
No engineering estimate on file; technical risk is scored from comparable work.
- Compare against strategic goals
Leadership has asked for a story, but no goal quantifies it.
- Name what is still unknown
1 gaps recorded with an owner and a discovery question.
- Check for conflicting stakeholder input
1 conflict(s) surfaced rather than averaged away.
- E-052 artifacts
On-prem demand is executive-driven; only one interview confirmed it as a blocker.
- E-111 artifact
The CEO's on-prem push is not tied to a named account or dollar figure.
- E-131 artifact
At least one enterprise VP explicitly does not need on-prem, regional residency + SOC 2 is enough.
Speculative; no named account and no figure.
One enterprise VP explicitly said they do not need it.
Leadership has asked for a story, but no goal quantifies it.
- Committing on executive intuition would consume the same enterprise capacity the SSO revenue depends on.
- An on-prem topology carries long-term support cost that no current account has agreed to pay for.
- Executive intuition reflects real demand.
Ranks last because the only supporting artifact is an executive request, and customer evidence points the other way.
The CEO has asked for an on-prem story by Q4, but customer signal is mixed and no named account cites on-prem as a hard blocker.
Ranks last: high risk, contradicts customer signal, no named revenue.
Recommendation quality
How well supported this recommendation is, measured against the evidence Juno could actually retrieve.
2 of 6 enterprise source types contributed at least one artifact.
Executive Request, Customer Interview
Disagreements are shown in Risks rather than resolved by Juno.
Whether every section of the brief could be filled from retrieved evidence.
No recommendation advances to the roadmap without an explicit decision.
Findings resting on one artifact are held at lower strength rather than stated with certainty.
Supporting evidence
Evidence strength reflects how many independent artifacts support this recommendation and how varied they are, not how certain the model sounds.
| Finding | Artifact | Severity | Corroboration |
|---|---|---|---|
E-05Inference On-prem demand is executive-driven; only one interview confirmed it as a blocker. | Executive Request Exec email: CEO on on-prem strategy | Med severity | Low confidence 2 artifacts |
E-11Fact The CEO's on-prem push is not tied to a named account or dollar figure. | Executive Request Exec email: CEO on on-prem strategy | Med severity | High confidence 1 artifact |
| Finding | Artifact | Severity | Corroboration |
|---|---|---|---|
E-13Fact At least one enterprise VP explicitly does not need on-prem, regional residency + SOC 2 is enough. | Customer Interview Interview: Sam, VP Eng (enterprise) | High severity | Med confidence 1 artifact |
Transparent scoring model
Risks
- Committing on executive intuition would consume the same enterprise capacity the SSO revenue depends on.
- An on-prem topology carries long-term support cost that no current account has agreed to pay for.
High technical risk, new deploy topology.
Leadership pushes on-prem (E-11) but customer + pipeline data point to SSO (E-01) as the actual blocker.
Additional discovery recommended
Juno names what it does not know, who can answer it, and how to ask, so limited confidence turns into a discovery step rather than a dead end.
Why it matters: It is the one number that would either justify the investment or close the question.
- What % of blocked enterprise deals cite on-prem vs SSO?
Recommended next step
Top-20 enterprise prospect survey on on-prem vs SaaS
Hypothesis: ≤20% of prospects treat on-prem as a hard requirement.
Juno proposes this step because it would close the largest gap listed above. You decide whether to run it.
Decision required. Juno recommends, you decide, and nothing reaches the roadmap without you.
Final prioritization decisions remain the responsibility of the Product Manager.