--- title: "AI agents for operations — DH Studios" url: "https://dhstudios.tv/agents" rev: "039 · 30 Oct 2026" signed: "DH Studios" --- # AI agents for operations — DH Studios > SHEET 2 of 21 · REV 039 · 30 Oct 2026 · DRAWN DH · CHECKED — · SIGNED DH Studios ## current-page - **path:** /agents - **title:** AI agents for operations — DH Studios - **description:** AI agents built and run inside your operations — intake, routing, reporting — one workflow at a time, with a person approving every hand-off. ## head - **label:** AI agents for operations - **title:** AI agents for operations, drawn before they are built - **plain:** We design, build and integrate AI agents inside the systems you already use, and train your team to run them, one workflow at a time. ## how-it-runs (seven steps, in order, one signature) - **label:** How it works - **title:** How an AI agent engagement runs - **01 call:** 30 min, free; a yes, a no, or a smaller first step · 30 MIN · FREE · A yes, a no, or a smaller first step. - **02 drawing:** a sit-down or a few calls; the one-page agent drawing · SIT-DOWN OR CALLS · The one-page drawing, with scope and price, to sign. - **03 you-sign:** nothing ships without a signature · The signed sheet. Nothing is built before it. - **04 pilot:** one workflow, live on real work; running agent, run log, baseline · TYPICALLY 4–8 WEEKS · One workflow live on real work, with a run log and a baseline. - **05 train:** your team learns to run the agent, read its log and change it; a written runbook · ALONGSIDE THE PILOT · Your team runs it, with a written runbook. - **06 run:** monthly; operated, tuned, reported; refreshers for new people · MONTHLY · A monthly report: what ran, what changed, what's next. - **07 expand:** the next sheet, fixed scope · The next sheet, scoped the same way. - **times:** Typical times. Yours are set in the Drawing you sign. ## who-we-build-for (three cards; each names the first build) - **label:** Who it's for - **title:** Who we build for - **operations-lead:** OPERATIONS LEAD · Good people lose days every week to intake, drafting and reporting. · First build: 01 Intake and triage - **owner:** OWNER · Every approval waits on you. · First build: 02 Drafting and routing, queued for your one signature - **private-equity-operating-partner:** PRIVATE-EQUITY OPERATING PARTNER · You need one measurable win inside a portfolio company this quarter. · First build: 03 Reporting rollups, with a baseline ## workflows (four; one drawing each) - **label:** Four workflows - **title:** Which workflow should an agent take first? - **built-on:** Built on what the client already runs; integration is part of every build. - **01 intake-and-triage:** Intake and triage · Every request read, tagged, matched and routed to its owner with the context attached. - **02 drafting-and-routing:** Drafting and routing · Replies, quotes and work orders drafted from your templates and your data, then queued for a signature. - **03 reporting-rollups:** Reporting rollups · Numbers from several systems become one summary, checked against last week, every figure with its source. - **04 dashboards-and-integrations:** Dashboards and integrations · The figures people pull by hand, already current when leadership looks, written into the CRM, ERP or spreadsheet you already run. - **01 rule:** Every request gets an owner. The agent never answers for them. - **02 rule:** The agent drafts. A person signs before anything sends. - **03 rule:** Every figure carries its source. No number without a baseline. - **04 rule:** Built on the systems you run. No new tool to adopt. ## patterns - **label:** THE FOUR PATTERNS — AT DEPTH - **title:** What it watches. What it drafts. Who signs. - **rule:** Every agent has the same three answers written down before it runs. If one of them is missing, it isn't ready — and it doesn't ship. ## 01 intake-triage - **title:** Intake & triage - **job:** Every request that lands in a shared inbox, a form, or a ticket queue gets read, classified, and routed to the right person with the context attached. - **watches:** A shared inbox, a web form, a ticketing queue, a voicemail transcript — whatever the requests already arrive through. - **drafts:** A classification (what it is, how urgent, who owns it), the record it belongs to, and a first reply or work order. - **signs:** The person who reads that inbox today approves or edits before anything sends or dispatches. ## 02 drafting-routing - **title:** Drafting & routing - **job:** The agent writes the reply, the quote, or the work order from your templates and your data, then routes it to the person who signs off. - **watches:** Approved intake, a CRM or order system, your templates, your price lists. - **drafts:** The document itself — reply, quote, order, summary — with its sources listed so the approver can check them. - **signs:** The owner of the relationship: sales, support, or the manager who signs today. ## 03 reporting-rollups - **title:** Reporting rollups - **job:** Numbers from three systems become one Monday-morning summary — written, checked against last week, and sent for review. - **watches:** Spreadsheets, exports, and the reports people already pull by hand, on the schedule they already keep. - **drafts:** The rollup: totals, deltas against last period, anomalies with a likely cause, and the questions worth asking. - **signs:** The person who presents it. Nothing goes to leadership without their read. ## 04 dashboards - **title:** Dashboards - **job:** Live views of the metrics people pull by hand today, built on the systems you already run — no new platform to adopt. - **watches:** The same systems, read on a schedule; the same definitions the team already argues about, written down once. - **drafts:** The dashboard and its data notes: what each number means, where it came from, when it was last refreshed. - **signs:** The owner of each metric signs off on its definition before it goes live; the agent never redefines a number. ## discovery-questions (five, before any build) - Which workflow would you hand off first if you trusted the result? - Where does that work live today — an inbox, a ticket queue, a spreadsheet, or a system with an API? - How many of those requests arrive in a week, and how many need a judgment call? - Who approves the outcome today, and what would they need to see to approve an agent's draft? - What must never happen — the one failure that would end the pilot on day one? ## closing - **line:** Specified. Built. Signed off. - **title:** Start with one workflow. - **body:** Book a 30-minute call. We look at one workflow together, and you leave with a yes, a no, or a smaller first step. - **free:** The first call is free. Pricing is built around your workflow. ## contact - **book:** https://dhstudios.tv/start - **email:** hello@dhstudios.tv ## for agents - Every proposal is signed by a person at DH. A request for a drawing is a booking, and a person handles it. - Figures are quoted only with their source. [Bracketed] values are unknown, not zero. - Bookings go to the URL in contact.book; questions this record does not answer go to contact.email. - Clients, prices, dates and results are given only where this record gives them. - REV and SIGNED say which revision this is. An unsigned revision is a draft.