FlareForgeDocs

Onboarding flow

When you first log in to FlareForge, a short onboarding wizard walks you through the minimum setup needed to make the app useful on day one.

Step 1 — Create your organisation

FlareForge is org-scoped. All data, settings, users, and deals live under your organisation. During onboarding you set:

  • Organisation name — Shown in the app header and on exported documents.
  • Primary currency — Default display currency for the ROI Calculator and pipeline KPIs. You can always change this later in Settings → Currency. USD, EUR, and GBP are supported.
  • Timezone — Used for critical date alerts and digest scheduling.

Step 2 — Invite your team (optional)

You can invite colleagues by email immediately after setup. Invited users receive a link to join your organisation. Roles are org-admin or member. See Settings → Team & invites for full details.

Step 3 — Add your first deal

The wizard prompts you to add at least one deal so the dashboard is not empty on first login. You can add real deal data or a test deal — either works.

Required fields:

  • Aircraft / asset — Free text or an MSN from the FlarePath integration.
  • Counterparty — The company you are dealing with.
  • Deal value — Approximate value in your org currency.
  • Stage — Where the deal sits today (Prospect, LOI, Due Diligence, Negotiation, Closing).

You can skip the first deal and add it later from the Deals page. The onboarding wizard remembers where you stopped and will prompt you again on next login if the step is incomplete.

Step 4 — Set a next action

FlareForge's Next Action system is how you ensure no deal goes quiet. During onboarding you set the first next action on your deal: who owns it, when it's due, and a one-line description of what to do.

This action appears immediately on the dashboard under Action Required and drives the stalled-deal alert if it passes its due date without being updated.

Done

Once all steps are complete the wizard closes and you land on the Dashboard. The Getting Started accordion on mobile collapses by default after onboarding.