PS Demo Build Skill

Purpose

Build a custom Process Street demo for a prospect. Output must be copy-paste ready for the PS AI Builder or manual workflow construction.

Inputs Required

Provide any combination of:

• Company name + URL
• Use case / goal (what workflow to build)
• A discovery-call transcript or recording
• SOPs, spreadsheets, or process documentation from the team
• Audience context (who will watch the demo and what they care about)

Output Structure

Always produce in this order:

1. Demo Scope Confirmation

Before building, confirm:

• Workflow title (what it will be called in PS)
• Trigger (manual, Salesforce, webhook, schedule)
• Primary user (who runs this workflow day-to-day)
• Key outcome (what "done" looks like)
• Demo constraints (time limit, live vs. recorded, AI Builder vs. manual)

2. GAP → Demo Mapping

3. Workflow Blueprint

Provide step-by-step, copy-paste ready:

## [Section Header]

### Task 1: [Task Name]
- Assignee: [role or person]
- Due date: [X days from trigger or specific]
- Form fields:
  - [Field name] — [type: text/dropdown/date/file/checkbox]
  - [Field name] — [type]
- Content/instructions: [what the task assignee sees]
- Conditional logic: [if X then Y]
- Automations: [what fires on completion]

### Task 2: [Task Name]
...

4. Integration Points

For each integration needed:

• Tool (Salesforce, Jira, Zapier, API)
• Trigger/action
• Whether PS supports it natively or via Zapier
• Any known gotchas

5. What to Say During the Demo

3–5 talking points that connect workflow steps to the prospect's specific pain from the discovery transcript.

Demo Build Speed Modes

Default to Standard unless the user specifies otherwise.

Common PS Components to Include

• Conditional logic: "If [field] = X then show/hide/assign Y"
• Approvals: Flag any task that should require sign-off
• Due dates: Use relative dates (e.g., "3 days after task X completes")
• Assignees: Separate tasks by role, not individual
• Automations: Slack/email notifications on completion, Salesforce field updates
• Form fields: Use dropdowns for compliance-sensitive fields; free text for context

Example Patterns