42 features, grouped by what they actually do for your firm. Select any card to open the detail below its row, or jump straight to the section you care about.
Compare the usual workaround
| Need | Spreadsheets | Asana / Monday | StellaJourney | |
|---|---|---|---|---|
| Client requests | Buried in long threads | Tracked by manual updates | Built for internal teams, with clients added later | Collected in structured journeys |
| Status visibility | Depends on who replies | Stale unless someone maintains it | Dashboards designed for staff, not clients | Shared, current and client-readable |
| Repeatable delivery | Copied from last time | Template tabs drift quickly | Reusable, but not shaped around the client relationship | Templates, tasks and approvals built in |
| Where it fits | Before, during and after the work | Before, during and after the work | Internal team workflow | After the sale, from onboarding through delivery |
Replace scattered emails with a workspace where progress, context and conversation live together.
Staff can create a journey for any client, drop in an opening message, prefill structured context from the client record, and hand it straight to the next owner. The journey starts with the right data attached instead of arriving as an empty shell someone has to chase down.
Each journey gets a dedicated workspace where everything that matters lives in one place: the request details, submitted intake fields, uploaded files, the discussion thread, every linked task, and the full lifecycle history. No more piecing context together from email, chat and a spreadsheet at 9pm.
Each journey has a real conversation thread, not a comment box. Rich text, @mentions and notifications mean the back-and-forth that used to live in email is captured against the work it actually relates to: searchable, attributable and visible to everyone who joins later.
Build workflows that match how you run a piece of work: name the statuses, define which transitions are allowed, set defaults, and choose what each status is called when a client sees it. Permissions decide who can move work where, so the process you designed actually gets followed.
Real client work doesn’t move forward in a straight line. Staff can request approval, cancel a journey, or reopen something that was finished, with a reason captured every time the status moves. Months later, you can still answer “why did this come back?” without guessing.
Tag journeys however your team thinks about work: by service line, urgency, source, or anything else you need. Bulk tag operations and combinable filters mean you can answer “show me everything tax-related, mine, still open” in a couple of clicks.
Collect what you need in the right format: todos, files and structured forms you can reuse.
Not every task is the same shape. Use a simple todo when you just need someone to do a thing, a file request when you need a document back, or a form-based task when you need structured fields filled out. Clients see exactly what they’re being asked to provide, and you get it back in a useful format.
Staff get one screen that pulls every task across every journey into a single inbox, grouped, filterable, with due dates surfaced and priority ordering applied. Even staff juggling fifty active journeys can answer “what should I work on next?” quickly.
A task isn’t just a checkbox. Each task gets its own focused page with the instructions to follow, the submission area, a comments thread, attached files, full lifecycle history, and clear guidance on what happens next. Clients know what’s being asked of them, and staff keep the audit trail.
Build the bundle of tasks you always send for a kickoff, an onboarding, or an annual review once. Then apply the whole bundle to a journey at setup, or any time later when scope grows. Every staff member starts from the same baseline without having to remember each step.
Codify the way you deliver a service into a journey template: which workflow it runs on, what intake fields the client should fill out, how it’s ordered, and what tasks it starts with. Newer staff can launch the same baseline process without copying from an old engagement.
Build the structured fields a journey or form actually needs: text, textarea, checkbox, select, date, URL, file upload, number and rich text. The data you’ve always collected by email finally lands as structured, searchable fields.
Define a form once, such as an intake questionnaire, risk profile, or KYC checklist, and reuse it as a structured task on any journey that needs it. Clients fill it out inside the portal; you get clean, structured answers; the form lives in a library you can update centrally.
See what's stuck, what's stale, and what's about to land without opening ten tabs.
A live, status-bucketed view of every journey across your account: how many are open, in progress, awaiting client, awaiting approval, done. The dashboard is the first thing your team sees when they sign in, and it tells them where attention is needed before they’ve even had coffee.
The dashboard surfaces journeys that have gone quiet, are unassigned, or have been sitting in the same status too long. The work that needs attention becomes visible before someone has to ask for an update.
Weekly charts show how journey volume is moving over time: opened, closed and in flight. You can see seasonality, growth, and the months when the team is carrying more work than usual.
A single spotlight layer lets staff search records, jump to any page in the app, or start create actions without leaving the keyboard. The record someone needs is easier to find while the client is still on the phone.
A guided checklist walks new accounts through the setup that matters: your logo, workflows, templates and first invitations. Restart it any time you onboard a new admin or want to revisit the foundations.
Give every staff member the right access, and keep client ownership clear.
Owners and admins manage the entire staff lifecycle in-app: invite new members, assign them a staff role, resend invites that got buried, archive people who’ve moved on, and remove memberships cleanly. No CSV gymnastics, no support tickets.
Create your own staff roles and grant or revoke fine-grained permissions per role, while the built-in system roles stay safe and untouched. Give each team member the access they need for their work, and keep sensitive areas limited.
Every client lives in a central directory you can search, filter, archive, restore and bulk-manage. Each client also has its own profile with core details, related journeys, users and activity history, so when a client calls, you have the full relationship in front of you.
Bring your existing client list across without retyping. Upload a CSV or XLSX, map the columns to fields, preview exactly what will be created, and only then commit. The migration moment most tools make terrible becomes a five-minute job.
Every client has a named manager. Assign them one at a time or in bulk, reassign when responsibilities shift, and never have a “I thought you were looking after them” moment again.
Give the right people at each client portal access, resend invites, archive or restore access as relationships change, remove memberships cleanly, and (when support requires it) impersonate an active client user to see exactly what they’re seeing.
A shared library of tags with colour coding stops every staff member inventing their own version of the same label. Quick-add lets new tags appear when you need them, but the library keeps things tidy.
A portal that shows clients what they need, when they need it.
Clients receive an invitation, activate access as either a new account or an existing one they already use elsewhere, and land in the correct portal automatically. No “wait, which login?” emails on day one.
When a client logs in they see their own work, not yours: active journeys grouped by status, pending task counts, and clear paths into anything that needs them.
Clients get a focused list of their own open requests and a prioritised view of their pending tasks across journeys, complete with due dates and one-click links into the right place. They never see anyone else’s work, and they do not have to dig for their own.
Clients can start a new journey themselves with a title and an opening message, never exposed to internal workflow choices, assignees or status mechanics. They feel in control; you keep the structure that makes the work runnable.
When a journey is waiting on a client to sign off, they can approve it or send it back with feedback in two clicks. The approval loop, including the reason for any revisions, is captured against the journey instead of getting lost in someone’s inbox.
Whatever you’ve asked the client to do, whether it is a todo, a file upload, or a structured form, they complete it inside the portal. Each task page surfaces the instructions, due date, submission area, discussion thread and journey context so they can finish the work without bouncing back to email.
Clients manage their own avatar, password and notification preferences without staff involvement. Your team gets fewer routine account requests, and clients stay in control of their own access.
Clients see a focused portal shaped around their work: what is due, what is done, and where to respond. The same workflow that powers a hundred firms stays out of the way so each client can get on with their part.
API tokens, webhooks, exports and billing controls for when your work gets more connected.
Generate API tokens scoped to the permissions an integration needs, with an optional expiry so they don’t outlive their usefulness. Connect the portal to your other tools without giving every integration full access.
Register webhook endpoints, choose which events you care about, send test deliveries, rotate signing secrets, and review every delivery, successful or failed, from the dashboard. Disable an endpoint cleanly when something downstream breaks without losing the audit history.
Queue an export from the client or journey area, get notified when the archive is ready, download it, and refer to the export history any time you need to prove what was sent and when.
Plan status, plan changes, billing email, Stripe billing access and invoice history all live inside the app. Finance teams can find the billing record without asking someone else to dig it out.
Each user controls which notifications they receive in-app and by email, with options scoped to what their role actually does. Staff can stay close to every update; clients get the prompts that help them act.
Users register and sign in with email and password. Clients follow their invitation into the right portal without having to understand your internal setup.
Users with active memberships in more than one account can switch between portals from a single in-app menu. This helps agencies, multi-brand firms and clients who work with more than one advisor keep the right portal in reach.
Owners can restart onboarding, transfer the entire account to a new owner, or permanently delete the account. Destructive controls sit behind the right permission, with confirmation steps that match the impact.
Set up your first journey, invite a client, and see how it feels.