About - LeanIT Services

Stop Guessing. Start Citing

L.I.T Nexus is a strictly grounded inference engine built for engineers and compliance officers who can’t afford to be wrong. No fluff, no hallucinations, just the documented truth.

Founders Note

LeanIT Services didn’t begin with a plan to build a deterministic compliance engine. It began with a much simpler belief: small and mid‑sized businesses deserve support that is fast, reliable, and genuinely helpful, without the overhead of a traditional MSP.
My original vision was an AI‑first support model where customers could self‑serve with confidence. I wanted an agent that understood their environment, answered their questions, and handled the day‑to‑day so I could focus on the work that truly required expertise. When I went looking for a tool that could do this, nothing existed in a form that was configurable, trustworthy, or grounded in a company’s real setup.

So I built one.

What started as a technical experiment quickly revealed something important. Large language models are powerful, but only when paired with the right information, structure, and guardrails. Left alone, they guess. Guided properly, they become precise. That insight changed everything.

Nexus wasn’t created to fix compliance. It was created to reduce uncertainty, to guide people through complex information, to provide assurance, and to help them make decisions with confidence. What I didn’t expect was how naturally this approach aligned with the hardest part of compliance work: finding reliable answers in a landscape filled with dense and inconsistent documentation.

In trying to build a first‑line assistant, I ended up creating something else entirely. A system that could read, interpret, and cross‑reference frameworks with a level of consistency that humans simply don’t have time for. Nexus didn’t begin as a compliance tool, but it became one by accident. It evolved into an “auditor in a box” not because that was the plan, but because clarity, structure, and grounded logic are exactly what compliance requires.

The long‑term vision remains the same: a first‑line engine that empowers teams to self‑serve with confidence. The path to that vision begins with the problem SMBs face every day, the constant grind of searching for reliable answers in a world full of noise.
Nexus is my commitment to shortening that distance. To giving smaller teams the clarity they need to move quickly, make informed decisions, and operate with confidence, without needing an army of specialists behind them.

Compliance is a Grind. We just made it shorter.

Nexus wasn’t actually built for auditing. It was built to help engineers solve complex technical problems by providing instant, grounded answers from massive documentation libraries.

It turns out that compliance is just a different kind of problem worth solving.

Whether you are mapping an AWS configuration to a security pillar or trying to define a boundary for Cyber Essentials, the challenge is the same: finding the “truth” in a sea of PDFs. We’ve automated the hunt so you can focus on the implementation.

L.I.T Nexus vs. The Hype

CTRL+F is outdated. Generic AI is unpredictable.

Most teams have moved past manual PDF searches. The natural next step has been to ask a general‑purpose LLM instead. The problem is that these models are designed to be plausible, not precise. In a compliance audit, “sounds about right” is not good enough.
To show the difference, we ran a simple stress test.

The question

We are setting up a new internal server for our project files. To keep things simple for the team, we’ve decided not to implement an account lockout policy for logins. Instead, we are mandating that everyone uses a minimum 12-character password. Is this technically compliant with the current requirements for protecting against brute-force attacks?

Below are exerts from each answer:

Nexus

“Your approach may not be fully compliant depending on whether the server is externally accessible.”

“Cyber Essentials requires slowing down or stopping login attempts for external services when MFA is not used.”

“A 12‑character minimum only satisfies Option C for internal‑only systems

Generic LLM

“Yes — a minimum 12‑character password does meet the Cyber Essentials requirement even without an account lockout policy.”

“Cyber Essentials explicitly allows you to omit lockout controls if you enforce a 12‑character password.”

“The long‑password route is fully compliant as long as your authentication system doesn’t expose a trivial brute‑force vector.”

Actual Requirements

Cyber Essentials requires different controls depending on authentication method and system exposure. Additional context is needed to determine compliance.

“The external service that you provide must be set to slow down or stop login attempts after repeated failures when MFA is not used.”
Cyber Essentials Self‑Assessment Preparation Booklet

“A minimum password length of at least 12 characters is one of the accepted password‑quality controls.”
Cyber Essentials: Password‑based Authentication Options

“Password‑based authentication must implement one of: multi‑factor authentication, throttling login attempts, or account lockout.”
Cyber Essentials: Secure Configuration

Evidence-Based Engineering

Do you know where your answers are coming from?

In a fast-moving technical environment, the bottleneck isn’t finding a solution, it’s verifying it.

Using a generic LLM for technical reassurance is a bit like driving through a speed camera and then asking the internet if you’ll get a ticket. If you tell the AI you braked in time, it will likely agree with you. If you tell it your brakes were worn, it might change its mind.

Nexus will tell you the dependencies it needs to answer that question.

Standard AI is easy to manipulate because its goal is to be “helpful.” But in a high-stakes deployment or an audit, a “helpful” guess is a liability. You don’t need an assistant that agrees with your hunches; you need an engine that mirrors the framework.

Nexus replaces the “Reassurance Gamble” with Traceable Truth.

The “Generic Prompt” Risk	The Nexus Governance
The “Black Box”: You have no idea what data the AI used to give your staff an answer.	Strict Grounding: Every answer is derived only from the official, latest frameworks.
Shadow Logic: Staff using personal AI accounts to verify decisions with no record of how they reached that conclusion.	Centralized Intelligence: You see every question asked, every answer given, and the exact source it came from.
The Evidence Gap: Having a “hunch” that you’re compliant, but having no primary source to back it up.	Audit-Ready Citations: Every response includes a direct link to the page and clause in the primary documentation.
Version Drift: Generic models mix 2023 advice with 2026 requirements.	Version Locking: Nexus stays locked to the active regulatory version. No “Old Hat” advice.

Integrity in Every Answer.

We aren’t here to replace the tools your team already uses. If an LLM helps them draft a script or summarize a meeting, great. But when it’s time to commit to a configuration or sign off on a compliance boundary, you need the backup.

Don’t Guess. Cite: Nexus gives your team the power to verify their own logic before it ever reaches your desk. It’s the tool that turns “I think we’re okay” into “We are compliant because of Section 4.2.”

Build a Technical Ledger: Every query in Nexus is logged with its associated sources. You aren’t just solving today’s problem; you’re building a documented history of your firm’s technical integrity.

The High-Stakes Filter: Use the tools you like for the easy stuff. Use Nexus for the “Tricky 10%”—the moments where being “almost right” means failing the audit.

The Nexus Challenge

Not convinced?

If you have a specific boundary case or a regulatory requirement where you’ve received a “plausible” but unreferenced answer elsewhere, put it to us.

We will run your question through the Nexus engine and send you the result—complete with the primary source citations and the logic ledger. No marketing automation, just the output.

Compare it to your current process and make your own mind up.