PageSourceSearch

https://xedrum.com/_next/static/chunks/169-72bda6c1623c51df.js

js xedrum.com collected 2026-10-09 00:02:57 UTC 34,873 bytes, 1 lines download raw bytes

1"use strict";(self.webpackChunk_N_E=self.webpackChunk_N_E||[]).push([[169],{4691:(e,a,t)=>{t.d(a,{HO:()=>c});var i=t(5048);let n={id:i.t7.caseStudies.aiFashion,title:"AI-Fashion Social Mobile App",heroTitle:"AI Fashion Social Mobile App: From Inherited Code to Production",websiteUrl:"https://dribbble.com/shots/25426350-Fashion-E-Commerce-mobile-app",overviewTitle:"From Legacy Code to a Production-Ready Social Ecosystem",description:"A Berlin-based fashion social mobile app for enthusiasts to share outfits, discover styles, and interact through core social features with AI-powered tagging.",tags:["Mobile App","Social Media","AI/LLM","iOS","Beta"],goals:["Complete and stabilize inherited codebase","Implement AI-assisted tagging via LLM API","Ship production-ready mobile experience","Build scalable infrastructure with cost trade-offs"],images:{preview:"/images/content/case-studies/ai-fashion-social-mobile-app/preview.webp",hero:"/images/content/case-studies/ai-fashion-social-mobile-app/hero.webp",secondary:"/images/content/case-studies/ai-fashion-social-mobile-app/secondary.webp",cards:"/images/content/case-studies/ai-fashion-social-mobile-app/cards-group.webp",showcase:"/images/content/case-studies/ai-fashion-social-mobile-app/showcase.webp"},caseCardBgSrc:"/images/content/case-studies/ai-fashion-social-mobile-app/preview.webp",industry:"Fashion/Social Media",location:"Germany, Berlin",size:"4 people",duration:"Ongoing",budget:"$25K",projectOverview:"We partnered with a Berlin-based founder building a fashion social mobile app for enthusiasts to share outfits, discover styles, and interact through core social features. Xedrum provided a dedicated product team (4 people) to take over existing early work, complete the MVP, implement an AI-powered tagging feature via an LLM API, and bring the product to production-ready quality. A key milestone was delivering a working beta to Apple TestFlight within a defined timeframe and budget, while preparing scalable infrastructure for growth.",ourApproachTitle:"How We Stabilized the Codebase & Shipped AI-Powered Tagging",ourApproach:"This was a startup-style engagement: move fast, ship a stable beta, and design the architecture to scale without burning money. Our approach focused on: Completing and stabilizing an inherited codebase, improving maintainability and delivery speed. Implementing AI-assisted tagging (LLM API) to improve content organization and discovery. Shipping a production-ready mobile experience, aligned with social app expectations (feeds, profiles, interactions). Building scalable infrastructure with cost trade-offs in mind (ready to grow, but lean for early-stage usage). Setting up monitoring and maintenance workflows to keep the app stable post-launch. Staying highly responsive to a startup environment with flexible hours and proactive problem solving. When issues appeared (including developer fit), we handled it quickly by swapping developers fast and smoothly, keeping delivery on track.",problemTitle:"Challenges in Scaling Content Discovery & Stability",problem:"The founder needed a reliable partner to: Add a meaningful AI feature (not 'AI for hype'), specifically automatic tagging to help users categorize and discover fashion content. Take over partially completed work from another developer and finish the MVP. Deliver a working beta quickly, without sacrificing core quality. Build an infrastructure that would be scalable, but still optimized for early-stage budgets. Ensure ongoing maintenance, monitoring, and feature rollouts as the product evolves.",solution:{title:"Working Beta and Product Foundation",description:"We delivered a working beta and product foundation that included:",features:[{title:"AI-Powered Tagging (LLM Integration)",description:"We implemented AI-driven tagging via an LLM API to support automatic tagging of user-generated fashion images/content, improved content organization and searchability, and better discovery experiences for users browsing styles and categories. This feature helped the app feel smarter and more 'social-feed ready' without requiring a complex custom ML pipeline at MVP stage."},{title:"Full-Stack Product Delivery",description:"We completed both frontend and backend development, turning early work into a cohesive product with stable performance and clean workflows."}
1,{title:"Scalable Infrastructure with Cost Trade-Offs",description:"We designed infrastructure to handle expected growth while keeping early-stage costs under control, with clear upgrade paths as traction increases."},{title:"Monitoring + Maintenance Setup",description:"We set up monitoring and support processes to detect issues early and keep the app stable during testing and rollouts."},{title:"Ongoing Feature Rollouts + Startup Guidance",description:"We supported the founder with best-practice advice, product decisions, and a flexible roadmap approach as priorities shifted."}]},outcome:"Delivered a working app on Apple TestFlight within the planned timeframe and budget. Strong client feedback around proactivity, responsiveness, and developer quality. Fast resolution when team adjustments were needed, keeping momentum without disruption."},r={id:i.t7.caseStudies.saasDashboard,title:"AI-powered SaaS Dashboard",heroTitle:"AI-Powered SaaS Marketing Dashboard for Advertising Analytics",overviewTitle:"Centralizing Marketing Intelligence for Agency Growth",websiteUrl:"https://zendash.com/",description:"A high-performance analytics platform that automates marketing reporting by aggregating data from major ad networks into a unified AI-driven intelligence hub.",tags:["SaaS","MarTech","Node.js","React","PostgreSQL"],goals:["Automate cross-platform data collection and normalization","Develop a unified attribution model for blended ROAS tracking","Build a scalable reporting engine for marketing agencies","Implement AI-driven anomaly detection for ad spend optimization"],images:{preview:"/images/content/case-studies/ai-powered-saas-dashboard/preview.webp",hero:"/images/content/case-studies/ai-powered-saas-dashboard/hero.webp",secondary:"/images/content/case-studies/ai-powered-saas-dashboard/secondary.webp",cards:"/images/content/case-studies/ai-powered-saas-dashboard/cards-group.webp",showcase:"/images/content/case-studies/ai-powered-saas-dashboard/showcase.webp"},caseCardBgSrc:"/images/content/case-studies/ai-powered-saas-dashboard/preview.webp",industry:"MarTech",location:"USA, New York",size:"6 people",duration:"8 months",budget:"$55K",projectOverview:"A marketing technology founder approached Xedrum to solve the 'spreadsheet nightmare' prevalent in digital agencies. The goal was to build a comprehensive SaaS solution capable of connecting to multiple marketing APIs (Meta, Google, TikTok), processing millions of rows of raw data, and presenting actionable insights through a high-performance dashboard. We focused on turning fragmented metrics into a 'single source of truth' for brands, allowing them to track real-time CAC and blended ROAS without manual effort.",ourApproachTitle:"How We Built a Unified AI Attribution Engine for Marketing Agencies",ourApproach:"Our technical strategy centered on a robust ETL (Extract, Transform, Load) pipeline and a lightning-fast data visualization layer. We implemented a resilient background worker system to manage complex API rate limits and ensure data freshness. On the backend, we designed a normalized PostgreSQL schema to unify disparate metrics into a consistent format. The frontend was built with custom-optimized React components to handle high-density charts without performance degradation. We followed a phased roadmap: 3 months for the core MVP and 5 months for advanced scaling and multi-tenant agency features.",problemTitle:"The Digital Marketing 'Spreadsheet Nightmare'",problem:"Digital marketing teams were struggling with extreme data fragmentation, where each platform used different attribution windows and naming conventions. This led to manual reporting errors, significant operational overhead (up to 20 hours per week per manager), and delayed decision-making. The challenge was to create a system that could normalize this data in real-time while maintaining 100% accuracy for financial reporting and budget allocation.",solution:{title:"Automated Intelligence for Performance Marketing",description:"We delivered a production-grade SaaS platform that acts as a centralized brain for marketing operations:",features:[{title:"Multi-Source API Orchestration",description:"Automated connectors for all major ad platforms and e-commerce stores. Data is synced hourly, ensuring that dashboards reflect the most current performance metrics."},{title:"Blended Metrics Engine",description:"A sophisticated calculation layer that aggregates spend and revenue across all channels to provide a holistic view of Marketing Efficiency Ratio (MER)."},{title:"Automated Agency Reporting",description:"A drag-and-drop report builder that generates professional, client-ready presentations automatically, saving teams hundreds of hours of manual labor."},{title:"AI Spending Guard",description:"An intelligent monitoring layer that uses machine learning to detect anomalies in ad performance and alert users to budget waste or tracking issues."},{title:"High-Performance Visualization",description:"Interactive, deep-drill dashboards designed to handle millions of data points while remaining intuitive for non-technical marketing managers."}]},outcome:"The platform successfully transitioned from a prototype to a commercial Sa
1aS. Within 6 months of launch, users reported an 85% reduction in reporting time and an average 15% improvement in ad spend efficiency. The system currently processes data for hundreds of ad accounts on a scalable AWS infrastructure with 99.9% uptime."},o={id:i.t7.caseStudies.agritechCloud,title:"Cloud-Based AI & ETL Platform for Agricultural Machine Learning",heroTitle:"Cloud AI & ETL Platform for Agricultural Machine Learning",websiteUrl:"https://www.osirix.co/",overviewTitle:"Scalable Infrastructure for Agricultural Intelligence",description:"A cloud-native system capable of orchestrating AI workloads, managing data pipelines, and storing results for an AgriTech company specializing in machine learning for field crop analysis.",tags:["AI/ML","Cloud Infrastructure","AWS","ETL","Data Pipeline"],goals:["Create robust execution layer for AI and data pipelines","Design modular system architecture on AWS","Support full lifecycle of AI workloads","Introduce strong observability and control mechanisms"],images:{preview:"/images/content/case-studies/cloud-ai-etl-platform-agriculture/preview.webp",hero:"/images/content/case-studies/cloud-ai-etl-platform-agriculture/hero.webp",secondary:"/images/content/case-studies/cloud-ai-etl-platform-agriculture/secondary.webp",cards:"/images/content/case-studies/cloud-ai-etl-platform-agriculture/cards-group.webp",showcase:"/images/content/case-studies/cloud-ai-etl-platform-agriculture/showcase.webp"},caseCardBgSrc:"/images/content/case-studies/cloud-ai-etl-platform-agriculture/preview.webp",industry:"AgriTech",location:"Israel",size:"3 people",duration:"3 months",budget:"$3
10K",projectOverview:"We collaborated with a European AgriTech company specializing in the application of machine learning and deep learning for field crop analysis. Their products relied on AI models that process large datasets and require reliable execution at scale. Xedrum was engaged to design and build a cloud-native system capable of orchestrating AI workloads, managing data pipelines, and storing results in a structured and accessible way. The goal was to create a stable backbone for current ML products while leaving room for future growth and experimentation.",ourApproachTitle:"AWS Architecture & ML Pipeline Design for AgriTech",ourApproach:"From the start, we approached this engagement as an AI infrastructure project, not just a backend implementation. Our focus was on: Creating a robust execution layer for AI and data pipelines, capable of handling compute-heavy jobs. Designing a modular system architecture on AWS that could later be adapted to other cloud providers if needed. Supporting the full lifecycle of AI workloads, from data ingestion to execution and output delivery. Introducing strong observability and control mechanisms for background jobs and long-running processes. Working in tight collaboration with the client’s technical leadership through structured sprints and regular reviews. Rather than over-optimizing for a single model or workflow, we built a flexible foundation that could support evolving AI use cases in agriculture.",problemTitle:"The Complexity of Orchestrating Large-Scale Agri-Data",problem:"The client needed a centralized system to: Trigger and manage ML and deep learning jobs in a consistent way. Process and store large volumes of agricultural data efficiently. Work with both relational and n
1on-relational data stores, depending on the workload. Schedule and monitor long-running jobs without manual intervention. Ensure the platform was stable, maintainable, and production-ready. Without this foundation, scaling AI solutions across different products and datasets would have been difficult and costly.",solution:{title:"Cloud-Based AI Execution Platform",description:"We delivered a cloud-based AI execution platform with the following capabilities:",features:[{title:"AI-Driven ETL and Workload Execution",description:"The system allows users to submit jobs via APIs, execute data-intensive AI workloads, and automatically persist results for downstream use. This created a repeatable and reliable workflow for running ML models in production."},{title:"Scalable AWS Infrastructure",description:"We built the platform using core AWS services such as EC2, AWS Batch, Lambda, S3, RDS (PostgreSQL), and DynamoDB. Each component was selected based on performance, scalability, and cost considerations."},{title:"Job Scheduling, Queueing, and Visibility",description:"Background jobs are scheduled and queued automatically, with monitoring in place to track execution progress, performance, and failures. This gave the team clear insight into system behavior at all times."},{title:"API-First System Design",description:"All core operations, including data upload, job execution, and result retrieval, are exposed through APIs. This made the platform easy to integrate with existing ML pipelines and future applications."},{title:"Operational UI",description:"We also delivered a lightweight user interface built with a modern frontend framework, allowing non-infrastructure users to monitor jobs and system status without touching cloud resources directly."}]},outcome:"A fully functional AI and ETL execution platform deployed on AWS. Reliable orchestration of machine learning and deep learning workloads. Centralized storage of outputs across object storage and databases. Predictable delivery through regular sprint planning and communication. Strong client confidence in the system design and technical execution."},s={id:i.t7.caseStudies.healthcareMvp,title:"AI-Powered Healthcare MVP for Patient Imaging Insights",heroTitle:"AI-Powered Healthcare MVP: Patient Imaging Insights",websiteUrl:"https://dock.health/",overviewTitle:"Empowering Patients through AI-Driven Clarity",description:"A New York-based healthcare MVP that helps patients better understand their medical imaging results through AI-assisted explanations in plain, human-readable language.",tags:["AI/ML","Mobile App","HIPAA","RAG"],goals:["Build HIPAA-aware AI architecture","Implement RAG architecture for verified medical sources","Create MVP to validate user demand","Prepare for clinician-in-the-loop workflows"],images:{preview:"/images/content/case-studies/healthcare-mvp-patient-imaging/preview.webp",hero:"/images/content/case-studies/healthcare-mvp-patient-imaging/hero.webp",secondary:"/images/content/case-studies/healthcare-mvp-patient-imaging/secondary.webp",cards:"/images/content/case-studies/healthcare-mvp-patient-imaging/cards-group.webp",showcase:"/images/content/case-studies/healthcare-mvp-patient-imaging/showcase.webp"},caseCardBgSrc:"/images/content/case-studies/healthcare-mvp-patient-imaging/preview.webp",industry:"Healthcare",location:"USA New York",size:"5 people",duration:"6 months",budget:"$35K",projectOverview:"A New York-based healthcare founder approached Xedrum to build a B2C healthcare MVP that helps patients better understand their medical imaging results. The core idea was simple but powerful: Patients upload medical images such as X-rays or scans and receive AI-assisted explanations in plain, human-readable language. The goal was not to replace doctors, but to reduce anxiety, confusion, and unnecessary follow-up questions by helping patients interpret results before or after clinical visits. The product was designed as a mobile-first MVP, focused on speed to market, HIPAA-aware architecture, and future scalability.",ourApproachTitle:"Our HIPAA-Aware AI Architecture & RAG Implementation",ourApproach:"We treated this project as both a healthcare MVP and an AI product foundation, even though AI was not intended to be a final diagnostic authority. Our approach focused on: Building a HIPAA-aware AI architecture, ensuring secure handling of PHI, encrypted data storage, controlled access, and audit-ready workflows. Implementing a RAG architecture, allowing AI responses to be grounded in verified medical sources, guidelines, and structured knowledge rather than raw model output. Creating an MVP that could quickly validate user demand with real patients. Preparing the system for clinician-in-the-loop workflows, future clinical partnerships, and deeper AI validation. Instead of starting with heavy AI training or custom medical models, we focused on practical AI integration, strong prompt orchestration, and reliable workflows that could evolve over time.",problemTitle:"The Gap in Patient Imaging Interpretation",problem:"Patients regularly receive medical imaging results that are: Hard to understand without medical training, Delivered with minimal explanation, Stress-inducing and unclear, especially outside clinic hours. From the business side, the founder faced several challenges: Doctors and clinics don’t have time to answer repetitive patient questions, Building a healthcare product requires careful compliance and wording, Overpromising AI capabilities could create legal and trust risks, Speed mattered more than building a 'perfect' AI model from day one. The challenge was to balance AI usefulness with healthcare responsibility, while still delivering a compelling consumer experience.",solution:{title:"Healthcare MVP with AI-Assisted Insights",description:"We delivered a Healthcare MVP with AI-assisted insights, designed for clarity, safety, and future expansion.",features:[{title:"AI-Assisted Image Explanation",description:"Patients can upload X-rays or other medical images. The AI provides educational explanations in simple language, focusing on general observations and common patterns, always framed as informational and n
1ot diagnostic."},{title:"Smart Context Layer",description:"Users can add context such as symptoms or doctor notes. AI uses this input to tailor explanations and highlight what questions patients may want to ask their physician."},{title:"Medical-Safe AI Prompting",description:"We implemented a carefully structured AI layer that avoids diagnosis or treatment advice, uses disclaimers and healthcare-safe language, and prioritizes clarity over certainty. This made the AI useful while remaining compliant and trustworthy."},{title:"Clean Patient-First UX",description:"The app was designed for non-technical users with simple upload flow, clear visual feedback, and human-friendly explanations instead of medical jargon."},{title:"Scalable & Compliant Architecture",description:"HIPAA-aware data handling, secure cloud infrastructure, and modular backend ready for future AI model upgrades or clinician dashboards."}]},outcome:"The founder received a production-ready MVP that validated patient demand for AI-assisted medical explanations, created a strong foundation for future AI improvements, and avoided regulatory and trust pitfalls common in health AI products. Most importantly, the product proved that AI in healthcare doesn’t need to diagnose to deliver real value. It can educate, guide, and empower patients when designed responsibly."},l=[s,n,o,{id:i.t7.caseStudies.ragSql,title:"RAG-Powered Natural Language to SQL for Accounts Payable Automation",heroTitle:"RAG NL-to-SQL: Natural Language Queries for Accounts Payable",websiteUrl:"https://caaps.com/",overviewTitle:"Democratizing Financial Data with Secure NL-to-SQL",description:"A proof of concept using RAG architecture to enable non-technical users to interact with accounting data through natural language queries translated into secure SQL.",tags:["RAG","AI/ML","FinTech","SQL","Azure OpenAI"],goals:["Design secure AI interface for financial SQL database","Implement RAG to ground AI output in database schema","Prioritize accuracy, safety, and auditability","Deliver fast PoC with production readiness path"],images:{preview:"/images/content/case-studies/rag-nl-to-sql-accounts-payable/preview.webp",hero:"/images/content/case-studies/rag-nl-to-sql-accounts-payable/hero.webp",secondary:"/images/content/case-studies/rag-nl-to-sql-accounts-payable/secondary.webp",cards:"/images/content/case-studies/rag-nl-to-sql-accounts-payable/cards-group.webp",showcase:"/images/content/case-studies/rag-nl-to-sql-accounts-payable/showcase.webp"},caseCardBgSrc:"/images/content/case-studies/rag-nl-to-sql-accounts-payable/preview.webp",industry:"Accounts Payable Automation",location:"Australia",size:"12 people",duration:"3 months",budget:"$15K",projectOverview:"We partnered with an Australia-based SaaS company operating in the Accounts Payable automation space to explore how AI could simplify and secure access to financial data stored in relational databases. The client’s objective was to validate whether Natural Language queries could be reliably translated into SQL, enabling non-technical users to interact with accounting data without writing queries. Xedrum was engaged to deliver a focused proof of concept using a production-aware, security-first architecture.",ourApproachTitle:"How We Built Secure Natural Language SQL with RAG & Azure OpenAI",ourApproach:"We approached this engagement as a RAG-driven AI data access project, rather than a generic NL-to-SQL experiment. Our focus was on: Designing a secure AI interface between natural language input and a financial SQL database. Implementing Retrieval-Augmented Generation (RAG) to ground AI output in database schema, metadata, and query rules. Prioritizing accuracy, safety, and auditability, critical for finance and accounting workflows. Delivering a fast PoC while maintaining a clear path to production readiness. Instead of relying on raw LLM output, we structured the system so the model reasons over retrieved schema context before generating SQL, significantly reducing errors and risk.",problemTitle:"The Data Access Barrier in Modern Accounting",problem:"For financial SaaS platforms, enabling easy data access introduces several challenges: Business users need insights but lack SQL expertise. Direct AI-to-database interaction can lead to unsafe or incorrect queries. Accounting data demands strict control, validation, and traceability. Any AI solution must integrate cleanly with existing cloud infrastru
1cture. The core challenge was proving that AI could generate accurate, secure SQL queries from natural language without compromising data integrity.",solution:{title:"RAG-Based NL-to-SQL PoC",description:"We delivered a working PoC and after MVP with the following capabilities:",features:[{title:"RAG-Based Natural Language to SQL",description:"A retrieval layer supplies the LLM with database schema and table relationships, column definitions and constraints, and predefined query boundaries. This context-driven approach enabled consistent, reliable SQL generation."},{title:"Secure Cloud Integration",description:"The solution integrated AWS RDS (SQL) as the data source and Azure OpenAI (GPT-4o) for language understanding and generation. Strict access controls ensured safe execution of generated queries."},{title:"API & Interface Layer",description:"We built a simple interface that accepts natural language questions, generates validated SQL statements, and returns structured results for downstream use."},{title:"Production-Aware Architecture",description:"Although delivered as a PoC, the system was designed with clear separation between AI, data, and execution layers, scalability and governance in mind, and readiness for future role-based access and logging."}]},outcome:"A successful NL-to-SQL proof of concept for Accounts Payable data. Secure and accurate SQL generation grounded in real schema context. On-time, on-budget delivery with clear and consistent communication. Strong alignment on long-term collaboration and product evolution."},{id:i.t7.caseStudies.ragFintech,title:"RAG-Powered Process Automation for a Fintech Platform",heroTitle:"RAG-Powered Process Automation for a UK Fintech Platform",overviewTitle:"Transforming Financial Operations with Intelligent Automation",websiteUrl:"https://www.kosli.com/",description:"A RAG-powered automation layer that enables teams to retrieve accurate information, automate internal workflows, and reduce manual processing across finance and operations.",tags:["RAG","FinTech","Process Automation","AI/ML","UK Compliance"],goals:["Design RAG architecture to ground AI in verified data","Automate repetitive operational workflows","Ensure UK financial compliance alignment","Deliver incremental value through automation"],images:{preview:"/images/content/case-studies/rag-process-automation-fintech/preview.webp",hero:"/images/content/case-studies/rag-process-automation-fintech/hero.webp",secondary:"/images/content/case-studies/rag-process-automation-fintech/secondary.webp",cards:"/images/content/case-studies/rag-process-automation-fintech/cards-group.webp",showcase:"/images/content/case-studies/rag-process-automation-fintech/showcase.webp"},caseCardBgSrc:"/images/content/case-studies/rag-process-automation-fintech/preview.webp",industry:"FinTech",location:"London, UK",size:"12 people",duration:"3 months",budget:"$15K",projectOverview:"We worked with a UK-based FinTech company providing digital financial services to small and mid-sized businesses. As the platform scaled, internal teams increasingly relied on large volumes of operational, transactional, and compliance-related data spread across multiple systems. Xedrum was engaged to design and deliver a RAG-powered automation layer that enables teams to retrieve accurate information, automate internal workflows, and reduce manual processing across finance and operations. The focus was on practical AI adoption, improving efficiency without disrupting regulated FinTech processes.",ourApproachTitle:"RAG Architecture & UK Financial Compliance Implementation",ourApproach:"We approached this project as a FinTech-grade AI automation initiative, where accuracy, traceability, and security were as important as AI capability. Our approach focused on: Designing a Retrieval-Augmented Generation (RAG) architecture to ground AI responses in verified internal data. Automating repetitive operational workflows using AI-assisted decision support. Ensuring the solution aligned with UK financial and compliance expectations. Delivering incremental value through automation, rather than replacing core systems. Instead of building a standalone AI feature, we embedded RAG directly into existing workflows to act as an intelligent operations layer.",problemTitle:"Manual Overload & Fragmented Data Challenges",problem:"As the FinTech platform grew, teams faced several challenges: Key information was fragmented across databases, internal documentation, and reports. Operations and finance teams spent significant time manually querying data and preparing summaries. Compliance-related questions required cross-checking multiple sources. Existing tools were powerful but not easily accessible to non-technical users. The client needed a way to automate data retrieval and decision support without exposing sensitive systems or introducing compliance risks.",s
1olution:{title:"RAG-Based Automation Solution",description:"We delivered a RAG-based automation solution designed specifically for FinTech operations:",features:[{title:"RAG-Powered Knowledge & Data Retrieval",description:"We implemented a RAG pipeline that retrieves structured data from internal databases, operational documentation and policies, and process-level metadata. The AI generates responses and summaries strictly grounded in retrieved sources, ensuring accuracy and auditability."},{title:"AI-Assisted Process Automation",description:"The system supports automation of internal operational queries, finance and reconciliation checks, and compliance-related information requests. This reduced manual effort and response time for recurring internal requests."},{title:"Secure, Controlled AI Access",description:"We implemented strict controls to ensure role-based access to data, separation between AI reasoning and data execution layers, and traceable outputs suitable for regulated environments."},{title:"API-First Integration",description:"The solution was integrated into existing systems via APIs, allowing teams to access AI-powered automation without changing their core workflows."},{title:"Production-Ready Architecture",description:"The system was designed with scalability in mind, clear logging and monitoring, and readiness for future expansion into customer-facing AI features."}]},outcome:"Reduced manual processing across finance and operations teams. Faster access to accurate, source-backed information. Improved consistency in compliance-related responses. A scalable AI automation foundation aligned with FinTech regulatory expectations."},r];l.map(e=>e.id);let c=()=>l},8431:(e,a,t)=>{t.d(a,{default:()=>u});var i=t(7066),n=t(1187),r=t(4423),o=t.n(r),s=t(3426),l=t(5608),c=t(5441),d=t(6790);let u=e=>{let{review:a,className:t=""}=e,{text:r,author:u,source:p,stars:g}=a,h=(0,s.useRef)(null),m=(0,s.useId)(),f=(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)("span",{className:"font-montserrat text-lg font-semibold leading-[1.35] tracking-[-2%] text-[#423F3F] truncate",children:u.name}),(0,i.jsx)("span",{className:"font-body font-normal text-sm leading-[1.43] text-gray-medium truncate",children:u.role})]});return(0,i.jsxs)("figure",{className:(0,l.cn)("group flex flex-col justify-between p-5 pb-7.5 gap-20 shrink-0","border border-[#EEEEEE] rounded-xl bg-white","transition-all duration-300 hover:shadow-[0_8px_30px_rgb(0,0,0,0.06)] hover:border-transparent focus-within:shadow-[0_8px_30px_rgb(0,0,0,0.06)] focus-within:border-transparent",p.link&&"cursor-pointer ",t),onClick:()=>{var e;return p.link&&(null==(e=h.current)?void 0:e.click())},children:[(0,i.jsxs)("div",{className:"flex flex-col gap-12",children:[(0,i.jsxs)("div",{className:"flex items-center justify-between gap-2.5 ",children:[g?(0,i.jsx)("div",{className:"flex items-center gap-0.5",role:"img","aria-label":"".concat(g," out of 5 stars"),children:Array.from({length:g}).map((e,a)=>(0,i.jsx)(c.I,{name:"star",className:"size-4.25 text-[#FCA006]"},a))}):(0,i.jsx)("div",{"aria-hidden":"true"}),(0,i.jsxs)("div",{className:"flex items-center justify-center p-2.5 text-black",children:[(0,i.jsxs)("span",{className:"sr-only",children:["Review on ",p.platform]}),(0,i.jsx)(c.I,{name:d.ll[p.platform],className:"h-4.5 w-auto"})]})]}),(0,i.jsx)("blockquote",{tabIndex:0,className:"font-body font-normal text-sm leading-[1.43] h-40 overflow-y-auto no-scrollbar text-gray-medium cursor-text focus-visible:ring-2 focus-visible:ring-green-primary/50",onClick:e=>e.stopPropagation(),children:(0,i.jsx)("p",{children:r})})]}),(0,i.jsxs)("figcaption",{className:"flex flex-row gap-2.5 items-center",children:[u.avatar?(0,i.jsx)(n.default,{src:u.avatar,alt:"",role:"presentation",width:45,height:45,className:"size-11.25 rounded-full object-cover"}):(0,i.jsx)(c.I,{name:"user",className:"text-gray-medium/20 size-11.25 rounded-full"}),p.link?(0,i.jsxs)(i.Fragment,{children:[(0,i.jsxs)("span",{id:m,className:"sr-only",children:["View original review on ",p.platform]}),(0,i.jsx)(o(),{href:p.link,target:"_blank",rel:"noopener noreferrer",ref:h,className:"flex flex-col min-w-0",onClick:e=>e.stopPropagation(),"aria-describedby":m,children:f})]}):(0,i.jsx)("div",{className:"flex flex-col min-w-0",children:f})]})]})}},9196:(e,a,t)=>{t.d(a,{J:()=>r});var i=t(7066);t(3426);var n=t(5608);let r=e=>{let{children:a,variant:t="default",className:r=""}=e;return(0,i.jsxs)("p",{className:(0,n.cn)("inline-flex items-center rounded-full whitespace-nowrap t-eyebrow shrink-0 w-fit",{default:"\n      text-black font-bold\n      gap-[0.6em] md:gap-[0.667em] \n      px-[0.8em] py-[0.4em] md:px-[1em] md:py-[0.583em]\n      bg-[linear-gradient(90deg,_#DEF1E4_0%,_rgba(255,255,255,0.11)_75%)]\n    ",hero:"\n      text-white font-bold md:font-medium\n      gap-[0.8em] md:gap-[0.667em]\n      px-[1.2em] py-[0.4em] md:py-[0.583em]\n      bg-[linear-gradient(45deg,_#A3D9B4_0%,_rgba(255,255,255,0)_75%)]\n    "}[t],r),children:[(0,i.jsx)("span",{className:"w-1 h-1 rounded-full shrink-0 bg-current","aria-hidden":"true"}),(0,i.jsx)("span",{children:a})]})}},9590:(e,a,t)=>{t.d(a,{A:()=>u});var i=t(7066),n=t(1187),r=t(3426),o=t(5608);let s={base:{w:400,h:514},"base-dark":{w:400,h:514},2:{w:364,h:336},3:{w:200,h:202},"group-1":{w:336,h:372},"base-cropped-1":{w:400,h:514},"base-cropped-2":{w:400,h:514}}
1,l={"float-x":"puzzle-float-x","float-y":"puzzle-float-y",none:""},c=(0,r.memo)(function(e){let{name:a,overlayName:t,className:r="",underlayClassName:c="",overlayClassName:d="",animation:u="float-y",...p}=e,g=t?"/images/ui/puzzles/puzzle-".concat(t,".webp"):"",h=s[a],m=t?s[t]:null,f=l[u]||"";return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.default,{src:"/images/ui/puzzles/puzzle-".concat(a,".webp"),alt:"",role:"presentation","aria-hidden":"true",width:h.w,height:h.h,className:(0,o.cn)("absolute object-contain pointer-events-none",f,r,c),...p}),t&&m&&(0,i.jsx)(n.default,{src:g,alt:"",role:"presentation","aria-hidden":"true",width:m.w,height:m.h,className:(0,o.cn)("absolute object-contain pointer-events-none z-35",f,r,d),...p})]})}),d=e=>{let{children:a,containerClassName:t="",noWrapper:n=!1,...r}=e,s=(0,i.jsxs)(i.Fragment,{children:[r.name&&(0,i.jsx)(c,{...r}),a]});return n?s:(0,i.jsx)("div",{className:(0,o.cn)("absolute inset-0 pointer-events-none",t),children:s})};d.Item=c;let u=d}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.