fpPathfinder

Helping Diligent Advisors Ensure They're On The Right Planning Path

Category: Client Service Calendar

2022 Expanded fpPathfinder Service Calendar

Annual client meetings can be overwhelming. There’s a lot to cover at one time. The 2022 Expanded fpPathfinder Service Calendar is your internal tool that offers 12 timely engagement ideas to help you plan your micro-engagements all year long. You’ll…
Read More

What Customers Are Saying About Us

Hundreds of other advisors are actively using fpPathfinder. Read what those lovely people have to say about us.
“ fpPathfinder is great. It's perfect for supplemental content to enhance our marketing efforts.”
— Ray, an advisor in California
“You just continue to put out great content on fpPathfinder. The 'What Issues Should I Consider Before The End Of The Year' checklist is fantastic.”
— Chris, an advisor in Illinois
“It’s brilliant to boil complex planning strategies into a one-page flowchart. It totally beats having to read 4 -5 articles to understand each nuance and exception, especially on the tax issues.”
— Meghan, an advisor in Georgia
“I can’t tell you how much I appreciate the Flow Charts you are providing. Helps me feel a little less crazy as an advisor.”
— Tami C, an advisor in Colorado
“This is one of my best subscriptions I pay for!”
— Sean, an advisor in California
“I love your resources, you guys & gals have helped us take our practice to the next level!”
— Trevor, an advisor in California
“I think fpPathfinder is the best tool I’ve ever seen in the financial planning realm. I spend an unbelievable amount of time researching some of these issues that have been boiled down to one page: consulting with other experts, citing specific sources as a backup, reviewing my work, and coming to a final conclusion.”
— Jeff S, an advisor in Missouri
Become a Member

Recent Blog Posts

Sign Up to Receive Updates

Join our mailing list to be updated as we release new flowcharts and checklists that might be of interest.
  • This field is for validation purposes and should be left unchanged.
[class^="wpforms-"]
[class^="wpforms-"]
[class^="wpforms-"]
[class^="wpforms-"]