Industry, team, systems
What type of business, which systems were involved and where decisions had to be made.
Projects
Anonymous examples from AI, ERP, RIVILE, automation, warehouse, data and IT strategy work. Each case shows the business outcome, the delivery risk and what can be reused in another company.
How to read the case studies
This model helps compare your situation: industry, problem, my role, outcome and the lesson that can be reused in another company.
What type of business, which systems were involved and where decisions had to be made.
Manual work, data, vendors, ERP/RIVILE, warehouse, AI knowledge or project governance.
Beyond recommendations: process clarification, decision preparation, vendor coordination and adoption.
Lower stock levels, clearer data, faster decisions, less manual work or a safer AI start.
Where to start, what not to buy too early and which first sprint fits the situation.
Themes
Problems

Employee questions, internal documents, and Microsoft 365 SSO connected into a safe AI usage model.

A roadmap for a growing company that needed clearer systems, vendors, risks, and priorities.

Warehouse logic, mobile work, QR codes, and less manual effort in goods movement.

Rules, reporting, and ordering logic that helped reduce stock and manage turnover.

Order across 800k files and a stronger foundation for AI usage.

Sales and HR processes connected with RIVILE, BSS, and SharePoint.
Mini project library
These are not fictional promises. They are short examples from real work, showing the problems I most often help solve and where a useful conversation usually starts.
A CRM, ERP, and BSS process map: fields, ownership, test scenarios, and less double entry.
Related case studyNot just a technical API connection: data fields, business rules, exception handling, and vendor ownership.
Related directionLocations, QR codes, goods flow, and test scenarios before mobile warehouse work starts.
Related case studyClear owners, structure, access, and document logic before AI is used with company knowledge.
Related case studyRequests, rules, approvals, exception handling, and reporting in one controlled flow.
Related directionA requirements map, process priorities, proposal comparison, and a clearer decision before investment.
Related directionAligning sales stages, reporting, ownership, and integrations across multiple teams and markets.
Related case studyConsistent sources, clear metric owners, and fewer arguments about which report is correct.
Related insightMin/max logic, turnover, supplier lead times, and clearer reorder signals with measurable impact.
Related case studyPractical scenarios, security rules, M365 sign-in, and responsible use in daily work.
Related directionHow to use this
The project examples help identify whether the issue sits in process, data, systems, vendors, or ownership. In the first conversation we choose the direction: audit, sprint, implementation leadership, or a few practical decisions.
No inflated promises, no unnecessary system replacement, with clear priorities and ownership.
Start with a diagnostic callAdded from practice
These examples safely anonymize project experience across integrations, automation, supplier selection and data governance.

CRM · ERP · integrations
When sales, operations, finance and service teams use different systems, integration must connect real work, not only technical fields.

Automation · audit trail
Manual work often hides more than time waste. It hides unclear responsibility, missing approvals and weak process history.

Suppliers · decision support
When buying a system or integration, the cheapest proposal is not always the safest path. The real question is who can deliver the operating result.