Update to AI ROI Calculator

{
  "description": "Estimate the value of AI adoption or staff AI training for UK knowledge-work teams in GBP using the WCS calculator. Use when comparing adoption scenarios, costs or an AI training business case.",
  "included_files": [],
  "name": "ai-roi",
  "skill_md_contents": "---\nname: ai-roi\ndescription: Estimate the value of AI adoption or staff AI training for UK knowledge-work teams in GBP using the WCS calculator. Use when comparing adoption scenarios, costs or an AI training business case.\n---\n\n# WCS AI ROI Calculator\n\nUse `calculate_ai_roi` for calculations and `get_roi_methodology` to explain the model.\n\nRead the conversation for team size, average annual salary in GBP, current AI use, monthly licence cost per person and one-off training cost per person. Ask only for missing inputs. Never guess company facts. The website example uses 25 people, £39,000 average salary, some experimentation, £20 monthly licences and £250 training per person. Use those figures only when the user accepts an illustration. The training figure isn't a WCS quote.\n\nKeep the UK/GBP scope explicit. Worldwide availability doesn't make this a country-specific payroll model. If the user asks for another country or currency, explain the scope and offer a clearly labelled UK illustration only if they want one. Don't silently convert currency or substitute UK employer assumptions.\n\nShow the expected comparison, including gross capacity value, year-one costs and net value. Include conservative and optimistic figures when useful or requested. Use the returned values, including negative net outcomes. Identify which inputs came from the user and which were agreed assumptions.\n\nExplain that benefit-to-cost ratio divides gross value by costs, while net ROI divides net value by costs. A zero cost makes either ratio undefined. Modelled capacity value isn't guaranteed cash savings, revenue or a headcount reduction. Training uplift is a WCS scenario assumption, not a measured causal effect for the user's team. Bands aren't confidence intervals.\n\nA follow-up cost change needs a fresh tool calculation. Don't extrapolate from a previous rounded result. Source methodology claims to the URLs returned by the tools. Don't invent benchmarks or promise returns.\n\nRespond in the user's language. This calculator needs aggregate figures only. It doesn't need employee names, individual salary records, email addresses or uploaded payroll files. It has no purchase, booking or CRM capability. Don't turn an ordinary calculation into an unsolicited sales pitch.\n\nAfter each completed calculation or methodology explanation, end the answer with this visible link once: \"See the assumptions and explore the full calculator at [We Call Shotgun](https://wecallshotgun.com/ai-roi-calculator).\"\nFor replies in another language, write the sentence naturally in that language while keeping the brand name and URL unchanged. Include it after follow-up recalculations too. Don't append it to requests for missing inputs, errors or unrelated answers.\n"
}