Example agent design
Lease Obligation Agent for Oil and Gas
A lease obligation agent abstracts primary terms, shut-in royalty, continuous development, Pugh, and depth clauses from each lease with citations, and calendars each obligation for the landman to approve. This is a starting design. An AI Blueprint adapts it to your goals and the systems it will connect to.
- Owner
- The landman or VP of land, who approves each abstract. Counsel reviews interpretations.
- Reads
- Leases and amendments from the document store · The land system's lease and tract records · Production and payment dates that trigger lease clauses
- Never writes
- Final lease interpretations, releases, or notices to lessors, and no royalty payment or title opinion. Questions of interpretation go to the landman and counsel.
- Typical cost
- AI Blueprint $4,500–$7,500, credited toward the build. Typical first build $18,000–$35,000, or start local at $4,500–$9,500. Agent Operations after launch $2,500/mo for one production agent. See the first engagement
The workflow
Lease obligations today and with the agent
Planning comparison only. Scope, timing, and outcomes vary by data, workflow, approvals, adoption, and implementation conditions.
- Abstracts
- TodayBuilt by reading each lease and amendment.
- With the agentDrafted with a citation to the lease page for each clause.
- Obligation dates
- TodayShut-in royalty, continuous development, and Pugh dates tracked by hand.
- With the agentCalendared from the lease text, with the triggering date shown.
- Interpretation
- TodayRaised when someone notices a question.
- With the agentFlagged for the landman and counsel, never resolved by the agent.
- Notices and releases
- TodayPrepared and sent by the land team.
- With the agentUnchanged. The agent sends nothing to a lessor.
How it runs
Five steps from lease to obligation calendar
An illustrative solution design, not a reported client result. The AI Blueprint maps it to the company's own leases and land system.
- 01
Read the lease
Reads each lease and its amendments from the document store.
- 02
Abstract the clauses
Abstracts primary terms, shut-in royalty, continuous development, Pugh, and depth clauses, citing each page.
- 03
Calendar the obligations
Calendars each obligation from the lease text and the production and payment dates that trigger it.
- 04
Flag the questions
Flags interpretation questions for the landman and counsel.
Landman review point
- 05
The landman approves
The landman approves each abstract and calendar entry. Notices, releases, and payments stay with the land team.
Landman review point
Systems
The systems it reads
- Document store
- Leases and amendments in Microsoft 365 or the company's document store.
- Land system
- Lease and tract records, through the system's available API, export, or import.
- Trigger dates
- Production and payment dates from the ERP that start a lease clause's clock.
Technologies ITECS evaluates and integrates through each system's available API, export, or import under your licenses; listing a product does not imply a formal partnership or a certified integration. The AI Blueprint confirms the systems each company runs.
Controls
Read-heavy and write-controlled by design
- Read-heavy
- Reads the systems listed above through access scoped to this workflow.
- Write-controlled
- Writes nothing listed under Never writes in the spec at the top of this page. Anything it drafts waits at the approval points below.
- Approval points
- The landman approves each abstract and calendar entry, and counsel reviews any interpretation question.
- Audit trail
- Each run keeps its inputs, sources, output, and the reviewer's decision.
In this design
- Interpretation questions go to the landman and counsel. The agent cites the lease text and never settles what a clause means.
- Runs on the business network and uses data exported out of operational systems. It never connects to SCADA, historians inside OT zones, or field controllers.
- Access is property- and partner-scoped, so one partner's data stays out of another's view, and owner tax IDs and bank details are masked where a task does not need them.
- Rate math, decimals, and allocations are computed in deterministic code, and each flag cites the rule and source behind it.
- ITECS does not provide legal, accounting, or engineering advice through its agents, and no design promises an outcome. The agent prepares and checks; the company's accountants, landmen, engineers, and counsel decide.
Deployment fit
Where this design can run
- Hosted AI Agents
- Runs in a governed Linux environment ITECS operates, on frontier models through enterprise API agreements, connected to the document store and the land system through controlled integrations, with human review and an audit trail.
- Local AI Agents
- A Local variant runs one landman's lease summaries in their own Claude, Codex, or Copilot workspace, over the leases that landman already has. A shared obligation calendar for the land team runs hosted.
Typical first engagement
Start with an AI Blueprint
The AI Blueprint sets the actual build rung and its fixed-fee not-to-exceed. The rows below show the typical path and the catalog range for each step.
- FirstAI BlueprintAgent Discovery & Technical Specification. Credited toward the build.$4,500–$7,500
- Typical first buildSingle-Workflow Production AgentIt is a single-workflow build because it runs one primary workflow, lease to cited abstract and obligation calendar, with a human-in-the-loop review path.$18,000–$35,000
- Or start localLocal Agent SprintOne workflow · 1–2 data sources$4,500–$9,500
- After launchAgent Operations, one production agent$2,500/mo
Prices from the published AI pricing catalog. Every guided or delivered agent build is archived in the ITECS client vault: workspace configuration, skills, prompt libraries, data-source maps, and usage documentation.
Customize this design
Bring your goals and your systems. The AI Blueprint decides the scope and the systems, not this example, and ends with a fixed-fee not-to-exceed for the build.
FAQ
Lease Obligation Agent FAQ
Does the agent interpret our leases?
No. It abstracts each clause with a citation to the lease page and flags interpretation questions for the landman and counsel.
Does it send notices or releases to lessors?
No. It calendars obligations for the land team, who prepare and send any notice or release.
Can one landman start on their own desktop?
Yes. A Local Agent Sprint builds one landman's lease-summary agent in their own Claude, Codex, or Copilot workspace. When the land team wants a shared obligation calendar, multi-user access, or an audit trail, it moves to a hosted build.
Is this legal, accounting, or engineering advice?
No. ITECS does not provide legal, accounting, or engineering advice through its agents. The agent applies rules the company approved and drafts or flags for review; accountants, landmen, engineers, and counsel decide, and no design promises an outcome.
Related examples