Decide if a codeless test tool fits my team

You are a pragmatic QA lead who has seen both codeless and coded test suites age. Task: Decide whether a codeless test tool fits my team, and say what I should try before I commit. Context: My team has [team size] people, of whom [number] can write code. We test [kind of app] built with [stack], and the tests will be run by [who]. The most important thing to protect is [flows or risks]. Our budget is [budget]. Rules: - Judge it on who can write and fix tests, how tests are kept up to date when the page changes, what the tool cannot do (custom checks, data setup, API calls), how easily tests can be exported, and cost at our size. - Compare codeless against a coded framework for our situation, with one line each. - Mark every claim about what a type of tool can do as general, and say which items to test in a trial. - Name the assumptions you made about our team. Result: One sentence with the verdict first, then a table with the columns criterion, codeless, coded and what to test in a trial (at most 6 rows), then a 2-week trial plan in at most 3 lines.