Skip to main content

​
1. document purpose

This document is the current product business verification test (BVT) for Zeus. It exists to answer three operational questions:
  1. Which product features are available to use right now?
  2. Which of those features are intended for end users versus admins?
  3. What should we verify before saying the product is ready for internal use, demos, or pilot validation?
This is a business-facing document. It focuses on user-visible behavior and business readiness, not engineering implementation.

​
2. current feature inventory

The feature list below reflects the current product surface that is visible in the web app and its supporting flows.

​
2.1 end-user features available now

AreaAvailable now
AuthenticationUser login, registration, logout, and session-based access to the application
DashboardCompany snapshot, linked asset count, self-managed asset count, recent transactions, AI suggestions, and bank-link launcher
ProfileEditable company/profile details and current banking profile status
AssetsView assets, create self-managed assets, edit self-managed assets, delete self-managed assets, and review synced versus manual asset types
TransactionsView transactions, create manual transactions, edit manual transactions, delete manual transactions, and review synced versus self-added records
GoalsView goals, create a goal, review goal details, and manage goal-oriented planning data
Plans MVPCreate a monthly plan, activate a plan, view safe-to-spend, log progress, set reminders, accept a rebalance, and review completed months
NotificationsView inbox notifications, mark items as read, open CTA links, and review AI suggestions surfaced through inbox items
AI suggestionsReceive dashboard and inbox suggestions, dismiss them, and mark them complete
Assistant chatUse the assistant to inspect data, create/update/delete manual transactions, create/update/delete manual assets, and create goal-planning flows inside chat
Bill SplitterCreate a split, browse split history, open a split detail, and use the shared split flow

​
2.2 admin and operator features available now

AreaAvailable now
BankHub settingsAdmin-only bank and sandbox settings page
Sandbox operationsGenerate and test sandbox transactions through admin settings flows
AI insights settingsTrigger AI analysis for a user and optionally push an inbox nudge
AI suggestion controlsReview recent suggestion activity and tune AI suggestion behavior
Admin chat managerReview user chat threads and send an admin-triggered reply into a user conversation

​
3. current AI assistant chat capabilities

The assistant is not only a read-only explainer. It can currently execute real product actions inside the user’s account.

​
Available assistant capabilities now

CapabilityWhat the assistant can do
Transaction inspectionList and summarize recent transactions
Asset inspectionList and summarize assets
Goal and plan inspectionList goals and planning-related records already available to the user
Suggestion inspectionSurface active AI suggestions and next-best actions
Manual transaction CRUDCreate, update, and delete self-added transactions
Self-managed asset CRUDCreate, update, and delete self-managed assets
Goal creationTurn future-goal intent into an in-chat planning flow and create a goal from the structured result
Structured collectionUse quick forms, smart actions, and guided prompts instead of relying only on free-text replies
Conversation historyPreserve chat thread history and continue work within the same thread

​
Important assistant boundaries

The assistant should currently be treated as safe for:
  • inspecting user data
  • creating and editing manual records
  • creating planning or goal records through supported flows
It should not be treated as a substitute for:
  • browser push notifications
  • variable-income planning
  • multi-goal plan prioritization
  • unrestricted edits to synced records

​
4. current business verification scope

The product is considered ready for internal use and structured demos when the following feature families all pass:
  • account access and session handling
  • dashboard loading and bank-link launching
  • assets CRUD
  • transactions CRUD
  • goals creation and review
  • plans MVP flows
  • notifications and AI suggestions
  • assistant chat action flows
  • bill splitter core flows
  • admin-only controls

​
5. BVT scenarios

​
BVT-1 authentication and access

Purpose Verify that a user can access the application with a valid account. Steps
  1. Register or log in with a valid account.
  2. Open the main application shell.
  3. Navigate between primary sections.
  4. Log out.
Expected result
  • The user can enter the authenticated app.
  • The sidebar and primary sections load.
  • Logging out ends the authenticated session.

​
BVT-2 dashboard and account connection

Purpose Verify that the dashboard acts as the main overview surface. Steps
  1. Open Dashboard.
  2. Review the company snapshot cards.
  3. Review recent transactions and asset snapshot.
  4. Launch the bank linking flow if available in the environment.
Expected result
  • Dashboard loads without hidden setup steps.
  • Snapshot metrics appear.
  • Asset and transaction previews appear when data exists.
  • The bank-link launcher is available from the dashboard.

​
BVT-3 profile and editable identity details

Purpose Verify that users can review and edit profile-facing company details. Steps
  1. Open Profile.
  2. Review status and transfer metrics.
  3. Edit one visible profile/company field.
  4. Save the changes.
Expected result
  • Profile details load.
  • Editable fields can be changed and saved.
  • Updated values persist on reload.

​
BVT-4 assets CRUD

Purpose Verify that self-managed assets can be managed directly in the product. Steps
  1. Open Assets.
  2. Create a self-managed asset.
  3. Edit that asset.
  4. Delete that asset.
  5. Confirm synced assets, if any, are still visible separately from manual ones.
Expected result
  • A manual asset can be created, updated, and deleted.
  • The asset list clearly distinguishes synced assets from manual assets.
  • The asset appears in dashboard and assistant contexts after creation.

​
BVT-5 transactions CRUD

Purpose Verify that manual transactions can be managed without damaging synced data. Steps
  1. Open Transactions.
  2. Create a manual transaction.
  3. Edit that manual transaction.
  4. Delete that manual transaction.
  5. Review any synced transactions still shown in the feed.
Expected result
  • A manual transaction can be created, updated, and deleted.
  • Synced transactions remain visible but non-editable.
  • The transaction feed reflects the changes immediately.

​
BVT-6 goals flow

Purpose Verify that users can create and review a financial goal. Steps
  1. Open Goals.
  2. Create a new goal.
  3. Open the goal detail view.
  4. Review the planning-oriented goal tabs and summary.
Expected result
  • A goal can be created successfully.
  • The goal appears in the list view.
  • Goal detail view opens and shows planning context.

​
BVT-7 plans MVP flow

Purpose Verify the currently available planning loop. Steps
  1. Create and activate a monthly plan.
  2. Review the active dashboard.
  3. Log progress.
  4. Enable a daily reminder.
  5. Trigger a warning.
  6. Accept the recommended rebalance.
  7. Open a completed historical month if available.
Expected result
  • The planning flow works from setup through intervention and review.
  • Reminder, warning, rebalance, and month-end reflection all behave credibly.
Reference: Plans MVP BVT

​
BVT-8 notifications and AI suggestions

Purpose Verify that Zeus can surface useful nudges across the dashboard and inbox. Steps
  1. Open Notifications.
  2. Review unread items.
  3. Open one CTA from a notification.
  4. Mark one item as read.
  5. Dismiss or complete one AI suggestion if present.
Expected result
  • Notifications load with unread state.
  • CTA links open the intended destination.
  • Suggestions can be dismissed or completed.
  • Read state updates correctly.

​
BVT-9 assistant chat inspection flow

Purpose Verify that the assistant can inspect user data in natural language. Steps
  1. Open Chat.
  2. Ask the assistant to show recent transactions.
  3. Ask the assistant to list assets.
  4. Ask the assistant to review active goals or suggestions.
Expected result
  • The assistant responds with relevant structured or textual results.
  • Returned information matches the user’s current account state.
  • The conversation stays within the same chat thread.

​
BVT-10 assistant chat action flow

Purpose Verify that the assistant can complete supported CRUD actions. Steps
  1. Ask the assistant to create a manual transaction.
  2. Ask it to update that transaction.
  3. Ask it to delete that transaction.
  4. Ask it to create a self-managed asset.
  5. Ask it to update that asset.
  6. Ask it to delete that asset.
  7. Ask it to help plan a future goal such as buying a house.
Expected result
  • The assistant completes supported manual transaction actions.
  • The assistant completes supported self-managed asset actions.
  • The assistant can start a structured in-chat planning flow for a future goal.
  • The resulting records match what appears in the corresponding UI surfaces.

​
BVT-11 bill splitter core flow

Purpose Verify the collaborative split-management surface. Steps
  1. Open Bill Splitter.
  2. Create a new split.
  3. Search for the created split.
  4. Open the split detail page.
  5. Open the shared view if available.
Expected result
  • A split can be created and found from the list.
  • Split detail page loads.
  • Shared-view flow is reachable for collaboration or review.

​
BVT-12 admin settings and operator controls

Purpose Verify the current admin-only product controls. Steps
  1. Log in as an admin.
  2. Open BankHub settings.
  3. Review sandbox controls.
  4. Open AI Insights Settings.
  5. Trigger an AI analysis for a user.
  6. Open Admin chat controls and review a user thread.
Expected result
  • Admin-only settings pages are accessible to admins.
  • Sandbox and AI controls render successfully.
  • Admin-triggered AI analysis can run.
  • Admin chat thread review is available.

​
6. pass checklist by feature family

Feature familyPass condition
AuthUsers can enter and leave the app normally
DashboardOverview data and navigation entry points load reliably
ProfileEditable profile/company details persist
AssetsManual assets support create, edit, delete, and list
TransactionsManual transactions support create, edit, delete, and list
GoalsA goal can be created and reopened
PlansThe monthly planning loop works end-to-end
NotificationsInbox items load, open, and change read state
AI suggestionsSuggestions can be reviewed, dismissed, and completed
Assistant chatSupported inspection and action flows complete successfully
Bill splitterA bill can be created and reopened
Admin toolsAdmin-only pages and trigger flows are usable by operators

​
7. features we should actively start using now

The following surfaces are ready to use immediately for internal testing, demos, and pilot-style workflows:
  • Assets manual CRUD
  • Transactions manual CRUD
  • Goal creation and review
  • Plans MVP including reminders, rebalance, and month-end review
  • Notifications inbox and AI suggestions
  • Assistant chat for supported inspection and manual CRUD tasks
  • Dashboard overview and bank-link launch entry points
  • Admin AI insight trigger and admin chat review

​
8. current caution list

The following are not reasons to block use, but they should be treated carefully during demos and pilot planning:
  • Browser push notifications are not part of the current reminder model
  • Some planning capabilities remain MVP-scoped and intentionally narrow
  • Synced records should still be treated as protected compared with self-managed records
  • Admin/operator tooling should be demonstrated only with an admin account

​
9. definition of pass

The current Zeus product surface passes business verification when:
  • each core feature family in section 6 passes
  • the assistant can successfully complete at least one supported CRUD workflow
  • end users can move between dashboard, assets, transactions, goals, plans, notifications, and chat without hidden setup steps
  • admins can reach the current operator controls and run the intended management flows
  • the product can be demoed using real visible flows instead of mocked-only behavior