The experience
From a flagged household to a client-approved rebalance, in four minutes.
An advisor with 118 households does not need another dashboard. She needs to know which four households need her today, and why, before a nine o'clock review. This demo opens on that answer — $312.4M of book assets, four prioritised households, each with the signal, the sentence and the number behind it — and then does the thing most tools stop short of: it turns one of those findings into a proposal, sends it, and brings back the client's approval with a timestamp.
Two halves of one product, on one dataset. The advisor workspace is where the work happens: dashboard, client book, household and account analysis, book of business, report library, week calendar. The client app is what the household sees: portfolio, the full picture including held-away assets, goals, documents, notifications. Seventeen screens, in three display versions, in light and dark, with the flow's state surviving every switch.
It was built by extending the client's own working prototype rather than reinterpreting it, so the analysis on screen is the product's own — its signal taxonomy, its drift arithmetic, its 5% single-name band, its rule that performance is never shown without a benchmark. The round trip on top of that analysis is ours, and it is labelled as ours on the screen where it happens, in the demo's About panel, and in every section of this page.
Watch analysis become an action a client approves
Read the workspace the way one of your advisors would
Leave knowing which integrations a pilot actually needs
Who this is for
The analysis is the solved part. The action is not.
Portfolio analytics, reporting and CRM can all be bought. What no vendor sells is the moment between a finding and a client saying yes — and that gap is where the advisor's afternoon goes.
Mid-size RIAs and wealth firms
Fifteen to a hundred and fifty advisors, running four to six unintegrated tools. Meeting preparation is manual and repeated per household, drift and concentration get noticed late, and the client sees a thinner picture than the advisor does. The book screen in this demo — 118 households, 264 accounts, $312.4M on one advisor — is the shape of book that belongs to a firm this size.
Multi-family offices
Five to thirty professionals, where held-away and self-reported assets matter more than book growth. The client's full picture already carries a linked read-only 401(k), two banks and self-reported property equity beside the managed portfolio, because the source product already modelled them.
Heads of technology weighing a build
You will be asked what it takes to connect custodial feeds, aggregation, billing and documents, and who owns the integration work. Every simulated area on this page is named, together with what it stands in for — so the estimate starts from a list rather than from a screenshot.
This positioning is a hypothesis derived from the product's own numbers and screen inventory, not a measured or client-confirmed segment. No market size, share, benchmark, competitor comparison, customer count or testimonial appears anywhere on this page, because none of them has been verified. The source document's own meeting-preparation figure is a vendor statement with no measurement behind it, so it is not here either.
The moment that sells it
Every tool in this category finds the problem. Watch this one act on it.
The household is flagged for concentration: one semiconductor position is 8.9% of a $4.86M managed portfolio, against the firm's 5% band, and the equity sleeve sits 6.4 points over target. Press Build rebalance proposal, then Send to client for approval — and stop talking for two seconds.
The allocation bars travel, and every target marker is met
Equities go from 68.4% to 64.5%, fixed income from 18.2% to 22.1%, each bar arriving at the marker it was missing. Total drift across the four sleeves falls from 13.2 points to 5.4. The proof is not a toast — it is the numbers moving on the screen you were already reading.
The finding card rewrites itself into a status
The dark position-check card stops describing a problem and starts reporting a decision: proposal PRP-OKA-0471, the 5% band, $189,435 released into fixed income, sent at 9:14 AM. The household's flag flips from Concentration to Rebalance sent, and the client's notification slides in, labelled In demo.
The band is a control, not a constant
Move it between 5%, 6% and 8% before you send, and the trade tickets, the released cash and the tax illustration all recalculate from the firm's own rule: 219 shares at $865 releasing $189,435 at the 5% band, 51 shares releasing $44,115 at 8%. The tax estimate moves with it, from $21,350 down to $4,972.
Ninety seconds later the same object comes back. Switch to the client, read one number before and one after and what it costs, tick the acknowledgement, approve — and back in the workspace the task has ticked itself, Needs attention reads three instead of four, the household reads On track, and the activity ledger carries Rebalance approved by client with the approval time. That round trip is what does not exist in the product today, and it carries a Proposed by Itexus label everywhere it appears. Under prefers-reduced-motion the same values change without the travel, and the flow still completes.
Suggested walkthrough
A guided path through the strongest moments.
Four minutes for the main story, about ten with the report and calendar flows. There is nothing to sign up for: the sign-in screen is pre-filled and the code arrives inside the demo. Press Reset demo before a showing to return to the clean starting state.
Sign in
The work email and password are already filled in. Press Sign in; a text message slides in with a six-digit code. Press Use this code, then Verify.
You land as Mira Solano, senior advisor. The message is drawn inside the demo and the code is derived from the seed, so it is the same on every run — nothing is sent anywhere.Read the dashboard, not the whole screen
$312.4M of book assets on the deep card with its sparkline, an insight line, and four households already prioritised in Needs attention.
Each card carries its signal, the sentence explaining it and the number behind it. The system has already decided who needs her today, which is the part a dense workspace has to earn in the first five seconds.Open Okafor Family Trust · Concentration
The household detail loads through the product's own skeleton state. Read the dark position-check card and the allocation panel beside it.
A single semiconductor name at 8.9% against a 5% house limit, the equity sleeve 6.4 points over target and rendered red, performance beside its benchmark over five periods, then holdings, accounts and the activity ledger. All of it computed by the product itself.Build the proposal and send it
Press Build rebalance proposal. Move the band between 5%, 6% and 8% and let the numbers move. Then press Send to client for approval.
The moment the demo exists for: the bars travel to their projected positions, the flag flips to Rebalance sent, $189,435 is stated as released into fixed income, and the client's notification arrives. This part is labelled Proposed by Itexus, because it is not in the product today.Approve as the client, then come back
Switch Viewing as to Client, open the proposal, read it in plain language, tick the acknowledgement and press Approve. Then switch back to Advisor.
One number before, one after, what it costs, and nothing else. Back in the workspace: the task is ticked, Needs attention is three not four, the household reads On track, the allocation sits at target, and the activity ledger carries the approval with its timestamp.Beyond the happy path
Scenarios: the situations the walkthrough does not reach.
The demo carries a Scenarios control in its top bar. It is a demo instrument rather than part of the product: each entry loads a different starting state — an edge case, a failure, a rule firing — and the screens recompute from it. The guided path shows the product working. The scenarios show what it does when the situation is not the ideal one.
One button, at any point in the demo.
Pick a scenario and the demo re-seeds itself and opens on the screen where that situation shows. Nothing has to be set up beforehand, and you can go back to the guided path whenever you want.
The states a product actually lives in
A limit that is used up, a figure that has gone stale, an approval that comes back as a question. These are the cases that decide whether a product survives contact with real users — and here each one is a state you can open, not a sentence you have to take on trust.
A rule you can trigger, then watch
A scenario sets up one condition and lets the system react to it. What appears on screen is computed by the same logic that runs the happy path, so the numbers, the blocks and the explanations behave as they do in the rest of the demo.
Your “what happens when…”, on the spot
The questions that decide a project are usually failure questions. If yours has a scenario, play it during the walkthrough and judge the answer on screen instead of waiting for a follow-up e-mail.
Scenarios are a demo control and never appear inside the product itself. Every state they load is built from the same fictional data, and Reset returns the demo to its clean starting seed.
Why this is not a mockup
Three rules that came out of a working product, not a design brief.
Anyone can draw an advisor dashboard. These three behaviours were read out of the client's own prototype and carried over unchanged, and each is the kind of thing an advisor notices in the first minute and a designer would not invent.
The signal taxonomy is closed
Seven states, no more, each with a fixed colour pair and a fixed explanation and metric on the dashboard card. Concentration reads "a single semiconductor name is 8.9% of the household — above the 5% band" and shows "8.9% single name". The two households on the dashboard that share that signal carry different explanations, because the copy is per household rather than per state. A closed taxonomy is a decision someone had to make and defend.
Performance is never shown alone
Always beside its benchmark, over five periods, on the same full-scale bar. Not a preference the demo added — it is how the product renders every performance figure it has, which is the sort of rule that exists because someone's compliance review asked for it.
The remedy is the product's own wording, quoted
Trim the single name to a 5% band and move the proceeds into fixed income, releasing 3.9% of household assets. That sentence is in the prototype's position-check copy, which is why the proposal builder computes exactly that rule rather than a rule we picked. Drift is flagged at three points of deviation per sleeve, and priority sorts High, Medium, Low then by assets descending — both also the product's.
Capability map
Clear about what you're experiencing.
Works in this demo
Implemented and clickable, on fictional data, in all three display versions and both themes.
- The advisor dashboard: $312.4M book hero with its sparkline, an insight line, four prioritised households, today's movers, tasks and the day's schedule
- The client book: search, priority / assets / RMD tabs, sortable columns, pagination
- Household and account analysis: single-name concentration against the band, allocation versus target, performance beside its benchmark over five periods, holdings, accounts and the activity ledger
- Book of business: assets, flows, book statistics, billing and top relationships over MTD, QTD and YTD
- The rebalance proposal: a 5% / 6% / 8% band control with live trade tickets, released cash, an estimated annual return, a tax illustration split into long- and short-term lots, and the projected allocation beside the current one
- Sending the proposal, the client reviewing it in plain language, approving it with an explicit acknowledgement, and the result flowing back into the workspace
- The client mobile app: portfolio total with period chart, the full picture with held-away and self-reported assets, goals, accounts, documents and notifications
- Report generation that produces a record and delivers it into the client's documents
- Calendar events that are actually added to the day's agenda and the week strip, and a client message that reaches a thread
- Loading, empty, validation, success and recoverable-error states on every screen, and a keyboard-operable route to all of them
- Light and dark themes, three display versions, Guided Mode, and one-click reset to the clean seed
Simulated here
Behaves like the real thing and reaches nothing. No message, no order, no payment, no filing.
- Sign-in and the second factor — the text message is drawn inside the demo with a code derived from the seed; nothing is sent
- The client's notification — push, e-mail and SMS are drawn inside the demo and labelled In demo
- The client's approval — a click here; in production it would be an attested consent record
- Custodial and market data — a bundled, frozen seed of 14 households, 4 accounts and 9 holdings; no feed, no intraday price
- The tax figure — three fixed lots at flat illustrative rates, labelled on screen as an illustration
- Order routing — deliberately not simulated anywhere, in any code path. Nothing is created, staged, routed or acknowledged
Ready to integrate
Candidates for a production build. Nothing here is connected, and nothing here is selected.
- Custodial feeds for positions, lots and transactions
- Account aggregation for held-away and linked bank accounts, with consent and refresh handling
- Market and reference data with entitlements, plus a corporate-actions feed
- The firm's model portfolios and each household's investment policy statement, as a versioned rule store with an owner
- Lot-level cost basis and a tax engine, or the firm's own rate table
- A billing engine for fee schedules, tiering, householding, accruals and exceptions
- Notification delivery with receipts, retries and a preference centre
- Client identity with step-up authentication, plus e-signature or attested consent
- Document storage with retention, entitlements and an audit trail
- An order-management system, if and when that boundary is meant to move
Completed and proposed
What came from the source, and what did not.
The analysis in this demo is the product's. The round trip on top of it is ours. That split is the whole point of showing it, so it is stated here, in the demo's own About panel, and on the screens where it happens — never quietly promoted into product capability.
The rebalance proposal builder, its trade tickets and its tax estimate
Proposed by ItexusThis capability does not exist in the product today. The rule it applies is the product's own stated remedy — trim to the band, proceeds into fixed income — but the surface that turns that sentence into tickets, released cash, a tax illustration and a projected allocation was added here. The claims register behind this page records it as possible, never as source-backed.
The client's review and approval, and the result coming back
Proposed by ItexusThe client app is the product's own and reads the same households, accounts, holdings and documents as the workspace. Reviewing a proposal in plain language, approving it with an explicit acknowledgement, and having the task close, the signal clear and an audit line appear on the advisor's side — that round trip is ours.
Sign-in and the two-factor code
Proposed by Itexus, and simulatedNo authentication exists in the source; two-factor over text message appears there only as a settings toggle. The screens were built for the demo and the message is drawn inside it, with a code derived from the session rather than generated. Nothing is sent, and no identity is checked.
Report generation, calendar events and the client message thread
Completed for the demoThree places where the prototype collected the inputs and produced nothing: the report modal ran a spinner and returned no artefact, Add to calendar only closed the dialog, and the client's message raised a toast with no thread behind it. Here a report becomes a record in the advisor's library and in the client's documents, an event lands in the agenda and the week strip, and the message reaches a thread.
A narrow-width advisor workspace
Completed for the demoThe source workspace was desktop-only. The narrow layout — single column, the sidebar as a bottom bar, tables as card rows, targets at 44 pixels — was built here, following the prototype's own logic rather than a new idea.
Guided Mode, the display-mode selector, the theme switch, About this demo and Reset demo
Demo shellScaffolding for showing the product, not claims about it. None of it exists in the source and none of it is offered as product functionality.
None of it changes a regulatorily significant behaviour. There is no suitability assessment, no risk-profile match, no best-execution logic, no KYC decision and no recommendation engine. The proposal is a draft one human sends and another approves, and no order is routed anywhere.
However you open it
Three display versions of the same demo.
One runtime, one route, one session, three versions, switchable from the header in the middle of the flow. The progress, the data and the proposal state all survive the switch — so a buyer can start on a shared screen and finish on the phone in their hand without losing their place.
Web · desktop
The prototype's advisor layout, unchanged: a 240px sidebar, content capped at 1180px, multi-column grids, five-column tables and hover density. At 1280 the projection, the flipped flag and the client's notification are all in view at once, which is what makes the wow moment read as one event rather than three changes.
Web · mobile
The same adaptive web layout at phone width: one column, the sidebar as a five-item bottom bar, tables as card rows, KPI rows wrapping, and every control at least 44 by 44 pixels. This layout did not exist in the source and was completed here.
Mobile app
The product's own client-app idiom extended across the workspace: status bar, large title, back affordance, bottom tab bar, sheet transitions. Framed as a 390px device when there is room around it, full-bleed on a real phone, and never a frame inside a frame. It is an emulation in a browser, not a native binary.
Narration built in
Guided Mode
On by default. A dismissible bubble on each screen says what the screen is, what you can do here and where to go next — including saying outright which parts are the product's and which are proposals. Turn it off if you are narrating yourself; the whole flow completes either way, and that is covered by a test rather than assumed.
From demo to production
What each simulated part is standing in for.
The demo is a browser-only illustration over a bundled seed. Here is the honest gap between it and a system a firm could put in front of its advisors and its clients. Nothing below is implemented, and none of it is a readiness statement.
The part worth raising before you start: a real system has to record who recommended what, when, and on what basis. Recommendations, client communications and approvals are exactly the artefacts that books-and-records obligations reach, and any performance figure shown to a client sits under marketing rules. That is why the approval in a production build is an attested act rather than a click, and why suitability — which this demo asserts nothing about — is a first-phase question rather than a later one.
Built to adapt
One firm's product. A pattern that fits any book of clients.
The source is one wealth firm's own workspace. What carries into another firm, another asset class or another regulated relationship is the state model underneath it — one object, coherent from two sides, in two idioms, on one code base.
The hard part is the round trip
A professional's action and a client's approval being the same object, seen from two sides, with the second one closing the first. That is the piece with no vendor to buy it from, and it is the piece this demo puts on screen.
Density that a specialist can read
Seventeen screens of tabular numerals, signal chips, sortable books and benchmark bars that stay calm rather than busy. Advisors do not want a simplified view of their own work, and a demo that simplifies it loses them in the first minute.
Honesty as a feature, not a footnote
The demo itself says what is real in the product, what was completed for the demo and what Itexus is proposing — in an About panel a prospect can open mid-meeting. It is a better answer to "how much of this exists?" than any slide.
Three versions from one build
An adaptive desktop workspace, the same workspace at phone width, and a mobile-app emulation — switchable mid-flow with the progress, the data and the proposal state intact.
Discuss with Itexus
Decisions to shape for your product
- How many custodians would a pilot have to read, and is a nightly file enough to start?
- Where do your band rules and model portfolios live today — a document, a spreadsheet, or a system with a change history?
- Who is allowed to send a proposal to a client, and who has to review it before it goes?
- What has to be true for a client's approval to count in your compliance review — e-signature, click-wrap consent, or something your supervisor already accepts?
- Does the boundary stay before order routing in a pilot, or does the OMS have to be in scope from the start?
- Which of the three display versions is where your advisors actually work?
Demo access
Everything you need to start.
Nothing is required to start: both fields on the sign-in screen are pre-filled and the code arrives inside the demo. They are listed here so you know what you are looking at, and so you can retype them after a reset.
Senior advisor
Fictional, on a reserved example domain, and not a sign-in to any real service. No identity is checked and no password is verified — the screen demonstrates a flow.
mira.solano@northrift.exampledemo-passwordTwo-factor code
Derived from the demo's seed, so it is identical on every run. The message is drawn inside the demo; press Use this code and it fills itself in, or type it by hand.
Text message, drawn in the demo206480Before you begin
Demo boundaries and data policy.
Known limitations
- One household carries the story. The rebalance proposal is offered on Okafor Family Trust, because that is the household whose client can approve it here. Other households show the same analysis without the action, and holdings and activity data are shared across households exactly as in the source prototype.
- The seed is frozen. "Today" is Wednesday 1 July 2026 and every figure is fixed, so the demo never looks stale in an inconsistent way — but it will not look current either. The dates are visible on screen; if you are shown this much later, that is why.
- No export, no delivery, no order. Download, share, join call, call, book time and the privacy policy each state in one sentence that they are outside the demo. No file is produced, no message is delivered, and no order is routed in any code path.
- One role on each side. The source product has a single advisor role and a single client role, so there is no supervisor, admin, back-office or multi-advisor view to show, and no team hierarchy is modelled behind the 118-household badge.
- Session state lives in one browser tab. Two tabs are two independent sessions, closing the tab ends the demo, and Reset demo returns to the clean seed.
- Accessibility was checked by automation only. An automated WCAG 2.1 A/AA audit with axe-core reports zero violations over ten screens in each of the three display versions, and roles, names, live regions and focus order are asserted programmatically. That is an automated sample: not an audit, not a conformance statement, and nobody drove this demo with a screen reader or tested it with disabled users. It is also a statement about the demo, not about the product.
- Verified in two browser engines, Chromium and WebKit, both pinned. Firefox was not tested.
- The timings on this page are machine speed. A scripted run reaches the proposal moment in a few seconds; a human clicking and reading needs the four minutes the walkthrough describes.
- Five light-theme colours were darkened from the prototype's values, because its greys, green and red did not meet AA contrast at the sizes it uses them, and one token was used both as a surface and as a foreground, which made dark-theme body text unreadable. Layout, type, spacing, radii, elevation and every other colour are unchanged.
- Typography follows the platform. The font stack is the prototype's own system stack with no webfont download, so on a Linux desktop without a matching family the browser falls back to a generic sans-serif and the demo looks slightly different from the screenshots.
Data and safety
- Every person, household, account, holding, transaction and document in this demo is invented. No real client data is used.
- Nothing is connected to a custodian, market-data provider, CRM, e-signature or messaging service.
- Nothing is sent and nothing is executed. The text message, e-mail and push notification are drawn inside the demo.
- No order is routed, no payment is made, no document is filed, and no message reaches anyone.
- Nothing here is investment, tax or legal advice. The rebalance proposal is a draft produced by applying a stated band rule, for a human to send and another to approve.
- The proposal contains no suitability assessment, and its tax figure is an illustration.
- Do not enter real personal, client or financial data.
- Parts of this demo are proposals, not product. Sign-in and two-factor, the proposal builder, the client approval, Guided Mode and the display-mode selector were added by Itexus and do not exist in the source product. The About this demo panel inside the demo lists the split in full.
- The demo makes no network request beyond its own origin and carries no third-party code — no dependency, no CDN, no webfont, no analytics and no tag manager — and its own content-security policy sets connect-src to none.
Provenance
- Source product
- The client's own working prototype of this product, read on 30 July 2026: 17 screens across an advisor workspace and a client app. Every statement about the product describes it at that point, and no source code was executed — the prototype was read, never run.
- Positioning
- A hypothesis derived from the product's own numbers and screen inventory, not a measured or client-confirmed segment. No market size, share, benchmark, competitor comparison, customer count, testimonial, ROI or time-saving figure appears on this page, because none has been verified.
- Conformance
- No audit, assessment or certification against any standard was performed. The demo makes no conformance statement about any regulation, and the accessibility result above is an automated sample rather than a conformance claim.
- Verification
- 54 of 54 acceptance tests pass in Chromium and WebKit, over the main flow, both auxiliary flows, the error and empty states, the reduced-motion path and all three display versions. Two independent design reviews found and closed 19 defects across three rounds and returned a verdict of pass. The checks ran against the demo package rather than against this URL.
- Content version
- 1.0.0, written on 30 July 2026 from the demo's own claims register. Every claim on this page is registered against evidence, and the ones that could not be backed are not here.