If you own a 10-to-250-seat business in Auburn, Fort Wayne, or the rest of DeKalb, Allen, Whitley, or Noble County, the most expensive thing you can do with AI in 2026 is treat it the way every consultant pitch deck does — as an unstoppable wave that either drowns your competitors or drowns you. That framing is wrong, and you do not have to take Cloud Radix's word for it. You can take it from the economist who won the 2024 Nobel Prize for studying how technology actually moves through economies.
In a Monday interview with MIT Technology Review, Daron Acemoglu — co-recipient of the 2024 Sveriges Riksbank Prize in Economic Sciences — laid out three signals he thinks business owners should be tracking. He is famously skeptical of the most aggressive AI productivity claims; his published research has consistently argued that the technology will deliver a smaller, slower boost to U.S. productivity than the hype cycle implies. As the MIT Technology Review Tuesday Download newsletter noted, two years after his original AI-productivity paper, “the data is still largely on his side.” Acemoglu is the right voice to listen to right now precisely because he is not selling anything.
This post takes his three signals — AI agents and the limits of task orchestration, the rapid hiring spree of in-house AI-company economists, and the gap between chatting with AI and actually using it productively — and translates each one into a concrete operational move that a Fort Wayne owner-operator can run this quarter without a McKinsey deck. Each move ends with a one-page action item. Each move is built for the operating reality of a 25-to-150-seat firm with no dedicated AI strategist on staff. And each move maps to a vertical we serve in Northeast Indiana — professional services, regional manufacturing, dental and legal practices, home services, regional banking, and healthcare.
Key Takeaways
- Daron Acemoglu, the 2024 Nobel laureate in Economics, is the cautionary voice business owners should be reading right now — his published research consistently argues AI will deliver smaller productivity gains than the hype cycle implies, and the macro data has been on his side.
- His three 2026 signals are (1) agentic AI's struggle with the task-switching fluency that real jobs require, (2) the rapid hiring of in-house economists by OpenAI, Anthropic, and Google DeepMind to shape the narrative, and (3) the persistent gap between people chatting with AI and people getting productive output from AI.
- Each signal translates into a Fort Wayne operational move: a task-level (not job-level) automation audit, a productivity-capture decision on how AI cost savings get shared, and a 2026 regulatory watch list pinned to Indiana AG, HIPAA, and FCC TCPA developments.
- Three of the verticals where these moves land hardest in NE Indiana are dental/legal professional services, regional manufacturing, and home services — each with a specific shape of “30 tasks the worker juggles” that matters for how to deploy AI.
- The fastest mistake to avoid is treating AI as a job-replacement strategy. The right framing is task-replacement inside the worker's day, which is also the framing that survives Acemoglu's macro argument.
Why Is Acemoglu's Voice the Right One to Listen to in 2026?
The MIT Technology Review interview is worth reading in full. The short version is that Acemoglu's macro position has not moved since his original paper: AI will provide only a small boost to U.S. productivity, current data does not show AI dramatically affecting employment rates or layoffs, and public skepticism about AI is growing — particularly around job loss. The headline framing in the Tuesday Download was that “the data is still largely on his side.”
This matters for Fort Wayne owners for a simple reason. The 2026 AI sales cycle is dominated by vendor pitches that imply your business will be wiped out within 18 months if you do not deploy their stack. Acemoglu's macro argument is that this framing is, on the data, wrong. The realistic picture is gradual, uneven, task-level adoption — closer to how spreadsheets diffused through accounting firms in the 1980s than how mobile phones replaced landlines. That gradualism is the operating climate most of the businesses we work with in DeKalb, Allen, Whitley, and Noble County are actually living through. Their staff is not being replaced. Specific tasks inside their staff's days are being augmented, and the firms that translate that augmentation into operating leverage are pulling ahead of the firms that wait for a wave that, by Acemoglu's reading, is not arriving.
Acemoglu's three signals, then, are not arguments to ignore AI. They are arguments to deploy it intelligently — task-level rather than job-level, productivity-share-aware rather than cost-cut-only, and regulation-aware rather than vendor-pitch-only. Each of the next three sections takes one signal and lays out the operational move.
Signal One: AI Agents Struggle With Task Orchestration — What Should a Fort Wayne Owner Do About It?
Acemoglu's first signal is that agentic AI — the buzzword that drove most of the 2025 funding cycle — does not yet replace human workers because it cannot fluidly switch between the many small tasks that make up a real job. His example in the MIT Technology Review piece was an x-ray technician, who he said juggles 30 different tasks during a shift. The technician moves between formats, databases, communication channels, and physical-world handoffs all day, and that fluidity is what makes the job a job. An AI agent that handles three of those tasks well does not replace the technician; it removes three tasks from the technician's day and leaves the other 27.
For Fort Wayne owners, the operational translation is to stop asking “which jobs can AI replace?” and start asking “which tasks inside which jobs can AI handle this quarter?” Run the inventory at the task level, not the headcount level. In our experience deploying AI Employees across NE Indiana, the firms that succeed do not target jobs; they target task lists, often the same kinds of tasks that show up on the bottom half of a job description — intake forms, appointment confirmations, after-hours phone coverage, invoice follow-up, document summarization, basic research, scheduling logistics, lead-status updates, recurring-report generation.
What that looks like by vertical:
Dental and legal practices (an Allen County professional-services category we cover heavily) have a predictable cluster of automatable tasks: new-patient or new-client intake, insurance verification calls, appointment reminder workflows, document collection, and after-hours phone coverage. None of those are the practice. All of them are tasks the staff juggles between the appointments and case work that is the practice. We covered the specific shape for Fort Wayne customer-service workflows in our Fort Wayne customer service AI with Netomi piece.
Regional manufacturers (DeKalb and Noble County have a strong concentration) have a different task cluster: RFQ intake and routing, quality-report drafting, certification document retrieval, supplier-correspondence triage, and basic production scheduling logistics. Same principle — none of those are the manufacturing; all of them are tasks engineers and floor supervisors juggle around the manufacturing.
Home services, real estate, and regional banking all have a task cluster around inbound-lead handling, follow-up sequences, scheduling, and document workflow that compounds dramatically when handled by an AI Employee 24/7 rather than a part-time office manager 9-to-5.
The operational move is a task-level audit, not a job-level one. We walked through the broader workforce-transition shape in our AI doubles workforce transition Fort Wayne planning piece, and the methodology shows up again in our Fort Wayne business automation 2026 guide. Both are written specifically for the operating reality of 10-to-250-seat Northeast Indiana firms.
One-page action item — this week, for a Fort Wayne owner-operator: pick one role in your firm. Sit with the person doing it for one hour. Write down every task they handle in that hour. Mark the tasks that are (a) repeatable, (b) data-driven, and (c) bounded by clear rules. Those are your task-level automation candidates. You do not need a consultant for this step; you need a notebook.
Signal Two: AI Companies Are Hiring Economists Fast — What Should a Fort Wayne Owner Do About It?
Acemoglu's second signal was a quiet warning. He noted that OpenAI hired Ronnie Chatterji as its chief economist in 2024 and partnered with Harvard economist Jason Furman; Anthropic formed an economic advisory council of ten leading economists; Google DeepMind hired Alex Imas as “director of AGI economics.” This is, on the surface, a healthy development — these are serious researchers. Acemoglu's caution, paraphrased from the interview, was that economists hired by AI companies should not be used “to further their viewpoints or further the hype.” The risk is narrative capture: when the loudest economic voices on AI become the ones with vendor paychecks, the story aligns with the vendor's commercial interest.
The Fort Wayne translation is sharper than it looks. If the macro story about AI's productivity impact is being shaped by economists employed by the vendors selling AI infrastructure, the small-business owner reading those narratives in the trade press is reading a marketing artifact. The defense is not to ignore the narratives; it is to read them with the same skepticism you would apply to a sponsored content piece in a trade magazine.
That skepticism has a specific operational consequence: how do you price the productivity gain when you deploy AI? If your AI Employee saves 20 hours per week of work for a $4,000/month deployment, who captures the value of those saved hours? The vendor's pitch will frame it as a cost cut, where the saving goes entirely to the firm's margin. Acemoglu's broader research argues the productivity capture question is the central question of any technology cycle — when railways, electricity, and computing all rolled through their respective decades, who captured the productivity gains shaped the labor and economic outcomes more than the technology itself did.
For a 75-seat Fort Wayne firm, the productivity-capture decision usually comes down to three options. One: the saving is reinvested into more output — the firm grows revenue with the same headcount, the AI Employee pays for itself, and the existing team's compensation moves up with the firm's profitability. Two: the saving is reinvested into the staff's experience — fewer overtime hours, fewer after-hours pages, better tooling for the part of the job that is the actual practice. Three: the saving is treated purely as a margin cut — same revenue, fewer hours, fewer people. All three are defensible. Option three is the most common vendor pitch and the most likely to age badly with your team, your local labor market, and (depending on vertical) your regulators.
We measure those three productivity-capture outcomes in our AI Employee performance metrics guide, which lays out the specific KPIs Fort Wayne firms can track quarterly to know which capture path they are actually on. Pricing the saving is the operational discipline; measuring the outcome is the audit.
One-page action item — this quarter: before signing your next AI deployment contract, write a one-page memo answering “if this saves 20 hours of staff time per week, what happens to those 20 hours?” If the answer is “we don't know,” you do not have a productivity-capture plan; you have a vendor pitch. Decide before you deploy.
Signal Three: AI Apps Are Still Hard to Use Productively — What Should a Fort Wayne Owner Do About It?
Acemoglu's third signal is the one most aligned with what Fort Wayne owners are actually experiencing in their own offices. He pointed out that AI lacks the everyday usability of earlier transformative software like PowerPoint — that people can chat with AI, but “it tends to take a while for the average worker to get practical and productive use out of it.” Per his framing, this gap is part of why AI has had minimal measurable economic impact so far.
The translation for a Northeast Indiana firm is that giving every employee a ChatGPT or Copilot license is not the same as deploying AI productively. We have walked into 40-seat firms with full Copilot rollouts where the actual usage was a handful of employees writing emails marginally faster. That is a small productivity gain, and it does not pay back the seat cost.
What we have seen work — the deployment shape that closes the usability gap Acemoglu describes — is the AI Employee model rather than the AI assistant model. The distinction is that an assistant requires the worker to formulate the request; an employee owns the workflow. A worker who has to remember to use AI for a task often does not. An AI Employee that handles the task on its own does not depend on the worker remembering anything. That difference is also why the chat interface does not, by itself, deliver the productivity Acemoglu's data has been missing — it requires the worker to be both the user and the supervisor of the AI, which most workers will not sustain for long.
This signal also intersects with a regulatory dimension that mid-market Northeast Indiana firms underrate. AI deployment touches consumer-protection rules at multiple points, and the rules are written by jurisdictions that are not waiting for Acemoglu's macro data to settle. The Indiana Attorney General's Consumer Protection Division enforces the state's Deceptive Consumer Sales Act and publishes ongoing guidance on data breach response and identity-theft prevention — both of which apply to firms deploying AI that touches consumer data. Healthcare and dental practices are still bound by HIPAA when AI tools touch protected health information, with no carve-out for AI vendors. Phone-using businesses — home services, contractors, real estate, lead-generation-heavy practices — remain bound by the FCC's Telephone Consumer Protection Act, and AI voice agents calling consumers need to comply with the same consent and identification rules as human agents.
That regulatory layer is the second part of the operational move. A 2026 AI deployment plan that does not have a regulatory watch list — what is changing in Indianapolis at the AG's office, what HHS is publishing on HIPAA and AI, what the FCC is signaling on TCPA enforcement against AI voice agents — is a deployment plan that will get re-litigated by your auditor at the next compliance cycle.
One-page action item — this month: assign one person on your team (does not have to be IT) to subscribe to (a) the Indiana AG consumer-protection bulletins, (b) the HHS HIPAA enforcement updates if your firm handles PHI, and (c) the FCC TCPA docket updates if your firm uses voice or SMS for marketing or appointment workflows. Their job is to flag, once a quarter, anything that affects how you can deploy AI legally in your firm. That is the regulatory-watch hygiene most 50-to-150-seat NE Indiana firms do not currently have, and it is cheap to install.
How the Three Moves Fit Together for a Northeast Indiana Owner
The three operational moves are designed to compose, not to be picked off independently. The task-level audit gives you a deployment plan with realistic scope. The productivity-capture decision gives you a memo that survives your next budget cycle and a measurable plan for what your team gains from the deployment. The regulatory watch list keeps the deployment compliant in a state and an industry that has not finished writing the rules.
The shape we see succeed in Auburn, Fort Wayne, and the surrounding counties is sequential: do the task audit in week one, write the productivity-capture memo before the contract goes to signature in week three, and stand up the regulatory watch list as a quarterly review with the same person who handles your insurance renewals or your annual audit prep. None of those steps requires hiring a Chief AI Officer. All of them require the owner to be in the room.
The Northeast Indiana labor market matters here, too. The 75-seat Allen County firm that captures the 20 saved hours by upskilling its existing staff and growing revenue typically holds onto its team in a market where qualified administrative and clinical workers are not easy to replace. The 75-seat firm that captures the same 20 hours by cutting staff usually finds itself rebuilding 18 months later, often at higher wages. The productivity-capture decision is therefore not just an ethics question; it is a labor-economics question Acemoglu has spent his career studying, and the answer for a 2026 NE Indiana owner usually favors reinvestment.
We covered the AEO and AI-search overlay in our Fort Wayne AI search traffic and AEO writeup, which is the marketing-side mirror of the same task-level approach: the firms winning AI-search results are the ones answering specific questions inside specific verticals, not the ones publishing generic AI thought leadership.
A Pilot for Northeast Indiana Owner-Operators This Quarter
Cloud Radix runs the three-move framework as a paid consult for NE Indiana owner-operators who want the task audit, the productivity-capture memo, and the regulatory watch list installed in one pass. The output is a one-page document per move — three pages total — that goes on the owner's desk before the next AI deployment contract gets signed. We size the engagement for 10-to-250-seat firms across Auburn, Fort Wayne, DeKalb, Allen, Whitley, and Noble Counties. If you are evaluating an AI Employees deployment this year and want the planning work done before the deployment work, the Cloud Radix AI Consulting intake is the right place to start.
Frequently Asked Questions
Q1.Who is Daron Acemoglu and why should Fort Wayne business owners care?
Daron Acemoglu is an MIT economist and a co-recipient of the 2024 Sveriges Riksbank Prize in Economic Sciences (the "Nobel Prize in Economics"). His research on how technology actually moves through economies has consistently argued that AI's productivity boost will be smaller and slower than vendor narratives suggest — and the macro data through 2026 has largely supported that view. For a Fort Wayne owner-operator, that matters because most of the AI sales cycle is built on the opposite premise. Acemoglu's framing is the closest thing to an unbiased counterweight in mainstream economic commentary on AI.
Q2.What did Acemoglu say AI cannot do yet?
In his MIT Technology Review interview, Acemoglu argued agentic AI cannot yet fluidly switch between the many small tasks that make up a real job. His example was an x-ray technician juggling 30 different tasks during a shift; AI agents that handle some of those tasks well do not replace the technician because the fluidity between tasks is what the job is. The Fort Wayne translation is to deploy AI at the task level, not the job level.
Q3.What is the task-level automation audit, and how long does it take?
The task-level audit is the practice of inventorying tasks (not jobs) inside a role, marking which are repeatable, data-driven, and bounded by clear rules, and treating those as your AI deployment candidates. For a single role in a 25-to-150-seat firm, a useful first pass takes about one hour with the person doing the role and a notebook. A full firm inventory takes a few days of part-time work over a quarter. The output is a list of task-level deployment candidates and the rough hours-saved estimate per task.
Q4.What is a productivity-capture decision and why does it matter?
A productivity-capture decision is the explicit memo a firm writes about who captures the value of hours saved by an AI deployment. The three options are reinvest into growth (more output with the same headcount), reinvest into the staff's experience (fewer overtime hours, better tooling), or treat the saving as a margin cut (same revenue, fewer hours, fewer people). It matters because the vendor pitch usually assumes the third path, while Acemoglu's research and the NE Indiana labor market usually argue for one of the first two.
Q5.What regulatory issues should a Fort Wayne owner watch in 2026?
Three docks are worth quarterly monitoring for a typical 10-to-250-seat NE Indiana firm. The Indiana Attorney General's Consumer Protection Division publishes guidance on deceptive practices and data-breach response that increasingly intersects with AI deployments. If the firm handles protected health information, HHS HIPAA guidance still applies with no carve-out for AI vendors. If the firm uses voice or SMS for marketing or appointment work, the FCC's Telephone Consumer Protection Act applies to AI voice agents the same way it applies to human callers. A one-person quarterly watch list is enough hygiene for most mid-market firms.
Q6.Is an AI Employee different from a Copilot or ChatGPT license?
Yes, structurally. A Copilot or ChatGPT license is an assistant — it requires the worker to remember to use AI to handle a task. An AI Employee owns the workflow — it handles the task on its own schedule and reports outcomes. Acemoglu's third signal is that the assistant model has been slow to deliver productivity precisely because it depends on workers being both the users and the supervisors of the AI. The Cloud Radix AI Employee shape is built specifically to close that usability gap by making the AI responsible for the task end-to-end.
Q7.What is the single first step a Fort Wayne owner should take this week?
Pick one role in your firm. Sit with the person doing it for an hour. Write down every task. Mark the ones that are repeatable, data-driven, and bounded by clear rules. That list is your task-level automation candidate pool. It is the cheapest, highest-leverage step in the whole framework, and it is the one most owner-operators can execute without hiring anybody.
Sources & Further Reading
- MIT Technology Review: technologyreview.com/2026/05/11/three-things-in-ai-to-watch-according-to-a-nobel-winning-economist — Three things in AI to watch, according to a Nobel-winning economist (2026-05-11).
- MIT Technology Review: technologyreview.com/2026/05/12/the-download-nobel-winner-ai-maintenance-of-everything — The Download: a Nobel winner on AI, and the maintenance of everything (2026-05-12).
- State of Indiana: in.gov/attorneygeneral/consumer-protection-division — Indiana Attorney General Consumer Protection Division.
- U.S. Department of Health and Human Services: hhs.gov/hipaa — Health Information Privacy (HIPAA).
- Federal Communications Commission: fcc.gov/general/telephone-consumer-protection-act-1991 — Telephone Consumer Protection Act overview.
- The Nobel Prize: nobelprize.org/prizes/economic-sciences/2024/summary — The Royal Swedish Academy of Sciences, 2024 Economic Sciences Prize.
Install the Three Moves Before Your Next AI Contract
We will run the task-level audit, draft the productivity-capture memo, and stand up the regulatory watch list for your 10-to-250-seat NE Indiana firm — three single-page outputs on your desk before the next deployment contract gets signed.
Book the Three-Move PilotFor Auburn, Fort Wayne, DeKalb, Allen, Whitley, and Noble County owner-operators.
