Hackathon submission
Account-aware OCI positioning from a company website
Core workflow
Analyze a public company website
Before
Manual research, generic decks, unsupported assumptions, inconsistent rep prep.
After
Website evidence, OCI fit, persona talk tracks, objections, exports, audit trail.
Reviewing public website content
Crawling priority pages, extracting business signals, and scoring OCI services.
Rubric proof
Why judges should care
Problem severitySales reps lose time turning public account research into credible cloud positioning.
Market scopeEvery enterprise sales team doing account-based selling faces this prep burden.
Solution fitThe first action is the natural rep workflow: enter a company website.
Demo proofOutputs include evidence, confidence, editable talk tracks, exports, and audit history.
DifferentiationCombines account evidence, OCI service mapping, AI governance, and enterprise controls.
Account brief
Company
Industry-
Signals-
Top OCI fit-
Review state-
Detected signals
Business and technology priorities
OCI fit map
Recommended Oracle Cloud positioning
Sales workspace
Editable talk track
Saved accounts
Analysis history
Trust model
AI governance and citations
Run an analysis to see website citations, official Oracle documentation, confidence methods, and review controls.
Guardrails
Claim discipline
FactsWebsite snippets and Oracle documentation links.
AssumptionsLikely priorities inferred from public language.
RecommendationsOCI positioning that must be reviewed before customer use.
AuditEvery create and edit action is recorded for enterprise accountability.
Total analyses0
Review rate0%
Avg recommendations0
Audit events0
Usage
Top OCI recommendations
Enterprise readiness
Controls and integrations
Audit trail
Recent events
Workspace settings
Enterprise controls
API readiness
Connector endpoints
POST /api/analyze
GET /api/analyses
PATCH /api/analyses/:id
GET /api/admin/metrics
GET /api/export/:id.md