Deep prospecting a foreclosure notice.

In this example, this is one that we had a deceased owner that was on file. It was a foreclosure that was coming in the next few weeks.

We really wanted to show a good example of the ones that most people just aren't getting. If you can reach the heir, you are the only person in that conversation.

It will do a good job of kinda ranking them all, especially if you say these are all foreclosures. So don't even factor that in. They're all bad.

One of the biggest deals I've ever done was a foreclosure obituary. If the person is deceased and they're going to foreclosure, reaching the heir beats door knocking that house. That is why stacking them in that order does well.

There's a ton of workflows embedded in the deep prospecting process inside of all of these workflows here. Once you've set them all up, you can do this without the API.

With the API it does more, but they are all programs that will function the same way without it. So nobody is blocked here.

When you come in, you can just say, hey, can you please deep prospect this property. Just do one thing at a time. I'll show the one off first, then the version at scale.

I show this example a lot because I think it's a really cool visual aid. It's that exact scenario I was outlining, from a foreclosure to an obituary filing. This was before we had obituary data, so it's not that property.

I plug this straight into the foreclosure notice itself, and this is what that actually looks like. This was a Daniel H Williams, a person that was going to auction soon.

It says, we're gonna start the deep process here on the foreclosure notice, and here's what I'm working with. Then it lays out what it has before it does anything.

Go on down and you can see it starting to log in and do research on all of the sites associated with that property address. This is in CoWork, so it pulls out all of the skills being used.

Claude has the ability to log in to pretty much any tool, assuming it doesn't have a captcha. If there is one, Scrapfly can get past it. Most of these auditor sites are not going to give you any trouble.

The first thing it does really well is log in to the recorder. Mine is the register of deeds. If you've never seen one before, you can look up any document number.

It pulls up PDFs and reads through them. It's very, very close to how a title agent would function, running through the documents and getting an idea of it.

This second thing is something most people here do not need. These are definitely for more advanced workflows if you want to bolt this on.

Ancestry.com is a site where you can also log in and actually find details of family trees. It can go in, log in on your behalf, and do research.

It finds the instrument, and it looks the same as it did in the register of deeds. Then it goes in and finds the exact deed of trust the foreclosure is being filed against. It says this is a consideration of 25,000, and that seems really odd for a mortgage. That is very, very low.

So it gets in and points out that the 25,000 is actually a home equity line of credit. It also found a mortgage, and that mortgage is for 168,000. These steps matter because it is finding the total debt load. It will also tell you if there is no point pursuing this on equity.

Say a property is free and clear but also heading to foreclosure. That 168,000 is hypothetically zero, and we would not know about the line of credit. Then it keeps going down and finds a couple more refinances and some warranty deeds. It is building out a full deed chain, and messy title needs that whole paper trail.

It uses all of that information to figure out who the decision maker is, if it is not the person on title. It uses all this research to compile a much higher quality answer.

That person did pass away, and this explains the foreclosure, because the payments likely stopped after death. That is a seven month time horizon from the death. It also ties into why that obituary six plus month range is so important.

Then it reads the obituary and finds the children mentioned in it. It also confirms his wife, Christine Williams, of forty one years, has passed away too. So right there it confirmed the owner on title and the spouse are both gone, and that is why it is in foreclosure.

As we go down, it finds the grandchildren, the sisters, the in laws, and the people still alive. Then it links it together using smart skip. It skip traces the two people on title, finds their relatives, and finds the potential heirs with mailing addresses and phone numbers.

When you use all the skills inside SiftStack, it takes that individual and ties it all together inside an Excel file.

Smart skip will tell you pretty much everyone associated, and roughly what it thinks that relationship is. This is all totally new for people who have been through the challenge in the past.

The input name is the person who is the owner on title, and the property address is linked right next to it. Every one of the other names is an heir, relative or associate of the person who passed away, with their individual mailing addresses.

The question in this workflow is why can we not reach them. When we deep prospect the obituary records, we already know the owner is deceased. So we ask who all the relatives and associates are. You see a child, a child, a child, and their spouse, their ages, and their mailing addresses.

So the new process is deep prospecting every obituary record with that workflow in Claude. You get an exact mailing list, and the phone numbers are tied in. Instead of saying hey David, are you interested in selling, we are saying hey Joseph, hey Michael, hey Natalie, hey Tammy. Then we follow up with the same sequential process to all of these individuals.