Most IBM i teams already know where the recovery risk is. What they often lack is a number finance can act on.
Start with two: cost per hour of downtime, and how much lost work staff could realistically recreate.
🔗nalashaa.com/as400-disaster-…
#IBMi #AS400 #DisasterRecovery
9
The EU Cyber Resilience Act’s first duties are already in force.
If your software is sold or installed in the EU, you may now face a 24-hour reporting clock.
🔗nalashaa.com/does-eu-cyber-r…
#CRA #ProductSecurity
13
Only 6% of organizations trust AI agents to run core processes end to end.
The risk is bigger than a bad answer. An agent can change records, send messages, or trigger payments.
🔗nalashaa.com/llm-guardrails-…
#AIAgents
7
AAIS Farmowners filings used to swallow entire weekends for a Wisconsin insurer. We built them a reporting layer on IBM i that validates every record before upload, without touching the core AS/400.
See how : nalashaa.com/case-studies/re…
#AS400 #IBMi #InsurTech
26
Adding an AI assistant to an existing web app is not a RAG vs fine-tuning decision. It is a question of which job the assistant has to do, in which order, under which permissions. Start with the jobs. The pattern follows.
🔗nalashaa.com/rag-fine-tuning…
#AI #ProductEngineering #RAG
14
Legal automation isn’t about replacing lawyers. It’s about reclaiming the hours they lose to admin, so judgment lands where it matters. We broke down where RPA and AI actually fit in legal workflows, and where they shouldn’t.
Read more: nalashaa.com/automation-in-l…
#LegalTech
12
The most useful thing to know about AI in Business Central: it does not repair a messy ERP. It reveals one. The teams getting real value from Copilot and agents are the ones who fixed their data, permissions, and dimensions first.
🔗nalashaadigital.com/blog/ai-…
#BusinessCentral
11









































