Farzan Ansari
Farzan owns architecture, integrations and deployment at Kastling, and reviews every build before it ships. He works across AWS and Azure, and designs the approval points that keep a named person in control of consequential decisions.
LinkedInWritten by Farzan
Data security and governance for AI in the enterpriseAI data security and governance means knowing which data each AI workflow touches, approving the sources it may use, checking what your AI provider does with prompts and outputs, and making the AI respect the same permissions as the person using it. It also covers defenses against prompt injection, logging with sensible retention, human approval for consequential actions and a clear usage policy for staff. Frameworks such as the NIST AI RMF and ISO/IEC 42001 give that work a structure.Read AI document processing for invoices, contracts and formsAI document processing combines three techniques: OCR to turn images into text, layout models to understand where values sit on a page, and language models to extract and interpret fields that vary between documents. The technique matters less than what surrounds it: validation rules that check extracted values against your own records, confidence thresholds that decide what a person sees, and a review queue somebody owns. Measure field level accuracy and the share of documents that pass without a human touch, not a single headline accuracy number.Read Running AI in production on AWS and AzureRunning AI in production on AWS or Azure means giving a model the same controls as any business system: identity, secrets, logging, cost limits, fallbacks and a named owner for every operating task. Managed services such as Amazon Bedrock and Azure OpenAI in Microsoft Foundry host the models, but the architecture, data boundaries and day-to-day operations remain your decisions to make and assign.Read Building an AI assistant on your company knowledgeAn AI knowledge assistant answers questions using your own approved documents rather than general model training, a pattern called retrieval-augmented generation. The work is less about the model and more about choosing which sources count as authoritative, enforcing the permissions those sources already carry, showing citations people can check, and deciding what happens when information is missing or two documents disagree. Buy Microsoft 365 Copilot, Gemini for Workspace or Glean when your knowledge lives in one mainstream suite, and build when it is spread across line of business systems or the answers must trigger work.Read AWS or Azure for AI workloads: how to chooseFor most companies, the right cloud for AI is the one where their identity, data and technical team already sit. As of September 2026, Amazon Bedrock and Microsoft Foundry both offer models from OpenAI, Anthropic and other providers, so model choice rarely settles the question alone. Identity, data location, compliance scope, skills and existing agreements usually do.Read Connecting AI to your ERP, CRM and data warehouseConnect AI to your ERP, CRM and data warehouse through the vendor's supported APIs, webhooks, event streams or an integration platform, not by writing straight to the database. Start with read access, send every write through a named approver until the workflow has proven itself, and check API limits, licenses, permissions and data quality before you commit to a design.Read Planning a legacy application migration to the cloudA legacy application migration to the cloud starts with deciding, application by application, whether to retire, retain, rehost, replatform, refactor or replace it. Then map dependencies and data, set a cost baseline, plan cutover with a tested rollback, and treat security and identity as part of the move rather than an afterthought. Add AI or automation during the migration only where you are already changing that part of the system.Read Model-agnostic AI architecture: avoiding vendor lock-inA model-agnostic AI architecture puts one internal interface between your application and any model provider, so swapping models is a configuration change rather than a rewrite. It matters because models are retired on published schedules, often within 12 to 18 months of launch. The real lock-in usually sits elsewhere: in proprietary vector stores, agent frameworks, fine-tunes and contract commitments.Read Technical debt in business systems: how to spot it and pay it downTechnical debt is the extra effort every future change costs because of shortcuts, age and neglect in the systems you already run. Leaders see it as slow changes, fragile integrations, spreadsheets holding processes together, one person nobody can replace, and software versions the vendor no longer supports. Pay it down where it blocks work you actually plan to do, in slices, rather than through a full rewrite.Read How to test AI before it touches your operationsTesting AI before deployment means scoring it against a set of real past cases, with the business owner agreeing in advance what counts as correct and what target has to be met. Run it in shadow mode or a limited pilot before it can change anything, keep human review on consequential decisions, and rerun the same test set every time a prompt or model changes.Read
Bring us a workflow.
Tell us where the work slows down. We will help you see where to start.
Book a discovery call