diff --git a/docs/user/usage/aggregation_methods.md b/docs/user/usage/aggregation_methods.md
index 2117e63..f5390e0 100644
--- a/docs/user/usage/aggregation_methods.md
+++ b/docs/user/usage/aggregation_methods.md
@@ -1,7 +1,7 @@
 ---
 title: Metric Aggreation Methods
 sidebar_label: Aggreation Methods
-sidebar_position: 4
+sidebar_position: 3
 ---
 Metrics can be aggregated in various methods, depending on the way your aggregate your methods will depend on what the metric usage value is. 
 
diff --git a/docs/user/usage/index.md b/docs/user/usage/index.md
index 805e6e9..a6c83e1 100644
--- a/docs/user/usage/index.md
+++ b/docs/user/usage/index.md
@@ -11,6 +11,5 @@ How it works is that you have metrics and you then create events reporting new u
 
 * [Metrics](./metrics)
 * [Aggregation Methods](./aggregation_methods)
-* Usage Estimate Costs
-* Pricing Models
+* [Usage Estimate Costs](./usage_estimate_costs)
 * [Events](./events)
diff --git a/docs/user/usage/usage_estimate_costs.md b/docs/user/usage/usage_estimate_costs.md
new file mode 100644
index 0000000..ba17932
--- /dev/null
+++ b/docs/user/usage/usage_estimate_costs.md
@@ -0,0 +1,6 @@
+---
+title: Usage Estimate Costs
+sidebar_label: Estimate Costs
+sidebar_position: 2
+---
+When doing usage billing your customers will know to know what the current costs are. However, due to how usage billing works you can only provide estimates of how what the costs are as it's possible events within your system haven't been processed our BillaBear hasn't processed the event fully.
\ No newline at end of file