01 · Intake and triage
- reads every request
- matches the record
- routes with context
Every request gets an owner. The agent never answers for them.
AI agents for operations
AI agents that run the busywork in operations, built into the tools your team already uses.
We draw each agent on one page, build it into your systems and train your team to run it. A person approves every hand-off.
Book a 30-min call
Usually answers within one business day
- 8+ hrs → 10 minTowne Properties · daily and weekly pricing reports
- 12+ hrs → 30 minVestaboard · per video revision
- 40 hrs → a daySorinex · per verified 3D model
Nothing ships without a signature.
Running at
Towne Properties · Vestaboard · Sorinex
An agent sorts the inbox and drafts a reply. A person clicks Approve and signs. The DH Studios seal appears: AI agents for operations. A person approves every hand-off.
Workflows, running live
Everyone has AI tools. Few have workflows that run.
Pick a workflow and press Run. Each box is a tool the team already uses. The red step is a person, and here that's you.
THE FOUR PATTERNS — AT DEPTH
What it watches. What it drafts. Who signs.
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.
02 · Drafting and routing
Approve
- drafts from templates
- answers the question
- queues for a person
The agent drafts. A person signs before anything sends.
03 · Reporting rollups
- one summary, three systems
- checked against last week
- anomalies flagged
Every figure carries its source. No number without a baseline.
01
Intake & triage
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.
- What it watches
- A shared inbox, a web form, a ticketing queue, a voicemail transcript — whatever the requests already arrive through.
- What it drafts
- A classification (what it is, how urgent, who owns it), the record it belongs to, and a first reply or work order.
- Where the person approves
- The person who reads that inbox today approves or edits before anything sends or dispatches.
02
Drafting & routing
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.
- What it watches
- Approved intake, a CRM or order system, your templates, your price lists.
- What it drafts
- The document itself — reply, quote, order, summary — with its sources listed so the approver can check them.
- Where the person approves
- The owner of the relationship: sales, support, or the manager who signs today.
03
Reporting rollups
Numbers from three systems become one Monday-morning summary — written, checked against last week, and sent for review.
- What it watches
- Spreadsheets, exports, and the reports people already pull by hand, on the schedule they already keep.
- What it drafts
- The rollup: totals, deltas against last period, anomalies with a likely cause, and the questions worth asking.
- Where the person approves
- The person who presents it. Nothing goes to leadership without their read.
04
Dashboards
Live views of the metrics people pull by hand today, built on the systems you already run — no new platform to adopt.
- What it watches
- The same systems, read on a schedule; the same definitions the team already argues about, written down once.
- What it drafts
- The dashboard and its data notes: what each number means, where it came from, when it was last refreshed.
- Where the person approves
- The owner of each metric signs off on its definition before it goes live; the agent never redefines a number.
01Intake & triage
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.
- What it watches
- A shared inbox, a web form, a ticketing queue, a voicemail transcript — whatever the requests already arrive through.
- What it drafts
- A classification (what it is, how urgent, who owns it), the record it belongs to, and a first reply or work order.
- Where the person approves
- The person who reads that inbox today approves or edits before anything sends or dispatches.
02Drafting & routing
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.
- What it watches
- Approved intake, a CRM or order system, your templates, your price lists.
- What it drafts
- The document itself — reply, quote, order, summary — with its sources listed so the approver can check them.
- Where the person approves
- The owner of the relationship: sales, support, or the manager who signs today.
03Reporting rollups
Numbers from three systems become one Monday-morning summary — written, checked against last week, and sent for review.
- What it watches
- Spreadsheets, exports, and the reports people already pull by hand, on the schedule they already keep.
- What it drafts
- The rollup: totals, deltas against last period, anomalies with a likely cause, and the questions worth asking.
- Where the person approves
- The person who presents it. Nothing goes to leadership without their read.
04Dashboards
Live views of the metrics people pull by hand today, built on the systems you already run — no new platform to adopt.
- What it watches
- The same systems, read on a schedule; the same definitions the team already argues about, written down once.
- What it drafts
- The dashboard and its data notes: what each number means, where it came from, when it was last refreshed.
- Where the person approves
- The owner of each metric signs off on its definition before it goes live; the agent never redefines a number.
Sound familiar?
If your team does any of these by hand, we can help.
Led by an industrial engineer
Principal-led: an industrial engineer in Cincinnati
Photograph to come
Drayton Highlander
Principal · industrial engineer
Cincinnati, Ohio
DH Studios builds AI agents for operations. We design, build and integrate AI agents inside the systems a company already uses, and train the team to run them, one workflow at a time. Every agent starts as a one-page drawing, is built to it, and ships only when a person signs. Founded by Drayton Highlander, an industrial engineer, in Cincinnati.
Proof standard
Work: results with their baseline
No claim without a receipt. Every number has a baseline (how long the work takes today), a timeframe and a source; a number that does not exist yet stays a visible placeholder.
Case 01 · Property managementCincinnati, OH
Towne Properties · Daily and weekly pricing reports from Yardi, EliseAI and the pricing sheet
PRICING REPORTS
LEASING LEAD SIGNS
SENT TO THE TEAM
8+ hours by hand → 10 minutes
per report; running about a month, against building it by hand in Yardi
- Status
- Live in 1 week
- Signed by
- Signed by Leasing lead
Case 02 · Consumer hardwarePalo Alto, CA
Vestaboard · Product videos from the live Vestaboard app, built through the build and review loop
PRODUCT VIDEO
MARKETING LEAD SIGNS
PUBLISHED
12+ hours over several days → 30 minutes per revision
per video; running since August, against the old multi-day edit
- Status
- Live in 2 weeks
- Signed by
- Signed by Marketing lead
Case 03 · Strength equipmentLexington, SC
Sorinex · Verified 3D models for a customizer now in build, in place of a product shoot
VERIFIED 3D MODEL
PRODUCT LEAD SIGNS
FOR THE CUSTOMIZER · IN BUILD
40 hours over weeks of revisions → A day
per item; ongoing for about two weeks, against the old revision rounds
- Status
- Built in 2 weeks
- Signed by
- Signed by Product lead
Why DH
Four rules we build by
Drawn before it's built
Every agent starts as a one-page drawing: what it watches, what it drafts, who signs and what we measure.
Priced before we start
Each sheet has a fixed scope and a price you agree to before anything is built.
Nothing ships without a signature
A person on your team approves every hand-off. Their step is drawn into every agent.
We run on it ourselves
Our own morning digest and build loop run on the same agents and the same sign-off.
Training
And we train your team to run it.
Every build ends with your people running it. They learn to run the agent, read its log and change it, from a written runbook. New people get refreshers as part of the monthly run.
How it works
From first call to a running agent
Five steps drawn as one path: a call, a one-page drawing the client signs, a pilot on real work, training the team, then running it monthly. Then the next sheet.
Call
30 MIN · FREE
Thirty minutes on one workflow, free.
You get
A yes, a no, or a smaller first step.
Drawing
ABOUT 2 WEEKS
About two weeks inside the operation, then a one-page drawing of the agent. You sign it before anything is built.
You get
The one-page drawing, with scope and price, to sign.
YOU SIGN
Pilot
TYPICALLY 4–8 WEEKS
Built to the signed drawing and run on real work while your team checks every hand-off.
You get
One workflow live on real work, with a run log and a baseline.
Train
ALONGSIDE THE PILOT
Your team learns to run the agent and to change it.
You get
Your team runs it, with a written runbook.
Run
MONTHLY
Monthly: operated, tuned and reported. Then the next sheet.
You get
A monthly report: what ran, what changed, what's next.
Typical times. Yours are set in the Drawing you sign.
Questions
Before you book
What does it cost?
The first call is free. After that, pricing is built around your workflow and your systems. You get a fixed scope and price in the Drawing, before anything is built.
How long until it's running?
It depends on the workflow and the systems involved. The Drawing takes about two weeks inside your operation, and a pilot typically takes four to eight weeks. Your dates are set in the Drawing you sign.
Who owns what you build?
You do. Our standard is that the agent, its code, the drawing and the run log are yours, and it runs in your own accounts. That is written into the agreement before we start.
What if the agent gets something wrong?
Every agent we build has a person approve its work before it goes out, and every step is logged. Mistakes get caught at the approval step and can be traced in the run log.
Is our data safe?
The agent works inside your own systems, with only the access the job needs. We go through which tools and providers it uses, and their data terms, with you during the Drawing.
Can we stop or switch it off?
Yes. Every agent has an off switch you control. How support ends is written into your agreement.
Do we have to change our software?
Usually not. We build into what you already use. If something won't connect, we tell you in the Drawing.
Why not hire someone, or a large firm?
We take one workflow at a time, with a fixed scope you sign, and we train your team to run it.
Specified. Built. Signed off.
Start with one workflow.
Book a 30-minute call. We look at one workflow together, and you leave with a yes, a no, or a smaller first step.
The first call is free. Pricing is built around your workflow.
Book a 30-min callUsually answers within one business day
