Author: Will Tygart

  • Millwright District Phase 2 Is Breaking Ground in 2026: Here’s What 300+ New Waterfront Homes Mean for Everett

    Millwright District Phase 2 Is Breaking Ground in 2026: Here’s What 300+ New Waterfront Homes Mean for Everett

    What is the Millwright District? The Millwright District is the 10-acre second and largest phase of the Port of Everett’s Waterfront Place mixed-use development. Phase 2 adds 300+ residential units, 60,000+ square feet of retail and restaurant space, and 200,000+ square feet of commercial and office space to Everett’s working waterfront near the downtown core.

    We’ve been watching the Millwright District take shape for years — the cranes, the construction fencing, the slow march of change along the waterfront. And right now, in spring 2026, the second and largest phase of Waterfront Place is officially underway. Private development partner Lincoln Properties is breaking ground on 300+ new residential units at the Millwright District, and when it’s done, the Port of Everett’s 65-acre waterfront transformation will look nothing like what stood here a decade ago.

    Here’s what we know, what’s coming, and why this matters for everyone who lives in or near Everett.

    What Is the Millwright District, Exactly?

    The Millwright District sits within the broader Waterfront Place development — the Port of Everett’s $1 billion-plus effort to transform 65 acres of working waterfront into a mixed-use neighborhood. Phase 1 of Waterfront Place has already delivered: Restaurant Row is now home to Tapped Public House (which opened March 2, 2026, with Snohomish County’s largest open-air rooftop deck), Rustic Cork Wine Bar, The Net Shed Fresh Fish Market & Kitchen, and more tenants arriving this spring.

    Phase 2 — the Millwright District — is a different scale entirely. We’re talking about a full 10-acre neighborhood being built from scratch, right on the waterfront near Everett’s downtown core. The project will deliver:

    • 300+ residential units — waterfront apartment homes on Everett’s marina edge
    • 60,000+ square feet of retail and restaurant space — a full neighborhood commercial district
    • 200,000+ square feet of commercial and office space — bringing employers to the waterfront

    Lincoln Properties, a national developer with a significant Pacific Northwest portfolio, is the Port’s private development partner on this phase. The groundbreaking for the first residential building was targeted for late 2025 into early 2026, with units expected to deliver as the project completes its build-out over the next several years.

    Why Apartments on the Waterfront Are a Big Deal for Everett

    Everett has been trying to bring residents to its downtown and waterfront for years. The Millwright District’s 300+ units represent one of the largest infusions of new residential supply the city has seen in a generation — and the location matters enormously.

    These aren’t apartments tucked behind a strip mall off I-5. They sit within walking distance of the marina, Restaurant Row, the future Waterfront Place hotel properties, and — if things go according to plan — the Sound Transit Everett Link Extension station that will eventually connect the waterfront to Seattle’s light rail network.

    Before Phase 2 breaks ground, the site already has 266 waterfront apartment homes from the first residential component of Waterfront Place. Add 300+ more units from the Millwright District, and you’re looking at nearly 600 waterfront homes where a working industrial port once sat. That’s a genuine neighborhood — with built-in foot traffic to support the retail and restaurant tenants the Port is recruiting.

    The Port Is Still Hunting for a Flagship Dining Tenant

    Alongside the residential groundbreaking, the Port of Everett is actively searching for one more piece of its restaurant puzzle: a high-end steakhouse or experiential dining concept willing to enter a long-term ground lease and build out a custom restaurant building on the final available parcel in the district.

    This is significant because it signals the Port isn’t done curating Waterfront Place’s tenant mix — they want a flagship anchor that can draw diners from across Snohomish County and beyond. The right operator would build their own building on Port land, which is the kind of investment that only happens when a developer believes in a location’s long-term trajectory.

    What the Full Waterfront Place Build-Out Looks Like

    To understand the Millwright District in context, here’s what the complete 65-acre Waterfront Place development delivers when fully built out:

    • 1.5 million square feet of total mixed-use development
    • Two hotels — already in the plan and on site
    • 566+ residential units (266 existing + 300+ Millwright Phase 2)
    • Restaurant Row — multiple dining tenants open or arriving spring 2026
    • Marine services — S3 Maritime opened early 2026 for recreational vessel maintenance
    • Expanded public parking — with a free waterfront shuttle updated for 2026

    The scale is hard to fully appreciate until you drive past it. This is not a small development. This is a new neighborhood being built on top of what used to be working waterfront infrastructure, and the pace has visibly accelerated since 2024.

    What This Means for Everett’s Housing Supply

    Everett’s housing market has been under pressure from demand and constrained supply for years. The latest data shows the median sale price in Everett near $547,000 in early 2026 — even amid some year-over-year softening. Adding 300+ new units to the waterfront won’t solve Everett’s affordability challenge on its own, but it adds meaningful supply in a location where none existed before.

    These will be market-rate waterfront apartments — which means they’ll serve a specific segment of the market. But their arrival matters for the broader supply picture. Everett needs units. The Millwright District is delivering them.

    Our Take

    The Millwright District Phase 2 groundbreaking is the moment Waterfront Place stops being a promise and becomes a neighborhood. Restaurant Row proved the concept works — Tapped Public House is already packing in customers, and more tenants are coming. Now the residential component is arriving at scale, which means the foot traffic, the energy, and the sense of a real waterfront district are all about to intensify.

    We’ll be at the waterfront watching the cranes go up. Follow along with us.

    Frequently Asked Questions

    When will the Millwright District apartments be ready?

    Lincoln Properties began the groundbreaking phase for Millwright District residential units in late 2025 into early 2026. The full build-out of the 300+ units will unfold over several years.

    Who is developing the Millwright District?

    Lincoln Properties is the Port of Everett’s private development partner for the Millwright District. The Port retains ownership of the waterfront land.

    How many apartments are in the Millwright District?

    The Millwright District Phase 2 will deliver 300+ residential units. Combined with 266 existing waterfront homes in Phase 1, the full Waterfront Place development will have approximately 566+ waterfront residential units.

    Is Millwright District the same as Waterfront Place?

    The Millwright District is the second and largest phase of the Port of Everett’s broader Waterfront Place development. Waterfront Place is the 65-acre, 1.5-million-square-foot mixed-use project; the Millwright District is its 10-acre Phase 2 component.

    What businesses are already open at Waterfront Place?

    Restaurant Row at Waterfront Place includes Tapped Public House (opened March 2, 2026), Rustic Cork Wine Bar, and The Net Shed Fresh Fish Market & Kitchen. Menchie’s at the Marina and Marina Azul Cocina & Cantina are expected to open spring 2026. S3 Maritime also opened early 2026 for marine services.

    Is there parking at Waterfront Place?

    Yes. The Port of Everett offers two-hour free parking zones and a free waterfront shuttle with expanded service coming spring 2026. The Port published a 2026 Visitor Parking “Insider’s Guide” with full details at portofeverett.com.

    What kind of flagship restaurant is the Port looking for?

    The Port of Everett is seeking a high-end steakhouse or experiential dining concept interested in a long-term ground lease on the final available parcel in the Waterfront Place district. The chosen operator would build their own restaurant building on Port-owned land.


    Go Deeper: We’ve published detailed knowledge nodes expanding on this story for specific Everett audiences:

  • Tide and Timber: Union, WA — The Olympic Peninsula Place That Wins Every Argument

    Tide and Timber: Union, WA — The Olympic Peninsula Place That Wins Every Argument

    The people who know the Olympic Peninsula best will tell you it is not one thing. It is a rainforest dripping into the Hoh. It is the Strait of Juan de Fuca with its freight traffic and its harbor seals. It is the Pacific coast at Kalaloch, and the mountain meadows at Hurricane Ridge, and the river valleys that cut down from the Olympics toward the water. It is also — though some will debate this, right up until they visit — Union, Washington, at the southernmost hook of Hood Canal.

    What this video captures is Union in its essential form: the light on the water, the timber closing in from every rise, the quiet that settles over the canal on a still afternoon. The song you are hearing is called Tide and Timber, and it was written for places exactly like this.

    Why People Leave the City for the Hood Canal

    On any weekend you can find people on the road from Seattle who are not heading to the mountains and not heading to the coast — they are heading to the canal. From Portland, the drive is longer but the pull is the same. From elsewhere in the world, the pull is more mysterious, the product of some article read years ago or a friend’s description that never quite left the back of the mind.

    They find Hood Canal and follow it south, and the further south they go the quieter it gets, until they reach Union and the road curves and the water opens up and they understand why the drive was worth it. The Hood Canal here is at its most intimate — narrow enough to feel like a river, tidal enough to remind you it connects to the ocean, surrounded by hills that catch the last light of the afternoon in a way that makes even seasoned travelers stop the car.

    The Music Scene That Nobody Talks About

    Union has open mics that draw musicians from across the Pacific Northwest and beyond — people who came to visit the canal and stayed, or who drove out from Seattle looking for a different room to play. The quality is serious. The community is real. On the right night, in the right room, you will hear something that stays with you the way that the best live music does: unexpectedly, completely, in a way that makes the venue and the town and the landscape around it all part of the same experience.

    This is not an accident. Union attracts a certain kind of person who values authenticity over spectacle, who can hear the difference between a musician playing for attention and a musician playing because the song demands it. The tide and the timber have a way of sorting people out.

    Union Belongs on the List

    The debate about whether Union counts as Olympic Peninsula is a small debate in the end. Geography has its arguments, and they are not uninteresting. But anyone who has driven the Olympic Loop and skipped Union has missed something — not a footnote, but a chapter. The hook of Hood Canal is where the peninsula gathers itself before the water widens back toward Puget Sound, and Union sits at that gathering point like a town that knows exactly what it is.

    The best lists of remarkable places on the Olympic Peninsula include Union. Not reluctantly, as a runner-up, but with the full weight of what the place actually is: a waterfront community at the intersection of the tidal canal, the old-growth timber, and a music scene that could hold its own anywhere. Come for the view. Stay for the song.

    Plan Your Visit

    Union is roughly 25 miles southwest of Belfair on Highway 106, along the southern shore of Hood Canal. The drive from Seattle takes about two hours and is worth every minute of it. Combine it with a visit to Twanoh State Park just to the east, or continue west along the canal toward Hoodsport and the trailheads into the Olympics. However you approach it, leave more time than you think you need.

    📱 Watch & Share on Facebook

    Copy the link below and paste it into a new Facebook post — Facebook will pull the video in automatically so your friends can watch it directly in their feed.

    🔗 https://tygartmedia.com/tide-and-timber-union-wa-olympic-peninsula-watch-page/

    The video is hosted right here on this page. No YouTube account needed — just share the link.

  • Tide and Timber: A Watch Page for Union, WA — Where the Music Never Really Stops

    Tide and Timber: A Watch Page for Union, WA — Where the Music Never Really Stops

    There is a place on the hook of Hood Canal where the land folds into the water like it has always meant to, where the timber stands close enough to the tide that you can smell both at once. That place is Union, Washington — and people come from everywhere to find it.

    They come from Seattle, leaving the steel and glass behind for a two-hour drive that deposits them somewhere that feels older and quieter and more honest than the city they left. They come from Portland. They come from across the country and from corners of the world that have never heard of Mason County. And when they arrive in Union, they tend to stay longer than they planned.

    The Best Live Music You Have Never Heard Of

    The open mics in Union are the kind of thing that travel writers should be writing about but somehow aren’t. On any given night you might be sitting next to someone who just drove down from Bainbridge or rode in from Bremerton, and the person up front playing guitar learned their craft in Nashville or New Orleans or Oslo — and ended up in Union because Union has a way of pulling people in and holding them there.

    There is something about the scale of the place. The Hood Canal narrowing to its southern reach, the Olympics rising to the west, the water sitting still on calm evenings while someone plays a song that was written somewhere else but sounds completely at home here. The local music community in Union is deep and serious and generous, full of working musicians who have played real stages and chose this life at the edge of the canal anyway.

    Tide and Timber — the song carrying this video — was recorded in that spirit. Listen to it as you watch the water move and the light change, and it will tell you everything you need to know about why this place matters.

    Union and the Olympic Peninsula Question

    You will hear people say Union is not part of the Olympic Peninsula. It comes up often enough to be its own small tradition — the argument that the Hood Canal is the eastern edge of the peninsula, and that Union, sitting at the canal’s southern hook, does not technically qualify.

    It is the kind of argument that dissolves the moment you visit. Drive into Union from any direction and you are surrounded by the same ancient forest, the same mountains catching clouds to the west, the same tidal rhythms that define everything to the north and west of it. The Hood Canal is not a boundary here — it is an artery. The peninsula breathes through it.

    Every argument that Union does not belong on a list of remarkable Olympic Peninsula destinations loses its footing once you have sat by that water at dusk, or stood in a room while a musician played to thirty people like it was the most important show of their life. The honest lists include Union. The good ones lead with it.

    When to Go

    Union rewards every season. Spring brings the rhododendrons and the first serious fishing traffic on the canal. Summer fills the waterfront and the open mics draw bigger crowds. Fall turns the hillsides amber and the oyster season comes into its own. Winter is quieter and colder and more honest, the kind of season that shows you what a place is actually made of.

    If you are planning a loop of Hood Canal — Hoodsport, Lake Cushman, the Skokomish Valley, and back out through Belfair — do not let Union be a waypoint. Let it be a destination. The music will still be playing when you get there.

    📱 Watch & Share on Facebook

    Copy the link below and paste it into a new Facebook post — Facebook will pull the video in automatically so your friends can watch it directly in their feed.

    🔗 https://tygartmedia.com/tide-and-timber-union-wa-watch-page-mason-county/

    The video is hosted right here on this page. No YouTube account needed — just share the link.

  • Hood Canal Shellfish Season Opens with New 2026 Rules — Tahuya Trail Closure and What’s Coming This Summer

    Hood Canal Shellfish Season Opens with New 2026 Rules — Tahuya Trail Closure and What’s Coming This Summer

    Spring is here and so is shellfish season along Hood Canal! If you’re heading out to dig clams or harvest oysters, take note of the new 2026 rules that kicked in April 1 — the minimum size for cockles is now 2½ inches, and geoduck limits have dropped to one per person per day. Potlatch State Park’s clam, mussel, and oyster season is open through May 31, so grab your shellfish license and your Discover Pass and get out there.

    Over at Tahuya State Forest, heads up that portions of the Howell Lake Loop Trail remain temporarily closed due to a washed-out bridge. Plenty of other trails are open for ORV riding, mountain biking, and hiking — just stick to marked routes and remember your Discover Pass.

    Looking ahead, the Theler Wetlands trail system is getting a major upgrade this summer. Construction begins on a new pedestrian boardwalk in the footprint of the removed levees, fully reconnecting the estuary trail loop. And Belfair State Park’s Tree Loop campground opens for reservations May 15 — start planning those summer weekends on the water.

    • Shellfish 2026 Rule Changes (April 1): Cockle minimum size 2½ inches; geoduck limit 1/person/day
    • Potlatch State Park shellfish season: Open through May 31
    • Tahuya Howell Lake Loop: Partial closure — bridge washout; other trails open
    • Theler Wetlands boardwalk: Construction starting summer 2026
    • Belfair State Park Tree Loop: Reservations open May 15
  • Belfair Business Beat: Sweetwater Creek Ribbon Cutting April 10, Industrial Development on the Horizon

    Belfair Business Beat: Sweetwater Creek Ribbon Cutting April 10, Industrial Development on the Horizon

    Something new is opening in Belfair this week — and it’s been a long time coming.

    The Sweetwater Creek Waterwheel Park holds its official ribbon-cutting celebration on Thursday, April 10 at 1 p.m., hosted by the North Mason Chamber of Commerce. The park sits just off Highway 3, right next to Belfair Elementary School and across from the Theler Wetlands.

    The Sweetwater Creek project was developed through a partnership between the Hood Canal Salmon Enhancement Group (PNW Salmon Center) and the Port of Allyn. It features the only freshwater ADA-accessible fishing access in Mason County, along with new bridges, trails, a nature playground built from natural materials like boulders and logs, native plant installations, solar panels, and a small hydropower system. It’s free and open to the public — and opened March 31.

    • Ribbon Cutting: Thursday, April 10 at 1:00 PM
    • Location: Next to Belfair Elementary School, across Hwy 3 from Mary E. Theler Wetlands
    • Developer: Hood Canal Salmon Enhancement Group + Port of Allyn
    • Admission: Free

    Also on the radar: Puget Sound West Industrial Development at 25400 SR-3 — a Class A industrial project at the Mason/Kitsap county line with up to 1.4 million square feet planned. Watch for leasing news.

  • Sweetwater Creek Waterwheel Park Opens in Belfair — Ribbon Cutting April 10

    Sweetwater Creek Waterwheel Park Opens in Belfair — Ribbon Cutting April 10

    Something special is happening right in the heart of Belfair — and if you’ve driven past Belfair Elementary on Highway 3, you may have already spotted it. Sweetwater Creek Waterwheel Park is opening its gates, and the North Mason Chamber of Commerce is hosting a ribbon-cutting celebration on Thursday, April 10 at 1 p.m.

    This isn’t just another park. Sweetwater Creek Waterwheel Park is a years-in-the-making community vision brought to life by the Hood Canal Salmon Enhancement Group (also known as the PNW Salmon Center, right off NE Roessel Road in Belfair). Tucked just across Highway 3 from the Theler Wetlands, the park features the only freshwater ADA fishing access in all of Mason County — a real game-changer for families and anglers of all abilities.

    The park also includes native plant gardens, a nature playground, solar panels, and interpretive trails connecting people to the salmon that make Hood Canal country so special. It officially opened to the public on March 31 and is free and open to all.

    The Salmon Center has been a quiet pillar of North Mason life for years — running Salmon in the Classroom, hosting story-time events for babies at their Belfair campus, and stewarding Hood Canal’s watershed one stream at a time. This park is their love letter to Belfair, and the whole community is invited to the celebration Thursday.

    Ribbon Cutting: Thursday, April 10 at 1:00 PM
    Location: Sweetwater Creek Waterwheel Park, next to Belfair Elementary, across Hwy 3 from Mary E. Theler Wetlands
    Hosted by: North Mason Chamber of Commerce — Free and open to the public

  • North Mason Schools & Youth Update — April 8, 2026

    North Mason Schools & Youth Update — April 8, 2026

    The biggest date on the North Mason School District calendar right now isn’t a school dance — it’s April 28. That’s when ballots are due for the district’s replacement levy, the third attempt after voters turned it down in both February and November 2025. The four-year levy would authorize up to $5.5 million per year to fund music programs, middle and high school athletics, school security officers, after-school activities, and help replace the aging community gymnasium roof.

    After the levy failures, Superintendent Kristine Michael told the Mason County Journal the district has been “squeezing every dollar,” with an estimated $1 million-plus shortfall from lower-than-projected enrollment already forcing staff reductions. Ballots should be arriving in mailboxes soon — registration deadline is April 20.

    On a brighter note, your NMHS Bulldogs baseball squad is off to a solid 4-2 start this spring. The ‘Dogs blanked East Jefferson 2-0 in Belfair on Saturday before topping North Kitsap on Monday. Spring sports are rolling, and it’s a great time to get out to Phil Pugh Stadium and cheer on North Mason’s student athletes.

    Looking ahead: Sand Hill Elementary hosts Future Cougar Night on April 14 for families with kids entering kindergarten this fall — a fun evening to meet teachers and tour the school. And mark your calendars for NMHS’s production of Mean Girls on May 29–30 at the Toni M. Smith Auditorium (6:30 PM, $10 w/ASB or $12 general admission).

    • April 20 — Voter registration deadline for April 28 levy election
    • April 14 — Future Cougar Night at Sand Hill Elementary
    • April 28 — NMSD replacement levy ballot deadline
    • May 29–30 — NMHS Mean Girls production, Toni M. Smith Auditorium
  • Claude Managed Agents Pricing: $0.25/Session-Hour — Full 2026 Cost Breakdown

    Claude Managed Agents Pricing: $0.25/Session-Hour — Full 2026 Cost Breakdown

    Updated May 2026

    Pricing updated to reflect current Opus 4.7 launch ($5/$25 per MTok) and the retirement of Claude Sonnet 4 and Opus 4 on April 20, 2026. Managed Agents moved to public beta — see the complete pricing guide for current rate details.

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    $0.08 Per Session Hour: Is Claude Managed Agents Actually Cheap?

    Claude Managed Agents Pricing: $0.08 per session-hour of active runtime (measured in milliseconds, billed only while the agent is actively running) plus standard Anthropic API token costs. Idle time — while waiting for input or tool confirmations — does not count toward runtime billing.

    When Anthropic launched Claude Managed Agents on April 9, 2026, the pricing structure was clean and simple: standard token costs plus $0.08 per session-hour. That’s the entire formula.

    Whether $0.08/session-hour is cheap, expensive, or irrelevant depends entirely on what you’re comparing it to and how you model your workloads. Let’s work through the actual math.

    What You’re Paying For

    The session-hour charge covers the managed infrastructure — the sandboxed execution environment, state management, checkpointing, tool orchestration, and error recovery that Anthropic provides. You’re not paying for a virtual machine that sits running whether or not your agent is active. Runtime is measured to the millisecond and accrues only while the session’s status is running.

    This is a meaningful distinction. An agent that’s waiting for a user to respond, waiting for a tool confirmation, or sitting idle between tasks does not accumulate runtime charges during those gaps. You pay for active execution time, not wall-clock time.

    The token costs — what you pay for the model’s input and output — are separate and follow Anthropic’s standard API pricing. For most Claude models, input tokens run roughly $3 per million and output tokens roughly $15 per million, though current pricing is available at platform.claude.com/docs/en/about-claude/pricing.

    Modeling Real Workloads

    The clearest way to evaluate the $0.08/session-hour cost is to model specific workloads.

    A research and summary agent that runs once per day, takes 30 minutes of active execution, and processes moderate token volumes: runtime cost is roughly $0.04/day ($1.20/month). Token costs depend on document size and frequency — likely $5-20/month for typical knowledge work. Total cost is in the range of $6-21/month.

    A batch content pipeline running several times weekly, with 2-hour active sessions processing multiple documents: runtime is $0.16/session, roughly $2-3/month. Token costs for content generation are more substantial — a 15-article batch with research could run $15-40 in tokens. Total: $17-43/month per pipeline run frequency.

    A continuous monitoring agent checking systems and data sources throughout the business day: if the agent is actively running 4 hours/day, that’s $0.32/day, $9.60/month in runtime alone. Token costs for monitoring-style queries are typically low. Total: $15-25/month.

    An agent running 24/7 — continuously active — costs $0.08 × 24 = $1.92/day, or roughly $58/month in runtime. That number sounds significant until you compare it to what 24/7 human monitoring or processing would cost.

    The Comparison That Actually Matters

    The runtime cost is almost never the relevant comparison. The relevant comparison is: what does the agent replace, and what does that replacement cost?

    If an agent handles work that would otherwise require two hours of an employee’s time per day — research compilation, report drafting, data processing, monitoring and alerting — the calculation isn’t “$58/month runtime versus zero.” It’s “$58/month runtime plus token costs versus the fully-loaded cost of two hours of labor daily.”

    At a fully-loaded cost of $30/hour for an entry-level knowledge worker, two hours/day is $1,500/month. An agent handling the same work at $50-100/month in total AI costs is a 15-30x cost difference before accounting for the agent’s availability advantages (24/7, no PTO, instant scale).

    The math inverts entirely for edge cases where agents are less efficient than humans — tasks requiring judgment, relationship context, or creative direction. Those aren’t good agent candidates regardless of cost.

    Where the Pricing Gets Complicated

    Token costs dominate runtime costs for most workloads. A two-hour agent session running intensive language tasks could easily generate $20-50 in token costs while only generating $0.16 in runtime charges. Teams optimizing AI agent costs should spend most of their attention on token efficiency — prompt engineering, context window management, model selection — rather than on the session-hour rate.

    For very high-volume, long-running workloads — continuous agents processing large document sets at scale — the economics may eventually favor building custom infrastructure over managed hosting. But that threshold is well above what most teams will encounter until they’re running AI agents as a core part of their production infrastructure at significant scale.

    The honest summary: $0.08/session-hour is not a meaningful cost for most workloads. It becomes material only when you’re running many parallel, long-duration sessions continuously. For the overwhelming majority of business use cases, token efficiency is the variable that matters, and the infrastructure cost is noise.

    How This Compares to Building Your Own

    The alternative to paying $0.08/session-hour is building and operating your own agent infrastructure. That means engineering time (months, initially), ongoing maintenance, cloud compute costs for your own execution environment, and the operational overhead of managing the system.

    For teams that haven’t built this yet, the managed pricing is almost certainly cheaper than the build cost for the first year — even accounting for the runtime premium. The crossover point where self-managed becomes cheaper depends on engineering cost assumptions and workload volume, but for most teams it’s well beyond where they’re operating today.

    Frequently Asked Questions

    Is idle time charged in Claude Managed Agents?

    No. Runtime billing only accrues when the session status is actively running. Time spent waiting for user input, tool confirmations, or between tasks does not count toward the $0.08/session-hour charge.

    What is the total cost of running a Claude Managed Agent for a typical business task?

    For moderate workloads — research agents, content pipelines, daily summary tasks — total costs typically range from $10-50/month combining runtime and token costs. Heavy, continuous agents could run $50-150/month depending on token volume.

    Are token costs or runtime costs more important to optimize for Claude Managed Agents?

    Token costs dominate for most workloads. A two-hour active session generates $0.16 in runtime charges but potentially $20-50 in token costs depending on workload intensity. Token efficiency is where most cost optimization effort should focus.

    At what point does building your own agent infrastructure become cheaper than Claude Managed Agents?

    The crossover depends on engineering cost assumptions and workload volume. For most teams, managed is cheaper than self-built through the first year. Very high-volume, continuously-running workloads at scale may eventually favor custom infrastructure.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.

    What to do next

    Now that you have the cost — here’s how to choose and implement

    You know the session-hour rate. The harder decision is whether Managed Agents is the right architecture vs. building on the raw API — or vs. OpenAI’s equivalent.

  • AI Agents Explained: What They Are, Who’s Using Them, and Why Your Business Will Need One

    AI Agents Explained: What They Are, Who’s Using Them, and Why Your Business Will Need One

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    AI Agents Explained: What They Are, Who’s Using Them, and Why Your Business Will Need One

    What Is an AI Agent? An AI agent is a software program powered by a large language model that can take actions — not just answer questions. It reads files, sends messages, runs code, browses the web, and completes multi-step tasks on its own, without a human directing every move.

    Most people’s mental model of AI is a chat interface. You type a question, you get an answer. That’s useful, but it’s also the least powerful version of what AI can do in a business context.

    The version that’s reshaping how companies operate isn’t a chatbot. It’s an agent — a system that can actually do things. And with Anthropic’s April 2026 launch of Claude Managed Agents, the barrier to deploying those systems for real business work dropped significantly.

    What Makes an Agent Different From a Chatbot

    A chatbot responds. An agent acts.

    When you ask a chatbot to summarize last quarter’s sales report, it tells you how to do it, or summarizes text you paste in. When you give the same task to an agent, it goes and gets the report, reads it, identifies the key numbers, formats a summary, and sends it to whoever asked — all without you supervising each step.

    The difference sounds subtle but has large practical implications. An agent can be assigned work the same way you’d assign work to a person. It can work on tasks in the background while you do other things. It can handle repetitive processes that would otherwise require sustained human attention.

    The examples from the Claude Managed Agents launch make this concrete:

    Asana built AI Teammates — agents that participate in project management workflows the same way a human team member would. They pick up tasks. They draft deliverables. They work within the project structure that already exists.

    Rakuten deployed agents across sales, marketing, HR, and finance that accept assignments through Slack and return completed work — spreadsheets, slide decks, reports — directly to the person who asked.

    Notion’s implementation lets knowledge workers generate presentations and build internal websites while engineers ship code, all with agents handling parallel tasks in the background.

    None of those are hypothetical. They’re production deployments that went live within a week of the platform becoming available.

    What Business Processes Are Actually Good Candidates for Agents

    Not every business task is suited for an AI agent. The best candidates share a few characteristics: they’re repetitive, they involve working with information across multiple sources, and they don’t require judgment calls that need human accountability.

    Strong candidates include research and summarization tasks that currently require someone to pull data from multiple places and compile it. Drafting and formatting work — proposals, reports, presentations — that follows a consistent structure. Monitoring tasks that require checking systems or data sources on a schedule and flagging anomalies. Customer-facing support workflows for common, well-defined questions. Data processing pipelines that transform information from one format to another on a recurring basis.

    Weak candidates include tasks that require relationship context, ethical judgment, or creative direction that isn’t already well-defined. Agents execute well-specified work; they don’t substitute for strategic thinking.

    Why the Timing of This Launch Matters for Small and Mid-Size Businesses

    Until recently, deploying a production AI agent required either a technical team capable of building significant custom infrastructure, or an enterprise software contract with a vendor that had built it for you. That meant AI agents were effectively inaccessible to businesses without large technology budgets or dedicated engineering resources.

    Anthropic’s managed platform changes that equation. The infrastructure layer — the part that required months of engineering work — is now provided. A small business or a non-technical operations team can define what they need an agent to do and deploy it without building a custom backend.

    The pricing reflects this broader accessibility: $0.08 per session-hour of active runtime, plus standard token costs. For agents handling moderate workloads — a few hours of active operation per day — the runtime cost is a small fraction of what equivalent human time would cost for the same work.

    What to Actually Do With This Information

    The most useful framing for any business owner or operations leader isn’t “what is an AI agent?” It’s “what work am I currently paying humans to do that is well-specified enough for an agent to handle?”

    Start with processes that meet these criteria: they happen on a regular schedule, they involve pulling information from defined sources, they produce a consistent output format, and they don’t require judgment calls that have significant consequences if wrong. Those are your first agent candidates.

    The companies that will have a structural advantage in two to three years aren’t the ones that understood AI earliest. They’re the ones that systematically identified which parts of their operations could be handled by agents — and deployed them while competitors were still treating AI as a productivity experiment.

    Frequently Asked Questions

    What is an AI agent in simple terms?

    An AI agent is a program that can take actions — not just answer questions. It can read files, send messages, browse the web, and complete multi-step tasks on its own, working in the background the same way you’d assign work to an employee.

    What’s the difference between an AI chatbot and an AI agent?

    A chatbot responds to questions. An agent executes tasks. A chatbot tells you how to summarize a report; an agent retrieves the report, summarizes it, and sends it to whoever needs it — without you directing each step.

    What kinds of business tasks are best suited for AI agents?

    Repetitive, well-defined tasks that involve pulling information from multiple sources and producing consistent outputs: research summaries, report drafting, data processing, support workflows, and monitoring tasks are strong candidates. Tasks requiring significant judgment, relationship context, or creative direction are weaker candidates.

    How much does it cost to deploy an AI agent for a small business?

    Using Claude Managed Agents, costs are standard Anthropic API token rates plus $0.08 per session-hour of active runtime. An agent running a few hours per day for routine tasks might cost a few dollars per month in runtime — a fraction of the equivalent human labor cost.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.

  • Claude Managed Agents vs. Rolling Your Own: The Real Infrastructure Build Cost

    Claude Managed Agents vs. Rolling Your Own: The Real Infrastructure Build Cost

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    Claude Managed Agents vs. Rolling Your Own: The Real Infrastructure Build Cost

    The Build-vs-Buy Question: Claude Managed Agents offers hosted AI agent infrastructure at $0.08/session-hour plus token costs. Rolling your own means engineering sandboxed execution, state management, checkpointing, credential handling, and error recovery yourself — typically months of work before a single production agent runs.

    Every developer team that wants to ship a production AI agent faces the same decision point: build your own infrastructure or use a managed platform. Anthropic’s April 2026 launch of Claude Managed Agents made that decision significantly harder to default your way through.

    This isn’t a “managed is always better” argument. There are legitimate reasons to build your own. But the build cost needs to be reckoned with honestly — and most teams underestimate it substantially.

    What You Actually Have to Build From Scratch

    The minimum viable production agent infrastructure requires solving several distinct problems, none of which are trivial.

    Sandboxed execution: Your agent needs to run code in an isolated environment that can’t access systems it isn’t supposed to touch. Building this correctly — with proper isolation, resource limits, and cleanup — is a non-trivial systems engineering problem. Cloud providers offer primitives (Cloud Run, Lambda, ECS), but wiring them into an agent execution model takes real work.

    Session state and context management: An agent working on a multi-step task needs to maintain context across tool calls, handle context window limits gracefully, and not drop state when something goes wrong. Building reliable state management that works at production scale typically takes several engineering iterations to get right.

    Checkpointing: If your agent crashes at step 11 of a 15-step job, what happens? Without checkpointing, the answer is “start over.” Building checkpointing means serializing agent state at meaningful intervals, storing it durably, and writing recovery logic that knows how to resume cleanly. This is one of the harder infrastructure problems in agent systems, and most teams don’t build it until they’ve lost work in production.

    Credential management: Your agent will need to authenticate with external services — APIs, databases, internal tools. Managing those credentials securely, rotating them, and scoping them properly to each agent’s permissions surface is an ongoing operational concern, not a one-time setup.

    Tool orchestration: When Claude calls a tool, something has to handle the routing, execute the tool, handle errors, and return results in the right format. This orchestration layer seems simple until you’re debugging why tool call 7 of 12 is failing silently on certain inputs.

    Observability: In production, you need to know what your agents are doing, why they’re doing it, and when they fail. Building logging, tracing, and alerting for an agent system from scratch is a non-trivial DevOps investment.

    Anthropic’s stated estimate is that shipping production agent infrastructure takes months. That tracks with what we’ve seen in practice. It’s not months of full-time work for a large team — but it’s months of the kind of careful, iterative infrastructure engineering that blocks product work while it’s happening.

    What Claude Managed Agents Provides

    Claude Managed Agents handles all of the above at the platform level. Developers define the agent’s task, tools, and guardrails. The platform handles sandboxed execution, state management, checkpointing, credential scoping, tool orchestration, and error recovery.

    The official API documentation lives at platform.claude.com/docs/en/managed-agents/overview. Agents can be deployed via the Claude console, Claude Code CLI, or the new agents CLI. The platform supports file reading, command execution, web browsing, and code execution as built-in tool capabilities.

    Anthropic describes the speed advantage as 10x — from months to weeks. Based on the infrastructure checklist above, that’s believable for teams starting from zero.

    The Honest Case for Rolling Your Own

    There are real reasons to build your own agent infrastructure, and they shouldn’t be dismissed.

    Deep customization: If your agent architecture has requirements that don’t fit the Managed Agents execution model — unusual tool types, proprietary orchestration patterns, specific latency constraints — you may need to own the infrastructure to get the behavior you need.

    Cost at scale: The $0.08/session-hour pricing is reasonable for moderate workloads. At very high scale — thousands of concurrent sessions running for hours — the runtime cost becomes a significant line item. Teams with high-volume workloads may find that the infrastructure engineering investment pays back faster than they expect.

    Vendor dependency: Running your agents on Anthropic’s managed platform means your production infrastructure depends on Anthropic’s uptime, their pricing decisions, and their roadmap. Teams with strict availability requirements or long-term cost predictability needs have legitimate reasons to prefer owning the stack.

    Compliance and data residency: Some regulated industries require that agent execution happen within specific geographic regions or within infrastructure that the company directly controls. Managed cloud platforms may not satisfy those requirements.

    Existing investment: If your team has already built production agent infrastructure — as many teams have over the past two years — migrating to Managed Agents requires re-architecting working systems. The migration overhead is real, and “it works” is a strong argument for staying put.

    The Decision Framework

    The practical question isn’t “is managed better than custom?” It’s “what does my team’s specific situation call for?”

    Teams that haven’t shipped a production agent yet and don’t have unusual requirements should strongly consider starting with Managed Agents. The infrastructure problems it solves are real, the time savings are significant, and the $0.08/hour cost is unlikely to be the deciding factor at early scale.

    Teams with existing agent infrastructure, high-volume workloads, or specific compliance requirements should evaluate carefully rather than defaulting to migration. The right answer depends heavily on what “working” looks like for your specific system.

    Teams building on Claude Code specifically should note that Managed Agents integrates directly with the Claude Code CLI and supports custom subagent definitions — which means the tooling is designed to fit developer workflows rather than requiring a separate management interface.

    Frequently Asked Questions

    How long does it take to build production AI agent infrastructure from scratch?

    Anthropic estimates months for a full production-grade implementation covering sandboxed execution, checkpointing, state management, credential handling, and observability. The actual time depends heavily on team experience and specific requirements.

    What does Claude Managed Agents handle that developers would otherwise build themselves?

    Sandboxed code execution, persistent session state, checkpointing, scoped permissions, tool orchestration, context management, and error recovery — the full infrastructure layer underneath agent logic.

    At what scale does it make sense to build your own agent infrastructure vs. using Claude Managed Agents?

    There’s no universal threshold, but the $0.08/session-hour pricing becomes a significant cost factor at thousands of concurrent long-running sessions. Teams should model their expected workload volume before assuming managed is cheaper than custom at scale.

    Can Claude Managed Agents work with Claude Code?

    Yes. Managed Agents integrates with the Claude Code CLI and supports custom subagent definitions, making it compatible with developer-native workflows.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.