Finance operations

Should Washington Community Banks Build AI Agents or Buy Them?

Washington community banks should compare configuring, buying, building and waiting, and price the sales tax that now reaches custom software and IT services.

In this guide

A community bank in Seattle or elsewhere in Washington should compare four options for each workflow: configure existing software, buy a service, build a narrow extension or wait. Start with the work and the access it requires. Select the option that meets the requirements with support the bank can sustain; neither bank size nor a claim that the process is unique settles the decision.

Buying does not remove internal work. Building does not necessarily mean training a model or replacing a core. A bank can license infrastructure and retain its own workflow configuration, while a purchased product can still require considerable integration and review. In Washington the comparison also has to carry sales tax, which reaches hosted subscriptions and, since October 2025, custom software and IT services.

Sei AI’s build-or-license analysis usefully separates platform ownership from workflow design. Treat its commercial assumptions as a supplier perspective. Your comparison needs your scope, existing contracts, staff capacity and test results.

Compare proposals with the open AI vendor evaluation scorecard.

Describe what the agent may actually do

This is a proposed bank buying method, not a vendor ranking or a guaranteed cost model.

Write down the trigger, inputs, systems read, outputs and permitted changes. “Summarize a loan file for an analyst” is materially different from “update the loan record and notify the applicant.” Name each dependency: document store, loan-origination system, core, identity service, messaging and reporting. Identify which interfaces are supported in the bank’s exact version and contract.

Then ask whether the task needs an agent at all. A fixed checklist, scheduled report or deterministic rule may fit existing configuration. If documents need interpretation, extraction or summarization may be enough. Autonomous selection of tools and actions should earn its additional complexity through a demonstrated need.

Compare the work left with the bank

OptionEvidence that favors itBank work that remains
Configure existing softwareThe required action is supported and can be tested without a new platformProcess design, permissions, configuration, training and monitoring
Buy a specialist serviceA supplier demonstrates the required workflow and support for the bank’s systemsData preparation, vendor oversight, user acceptance and exception handling
Build a narrow extensionA material gap remains and the bank can maintain a bounded solutionEngineering, testing, deployment, support, documentation and dependency changes
Wait with a review dateA credible release can meet the need and interim costs are acceptableMaintaining the current process and checking whether the release actually arrives

A distinctive credit policy is not proof that the entire platform must be custom. Ask a supplier to demonstrate the policy gap before treating it as unconfigurable. Equally, a familiar core-provider logo is not proof that a feature is available, included or adequate.

Use the same cost boundary for every proposal

Compare a chosen planning horizon using implementation plus recurring external charges, retained bank labor, change work and exit costs. State transaction volume, document size, usage and support assumptions. Include licensing, integration access, hosting or model usage, security review, testing, training and operating support where applicable.

Separate costs paid regardless of the decision from costs the option actually changes. Existing employees still have limited capacity, but their time is not automatically a new cash expense or a cash saving. If a proposal relies on moving people to other work, name that work and the manager who can make the change.

Request a low, expected and high usage case. Identify the fees triggered by extra documents, retries, long calls or additional environments. Compare change orders and renewal terms, not just the initial subscription. A purchased system with extensive custom connectors can have many of the same maintenance obligations as a build.

In Washington, put sales tax on every purchased line

Since October 1, 2025, Washington’s retail sales tax has applied statewide to custom software and the customization of prewritten software, and to information technology services such as IT consulting, help desk, network support, training, data processing and data entry, according to the Department of Revenue. A charge for the right to access and use prewritten software that the seller or a third party keeps, the usual hosted subscription, is also a retail sale under RCW 82.04.050. So the licensed service, the contractor who builds the narrow extension and the firm that customizes the core provider’s software can all carry the tax, while work by the bank’s own employees is not a purchase.

The tax is statewide but the rate is local. The Department’s rate table for October through December 2026 lists combined rates of 10.55 percent in Seattle and 10.3 percent in Bellevue (8.9 percent at Bellevue locations outside the Regional Transit Authority area). On an illustrative $150,000 build contract that is $15,825 in Seattle or $15,450 in Bellevue. The version of RCW 82.04.050 that takes effect January 1, 2029 no longer treats custom software or its customization as a retail sale, so a multiyear comparison should apply the tax year by year. The Department also notes that parts of the 2025 law are being challenged in court and says affected taxpayers must still collect and remit under current guidance. Ask each supplier to show the tax on its proposal, and have the bank’s tax adviser confirm how each contract is classified and which location’s rate applies.

In Chicago, the city’s lease tax falls on hosted use

A Chicago bank meets the tax on a different line. The city’s Personal Property Lease Transaction Tax reaches paid use of a provider’s computer or software from Chicago, which a Department of Finance bulletin says includes software as a service, and the rate rose to 15 percent on January 1, 2026, from 11 percent. The same bulletin recognizes an exclusion for services, including software custom designed for the customer, and an exemption for use that effects the deposit, withdrawal, transfer or loan of money. So in Chicago the hosted subscription is the taxed line and the custom build may not be, while Washington taxes both through 2028; have the bank’s tax adviser sort each tool before the comparison is priced.

Rehearse a year-two change before signing

Ask the internal team and each supplier to walk through the same scenario: the bank changes a document requirement and an upstream interface changes its field format. Who identifies the impact, updates the workflow, revises the test set, approves release and supports a failure?

Require names or accountable roles on both sides. Request an example change record, the evidence retained before and after release, and the way the prior process can be restored. Have someone other than the original builder explain the recovery steps. If the explanation depends on one person’s memory, handover is incomplete.

The federal agencies’ community-bank third-party release describes risk management across the relationship. A vendor contract is therefore the beginning of an operating arrangement, not the end of bank oversight. The bank’s risk and compliance owners should determine the applicable review requirements for the actual use.

Model risk guidance will not settle the question for an agent. In April 2026 the OCC, the Federal Reserve and the FDIC replaced SR 11-7 with revised model risk management guidance that applies to community banks subject to its limitations, is expected to be most relevant to banking organizations with over $30 billion in total assets, and states that generative AI and agentic AI models are not within its scope. Do not assume a model validation program covers the agent; decide explicitly how the bank's third-party, information security and compliance reviews will test and monitor it.

Waiting needs evidence too

Ask the core provider for the proposed feature, supported version, release status, dependencies, pricing and a way to evaluate it. Distinguish a roadmap discussion from a generally available capability. Set a decision date and record what would make the bank stop waiting.

Include interim processing effort and any service or control problem in that decision. Waiting can be reasonable when the existing process is acceptable. It is less compelling when an unresolved bottleneck keeps growing and the roadmap has no reliable commitment.

End the comparison with the selected workflow, chosen delivery model, unresolved evidence, budget assumptions and named operational owner. Use the open supplier scorecard for proposal evidence and the finance operations overview to place the project in the bank’s priorities.

Quick answers

Should a community bank build or buy AI agents?

Compare four options for each workflow: configure existing software, buy a service, build a narrow extension or wait with a review date. Choose the one that meets the requirements with support the bank can sustain.

Does model risk management guidance cover AI agents?

Not the April 2026 interagency guidance. It replaced SR 11-7, is expected to be most relevant to banks with over $30 billion in assets, and states that generative AI and agentic AI models are not within its scope, so the bank must define its own testing and monitoring for an agent.

What does a bank still own after buying an AI agent?

Data preparation, vendor oversight, user acceptance, exception handling and the operating relationship itself. The agencies' third-party guidance treats the contract as the start of ongoing risk management, not the end of it.

Does Washington sales tax apply to AI software a bank buys or commissions?

Since October 1, 2025, Washington’s retail sales tax applies to custom software, customization of prewritten software and IT services such as consulting and data processing, and a charge to use software the seller hosts is also a retail sale. Work by the bank’s own staff is not a purchase. Have a tax adviser confirm each contract.

When is it reasonable to wait for the core provider?

When the current process is acceptable and a credible release can meet the need. Get the feature, supported version, status and pricing in writing, and set a date to stop waiting.

Sources

  1. Sei AI’s build-or-license analysis · seiright.com
  2. Department of Revenue · dor.wa.gov
  3. RCW 82.04.050 · app.leg.wa.gov
  4. rate table for October through December 2026 · dor.wa.gov
  5. Department of Finance bulletin · chicago.gov
  6. rate rose to 15 percent on January 1, 2026 · chicago.gov
  7. federal agencies’ community-bank third-party release · federalreserve.gov
  8. In April 2026 the OCC, the Federal Reserve and the FDIC replaced SR 11-7 · occ.gov

Revision note · October 5, 2026: Refocused on Seattle; removed sales tax figures for other Washington cities.

How we research and review these guides

AI transformation with Clairvance

Put the ideas to work in your business.

We provide AI consulting and implementation for finance operations teams. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.

Discuss your project →

Still exploring? Explore the Workflow Opportunity Workbook →