Your First Week on Rexfin: What Actually Happens

Most finance software onboarding is a kickoff call, a slide deck, and then radio silence until something breaks. Rexfin’s first week is built to be smaller than that and more honest about it: a short, role-specific tour instead of a training program, and a support model that tells you upfront what it can and cannot promise at this stage of the company.

Day one: an account, not a demo

Signup is invite-only. Someone on your team creates the workspace and invites the rest of you; there is no open self-registration where a stranger could land in your data. Sessions are checked server-side on every request, not just at the login screen, so if someone leaves the team or a session needs to be killed, it actually stops working immediately rather than staying valid until a cookie expires. Once you are in, what you see next depends on who you are: Rexfin does not hand a viewer the same first screen as an owner.

The tour matches the role, not a generic checklist

Rexfin’s first-run tour is role-based, and each role gets a genuinely different path. An owner is walked through upload, review, budget-vs-actuals, and generating a board pack. An editor sees upload, review, budget-vs-actuals, and building scenarios. A viewer is walked through the dashboard, statements, and asking questions, deliberately never pointed at upload, because a viewer cannot upload and showing them a button they cannot use is not a tour, it is a tease. If your team hasn’t settled who holds which role yet, the permissions model is worth reading before your first invite goes out, not after.

The tour itself is intentionally unambitious about how much space it takes. It is a single fixed card in a corner of the screen: no full-page overlay, no blocking backdrop, no trapped focus that stops you from clicking around it if you’d rather explore on your own. Escape dismisses it. Once you skip or finish it, it does not come back to nag you on your next login.

Alongside the tour, a command palette (the usual keyboard shortcut opens it) surfaces the actions available to your specific role first (upload for editors and owners, inviting a teammate for owners only), plus full navigation and your recently used items. It is a faster way to find your footing than clicking through every menu once you already know roughly what you’re looking for.

What happens when something is unclear

The first week is when most questions get asked, and Rexfin sorts them into one of four buckets before drafting a reply: a production-impacting issue, a wrong or suspicious cited number, an ordinary how-to question, or a feature request. That second bucket is treated as categorically different from the first: a wrong number is a trust problem, not a routine glitch, and it gets its own response path rather than being folded into a generic incident queue.

At this stage, support is not a ticketing platform with tiered queues; it is a small team responding directly, sized honestly to what that team can actually back. On the Pilot tier specifically, Rexfin does not publish uptime commitments it cannot yet measure reliably: same-day response for ordinary issues, a best-effort under-four-hours for anything blocking a close, but no formal SLA language until the metrics behind it are solid enough to stand behind. If you are based in the GCC, business hours are set to your actual clock: Sunday through Thursday, adjusted for Gulf Standard or Arabia Standard time depending on where you are, with Ramadan hours and local holidays honored rather than assumed away. If a founder or a small team is traveling, active customers get advance notice rather than finding out from a slower response.

The point of the first week

None of this is designed to impress you with scale Rexfin doesn’t have. It is designed so that what you see in week one (a role that fits your job, a support answer you can actually hold someone to, honest limits stated plainly) is the same thing you get in month six. If you’re evaluating Rexfin as a pilot rather than a full rollout, how pricing works for a pilot and the support model in full are the two pages worth reading next. For the rest of what’s under the hood, see the pillar hub.