diff --git a/src/pages/ink-builder-program/_meta.json b/src/pages/ink-builder-program/_meta.json
index 9bca638..19f019f 100644
--- a/src/pages/ink-builder-program/_meta.json
+++ b/src/pages/ink-builder-program/_meta.json
@@ -2,5 +2,6 @@
   "overview": "Overview",
   "spark-program": "Spark Program",
   "forge-program": "Forge Program",
-  "echo-program": "Echo Program"
+  "echo-program": "Echo Program",
+  "office-hours": "Office Hours"
 }
diff --git a/src/pages/ink-builder-program/office-hours.mdx b/src/pages/ink-builder-program/office-hours.mdx
new file mode 100644
index 0000000..a769650
--- /dev/null
+++ b/src/pages/ink-builder-program/office-hours.mdx
@@ -0,0 +1,61 @@
+# Office Hours
+
+Ink Office Hours are short, focused 15-minute sessions for teams already building on Ink (or actively preparing to deploy).
+
+Bring one clear question, leave with clear next steps.
+
+> We prioritize requests that come with real context: a demo, repo, contract, logs, or a concrete integration plan.
+
+## **What Office Hours Are For**
+
+### **1. Integration + Deployment Blockers**
+
+Use Office Hours when you're stuck and need help unblocking shipping.
+
+- Contract/API/RPC issues
+- Debugging errors, failed calls, unexpected behavior
+- Deployment/config problems, infra wiring, integration friction
+
+### **2. Architecture Review (for something you've already built)**
+
+Use Office Hours to sanity-check technical direction and avoid expensive mistakes.
+
+- Architecture validation for an existing MVP
+- Integration approach review (how to connect to Ink-native infra)
+- Security and production readiness checks (lightweight, not a full audit)
+
+### **3. Product Feedback (for established products)**
+
+Use Office Hours if you have a real product and want fast, practical feedback.
+
+- UX/onboarding improvements
+- MVP refinement and feature prioritization
+- Activation/retention feedback based on your current users
+- "What should we ship next?" based on your product today
+
+### **4. Launch Readiness on Ink**
+
+Use Office Hours when you're serious about deploying/expanding to Ink and want to pressure-test the plan.
+
+- What you need to launch cleanly
+- Dependencies, integration checklist, rollout sequencing
+- Clear next steps to get to mainnet
+
+## **What Office Hours Are Not For**
+
+To keep sessions high-signal, we don't use Office Hours for:
+
+- Grant status updates, decisions, or rejection discussions
+- Token topics (tokenomics, listings, incentives negotiation)
+- Legal or compliance advice for your project
+- Fundraising requests or VC introductions.
+
+## **How Requests Are Handled**
+
+1. **Submit a request here: [Request Office Hours](https://tally.so/r/lbRVDW)**
+
+> **Note:** Office hour **sessions are only 15 minutes**, please come prepared. If the request is too broad or has no context, we won't be able to accept it.
+
+1. **We triage within ~72 hours**
+2. **If it's a fit, you get a scheduling link** (15-min session)
+3. **If not, you still get a reply** with the right next step/resources