Solutions
Implementation Org Review Org Monitoring Managed Services
Agents
Discovery Agent Metadata Agent Design Agent Build Agent Test Agent Governance Agent Support Agent
Industry Solutions
Financial Services
Healthcare & Life Sciences
NDIS & Disability Services
Nonprofit
Not-for-Profit
Other Industries
Recruitment & Staffing Real Estate Cosmetic Procedures
Agentforce Claudeforce Blogs Pricing
Discovery Agent

Every workshop planned, recorded and turned into requirements.

Plan discovery with AI from your SOW and the as-is org. A bot joins every call, transcribes it, asks the questions you forgot, and hands Design and Build industry-aware themes, epics and user stories.

Plan a discovery with us See who it helps
Discovery / Acme Corp · NDIS provider
Plan meetings with AI
Inputs
Statement of Work
Acme_NDIS_SOW_v3.pdf · 42 pages
Metadata Agent as-is analysis
Health score 62 · 47 findings
Project background
Brownfield · Health Cloud + Field Service
Industry skill
NDIS SCHADS PACE / PRODA Restrictive practice
Cloud skills
Health Cloud12 skills
Field Service9 skills
Experience Cloud6 skills
Agentforce4 skills
Generated plan · 6 sessions over 3 weeks
Scope-aligned to SOW
01
Participant intake & plan management
Business Process · Wk 1 · Tue
18 questions ready
Agenda
Current intake channels and referral sources
Plan budget visibility for coordinators
Plan management handover points
Pain points in participant onboarding
Questions to ask
?How does a coordinator know a plan is about to run out of funding today?
?Where do referrals arrive from, and who triages them?
?What breaks when a participant changes plan manager mid-plan?
4 attendees2h · Google MeetSOW §3.1 · As-is: 6 findings
02
Rostering, SCHADS & worker compliance
Business Process · Wk 1 · Thu
22 questions ready
03
Claims, PACE & PRODA integration
Data & Integration · Wk 2 · Tue
16 questions ready
04
Incident & restrictive practice reporting
Business Process · Wk 2 · Thu
14 questions ready
05
Current org walkthrough · as-is gaps
Technical · Wk 3 · Tue
20 questions ready
06
Product fitment · Health vs Field Service
Product Fitment · Wk 3 · Thu
12 questions ready
60%
less workshop prep
Plans, agendas and question sets generated from the SOW and as-is org.
100%
of sessions captured
Bot recording with speaker attribution, plus transcript and recording fallbacks.
50%
shorter as-is phase
Themes, epics and user stories from the first session, not the last.
1 click
from insight to backlog
Impact analysis proposes new and updated user stories you approve.
Industry skills

No guessing before you walk in.

Every plan, agenda and question set is powered by an industry skill and the Salesforce clouds you’re deploying. So the first workshop already speaks the customer’s language.

Industry skills · pick a seat
Knows PACE, PRODA and SCHADS before the first question.
Plan budgets, support categories and claim rejection patterns
Rostering, SCHADS award rules and worker compliance
Incident and restrictive-practice reporting obligations
Powered by · Salesforce clouds
Health Cloud
Field Service
Experience Cloud
Agentforce
Sample question the agent asks first
“Walk me through what happens when a PACE claim is rejected. Who sees it, and how long before the participant is affected?”
What it does

From SOW to structured requirements in four moves.

01
Plan
Plan Meetings with AI reads the SOW, project context and Metadata Agent as-is analysis to propose a scope-aligned schedule with agendas and questions.
02
Capture
The bot joins the live meeting, records and transcribes with speaker attribution. Documents, notes and recordings join the same session record.
03
Structure
Generate and process questions into insights; apply the discovery template to produce themes, epics and user stories, then ask the Process Agent for flows, ER and architecture diagrams.
04
Evolve
Link to Design or Build. Impact analysis turns new findings into proposed story changes you accept or reject; regeneration keeps artifacts in sync.
See it in action

One session, end to end.

BH
Brian Hughes
hughes.brian@company.com
Agents
Discovery Agent
Metadata Agent
Design Agent
Build Agent
Test Agent
Support Agent
Claims Management Discovery Workshop
Business Process Discovery · Tue 10:00 · Google Meet
Bot recording
Live transcript
Sarah · Ops LeadAnything over five thousand goes to a manager. We aim for 48 hours but honestly it slips.10:42
Brian · GetGenIs the 48 hours a policy or a target? Who tracks it today?10:43
Sarah · Ops LeadTarget. It lives in a spreadsheet. Nobody trusts it.10:43
Dev · FinanceAnd PACE rejections come back by email. We find out days later.10:45
Ask nextLive assist
?What happens to the participant while a claim sits rejected?
?Who should own the 48h SLA once it lives in Salesforce?
?Which PACE rejection reasons are most common?
Insights
14 questions · answered from transcript + 3 documents
Process with AI
What is the approval threshold and SLA for referrals?
Referrals above $5k require manager approval within a 48-hour target; below $5k auto-approve. SLA currently tracked in a spreadsheet.
Transcript 10:42Validated
How are PACE claim rejections surfaced today?
Via email from the finance inbox, typically 2–3 days after rejection. No visibility for the support coordinator.
Transcript 10:45Validated
Which award rules affect rostering?
SCHADS Level 2–4 with broken-shift and sleepover allowances; current roster tool does not validate against them.
Roster_Rules.xlsxValidated
What is out of scope for phase 1?
Payroll integration and participant portal are explicitly excluded in the SOW; both flagged as phase 2.
SOW §4.2Validated
Themes, epics & user stories
Synthesised from the Business Process Discovery template
Download
Overview
Key action items
Risks & dependencies
Current state processes
User stories
Themes & epics
Integration requirements
User stories · Epic: Claims & funding
5 of 14 · grounded in transcript
US-01
As a support coordinator, I am notified within 1 hour when a PACE claim is rejected.
Today rejections arrive by email 2 to 3 days later. Source: session 03, 10:45.
US-02
As an ops manager, I see the 48h approval SLA on every referral above $5k.
Below $5k auto-approves. Replaces the spreadsheet tracker. Source: session 01, 10:42.
US-03
As a rostering lead, my roster is validated against SCHADS allowances before I publish.
Rules supplied in Roster_Rules.xlsx. Out of scope: payroll integration (phase 2).
US-04
As a coordinator, I am alerted when a participant has 20% of plan budget remaining.
Requested by Finance to reduce overspend at plan end. Source: session 02.
US-05
As a practitioner, I can log a restrictive-practice incident with all NDIS Commission fields required.
Current form misses two required fields. Source: Incident_Policy.pdf, session 04.
Process map · Claims intake to approval
Generated by the Process Agent from the full session context
Flow chart
Claim lodged Eligibility check > $5k? Auto-approve Manager review · SLA 48h
2 decision points1 SLA capturedValidated with client
Capture everything

The bot is in the room. Your consultants can listen.

The bot joins the live meeting and transcribes it with speaker attribution. While you talk, the assistant suggests the next question, flags decisions and captures actions. Everything lands in one session record.

Scheduled sessions
Bot joins automatically and records.
Ad-hoc meetings
One click to bring the bot in.
Transcripts
Paste any transcript; processed the same way.
Audio & video uploads
MP3, WAV or recordings become searchable text.
Documents & notes
SOWs, decks, spreadsheets and notes join the context.
Claims Management Discovery Workshop
Business Process Discovery · Live
Bot recording
Live transcript
Sarah · Ops LeadAnything over five thousand goes to a manager. We aim for 48 hours but honestly it slips.10:42
Brian · GetGenIs the 48 hours a policy or a target? Who tracks it today?10:43
Sarah · Ops LeadTarget. It lives in a spreadsheet. Nobody trusts it.10:43
Dev · FinanceAnd PACE rejections come back by email. We find out days later.10:45
Discovery assistantContext: 3 sessions · 5 docs
What questions should I ask next? Summarize the meeting What are the key action items? Who attended?
What did the client decide about the referral approval SLA?
48 hours for referrals over $5k, confirmed by Sarah (Ops Lead) at 10:42. Below $5k auto-approves. Two people flagged the threshold should be reviewed after go-live. I’ve added it as an open action.
Who it helps

Built for the people who run the room.

Four roles, one workspace. Pick a seat.

Consultant / BA
80%
less time planning, note-taking and writing up
Walk into discovery already knowing the org and the industry. No guesswork.
AI-planned workshop schedule from the SOW and as-is analysis
Industry-specific question sets ready before the call
Themes, epics and user stories generated from the discovery template, not from memory
Impact analysis

Discovery keeps changing the backlog. On purpose.

Link the session to a Design or Build project. Every new insight is analysed against existing themes, epics and stories; you approve the changes, the backlog updates.

New storyClaims & funding
As a support coordinator, I am notified within 1 hour when a PACE claim is rejected.
Discovered in session 03. Rejections currently surface by email 2–3 days later.
AcceptReject
UpdateReferral management
Referral approval SLA is 48h for referrals over $5k, tracked on the record.
Existing story assumed a flat 24h SLA; corrected from transcript at 10:42.
AcceptReject
New storyRostering
Roster validates against SCHADS broken-shift and sleepover allowances before publish.
Roster_Rules.xlsx uploaded in session 02; not represented in backlog.
AcceptReject
Plan your next discovery

Walk into your next discovery already knowing the answers.

Send us one SOW. We plan the workshops, the bot joins the calls, and your consultants walk out with themes, epics and user stories, process maps and a backlog impact report. No guesswork, no lost notes.

Book a discovery planning call
What you get
AI-planned workshop schedule from your SOW and as-is org
Industry question sets before the first call
Bot-recorded sessions with speaker-attributed transcripts
Themes, epics and user stories, plus process maps and diagrams
Backlog impact analysis you approve before it lands