Power Automate AI contract reader using 150k+ tokens per document. How would you redesign this?

[u/AbleComplaint9816]

Hi all,

First time posting here and yes used Ai to help me cultivate my post that makes more sense to you experts. Any advice is greatly appreciated.

I'm looking for some guidance from people who have built large document-processing solutions in Power Automate.

I built a contract intelligence solution that takes customer contracts (PDF/DOCX), extracts the text, and then uses AI prompts to identify and extract specific business information.

Current design:

• Contract uploaded to SharePoint
• Text extracted from entire document
• 7 separate AI prompts run against the contract
• Each prompt extracts a different category of information:
  • Customer details
  • Contract dates
  • Commercial terms
  • Billing details
  • Contacts
  • Renewal information
  • Other contract metadata
• Results are written to SharePoint lists

The solution works, but token consumption is becoming a major issue.

Some contracts are 100+ pages and the flow is consuming ~150k+ tokens per execution. With multiple test runs I'm exhausting my AI credits very quickly.

Before I redesign everything, I wanted to ask the community:

1. Would you combine the 7 prompts into a single structured extraction prompt?
2. Is it better to chunk contracts first and only send relevant sections to AI?
3. Are there Power Automate patterns that significantly reduce token usage?
4. Has anyone moved part of the extraction logic outside of AI and into traditional parsing/rules?
5. Are there any obvious anti-patterns in my design?

My goal is to extract 80-100 contract attributes as accurately as possible while keeping AI costs manageable.

Would appreciate any architecture suggestions or lessons learned from people who have built similar contract intelligence solutions.

Thank you in advance and any advice or direction is greatly appreciated.