diff --git a/blog/260116-xero-pricing.md b/blog/260116-xero-pricing.md
new file mode 100644
index 000000000..63caa6ff1
--- /dev/null
+++ b/blog/260116-xero-pricing.md
@@ -0,0 +1,34 @@
+---
+title: "Xero: Updates to developer pricing model"
+date: "2026-01-16"
+tags: ["Xero", "Update"]
+authors: psimpson
+draft: false
+---
+
+Xero recently announced an update to its [developer pricing model](https://developer.xero.com/pricing) with plans to introduce a tiered, usage-based pricing structure. This will take effect on 2 March 2026, alongside updates to their Developer Terms and Conditions.
+
+<!--truncate-->
+
+## What’s changing?
+
+For ecosystem app partners Xero is introducing five pricing tiers based on:
+
+- Number of customer connections (tenants) linked to your app.
+- API data egress (how much data your app pulls from Xero via the API).
+
+The tiers each have different connection limits, included API egress usage, and monthly fees.
+
+## Why this matters
+Depending on your current connection volumes and API usage, you may need to:
+- Select a tier.
+- Add a payment method in [Xero’s developer portal](http://developer.xero.com/app/manage/) (required once moving beyond Starter).
+- Monitor and optimise API usage to manage costs.
+
+## What you should do now
+To avoid disruption and ensure you’re ready ahead of March, we recommend you:
+
+- Review [Xero’s pricing and tier model](https://developer.xero.com/pricing#tier-fees-connection-limits-and-api-volume-usage).
+- Login to your [Xero developer app](http://developer.xero.com/app/manage/) and check your API usage.
+- Plan for tier selection/billing readiness ahead of March 2026.
+- Please review your datasets' [sync frequency](https://docs.codat.io/using-the-api/queueing-data-syncs#sync-frequency) in the Codat portal. It is always reccomended that you only sync data as often as is essential for your use-case.