01
Three more sessions
Different jobs.
Same loop.
An ops manager building an internal portal. An HR generalist clearing the May leave batch. A sales rep working through stale opportunities. Each opens Neo, asks in plain language, sees the plan, approves before any change lands.
FIG.02 OPS, Build a partner portal
Internal portal for partners and deals
You ask for an internal portal: partners log in, submit deals, approvers route them. Neo drafts the records, pages, roles, and an approval flow on a draft copy of the workspace, and waits for you to apply.
-
4 record types: Partners, Deals, Approvals, History
-
4 pages: Portal, Deal queue, Deal detail, Founder dashboard
-
1 approval flow: Submit / Review / Approve / Notify
-
3 roles: Founder, Partner, Reviewer
-
Lands on a draft copy of the workspace, apply when ready
FIG.03 HR, May leave batch
Clear the batch without dropping team coverage
Seventeen leave requests have been waiting for over three days. You ask Neo to clear the batch under one rule: don't drop coverage below 80% in any team. Neo approves what passes, sets the rest aside for review.
-
14 requests pass the coverage rule, staged for approval
-
3 requests would drop coverage below 80%, set aside for review
-
Coverage stays at or above 80% in every team
-
Nothing approved until you sign off on the batch
FIG.04 SALES, Stale pipeline triage
Re-engage 47 stale opportunities, owner by owner
Forty-seven opportunities haven't moved in 30 days. You ask Neo to triage them and draft re-engagement notes per owner. Neo scores, groups, drafts, and waits for you before sending anything to the owners for their review.
-
47 deals scored and grouped by owner
-
47 drafts written, one per deal
-
6 owners receive their drafts for individual review
-
Nothing goes out until each owner approves their batch