Your firm is moving to Pennylane

A migration to Pennylane is rarely a tool problem. It is a whole team relearning its habits while still producing, and for months the same question comes up in every office: how did we use to do this, again, in the old world, and how do we do it here.

What the assistant has already read

Pennylane's public help is substantial: 684 articles, with screenshots and videos. The assistant reads them, resyncs as the platform evolves (and it evolves fast), and answers questions asked in plain language, citing the original article. During a migration, that's the difference between a team that interrupts its go-to person ten times a day and a team that gets on with the work.

What your teams teach it

Your firm's own choices are written down nowhere at Pennylane: your chart of accounts, your approval circuits, your naming conventions. The assistant learns all of it from your teams, and also consolidates the answers you get from Pennylane support, whether through the app chat or by phone. What has been solved once is settled for everyone.

Between your teams and Pennylane support

When the answer exists nowhere, the assistant takes over: it raises the request with support itself, tracks it, chases it up if needed, and brings the answer back to you. Who asked and for which client file, how long the wait has been: the tracking is there in front of you, which matters when a team in the middle of a migration is asking a lot of questions at once.

What the vendor gains

A firm that migrates with proper support calls on vendor support less, and the published figures back this up: between a quarter and nearly half of requests find their answer without ever reaching it, according to field measurements. On the team side, the study Generative AI at Work (Quarterly Journal of Economics, 2025) measures 14% more cases resolved per hour, and 34% among newcomers. A team in the middle of a migration is, by definition, a team of newcomers.