Never Let Go

Saturday might mean sleeping in for some people, but for me, it means getting up early and heading off to open the coffee shop for all those happy people who are having a laidback morning sipping a latte at their favorite table.

Full-disclosure: I’m writing this before heading to work on Thursday because I really didn’t want to get up any earlier than I had to on Saturday. 😉

FIRST OFF, SOME STATS:

Find the book on: Amazon and Goodreads
Pages: 368
Publisher: Revell
Release Date: February 5, 2019
Title: Never Let Go
Fiction

1.jpg

ABOUT THE BOOK

As a forensic genealogist, Willow Anderson is following in her late grandfather’s footsteps in her quest for answers about a baby abducted from the hospital more than twenty years ago. The case may be cold, but things are about to heat up when someone makes an attempt on her life to keep her from discovering the truth.

Ex-FBI agent–and Willow’s ex-flame–Austin McKade readily offers his help to protect the woman he never should have let get away. Together they’ll follow where the clues lead them, even if it means Austin must face the past he’s spent much of his life trying to forget. And even if it puts Willow’s tender heart at risk.

WHY I CHOOSE THIS BOOK

I’m working on writing a book that includes a mystery plotline, so therefore I’ve been trying to read more books that have mysteries in them. When I saw this one on NetGalley it looked like a clean, interesting read. Plus, I have a thing for mysteries that include a cold-case abduction. (And, that’s exactly what this was.)

WHAT I THOUGHT ABOUT THIS BOOK

It took me a while to get into the story – I’m really not sure why this was, but for the first quarter of the book I would pick it up and set it down without really caring much about what happened. This took place over the period of about a week or two, then it was like a switch was flipped and I suddenly felt quite invested in the book. I settled in with it one evening and read the last three-quarters of the book without stopping.

I’m not exactly sure how to rate this book on the spectrum of scariness. I didn’t find it creepy (I would have stopped it if I had), but there were plenty of scary situations that the characters found themselves in.

There are a couple of mystery authors who I’ve been really into recently, but after reading/listening to a handful of their books, I’m able to predict the plotline nearly immediately. I’m not sure if it was because this author was new to me, or because she’s just really good with throwing out red herrings, but I really wasn’t sure about where the book was going or who was who until it was disclosed. That’s one of the main reasons I gave the book such a high rating. Way to go, Miss Elizabeth! (Seriously, I was barking up the wrong tree nearly the whole book.)

As always there were some elements to the story I didn’t like – including how long it took me to get into the book – but overall I really did like it. And, even though I’m about ready to get off my mystery kick, I’m interested in reading more books by this author.

CONCLUSION (With SPOILERS)

*Spoiler Alert* This part right here has spoilers in it, so stop reading the review if you don’t want to hear about the bad things that happen in the story: They found out that someone who they thought had died accidentally was actually murdered, there were a few attempts to kill the main character, there were break-ins, arson, and abductions. None of it was talked about in too much detail.

RATING

I’m giving Never Let Go four out of five stars – I’m thankful to NetGalley for providing me with an ecopy to review.

3 thoughts on “Never Let Go

Leave a Reply to Emily Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s