What's New

Books Like

Books Like Moscow X: Novels About Money, Secrecy, and Betrayal

What readers love about books like Moscow X is not just that it is a spy novel. It is that the book turns espionage into a pressure chamber. The official setup is already rich with danger: CIA officers Sia and Max enter Russia under commercial cover to recruit Putin’s banker, only to find themselves inside a world of luxury, gangland violence, shifting loyalties, and a Russian intelligence officer playing her own game. Critics also praised the book for its insider detail, double- and triple-crosses, and its hard-edged commentary on truth, loyalty, and vengeance.

books like moscow x Espionage night in a snowy city

Books Like Moscow X

That is why Moscow X works so well for thriller readers who want more than a mission plot. It gives them plot architecture, yes, but also emotional abrasion. The world is full of money, state power, betrayal, and professional tradecraft, yet the real grip of the novel comes from exposure. Nobody is standing on clean moral ground for long. The book keeps tightening because access, trust, and performance are always unstable. Even readers who found the opening deliberate tend to point to the same reward: once the machinery locks into place, the novel gathers force and becomes deeply absorbing.

That is exactly where Snodgrass becomes the right next read.

Snodgrass is not another Russia novel and it does not pretend to be espionage in the same register. What it does share with Moscow X is the thing that matters more: a protagonist under layered pressure, a world where danger comes from systems as much as from individuals, and a story driven by the psychological cost of living inside those pressures. On Mark Bertrand’s site, Snodgrass is positioned as book one in the Married Stupid trilogy, a crime thriller based on a true story of courage, combat, and crime. The larger series is explicitly built around early damage, adaptive intelligence, and a protagonist who learns to read people by studying what they worship and where they are weakest.

That framing matters, because readers who love Moscow X are usually not just looking for another professional operator in another geopolitical plot. They are looking for a book where character, plot, and pressure are fused. They want competence, but not clean competence. They want danger, but not empty action. They want the feeling that everybody in the book is carrying more than the plot alone can explain. Snodgrass fits that appetite because it works from inside a damaged man rather than from outside him. As Bertrand’s own comparison pages keep arguing, this is a novel where a man becomes dangerous and complicit at once, then still has to carry the mission forward.

Plot: Why This Kind of Thriller Hooks Readers

The plot engine in Moscow X is built on layered infiltration. Sia and Max work under commercial cover, move toward a powerful financial target, and discover that everyone around them is running a parallel game. That design is why the novel feels so alive. The plot does not move in a straight line. It keeps folding back on itself. Every apparent alliance comes with a hidden cost, and every step deeper into the operation creates new uncertainty about who is using whom.

Readers love that framework because it produces a particular kind of suspense. It is not only “what happens next?” It is “what is really happening here?” That is the deeper addiction in serious espionage fiction. Information is never stable. Motive is never transparent. You read not just for outcome, but for the gradual revelation of what kind of game the book has been playing all along.

Snodgrass taps into that same reading pleasure, but through a military-crime design rather than a Moscow intelligence design. The tension comes from the overlap of courage, combat, and crime, and from a protagonist whose life is already split between official structures and harder private realities. In that sense, Snodgrass gives readers the same feeling of layered risk. The surface story moves through military pressure and criminal consequence, but beneath that surface is a deeper question about what kind of man survives by learning how systems really work.

Character: Why Readers Need More Than Competence

One of the great strengths of Moscow X is that its characters are not decorative pieces moving through a clever plot. The novel’s central figures operate under pressure, but they are never reduced to function. That is why the book lands. Sia, Max, Anna, and the people around them are not there simply to transmit secrets and execute tradecraft. They are compromised people inside compromised systems. The novel’s emotional electricity comes from that.

That same adult seriousness is exactly why Snodgrass belongs here. The Married Stupid series is explicitly built around “early damage and adaptive intelligence,” which is a far better foundation for a thriller protagonist than generic toughness. Snodgrass is not interested in a hollow action hero. It is interested in a man who has learned to survive by reading weakness, exploiting attachment, and functioning under conditions that would flatten softer people. That gives the character more psychological gravity than the average military thriller lead.

And that is the real handoff between the books. If Moscow X gave you characters who feel intelligent, pressured, and morally bruised, Snodgrass gives you a protagonist shaped by a different but equally volatile mix of damage and discipline. Readers who want the next read to feel adult rather than generic will recognize the difference immediately.

Pace: Slow Burn, Tightening Pressure, and the Payoff of Serious Thrillers

Moscow X is not built like a disposable airport thriller. Even sympathetic readers often note that it asks for attention early because it is laying down people, places, loyalties, and cover structures. But that is part of what readers who love this kind of book enjoy. The pace is not careless. It is cumulative. Once the lines tighten, the book starts hitting with the force of everything it has carefully set in place.

That matters because there are two broad kinds of thriller reader. One wants speed right away. The other wants pressure that earns its speed. Moscow X is for the second reader. It is a slow-burn espionage novel that deepens before it detonates. That is also why it attracts readers who care about atmosphere, motive, and emotional risk as much as mechanics.

Snodgrass answers that appetite in a rougher, harder register. It is not elegant in the way a Russia espionage novel is elegant. It is more intimate, more bruised, and more dangerous from the inside out. But it offers the same underlying reward: pressure that means something. The story is not asking readers to admire movement alone. It is asking them to feel what it costs to keep moving.

Theme: Truth, Loyalty, Power, and the Systems Around the Characters

Norton’s own copy for Moscow X emphasizes truth, loyalty, and vengeance, and that is exactly right. This is a thriller about the shadow war between states, but it is also about what power does to intimate trust. Once money, intelligence, and loyalty are braided together, every human bond starts taking on operational weight. That is one of the reasons readers stay with the book. It treats geopolitics as personal corrosion.

This is where Snodgrass becomes more than a fallback recommendation. It works on the same nerve. The Married Stupid frame is built around what people serve, defend, and sacrifice for, and how those devotions become leverage. That makes the series less interested in superficial crime than in the deeper machinery underneath crime: loyalty, self-deception, identity, status, tribe, and the stories people cling to because they cannot bear life without them.

That is a serious thematic match for Moscow X readers. Both books understand that the most dangerous systems are not always visible as systems. Sometimes they look like patriotism. Sometimes they look like romance. Sometimes they look like duty. Sometimes they look like the story a person tells himself so he can keep standing. Readers who love thrillers where power and belief distort human behavior will feel at home in both books.

Why Readers Love This Type of Thriller

Readers love this kind of thriller because it respects them.

It does not hand them easy villains and easy heroes.
It does not confuse movement with depth.
It does not pretend that violence is meaningful unless the people inside it are meaningful too.

Books like Moscow X work because they combine operational intelligence with emotional consequence. Readers feel that combination. They get the pleasure of complexity, but also the ache of compromised lives. That is what makes the book feel rich instead of merely busy.

Snodgrass belongs in that lane because it offers the same double reward in a different form. It gives readers a crime-and-combat story with psychological depth, adaptive intelligence, and the hard tension of a man trying to function inside systems that do not care what he is becoming. That is why it is not just a decent recommendation after Moscow X. It is the right one.

Final word

If you want books like Moscow X because you love espionage as a game of unstable loyalties, hidden motives, and moral bruising, then Snodgrass is your next read.

Not because it copies the Russian intelligence setting.

Because it understands the same deeper pleasure:
a pressured protagonist,
a world built on leverage,
and a thriller where character damage is not background texture but the engine itself.

Snodgrass book cover for book 1 in the crime thriller trilogy
Connected evidence

Your Next Read

The investigation does not end at the bottom of the page.
IMD Operations

IMD Operations File #009 The Billionaire Landlords

Forty-one hours before a public housing hearing, the billionaire landlords struck. The tenants’ evidence site disappears. Rent records. Eviction notices. Maintenance complaints. Photos of mold, broken heat, and ignored repairs. The proof was there. Then the domain was suspended. The landlords call it compliance. The families call it burial. But IMD sees the fracture. The Analyst follows the harm. The Coder traces the system chain. The Operator forces exposure. Behind the seizure is The Council: The Technologist, The Financier, The Merchant, The Architect, and The Narrator. They do not need to meet. They do not need to coordinate. The system does that for them. When systems designed to protect people begin protecting power— IMD activates: Integrity. Morality. Decency.

IMD OPERATIONS // FIELD FILES

Start the Operation

Watch the files in order. Each operation exposes another part of the machine.

Start File 001
0 of 12 files completed
Files 001–010
FILE 001 Still to see

The Housing Auction

The housing auction file #001 IMD Operations helps an elderly couple pushed toward foreclosure during a medical emergency while a hidden system…

Watch File 001
FILE 002 Still to see

The Loan Denial Algorithm

The Loan Denial Algorithm | IMD Operations File 002 A man qualified for the mortgage. The algorithm said no. IMD Operations File…

Watch File 002
FILE 003 Still to see

Who Controls the System

Who Controls the System Systems do not run the modern world by accident. Someone built them. IMD Operations File 003 — Who…

Watch File 003
FILE 004 Still to see

The Algorithm Denied His Life

A doctor prescribed the treatment. The algorithm denied his life. Not because it wouldn’t work. Because an algorithm decided the patient wasn’t…

Watch File 004
FILE 005 Still to see

He Lied Legally

He took an oath. He lied legally. And nothing happened. In this IMD Operation, public funds are not stolen… they are redefined.…

Watch File 005
FILE 006 Still to see

The Property Tax Trap

A retired couple falls behind on property taxes during a medical crisis. The property tax trap. What follows is not chaos. It…

Watch File 006
FILE 007 Still to see

The Credit Score Collapse

A man misses one payment. Then, the credit score collapse. The system recalculates. His credit score drops. Housing disappears. Loan access vanishes.…

Watch File 007
FILE 008 Still to see

The Childcare Network

A family does everything right. They work. They plan. They pay. But the childcare network system was never built around care. In…

Watch File 008
FILE 009 Still to see

The Billionaire Landlords

Forty-one hours before a public housing hearing, the billionaire landlords struck. The tenants’ evidence site disappears. Rent records. Eviction notices. Maintenance complaints.…

Watch File 009
FILE 010 Still to see

The Survivor Protocol

IMD was never a room. It was never a group of hackers. It was a counter-system. In File 010: The Survivor Protocol,…

Watch File 010
FILE 011 Still to see

The Coder Awakens

“Yesterday was brutal. The whole team has been killed and slaughtered. The office is destroyed. They took everything. They mashed all the…

Watch File 011
FILE 012 Still to see

The Union Breaker

IMD Operations File #012: The Union Breaker — Part 1 IMD Operations File 012: The Union Breaker Part 1 — The Store…

Watch File 012

The Billionaire Landlords

Forty-one hours before a public housing hearing, the billionaire landords struck. The tenants’ evidence site disappears. Rent records. Eviction notices. Maintenance complaints. Photos

Not A Real Publisher LLC… production

Mark Bertrand presents IMD Operations.

The website did not sell products.

It did not sell subscriptions.

It did not sell hope.

It held evidence.

Rent increases.

Eviction notices.

Maintenance complaints.

Emails from property managers.

Photos of mold.

Photos of broken heat.

Photos of children sleeping under coats in apartments owned by men who never had to know their names.

The site was built by tenants.

Single mothers.

Retired workers.

Disabled veterans.

Immigrants who paid every month and still lived one algorithm away from the street.

For seven months, they uploaded proof.

For seven months, they organized.

For seven months, they prepared for one public hearing where the city would finally have to see what billionaire ownership had done to ordinary lives.

Then, forty-one hours before the hearing, the domain disappeared.

Not hacked.

Not debated.

Not judged.

Suspended.

A complaint had been filed.

A policy had been triggered.

A registrar had acted.

The site went dark.

The evidence vanished.

The tenants refreshed the page until their phones died.

The landlord consortium released a statement before noon.

They called the site misleading.

They called the tenants confused.

They called the disappearance a technical matter.

The families called it what it was.

A burial.

This is IMD Operations.

IMD is not a group of hackers.

IMD is a counter-system.

Three roles.

Always present.

The Analyst.

The Coder.

The Operator.

They don’t guess.

The Analyst identifies the fracture.

The Coder traces how one decision becomes many.

The Operator acts precisely.

And when systems designed to protect people begin protecting power—

IMD activates.

Integrity.

Morality.

Decency.

Episode File #009.

The Domain Seizure.

IMD Operations in process.

The Council did not appear on camera.

They never do.

The Technologist had already built the machinery.

A complaint form.

A risk flag.

A suspension protocol.

One button that could silence thousands.

The Financier had already measured the value of silence.

Every delayed hearing meant another month of rent.

Another late fee.

Another family pressured into leaving before the record became public.

The Merchant understood the inventory.

Homes were not homes.

They were units.

Tenants were not people.

They were yield behavior.

The Architect had shaped the legal maze.

Private ownership.

Third-party registrar discretion.

Terms of service.

Trademark language.

Jurisdiction folded inside jurisdiction until no ordinary citizen could find the door.

And The Narrator performed the final cruelty.

He gave theft a professional voice.

Brand protection.

Community safety.

Policy enforcement.

Platform integrity.

That was how billionaires prayed over a machine after feeding it human beings.

The Analyst entered first.

Not through the website.

Through the harm.

Three thousand two hundred families.

Seventeen apartment complexes.

Nine shell companies.

One ownership group.

Rent spikes in the same month.

Eviction notices in the same week.

Complaint withdrawals after private settlement offers.

Public records delayed.

Inspection reports missing.

And now the evidence site removed before the first public hearing that could connect all of it.

The Analyst marked the fracture.

The harm was not the domain.

The harm was memory.

The system had not deleted a website.

It had deleted the place where ordinary people became undeniable.

Then The Coder entered.

Not to break the system.

But to move through it.

The complaint had come from a legal vendor.

The legal vendor served a holding company.

The holding company served a real estate trust.

The trust held properties through separate entities.

Separate names.

Separate addresses.

Separate liabilities.

One billionaire family office sat behind them all.

Nothing illegal on the surface.

That was the genius of it.

Evil no longer needed a dark room.

It needed subsidiaries.

The Coder traced the sequence.

Complaint filed at 1:06 a.m.

Domain locked at 1:11.

Evidence site offline at 1:14.

Tenant email list disrupted at 1:22.

Search result removed from the first page by morning.

Paid ads purchased by the landlord consortium before breakfast.

Public statement issued by noon.

The Council had not silenced the tenants by shouting over them.

They had removed the room.

The Coder found the second layer.

The complaint claimed trademark misuse.

But the disputed phrase was not a trademark.

It was the name of the apartment complex.

The tenants used it because they lived there.

The system accepted the complaint anyway.

Because the complaint came dressed in money.

And money is the oldest password in every modern system.

The Operator moved last.

Not loudly.

Not publicly.

Precisely.

The evidence was mirrored.

The chain of ownership was mapped.

The false complaint was documented.

The registrar’s timing was exposed.

The paid search campaign was captured.

The shell companies were connected.

The tenant affidavits were sealed into a release packet with one sentence at the top:

This was not enforcement.

This was suppression.

The Operator did not send it to one place.

One place could be ignored.

The packet went to the city clerk.

The housing committee.

The state attorney general’s office.

Three local reporters.

Two national housing journalists.

Every tenant attorney already preparing for the hearing.

And then IMD did the one thing The Council fears most.

It made the invisible alignment visible.

By sunset, the mirror site was live.

By nightfall, the ownership map was circulating.

By morning, the landlord consortium’s statement had collapsed under its own timing.

At the hearing, the tenants did not arrive as scattered complaints.

They arrived as a record.

Names.

Dates.

Receipts.

Photos.

Rent histories.

Emails.

Eviction notices.

A map of ownership showing one empire pretending to be seventeen separate landlords.

The Council had tried to erase the witness stand.

IMD rebuilt it in public.

The hearing did not fix housing.

No single hearing ever does.

The rents did not fall by magic.

The mold did not vanish.

The billionaires did not discover shame.

But for one day, the machine failed to hide its hand.

For one day, tenants were not isolated.

For one day, wealth had to answer with lights on.

And that matters.

Because systems survive by convincing the injured they are alone.

IMD broke that lie.

Across the network, The Council adjusted.

The Technologist rewrote the complaint filter.

The Financier recalculated delay.

The Merchant looked for weaker tenants.

The Architect prepared a cleaner policy.

The Narrator changed the language from suppression to safety.

They were not finished.

Predators never are.

They only learn where the fence shocked them.

IMD Operation complete.

The domain returned.

The evidence survived.

The hearing proceeded.

The tenants were seen.

Not saved.

Not yet.

Seen.

And sometimes, in a system built to erase people, being seen is the first act of war.

The machine will try again tomorrow.

The story is fiction.

The system is real.

The investigation continues in The Reader’s Court.

reckoning by MARK BERTRAND book cover image

Reckoning

Ebook purchase now image
paperback purchase now image
Connected evidence

Continue the Operation

The investigation does not end at the bottom of the page.
IMD Operations

IMD Operations File #008 The Childcare Network

A family does everything right. They work. They plan. They pay. But the childcare network system was never built around care. In this episode of IMD Operations, we expose how childcare has been turned into a network of extraction—where waitlists become leverage, staffing becomes strain, and stability becomes something families must constantly fight to keep. This isn’t a failure. It’s design. IMD steps in to reveal how the system operates beneath the surface—and what happens when that system is forced into the light. IMD Operations in process.

IMD OPERATIONS // FIELD FILES

Start the Operation

Watch the files in order. Each operation exposes another part of the machine.

Start File 001
0 of 12 files completed
Files 001–010
FILE 001 Still to see

The Housing Auction

The housing auction file #001 IMD Operations helps an elderly couple pushed toward foreclosure during a medical emergency while a hidden system…

Watch File 001
FILE 002 Still to see

The Loan Denial Algorithm

The Loan Denial Algorithm | IMD Operations File 002 A man qualified for the mortgage. The algorithm said no. IMD Operations File…

Watch File 002
FILE 003 Still to see

Who Controls the System

Who Controls the System Systems do not run the modern world by accident. Someone built them. IMD Operations File 003 — Who…

Watch File 003
FILE 004 Still to see

The Algorithm Denied His Life

A doctor prescribed the treatment. The algorithm denied his life. Not because it wouldn’t work. Because an algorithm decided the patient wasn’t…

Watch File 004
FILE 005 Still to see

He Lied Legally

He took an oath. He lied legally. And nothing happened. In this IMD Operation, public funds are not stolen… they are redefined.…

Watch File 005
FILE 006 Still to see

The Property Tax Trap

A retired couple falls behind on property taxes during a medical crisis. The property tax trap. What follows is not chaos. It…

Watch File 006
FILE 007 Still to see

The Credit Score Collapse

A man misses one payment. Then, the credit score collapse. The system recalculates. His credit score drops. Housing disappears. Loan access vanishes.…

Watch File 007
FILE 008 Still to see

The Childcare Network

A family does everything right. They work. They plan. They pay. But the childcare network system was never built around care. In…

Watch File 008
FILE 009 Still to see

The Billionaire Landlords

Forty-one hours before a public housing hearing, the billionaire landlords struck. The tenants’ evidence site disappears. Rent records. Eviction notices. Maintenance complaints.…

Watch File 009
FILE 010 Still to see

The Survivor Protocol

IMD was never a room. It was never a group of hackers. It was a counter-system. In File 010: The Survivor Protocol,…

Watch File 010
FILE 011 Still to see

The Coder Awakens

“Yesterday was brutal. The whole team has been killed and slaughtered. The office is destroyed. They took everything. They mashed all the…

Watch File 011
FILE 012 Still to see

The Union Breaker

IMD Operations File #012: The Union Breaker — Part 1 IMD Operations File 012: The Union Breaker Part 1 — The Store…

Watch File 012

The Childcare Network

But the childcare network system was never built around care. In this episode of IMD Operations

Not A Real Publisher LLC production

Mark Bertrand presents IMD Operations.

Two parents keep their jobs.
Their child loses stability.

The center is licensed.
The payments are made.
The waitlist is long.
The promise is simple.

Care.

But the promise does not hold.

This is IMD Operations

When systems built to protect people begin protecting power, IMD activates three principles.

Integrity.
Morality.
Decency.

This operation is File #008.
The Childcare Network.

Operation briefing.

The modern economy makes a quiet demand.

Both parents must work.

But work requires care.
And care has been turned into a market.

Not a public guarantee.
Not a shared structure.

A market.

Where access depends on price.
Where stability depends on margin.
Where children become units moving through a system designed for throughput, not attention.

The Council never has to say it aloud.

The Technologist builds enrollment systems that rank and filter.
The Financier structures ownership, extracting yield from centers that cannot afford to fail.
The Merchant prices care as a necessity families cannot refuse.
The Architect creates deserts, waitlists, and limited supply.
The Narrator explains that parents must plan better.

They do not need to meet.

The system does that for them.

A family applies before the child is born.
They wait.
They call.
They accept the only available slot.

The center is clean.
The staff is kind.
The ratios are legal.

On paper.

Behind the paper, the system moves differently.

Staffing shifts stretch beyond what attention can hold.
Turnover becomes constant because wages cannot sustain the workers providing the care.
Rooms fill faster than they empty.
Incidents are recorded, then softened, then buried in language that protects compliance.

Nothing in the report sounds like harm.

That is the design.

A mother receives a message that the center is closing early due to staffing shortages.
A father leaves work again, knowing the next absence will not be forgiven.
A child is moved between caregivers who do not have time to know their name before the day ends.

The family adjusts.

Then adjusts again.

Then breaks.

Not in one moment.

In accumulation.

Missed work becomes lost income.
Lost income becomes risk.
Risk becomes penalty.

The system calls this instability.

The system does not call itself the cause.

This is the network.

Not one bad center.
Not one careless worker.

A structure where care exists only as long as it remains profitable to provide it.

This is where IMD enters.

The Analyst identifies the fracture.

Not the parent.
Not the child.

The fracture.

The exact point where care becomes throughput.
Where responsibility becomes margin.
Where a child’s presence is converted into a revenue unit moving through a constrained system.

The Coder enters next.

Not to break the system—
but to move through it.

Enrollment algorithms.
Subsidy pathways.
Staffing ratios versus actual presence.
Incident reporting language.
Ownership structures linking multiple centers under financial control.
Waitlist manipulation tied to pricing tiers.
Public funding routed through private operators with invisible constraints.

One center shows strain.
Ten centers suggest pressure.
Hundreds reveal design.

The records do not show failure.

They show alignment.

Centers with the lowest wages have the highest turnover.
Centers with the highest turnover have the highest incident rates.
Incident rates decline on paper after internal review.
Subsidy funds stabilize the system, but only enough to maintain operation—not enough to create safety.

The machine is not breaking.

It is holding exactly where it is designed to hold.

The Operator acts.

Not loudly.
Not publicly.

Precisely.

Internal guidance surfaces.
Staffing records are placed beside incident timelines.
Subsidy allocations are matched against executive compensation.
Parent communications are aligned against internal risk language.

The distance between care and control becomes visible.

And then the wound lands.

Not in private.

In daylight.

A hearing room.
A regulator reading internal staffing notes.
A reporter holding two documents side by side—one describing compliance, the other describing reality.
A spokesperson repeating the language of safety while the data refuses to cooperate.

For a moment, the machine loses control.

Not of the centers.
Not of the money.

Of the narrative.

The public sees what it was never meant to see.

That the waitlists were not just demand.
They were leverage.
That the shortages were not temporary.
They were structural.
That the instability parents were blamed for navigating
was produced by the system itself.

The Technologist is trapped inside the logic.
The Financier holds position without explanation.
The Narrator reaches for reassurance and finds the story no longer holds.

The Council is not defeated.

It is embarrassed.

Because the illusion has been broken in public.

Care was never the product.

Stability was.

And stability was never delivered.

IMD Operations in process.

Integrity.
Morality.
Decency.

Protocol activated.

The records hold.
The pattern holds.
The testimony bends.
The documents do not.

One family did not fail to plan.
One child was not lost in a single mistake.
One center did not collapse in isolation.

A network made the choice.

A clean network.
A respectable network.
A legal network.

And now it has been seen.

This is how the machine is wounded.

Not when it is criticized.
When it is understood.

Not when people complain.
When the architecture becomes legible.

That is why The Council will strike back.

Because humiliation teaches power nothing except adaptation.

The next move will not arrive as anger.
It will arrive as refinement.
New language.
Stronger narratives.
Better insulation between harm and visibility.

That is how the machine survives exposure.

It studies the wound.

IMD Operation complete.

The machine will try again tomorrow.

The story is fiction.
The system is real.

The investigation continues in The Reader’s Court.

This Could Be Itby MARK BERTRAND book cover image of the gamma field striking the dome city and the countdown to the end encircling the whole of the city

THIS COULD BE IT

Ebook purchase now image
Connected evidence

Continue the Operation

The investigation does not end at the bottom of the page.