Portal examples
Use these examples as starting points for portal structure and prompt shape.
Writing tips
- Name the client clearly in the prompt. Weak prompts usually hide who the portal is for.
- Use real transcripts when possible. They give the model more concrete detail to shape around.
- Tell Claude what tone you want: concise, sales-focused, delivery-focused, or onboarding-friendly.
- Add the source context if it matters: pasted transcript, Granola meeting, or follow-up after a specific call.
- Ask for supporting docs and a timeline only when the source material actually supports them.
- Preview locally before publish and fix factual issues first, polish second.
Common portal types
Sales follow-up
A call where you need a crisp recap, next steps, and the right supporting docs in one place.
Prompt shape
Create a portal for my client Acme based on this sales call transcript. Make the summary crisp, pull out buying signals, and end with concrete next steps and attached materials.
- Short summary written for the client
- Decision points or buying signals
- Next steps with clear ownership
- Proposal, deck, pricing, or other follow-up files
Consulting handoff
A delivery or consulting conversation where dates, scope, and sequencing matter more than persuasion.
Prompt shape
Create a portal for my client Northstar based on this consulting kickoff transcript. Focus on scope, timeline, deliverables, and who owns each next step.
- Project overview in client language
- Timeline or phases if they were discussed
- Deliverables and dependencies
- Links to docs, specs, or notes
Onboarding portal
A portal that needs to orient a new client, team, or customer after an onboarding or implementation call.
Prompt shape
Create an onboarding portal for my client Beacon based on this transcript. Make it welcoming, practical, and easy to navigate. Prioritize setup steps, owners, and useful resources.
- Warm opening and orientation
- Setup checklist or milestones
- Useful links and documents
- Support contact details and what happens next
Repeat workflow
A simple repeat workflow is /portal-create or /portal-update, then /portal-preview, then /portal-deploy.
Use the wizard again
Use /portal-onboard again when you want the full guided flow or when a teammate is new to Showpane.
Common mistakes
- Treating the portal like an internal note dump instead of client-facing communication.
- Publishing before you check whether the summary and next steps are actually true.
- Using a generic prompt with no client name, no source details, and no desired outcome.
- Overloading the first portal with too many sections before the core story is clear.