31 May Troy’s Take on Why You Should Hire a 3(16)
I caught up with Troy Tisue the other day to ask him a question, “Why should you hire a 3(16)?”
That’s a topic we’ve been asking a lot lately to make sure TAG Resources is giving you the most thorough and complete reason to do so. Here’s Troy’s take on 3(16)s countering the responses he hears most often:
- “Too Expensive”
- “I can get a local TPA to add-on a 3(16)”
- “There is no need for a 3(16)— the TPA and RK (and FA) do all of this for me already”
- “Too Expensive”
Cost is a relative thing. You cut cost, you generally are cutting back on something. When you’re dealing with other people’s money, it is a good idea (as a fiduciary) to really dig into what you’re paying for (or scaling back on) when you talk fees. Fiduciary Liability Insurance is a perfect example. As a 3(16) is the day to day operations component of a plan— insurance through action— protecting a Plan Sponsor from regulatory failures the plan is “covered”. Insurance can be one of those things, too, that you go cheap on… at least for yourself. However, when you weigh the impact of your decision on others, as in the case of retirement plans and Fiduciary Liability Insurance, you seldom take the cheapest route, as success becomes more important.
So again: too expensive relative to what? To other 3(16) firms? This one is easy. How do the other 3(16) firms integrate (real time) with the RK? How do they capture and police data? Are they named in the Plan Document or named in a service agreement? How long have they been offering 3(16) services to clients? Experience is a big deal. What kind of fiduciary-specific coverage do they have? Most firms are smoked out early with these questions.
- “I can get a local TPA to add-on a 3(16)”
- “There is no need for a 3(16)— the TPA and RK (and FA) do all of this for me already”
Well, this one is tough. I never wanted to tell my kids about Santa and the Easter Bunny, either. I like to believe mermaids and unicorns could be real… somewhere. Sorry to tell you this, but, No.
No Comments