one practice,
one way of working.
a single adviser can run shandy out of the box. a firm needs more than that: control over who sees what, one template library everyone draws from, one bill, and oversight that covers every client interaction rather than the handful a reviewer had time to sample.
the team tier is the same assistant with the firm's structure around it. advisers get the hours back. the practice gets consistency, and a compliance function that is looking at the whole book instead of a slice of it.
practice management,
built in.
these are the four things a firm asks for in the first ten minutes of any serious conversation about software: who is on it, who can see what, who pays, and whether the output will look like ours. all four are handled in one place.
-
01
member administrationadvisers and support staff
add advisers, paraplanners and client service staff, and structure them into teams that reflect how the practice actually works rather than how an org chart draws it. one place to see who has access, who is active, and which clients sit with which team.
-
02
permissionsaccess, set by the firm
decide who can see and do what across clients, records, drafts and settings. an adviser's own book, a team's shared clients, and firm wide oversight are separate levels of access rather than one undifferentiated login, and drafting rights can be granted without granting sign off.
-
03
central billingone account, one invoice
the firm's account is administered centrally. seats are added and removed by whoever runs the practice, and billing is handled in one place instead of being reconciled from individual adviser subscriptions at the end of the quarter.
-
04
shared templatesthe house style, once
the firm's document templates and house language live in a shared library. when compliance approves a change to the review template, every adviser's next draft uses it. consistency stops depending on whether someone remembered to use the right file.
compliance that sees everything, not a sample of it.
file review has always been an exercise in sampling. a reviewer takes a handful of cases, reads them properly, and extrapolates. it is the only approach that fits the hours available, and everyone involved knows what it cannot catch.
shandy understands regulatory language. it reads client interactions, identifies the disclosures each one requires, and surfaces what is missing while the conversation is recent enough to put right. that changes the arithmetic of oversight: the question is no longer which files to read, but which flags to act on.
reviewers keep the judgement. shandy narrows the field they have to cover, which is the part that was never solvable by working harder.
- disclosures identified against the interaction that required them
- gaps surfaced soon after the conversation rather than at quarter end
- one view across every adviser in the practice, not adviser by adviser
- every flag traceable to the moment in the meeting that caused it
from a slice to all of it.
decided by the practice,
not at five in the afternoon.
the difference between a firm and a group of advisers with the same logo is whether the answers to these questions are the same across every desk. shandy puts them in one configuration rather than in everyone's habits.
start with one team, not with a programme of work.
firms have been burned by software that needed six months of configuration before anyone could judge whether it helped. shandy is self service and free to start, which means the sensible rollout is small, quick and evidenced.
one adviser, one week
switch it on for a single adviser's meetings and read what comes back. no procurement, no kickoff, no commitment beyond the week.
load the templates
add the firm's review and policy statement templates and the standing wording compliance has approved, so drafts arrive in house shape.
set permissions and fields
decide access by team, and set which form fields may be completed automatically and which stay fixed. this is the configuration that matters.
extend across the practice
add the remaining advisers and support staff. they inherit the templates, permissions and retention policy already in place.
- which templates represent the house standard
- who may see which clients, and who may sign off
- which form fields are fixed and which may be filled
- how long recordings and transcripts should be retained
- an implementation project or a configuration phase
- a data migration before anyone can try it
- training sessions for a tool that works inside existing meetings
- a decision about the whole practice before testing one desk
the firm sets the standard.
shandy keeps to it.
templates, permissions, fixed fields and retention are the practice's decisions. advisers work faster inside those rules rather than quietly around them, which is the only version of consistency that survives a busy quarter.
tell us how the firm is structured and we will show you how the team tier maps onto it.