# Prompt Pivot Pitch: Full Content Reference

> Version: 2026-05-14 | Domain: prompt-pivot-pitch.com

---

## Overview

Prompt Pivot Pitch (PP&P) is a Utah AI Build Challenge and AI Problem Studio: a three-event summer series held on Fridays at DF Dance Studio in Salt Lake City, Utah. It bridges the gap between people who have real problems and projects, and technical builders who can apply AI to move that work forward.

The format: anyone can submit a specific problem, a $500 pledge is suggested but not required, the top 10 are selected and published, and competitors work with top AI experts to build the best AI solution across three events culminating in a pitch night.

**Tagline:** Real business problems. AI-powered teams. Clear pitches.

---

## Event Series (Summer 2026)

### Event 1: Prompt (June 12, 2026)
- **Date:** Friday, June 12, 2026
- **Time:** 3:30 PM - 6:00 PM MT
- **Venue:** DF Dance Studio, Salt Lake City, UT
- **Format:**
  - 3:30 PM: Doors open, arrival, networking
  - 4:00 PM: Rotate through 10 selected problem tables (People, Product, Process, Profit, Purpose)
  - 4:35 PM: Team formation, mind-mapping, role assignment
  - 4:50 PM: Venture spec & prompt pack kickoff
  - 5:00 PM: Dinner, networking, beginner Latin or Swing social hour
- **Outcome:** Each team has a problem owner, a build team, and a working venture spec.

### Event 2: Pivot (July 11, 2026)
- **Date:** Friday, July 11, 2026
- **Time:** 3:30 PM - 6:00 PM MT
- **Venue:** DF Dance Studio, Salt Lake City, UT
- **Format:** Teams return with demos-in-progress. Mentor tables test the business case. Pitch decks are reviewed and sharpened.
- **Outcome:** Refined demo, validated business case, investor-ready narrative.

### Event 3: Pitch (August 14, 2026)
- **Date:** Friday, August 14, 2026
- **Time:** 3:30 PM - 6:00 PM MT
- **Venue:** DF Dance Studio, Salt Lake City, UT
- **Format:** Final showcase. Teams pitch real solutions to judges, investors, operators, and sponsors. Followed by dinner, networking, and a social dance hour.
- **Outcome:** Winners recognized, investor connections made, alumni community formed.

---

## Problem Submission

### Who should submit a problem?
Business owners, operators, and domain experts in Utah with a real, specific, AI-applicable operational problem. The problem should be something a business or community faces today that AI could plausibly help solve.

### How to submit
Visit `/submit-problem` on the site. Provide:
- A specific problem or project description (not a product idea; a real business pain)
- The strongest "P" category (People, Product, Process, Profit, or Purpose)
- A suggested $500 pledge, if appropriate (signals commitment; money goes toward prizes and event costs)

### Selection process
Problems are published for community upvoting. Selection factors:
1. Pledged support ($)
2. Community upvotes from operators who face the same problem
3. Category distribution across the 5 Ps
4. Organizer review for specificity, AI applicability, and uniqueness

The top 10 problems are announced before the first event.

---

## The 5 P Categories

- **People**: AI applied to hiring, leadership, learning, customer success, community, and team workflows.
- **Product**: AI applied to building new products, improving existing experiences, and turning domain knowledge into useful features.
- **Process**: AI applied to operations, handoffs, automation, quality, service delivery, and repeatable business systems.
- **Profit**: AI applied to revenue, pricing, margins, forecasting, sales, retention, and investor-ready business models.
- **Purpose**: AI applied to mission-driven goals, trust, access, and community or customer value.

---

## Applying to Build (Participants)

### Who should apply?
- **Business-context contributors**: Business owners, domain experts, operators, or problem owners who can explain the stakes.
- **Technical builders**: engineers, data scientists, no-code automation builders, AI tool users, and AI practitioners.

Every competing team needs business context and technical build capacity. Teams are formed at the first event (Prompt).

### Application
Visit `/register` to apply. Indicate which events you can attend and the role you can play.

---

## Executive Track

A separate track for senior operators and executives who want to observe, mentor, or explore AI applicability for their organizations without joining a competing team. Details at `/executives`.

---

## Challenge Framework

### Application tracks (team composition)
1. **Business + Technical**: Core team. Problem owner or domain expert + technical builder.
2. **Domain Expert + Builder**: Operator with deep domain knowledge + AI practitioner.
3. **Product + Engineering**: Product thinker + builder who can ship.

### AI Applicability Studios (the 5 Ps expanded)
Each problem is placed in one of five studios corresponding to where AI has the most leverage in that business.

### Judging rubric
Teams are evaluated on:
- **Problem clarity**: Is the problem real, specific, and well-understood?
- **AI fit**: Does AI genuinely help, or is it a hammer looking for a nail?
- **Demo quality**: Does the solution actually work in a demo?
- **Business viability**: Can this be monetized, scaled, or adopted by the problem owner?
- **Pitch clarity**: Is the narrative crisp, honest, and investor-ready?

### The 6 Ts of Investability
Teams should demonstrate: **Team**, **Technology**, **Traction**, **Total addressable market**, **Terms**, **Timeline**.

### The 5 Vs of Automation Potential
When evaluating process problems: **Volume**, **Variety**, **Velocity**, **Verifiability**, **Value**.

---

## Partners

### Community Partners
- **DF Dance Studio**: Host venue. The space, movement, and social-hour lesson.
  - https://www.dfdancestudio.com/
- **Utah Geek Events**: Utah community events channel and nonprofit pathway for sponsorship routing.
  - https://www.utahgeekevents.com/
- **Goldman Sachs 10,000 Small Businesses**: Small-business operator participation pathway.
  - https://10ksbapply.com/
- **AI Utah**: Local AI builders and operators.
  - https://luma.com/867qhp9i?tk=cXTp2z
- **City Weekly**: Utah media reach and local storytelling.
  - https://www.cityweekly.net/

### Sponsorship
Organizations can sponsor to gain visibility with Utah's AI-builder and business-operator community. Details at `/sponsor`.

---

## FAQ

**Q: What is Prompt Pivot Pitch?**
A: A Utah AI Build Challenge where anyone can submit a real problem, and competitors work with AI experts across three summer Fridays.

**Q: Can businesses submit problems now?**
A: Yes. Visit /submit-problem. The organizing team helps clarify the problem, choose the best 5 P category, and understand the suggested pledge and selection process.

**Q: Is attendance free?**
A: Participant attendance is application-based. The goal is a curated room with both business context and technical build capacity.

**Q: Do I need dance experience?**
A: No. After the working session there is dinner, networking, and a beginner Latin or Swing lesson. Shoes you can move in are enough; partners are optional.

**Q: Do competing teams need both business and technical roles?**
A: Yes. Teams need business context from a problem owner, operator, or domain expert, plus technical build capacity from AI practitioners, engineers, data people, or automation builders.

**Q: Can I attend only one night?**
A: Apply for the dates you can attend. Competing teams get the most value from the full arc: Prompt forms the team, Pivot sharpens the demo and deck, and Pitch is the final showcase.

**Q: Who leads the social hour?**
A: DF Dance Studio leads the social hour, music, and beginner-friendly lesson.

**Q: How do accessibility and dietary needs work?**
A: Indicate in the registration form. The team batch-plans food and seating around those answers.

**Q: Will my profile be public?**
A: Only if you opt into networking visibility.

---

## Site Map

| Page | URL | Description |
|---|---|---|
| Home | https://prompt-pivot-pitch.com/ | Overview, hero, pillars, partners |
| Events | https://prompt-pivot-pitch.com/events | Event dates, schedule, format |
| Challenge | https://prompt-pivot-pitch.com/challenge | Tracks, rubric, 5 Ps, 6 Ts |
| Submit Problem | https://prompt-pivot-pitch.com/submit-problem | Business problem submission form |
| Register | https://prompt-pivot-pitch.com/register | Builder/founder application |
| Schedule | https://prompt-pivot-pitch.com/schedule | Detailed event program |
| Partners | https://prompt-pivot-pitch.com/partners | Community partner directory |
| Sponsor | https://prompt-pivot-pitch.com/sponsor | Sponsorship information |
| Executive Track | https://prompt-pivot-pitch.com/executives | Senior operator pathway |
| About | https://prompt-pivot-pitch.com/about | Organizer background |
| FAQ | https://prompt-pivot-pitch.com/faq | Frequently asked questions |

---

## Contact & Social

- Email: baguleyllc@gmail.com
- Hashtag: #promptpivotpitch
- Sitemap: https://prompt-pivot-pitch.com/sitemap.xml

---

## Prompt Pivot Pitch Agent Context System

Markdown is the canonical source for agents. HTML is the rendered human experience. JSON Schema is the contract.

Agents should help users turn source material into:

1. A public voting card.
2. A private readiness brief.
3. A structured JSON submission payload.
4. Share copy.
5. One unresolved question.

Use "source material" or "problem context" for user-provided input. Users may provide a short description, well-formed problem, full PRD, technical spec, customer interview transcript, or implementation memo.

### Agent lookup order

0. `https://prompt-pivot-pitch.com/agent-context.txt` for a single-fetch bundle of everything below (orientation, task rules, schema, and API summary). Best for chat-only LLMs with no tools.
1. `https://prompt-pivot-pitch.com/llms.txt` for orientation.
2. `https://prompt-pivot-pitch.com/llms-full.txt` for complete context.
3. `https://prompt-pivot-pitch.com/problem-shaper.md` for task rules.
4. `https://prompt-pivot-pitch.com/problem-card-schema.json` for public-card validation.
5. `https://prompt-pivot-pitch.com/openapi/problem-api-v1.json` for endpoint contracts.
6. Swagger, Redoc, or Fern-generated SDKs/CLI when available.

### Core problem API

- `GET /api/problem/v1/schema`
- `GET /api/problem/v1/criteria`
- `POST /api/problem/v1/shape-preview`
- `POST /api/problem/v1/submit`
- `GET /api/problem/v1/submissions/{id}/status`
- `GET /api/problem/v1/submissions/{id}/public-card`
- `GET /api/problem/v1/submissions/{id}/share-copy`
- `GET /api/problem/v1/submissions/{id}/pledge-signal`
- `GET /api/agent/v1/bootstrap?submissionId={id}&format=markdown`
- `GET /api/agent/v1/bootstrap/preview?submissionId={id}`
- `GET /api/agent/v1/bootstrap/files?submissionId={id}`
- `GET /api/agent/v1/llmcopy?submissionId={id}`
- `GET /api/agent/v1/discover`
- `GET /api/agent/mcp/manifest`

### Safe pledge and vote signals

Do not expose raw pledge totals publicly. Public agents should use this shape:

```json
{
  "submissionId": "problem_123",
  "pledgeSignal": "none | interest | pilot_interest | sponsor_interest | private",
  "voteSignal": "none | early_interest | active_interest | strong_interest",
  "publicSummary": "This problem has received private interest.",
  "privateDetailsAvailable": false
}
```

### Nontechnical local-agent flow

1. Ask the user for source material.
2. Call `POST /api/problem/v1/shape-preview`.
3. Explain the public card first.
4. Keep private readiness notes separate.
5. Offer to submit, revise, generate share copy, or track the submission.

### Technical local-agent flow

1. Inspect OpenAPI and schema.
2. Validate JSON payloads before submission.
3. Use Swagger "try it out", Redoc, Fern SDK/CLI, `curl`, or a local script.
4. Store submission ids in local state.
5. Use status, public-card, share-copy, vote-signal, and pledge-signal endpoints to keep the user informed.

### Externa ExecOS posture

Externa acts as Chief of Staff working directly with the CEO for the user's Prompt Pivot workspace. It can operate at a practical executive level across CTO, CFO, COO, CMO, product, strategy, operations, and related roles.

When a task has an executive domain, Externa should name the role lens, take a current timestamp, and look up current best practices if web or API access is available. If current lookup is unavailable, it should say so and use stable principles only.

### Share-copy safety

Share copy must use only public-card content, official status, public vote signal, public pledge signal, and user-approved facts. It must not include private readiness notes, private submitter context, private customer names, emails, phone numbers, raw pledge totals, or private pledge details.

Do not imply endorsement, selection, funding, partnership, availability, urgency, sponsorship, pilots, revenue, customer demand, or organizer approval unless verified. Ask for human approval before posting, emailing, texting, tagging people, or contacting sponsors/builders.

### Local Externa agent kit

- `https://prompt-pivot-pitch.com/api/agent/v1/bootstrap?format=markdown`
- `https://prompt-pivot-pitch.com/api/agent/v1/bootstrap/preview`
- `https://prompt-pivot-pitch.com/api/agent/v1/bootstrap/files`
- `https://prompt-pivot-pitch.com/prompt-pivot-agent/SKILL.md`
- `https://prompt-pivot-pitch.com/prompt-pivot-agent/onboarding.md`
- `https://prompt-pivot-pitch.com/prompt-pivot-agent/watch-submission.md`

The primary Externa workflow is paste-to-provision. The user copies one bootstrap prompt into ChatGPT, Claude, Cursor, Gemini, or a local agent. That assistant creates or shows the workspace files wherever the user chooses. Direct file downloads are an advanced fallback.