Getting Started

This guide explains how to start using GetProa with the right expectations and flow.

Before You Begin

GetProa works best when you treat it as a decision system, not a collection of isolated tools.

Prepare these inputs first:

• Your current portfolio context (wallets, risk horizon, priorities)
• Your monthly cashflow baseline
• A clear question you want to answer this week

Access and Permissions

Some modules are public, while others require authentication and specific access groups.

If a module is not available in your account, that is expected behavior based on access policy.

First Session Playbook

Step 1: Start with a concrete question

Examples:

• "Am I over-allocating capital in one bucket?"
• "Where is monthly execution breaking?"
• "What evidence do I need before changing direction?"

Step 2: Use one module with intent

• Use Investments for portfolio structure decisions
• Use Budget for monthly execution discipline
• Use Assistant to ask grounded questions across enabled Proa data
• Use Reports to review prior decision context

Step 3: Enable Proa AI only when you want grounded chat

If you use Assistant:

1. Open Settings in the app
2. Enable Proa AI
3. Choose whether Assistant may read Budget, Investments, Reports, or a smaller set
4. Ask one review question at a time

Examples:

• "Review Budget and Investments together before I make a decision."
• "What should I inspect before closing this month?"
• "Which report should I revisit before changing allocation?"

Step 4: Save decision artifacts

When available, preserve outputs in Reports so your next cycle starts from evidence, not memory.

Behavioral Rules That Keep Results Stable

• Keep one main objective per cycle
• Do not optimize every variable at once
• Prefer repeatable routines over reactive changes
• Revisit previous reports before changing direction

Common Setup Mistakes

1. Starting in a restricted module without required access
2. Using tools without a defined decision question
3. Treating weekly noise as structural signal
4. Ignoring report history when planning next actions
5. Asking Assistant to make financial decisions instead of reviewing your data

Where to Go Next

• Build structure in Investments
• Tighten monthly process in Budget
• Ask grounded questions in Assistant
• Revisit previous context in Reports
• Review common concerns in FAQ