Marloo just got smarter, and so did your firm.

Every advice firm runs on a layered set of rules

• At the top, the regulator: what the rules permit and the law demands.
• Then the firm's own standards: compliance framework, house advice philosophy, approved wordings, approved fund list.
• The adviser sits underneath that: their judgement, their voice, their clients.
• And the team works from what the adviser sets: the paraplanner taking on the case, the support staff running the reviews.

That hierarchy governs everything that happens in an advice firm.

Where the standards actually live

Every firm has a house style for client letters. File notes that need specific things in them. Recommendations that must be evidenced in a particular way. An approved list with conditions attached. Disclaimers that are mandatory, not optional.

None of that lives inside a tool. It is often contained in a policy document that gets written once and referred to very infrequently. Or, worse still, it lives in the head of whoever has been at the firm the longest.

Because of this, consistency gets enforced the only way it can: after the work is done. A compliance review samples a slice of the book. A peer check catches what it catches. A file goes back for rework.

This is what happens when a tool holds data but understands nothing about how the firm works. The practice management system knows what happened. It has no idea what the firm believes about how to document it.

Generic AI made it faster and less consistent

When advisers start using general-purpose AI, output gets faster and less consistent at the same time.

A generic model writes fluently in nobody's voice. Every adviser gets output pitched slightly differently, worded slightly differently, structured slightly differently. The model doesn't know how this firm works, so you pay a correction tax on every document: the same manual pass, bringing it back in line with standards that exist in people's heads and nowhere the tool can reach.

Three layers. The same ones you already operate in.

The Knowledge tab is built around the hierarchy that already governs how advice firms work.

Regional

The foundation. Marloo's maintained reading of what a compliant piece of work needs to show, including rates, rules and regulation. Firms can't edit it, because it is the standard everything else builds on and the layer our compliance tooling will hold files against.

Company

The firm's own standards. This is where you put the advice framework, the compliance documentation, the standard wordings, the approved list, the terms of business. It is also where you set firm-wide instructions that apply to every piece of work every adviser produces: how client letters should read, what a file note must always include, what Marloo must never do.

Company instructions are the rules you would want enforced if you hired a new adviser tomorrow. Anything more personal than that belongs in the layer below.

User

The individual adviser, layered on top of the firm's standards. How you sign off a client email. Whether you want meeting notes in bullets or prose, and what always comes first. The phrases you never use. The things you always check. It changes how Marloo works for you without touching what the firm has set.

Standardisation at the firm level. Personalisation within it. The hierarchy you already operate in, made operational at the point of production.

Knowledge flows through the team

The adviser's context flows to the paraplanner taking on the case, the admin handling correspondence, the support staff running the reviews.

This is where the user layer matters beyond the individual.

When an adviser sets how they work, that context is there for the whole team. A paraplanner knows their preferences without asking. An admin drafts in their voice, not a template. A new hire picks up in weeks what used to take months.

The firm’s knowledge stops leaving with people. The senior adviser who has always been the informal keeper of the house style writes it down once, in the company layer, and it stays.

It applies differently depending on where you sit

A sole adviser or small firm has no compliance department. You are the house style. Put how you work in the company layer once, and stop repeating it to the tool every day.

A principal or director knows how the firm’s work should read but has no way to enforce it. Turn every note you make in review into a rule the draft is written from.

A paraplanner already knows the six things that always come back from compliance. Upload them, and they stop being things to check for.

A compliance function has a framework for what a good file needs to show. In Marloo, it shapes the work from the start, not just the review.

Getting started

Open the Knowledge tab and start a conversation. Marloo will ask a few questions and build your company instructions from your answers. Then upload what's behind them: the advice framework, the compliance documentation, the standard wordings.

That’s the whole setup. The hierarchy was already there. Now it has somewhere to live.