Spryple Product Owner handbook
Fact-only. This handbook describes Spryple exactly as its own documentation states it. It contains no assumptions, no inferences and no recommendations, and it does not describe our planned product. Every statement cites its source:
- a breadcrumb such as
Help › For Managers › Payroll Management › Assign Pay Group(the Help Center text);- [SS] §21.x (a Help Center screenshot or app store listing, recorded in spryple-analysis.md §21);
- [WEB] (the vendor marketing site, quoted).
Where the sources are silent, the handbook says "Not documented".
Sources
| Source | Coverage | Evidence |
|---|---|---|
| Help Center (https://spryple.com/help/ = https://help.spryple.com/) | 43 of 43 pages, crawled recursively through the E2E engine on 2026-11-14, unchanged since 2026-10-31 | research/raw/e2e-crawl/, source inventory |
| Help Center screenshots | Partial: Super Admin about 27/42, Mobile about 75, Employee about 60/115, Managers 23/263, LMS 1/19, Admin 1/203 | spryple-analysis.md §21 |
| Vendor site | Home and pricing pages | research/raw/marketing/ |
| App stores | Google Play and App Store listings | §21.1 |
Fourteen ways to understand the product
| # | View | Use it to answer |
|---|---|---|
| 1 | Product overview | What is it, who is it for, how do people get in, what does it cost? |
| 2 | By role | What exactly does each audience see, screen by screen? |
| 3 | By module | For one module, which audience has which screen? |
| 4 | Workflows | What are the steps of each process, who does each step, and what is the status after it? |
| 5 | Configuration | What can an admin configure: every rule, toggle and master? |
| 6 | Data & fields | What does each form capture? |
| 7 | Statuses & lifecycles | What states can each record be in, and what actions are allowed in each? |
| 8 | Reports & dashboards | What can each audience see, filter and export? |
| 9 | Notifications & alerts | Which emails, reminders and alerts exist? |
| 10 | Mobile apps | What do the four apps do, for which roles? |
| 11 | Devices, integrations & dependencies | What external things does it connect to, and which modules depend on which? |
| 12 | Not documented: open questions | What do I still need to ask the vendor or the team? |
| 13 | Documentation defects | Where is the Help Center itself wrong or inconsistent? |
| 14 | Glossary | What does each Spryple term mean, in Spryple's own usage? |
The complete raw inventory of every option, with breadcrumbs, is in the feature tree. Read it alongside views 2 and 3.
Suggested reading order for a new product owner
- Day 1: views 1, 2 and 3. This gives you the shape of the product and who uses which part.
- Day 2: views 4 and 7. This gives you how work flows and what state each record is in.
- Day 3: views 5 and 6. This gives you what is configurable and what data is captured.
- Day 4: views 8, 9, 10 and 11. This covers outputs, communications, mobile, and the links between modules.
- Day 5: views 12, 13 and 14. This gives you your question list for the vendor or team, the known documentation errors, and the vocabulary.
How this handbook differs from the other research documents
| Document | Contains |
|---|---|
| This handbook | Facts only, about Spryple as documented |
| spryple-analysis.md | Facts plus inferences and critique (labelled [Inferred] / [Proposed]) |
| gap-analysis.md | Spryple compared with our planned product (Spyrl) |
| reverse-kt.md | A presenter's teaching guide (includes some interpretation) |