ServisFirst Bank has selected Covecta, an agentic AI company focused on financial services, to deploy AI agents across its operations. The most useful part of the announcement is not the adoption itself. It is the decision about where those agents should begin working.

Covecta says the initial focus is on manual work performed outside mission-critical systems, describing the approach as innovation from the 'outside-in'. Michael Lindsey, Chief Information and Operations Officer at ServisFirst Bank, said the bank selected Covecta because its agents bring banking-domain expertise.

That outside-in model offers a practical way to think about one of the hardest questions in enterprise agent adoption: where should organisations allow software to act before they are comfortable giving it access to core systems? In practice, lower-consequence work at the edges of mission-critical systems could include information gathering, reconciliation, exception handling, document processing or workflow hand-offs. Those examples are an AI360 interpretation of the operating model, not activities ServisFirst specifically says it has assigned to Covecta.

Conquered Your Data? - Now Combat Your AI
Souvik Choudhury, an AI and Data Governance Specialist at Fractal Analytics with a background spanning Infosys, HSBC and several startups, joins Stewart Tinson to unpack why data governance and AI governance can’t be treated as sequential problems, and why so many organisations discover the gap between them the hard way. Souvik argues that traditional data governance remains the foundation everything else is built on, and that AI agents amplify existing weaknesses rather than replacing the need for accountability, contextualisation and lineage. He walks through a real project example where an organisation believed it had solved data governance by using agents to generate column definitions, only to discover the definitions were pulled from generic internet knowledge rather than the organisation’s own policies, leaving a false sense of confidence behind a genuinely ungoverned dataset. The conversation covers where accountability actually sits when an autonomous agent makes a bad decision, why third-party models don’t dilute an organisation’s own responsibility for outcomes, and why Souvik pushes back on the idea that governance is an innovation-killing bureaucracy rather than the structural work that makes innovation possible in the first place. He also sets out a practical, staged approach to evaluating AI governance tooling rather than jumping straight to an enterprise platform, and offers a way to actually measure AI governance maturity using a weighted scoring model across multiple pillars. The discussion closes on an unexpected angle: the sustainability cost of AI infrastructure, and why Souvik believes environmental impact deserves a seat alongside profitability and productivity in any serious cost-benefit conversation about agentic AI.

The distinction matters because an AI agent is different from a conventional assistant. A chatbot can produce a poor answer that a human chooses not to use. An agent can be given permission to retrieve information, invoke tools and execute parts of a process. The more consequential the action, the more important identity, permissions, auditability and rollback become.

Starting outside the core gives an institution room to test those controls. Teams can establish who owns each agent, what data it can access, which tools it can call, how its actions are logged and how exceptions are escalated. They can also compare productivity gains with the cost of supervision before expanding autonomy.

The strategy may be particularly attractive in financial services because banks often have large amounts of manual work around legacy platforms that are difficult or risky to change directly. An agent that can reduce work at the edges of those systems may deliver value without requiring a major core transformation on day one.

The longer-term question is how an organisation earns the right to move agents deeper into the operating environment. Successful pilots will not remove the need for governance; they will create evidence about where controls work and where they do not. The useful metric is therefore not simply how capable an agent appears, but the consequence of the actions it is allowed to take.

ServisFirst’s deployment is a useful case study because it turns an abstract debate about agentic AI into an operating model: begin where the cost of error is containable, prove the controls, and expand authority only when the evidence supports it.


Garbage In, Garbage Faster: Why Agentic AI Exposes Your Organisational Debt
If Agentic AI follows your documented processes, what happens when those processes don’t reflect reality? Most organisations assume AI will figure things out. Business Architect Laura Van Weegen argues the opposite: AI doesn’t create new problems — it removes your ability to ignore the ones that have existed forever and a day. Undocumented workflows, undefined decision ownership, and human workarounds masking broken systems all get amplified at machine speed. You’ll learn: • Why “garbage in, garbage faster” is the real Agentic AI risk • The critical difference between feeding AI data versus information • How process debt compounds the same way technical debt does • Why exception handling is the new decision design priority • What one conversation reveals more than most AI readiness assessments • How to build explainability in from day one Key topics: Agentic AI readiness • Information architecture • Process debt • Data vs information • Contextual blindness • Decision ownership • Explainability vs traceability • Semantic infrastructure • Exception handling • Organisational accountability • Workflow documentation • AI governance Essential viewing for CISOs, CIOs, CFOs, and Chief Legal Officers evaluating Agentic AI deployment — before the human safety net disappears.
Share this post
The link has been copied!