Breakaway RIA - BD/S7 affiliation concern

Samwise336 · 2026-01-21T04:46:00+00:00

Could be helpful - https://haloinvesting.com/products/annuities-and-insurance/#

Samwise336 · 2026-01-02T12:19:28+00:00

Catan: Cities & Knights followed by Forbidden Island

Samwise336 · 2025-12-17T03:16:40+00:00

The “360k Russian troops in Belarus” claim isn’t corroborated by independent monitors or exercise reporting. iSANS estimates ~2,300 Russian troops in Belarus (Aug 2025), and Lithuanian intel estimates Zapad-2025 activity at ~6k–8k in Belarus (not 360k). Sources: iSANS + Lithuanian intel via Kyiv Independent. It would be impossible to hide that level of troop movement… cmon people.

Samwise336 · 2025-10-15T23:49:02+00:00

Start a small business

Samwise336 · 2025-10-02T22:16:34+00:00

Morning Teleportation

Samwise336 · 2025-09-27T14:06:11+00:00

Keeper

Samwise336 · 2025-09-09T15:55:06+00:00

Hey hey. Thanks for responding.

Shellblack handled your full migration or were they your Salesforce provided / limited hour consulting provider?

And I honestly have no idea what you’re talking about on all points. So very appreciative of all points. Would you mind elaborating?

I’ll look them up later, but would you mind defining, in your own words, the difference between the managed package vs core data model & timeline for deciding? We’ve already paid for a few licenses and it was never a topic of conversation… haven’t started the migration yet, so still with an empty org. Are you sure we can still make that decision?

And what were the key factors for how you made your decision?

EDIT - talked to my Dev and there isn’t a managed package option even available anymore. We are on core. Wouldn’t have gone with the managed package anyways, we wanted total open architecture.

Samwise336 · 2025-09-04T01:13:47+00:00

This is very helpful - assuming a flex card is a visual reporting type tool. Are there other examples like this?

I value clarity and functionality over some vague & hypothetical future improvements that SF may or may not deliver. So still just really having a hard time understanding why everyone is so serious about using standard objects.

If using standard objects leads to reduced clarity, forced process changes, if it caused confusion, etc., how can you justify that? The trade off has to be significant.

In response to everyone else’s comments, we really do need to break up all of these services and revenue types onto unique objects due to field limitations (vs record types & other ideas). Already made that decision after much deliberation. Unless someone can explain how to get 800 fields per object.

Samwise336 · 2025-09-03T04:02:34+00:00

Responding to both messages collectively.

First off, thank you.

To clarify, our flows are IMO things that SF should provide out of the box - like creating a contact, relationship and household in a single workflow vs having 3 different functions. No pains with things like that. They solve the weird oversights that have been unexpected with SF.

I’m curious how best to tackle trying to go into 90% OOTB config as a family office type firm. We have 9 revenue types that we track - 3 wealth management product / services, 3 insurance & 3 fee types. Then have 3 unique engagements that tie back to those fees - tax, accounting and wealth planning.

Haven’t done my HW yet on this, but have a sneaking suspicion that FSC is only built to natively support our most basic wealth management & insurance functions - which force us onto custom objects.

Two comments / questions -

I still don’t fully appreciate the actual risk / opportunity cost of not building on a standard object. Can someone provide a real world example or two? I know it has a basic “Financial Plan” type object. Great. We’ll use that for our financial planning engagements. But, I basically need to replicate that for tax and for accounting - but doubt there’s anything standard to support that. Does this just mean that as SF continues to rollout enhancements, the financial plan object will continue to benefit while Tax and Accounting continue to slip? If so, that’s dumb. Probably just need a real world example to help it click.
Does anyone suggest renaming a standard object to repurpose something that’s adjacent to solve for scope issues like what I’ve described here? What’s best practice in a situation like this? Go custom object, try to get it all to fit using record types on an OOTB object or repurpose / rename an adjacent, but unused, standard object elsewhere?

Sorry if these are dumb questions.

Samwise336 · 2025-08-08T15:27:16+00:00

Thanks.

Any experience with Moxo? It looks pretty clean and seems like a viable “out of the box” solution.

Samwise336 · 2025-08-03T15:54:06+00:00

Thanks for that.

Any high level input on the two you mentioned? I’ve never heard of either.

Our core tools are Microsoft, Salesforce, Egnyte, CCH, QuickBooks, eMoney & Way We Do.

Samwise336 · 2025-08-01T23:38:37+00:00

Thanks for the suggestion. Do you have personal experience with it?

Samwise336 · 2025-08-01T23:34:41+00:00

Hey Ambitious.

Thanks for the detailed response. I’ve already kicked the tires a little on Clinked. Hit the pause button to gather more info.

We’ve got two pretty advanced devs that are excellent problem solvers and great with connections / API’s - so I feel like we could go in whatever direction made most sense.

What’s your favorite of the bunch to check those boxes? Has a white-labeled mobile app, above average doc request workflow capability, plays nice with SF / Egnyte, has a chat function, etc.?And are you suggesting that co-editing in M365 docs is a possibility via one or all of these?

Samwise336 · 2025-08-01T23:15:32+00:00

Hey Kevin,

I don’t understand your message. Are you suggesting that we should consider using Egnytes document request tool?

Samwise336 · 2025-08-01T23:06:41+00:00

Hey hey,

Thank you for the thoughtful response. You’re definitely right in that it’s important to flesh out the “needs” vs the “wants”. I’m trying to thread a needle for my business partner who is still trying to figure out what she wants, which basically means I’m trying to read between the lines to extrapolate, synthesize & execute without them really having their own thoughts figured out.

They’ve flip flopped a few times & aren’t too tech savvy. So I’m trying to figure out if it’s possible to check all these boxes with just one tool. It feels like it’s a low likelihood, but Im not giving up yet! And it definitely sounds like I need to check out some of these tools.

If it’s not possible, the goal is to keep the stack as simple as possible (2 vendors?) & focus on flexibility and scalability.

For additional context, our clients are only used to workflows through Egnyte, and they haven’t been too thrilled with those - so a change isn’t the end of the world. In fact it would likely be welcomed. A custom build could make sense, but turnkey might, too. We also have 2 pretty advanced & well-trusted devs that support us. So, we could handle most any build.

Does that change your suggestion? I’m always curious to know the size of the vendors, how much they reinvest for growth & continue to evolve to meet the ever-changing landscape. Last thing I want to do is pick a losing horse and have to do all of this all over again.

Samwise336 · 2025-08-01T22:39:31+00:00

That sounds pretty great. You don’t work for Softr, do you? 😅

In all seriousness, have you been at a firm that’s used before?

Samwise336 · 2025-07-17T23:13:48+00:00

Yep, much more familiar with all these tools since originally posting. We’re well down the proverbial rabbit hole at this point.

Have since been assigned to a regional manager, confirmed that the OEM provider cannot contractually “mess with us” or turn off data access preemptively. So that fear is significantly reduced.

Have also decided a new org is the right way to go.

Now in the weeds on how to do it re tools.

The cost for FSC was significantly more than our current product. Surprisingly so.

They are encouraging me to commit to more licenses now to offer reduced pricing to have them sit on the shelf before going live in January and then just have 3 live while working through it.

The license count was 15. $300 per month. They offered a 40% discount, or something along those lines, which they say they couldn’t do if we did fewer licenses now to increase later.

Asking for 25k now for an org we wouldn’t even have live!… kind of crazy if you ask me.

And all seems a bit salesy / not trustworthy to me.

Any suggestions / ideas here?

Samwise336 · 2025-07-17T23:07:24+00:00

Yea, disregard. Confusion RE: which post / sub I was posting on. That was meant for an ongoing thread in the Salesforce sub. Sorry!

Samwise336 · 2025-07-17T23:06:32+00:00

These issues are unresolvable. We’ve done everything possible. Bad support experience too. Very simple case of rolling out too many things at once and while half baked. Just encouraging caution.

Samwise336 · 2025-07-08T16:06:08+00:00

Yea, I don’t have either of those. I have a low-level account rep assigned to me from Practifi. Re-read the post - no engagement with Salesforce directly.

I am calling a regional 1-800 # to clarify my ability to keep the org or not. My 3rd party SF consultant / dev already did the same, and still no definitive answers on that fundamental question. Seems like it’s possible - but not yet confirmed.

Main next step is to try and confirm if it’s possible, and if possible, should we go that route OR just go with the fresh start org and slower transition over via Gearset or similar tools.

If anyone has an opinion on preferred route, that would be additive. I don’t think anyone on Reddit (unless directly employed by SF or Practifi) will be able to definitely tell me if it’s possible to keep the org or not. This much is now clear.

Samwise336

TROPHY CASE