The Hub @ Everett, in plain English?

The Hub @ Everett is the rebrand and redesign of the former Everett Mall. The owner, Brixton Capital, announced the transformation in August 2022 and has spent the years since working through demolition, permitting, transit relocation, and tenant negotiations. The big idea is to flip the model. Instead of an indoor mall with everything pointed inward and a parking moat around the outside, The Hub is an outdoor walkable shopping street that runs through the middle of the property.

The Topgolf at The Hub is going up on the southeast side of the property, next to the Regal Cinemas and LA Fitness. The permitted plan is a three-level, 68,000 square foot building with restaurant, bar, event space, and the chain’s signature outfield with electronic targets that golf balls embed RFID tags to score. Everett approved the building permits for the Topgolf project in January 2025. That is the good news. The complicated news is that the opening date is no longer a sure thing.

What is actually open and moving?

While Topgolf waits, the rest of The Hub is not waiting on it. Two big tenant moves are reshaping the rest of the property right now. The first is Ulta Beauty. The second is At Home. Both are relocating into the former Sears building on the north side of the mall — a 100,000-plus square foot box that has been vacant since Sears closed and that has been the single biggest empty space on the property.

Why this matters for Everett’s south end?

The Everett Mall has been the center of gravity for retail south of 41st Street for about 45 years. When it opened in 1980, it pulled shoppers from every direction. By the late 2010s, it was doing what almost every American indoor mall has done — bleeding tenants, struggling on Saturday traffic, and watching anchor stores close and not get replaced. Sears, Macy’s, JCPenney — the cycle was familiar.

The honest read on the timeline?

The original target for The Hub was a 2026 opening for the redeveloped portions, with Topgolf as part of that opening. As of April 2026, the realistic read is more nuanced: The mall station is open. The non-Topgolf tenant moves are progressing. Ulta and At Home moving into the former Sears is real. The outdoor walkable design is being built out in the central portion of the property. The Topgolf opening is the part that has slipped, and nobody is publicly committing to a new date.

Blog

Everett Mall Redevelopment: Topgolf Status & 2026 Updates

What is The Hub @ Everett? The Hub @ Everett is the new name and design for the redeveloped Everett Mall — an outdoor walkable shopping district replacing the former indoor mall, anchored by a planned three-level Topgolf, with Ulta Beauty and At Home moving into the former Sears box. The relocated $2 million Mall Station opened in December 2025, and the broader redevelopment is targeted to open in 2026, though Topgolf’s exact opening date is on hold pending the company’s corporate restructuring.

If you have driven past the Everett Mall in the last six months, you have already noticed it: the old indoor mall is becoming something else. The interior food court is gone, the central building has been carved up, and the walls between the parking lot and the storefronts are coming down. What is going up in its place has a new name — The Hub @ Everett — and a very different idea of what a shopping center is supposed to do in 2026.

We have been watching this one for a while because it is one of the largest physical transformations happening anywhere in the city right now, and it is the rare Everett project that is changing what the south end of town actually looks like — not just adding apartments, but completely rethinking 11 acres at the corner of Everett Mall Way and the Mall Station bus loop.

Here is where things actually stand in April 2026.

The Hub @ Everett, in plain English

The Hub @ Everett is the rebrand and redesign of the former Everett Mall. The owner, Brixton Capital, announced the transformation in August 2022 and has spent the years since working through demolition, permitting, transit relocation, and tenant negotiations.

The big idea is to flip the model. Instead of an indoor mall with everything pointed inward and a parking moat around the outside, The Hub is an outdoor walkable shopping street that runs through the middle of the property. Storefronts open to the sidewalk. Restaurants get patios. The center spine becomes the front door. Brixton’s design team at AD Collaborative described it as turning the mall inside out.

The result is roughly a 20% reduction in overall retail square footage, traded for outdoor walkways, gathering space, restaurant patios, and the new entertainment anchor that is supposed to give the whole district a reason to exist after 8 p.m.

That entertainment anchor is Topgolf.

The Topgolf piece

The Topgolf at The Hub is going up on the southeast side of the property, next to the Regal Cinemas and LA Fitness. The permitted plan is a three-level, 68,000 square foot building with restaurant, bar, event space, and the chain’s signature outfield with electronic targets that golf balls embed RFID tags to score. Everett approved the building permits for the Topgolf project in January 2025.

That is the good news. The complicated news is that the opening date is no longer a sure thing.

Topgolf’s parent company has been working through a corporate restructuring since late 2024 that has affected new construction starts across the country. As of late December 2025, Brixton Capital said publicly that they look “forward to working with them further as they solidify their timing,” which is the polite way of saying nobody has a confirmed opening date for the Everett location. A Topgolf spokesperson confirmed at the same time that the company has no updates to share on the Everett project specifically.

So the permits are in. The site is ready. The financing on the broader Hub project is moving forward. The question is when Topgolf the company is in a position to actually start vertical construction on a 68,000 square foot building in south Everett. That answer has not arrived yet.

What is actually open and moving

While Topgolf waits, the rest of The Hub is not waiting on it. Two big tenant moves are reshaping the rest of the property right now.

The first is Ulta Beauty. The second is At Home. Both are relocating into the former Sears building on the north side of the mall — a 100,000-plus square foot box that has been vacant since Sears closed and that has been the single biggest empty space on the property. Putting two anchor-scale national tenants into that building is the most important leasing event the redevelopment has had to date, because it solves the dead-anchor problem that hollowed out so many American malls in the late 2010s.

The third big move is one most people have already used without thinking about it. Everett Transit’s Mall Station — the bus loop where Everett Transit and Community Transit routes meet on the south side of the property — relocated about 500 feet west of its original location and reopened in December 2025. The City of Everett funded the $2 million station relocation specifically because the old station was sitting on a piece of land that Brixton needed to redevelop. Now riders board from a rebuilt facility, and the redevelopment got the parcel back.

That is the kind of unsexy infrastructure handshake that has to happen before private redevelopment can actually move forward, and the fact that it closed cleanly is one of the reasons the rest of The Hub is on schedule.

Why this matters for Everett’s south end

The Everett Mall has been the center of gravity for retail south of 41st Street for about 45 years. When it opened in 1980, it pulled shoppers from every direction. By the late 2010s, it was doing what almost every American indoor mall has done — bleeding tenants, struggling on Saturday traffic, and watching anchor stores close and not get replaced. Sears, Macy’s, JCPenney — the cycle was familiar.

What is happening at The Hub is the bet that the cure for an old indoor mall is not a slightly nicer indoor mall but a fundamentally different kind of place: an outdoor district with food, entertainment, and walkable retail that gives people a reason to stay for hours instead of running in for one errand.

If that bet works, the practical effect for Everett residents is significant. The Hub sits at one of the most accessible spots in the city — Everett Mall Way, with direct freeway access from I-5 and SR 526, and the relocated Mall Station for transit riders. A redeveloped center with Topgolf, two new anchor tenants, restaurants, and outdoor space puts a real entertainment-and-retail destination on the south end of town for the first time since the original mall’s heyday.

If the bet does not work — if Topgolf’s restructuring drags on, if the outdoor format does not pull Saturday traffic the way Brixton expects — then south Everett gets a partially redeveloped property with empty pad sites for years. That is the version every city in the country is trying to avoid right now with mall redevelopments.

The honest read on the timeline

The original target for The Hub was a 2026 opening for the redeveloped portions, with Topgolf as part of that opening. As of April 2026, the realistic read is more nuanced:

The mall station is open. The non-Topgolf tenant moves are progressing. Ulta and At Home moving into the former Sears is real. The outdoor walkable design is being built out in the central portion of the property. The Topgolf opening is the part that has slipped, and nobody is publicly committing to a new date.

That makes The Hub one of those projects where the headlines and the ground truth are pulling in different directions. The headline version is “mall redevelopment opens in 2026.” The ground truth version is “the mall redevelopment is opening in pieces over the next 18 to 24 months, with the Topgolf piece on its own timeline that depends on a national chain’s restructuring.” Both are true.

What to watch

A few specific things will tell us where The Hub actually lands over the next year:

Watch when Ulta and At Home actually open in the former Sears box. Permits, signage, and hiring announcements are the leading indicators. Both tenants closing the gap between “moving in” and “open for business” is the most important leasing milestone for the redevelopment.

Watch for any movement on the Topgolf vertical construction. Right now the site is permitted and ready. A Topgolf groundbreaking would change the conversation about The Hub immediately. Right now there is silence.

Watch the rest of the central spine. The reason the outdoor walkable design works — or does not — is the smaller restaurants and shops that fill in between the anchors. Brixton has not announced a complete tenant lineup yet for the central walkway portion of the project. Each new lease announcement is a real signal about how attractive the redevelopment is to mid-size national and regional tenants.

We will keep watching. The Hub @ Everett is one of those projects where the version of south Everett that exists in 2030 is going to be meaningfully different depending on how this redevelopment lands. Worth paying attention to.

Frequently Asked Questions

Where is The Hub @ Everett located?

The Hub @ Everett is the redevelopment of the former Everett Mall at 1402 SE Everett Mall Way in south Everett, on roughly 11 acres at the intersection of Everett Mall Way and the relocated Mall Station bus loop.

Is the old Everett Mall closed?

Parts of the original indoor mall have been demolished as part of the redevelopment, including the central food court area. Some existing tenants are still operating, and others — including Ulta Beauty and At Home — are relocating to the former Sears building as the new outdoor walkable design is built out around them.

When will Topgolf in Everett open?

The City of Everett approved the building permits for the three-level, 68,000 square foot Topgolf in January 2025. As of April 2026, Topgolf has not announced a confirmed opening date. The chain’s parent company is working through a corporate restructuring that has affected new construction starts nationally, and Brixton Capital — the mall’s owner — has said publicly that the timing is still being worked out.

What is replacing the old Sears at the Everett Mall?

Ulta Beauty and At Home are relocating into the former Sears building on the north side of The Hub @ Everett. Putting two national anchor-scale tenants into that space is the biggest leasing event the redevelopment has had to date.

Why was the Mall Station moved?

Everett Transit’s Mall Station was relocated about 500 feet west of its original location to clear the parcel for Brixton Capital’s redevelopment. The new $2 million station opened in December 2025 and serves Everett Transit and Community Transit routes.

Who owns the Everett Mall?

The Everett Mall is owned by Brixton Capital, a private real estate investment firm, which announced the redevelopment plan and rebrand to The Hub @ Everett in August 2022.

What does The Hub @ Everett look like compared to the old indoor mall?

The Hub flips the indoor mall model into an outdoor walkable shopping district. A central pedestrian street runs through the property with storefronts, restaurants with patios, and gathering spaces opening directly to it. The redesign reduces overall retail square footage by about 20% in exchange for outdoor walkways, restaurant patios, and the entertainment anchor space for Topgolf.

April 26, 2026
Notion AI for Finance: Automate Close & Reconciliations
Anchor fact: Custom Agents can manage close calendars, draft variance commentary, sequence reconciliations, and produce audit-ready documentation — but should never autonomously approve journal entries or sign off on financial statements.

How does a finance team use Notion AI?

Finance teams use Custom Agents to manage close calendars, draft variance commentary, surface reconciliation exceptions, and prepare audit documentation. The agents handle the documentation and synthesis layer; humans retain decision authority for journal entries, approvals, and any output that gets signed.

The 60-second version

Finance work is 60% documentation and synthesis, 40% judgment. Custom Agents handle the documentation and synthesis layer well. Close calendars, variance narratives, reconciliation status, period-over-period write-ups — agents produce these faster than humans and the audit trail is cleaner. The judgment layer — booking entries, approving reconciliations, signing financial statements — stays human. The split is clean and the leverage is real.

Four finance-specific agent patterns

Four finance-specific agent patterns.

1. The close calendar agent. Manages the month-end close sequence. Reads the close database, identifies dependencies, sequences tasks, surfaces blockers daily. Produces the close standup in three sentences instead of a 30-minute meeting.

2. The variance commentary agent. Reads actuals vs budget. Decomposes variances into drivers. Drafts narrative commentary in your team’s house format. Human reviews, tightens, signs.

3. The reconciliation status agent. Reads the reconciliation database. Flags reconciliations that have stalled, items aging beyond threshold, balances that don’t tie. Surfaces priority queue for the controller’s morning review.

4. The audit prep agent. Pulls evidence packages on demand. Given a control number, assembles the testing workpaper, the sample selections, the evidence references, and the deficiency log. Auditor asks for X; you have it in 15 minutes instead of a week.

What absolutely stays human

What absolutely stays human.

The lines that don’t move:
- Booking journal entries (agent drafts, human posts)
- Approving reconciliations (agent surfaces, human signs)
- Signing off on financial statements (agent prepares; human owns)
- Estimates and judgmental accruals (the judgment is the work)
- Anything that goes to a regulator (period)
The agents do the work that prepares the human to make these calls faster. They don’t replace the calls themselves.

The audit posture shift

The audit posture shift.

For SOX-regulated entities, agent audit trails change the conversation with internal and external audit. Every agent action is logged. The reproducibility of evidence packages improves. Sample selections that used to take days assemble in hours. This isn’t theoretical — finance teams running this pattern in 2026 are reducing audit-prep cycle time meaningfully.

The caveat: audit doesn’t accept “the agent did it” as substantiation. The human review at each gate has to be visible in the trail.

Where finance teams go wrong

1. Letting the agent draft commentary without source attribution. Every variance number needs to tie back to an underlying report or pull. Agents that produce commentary without citations are a control weakness.

2. Skipping period-end re-runs. Agent output reflects the moment it ran. If data changes after the agent drafted commentary, the commentary is stale. Build re-run discipline into the close.

3. Building one mega-agent for finance. Specialized agents (close, variance, recon, audit) outperform a single agent trying to do everything.

Agent drafts, human posts. That line doesn’t move.

Sources
- Notion 3.3 release notes (February 24, 2026)
- Tygart Media editorial line
Continue the journey

This article is part of the May 3 Cliff Decision journey-pack on Tygart Media. Here’s where to go next:
April 25, 2026
Scale Notion AI Output: Why Quality Gates Beat Volume
Anchor fact: AI amplifies whatever editorial infrastructure you have. Tighter inputs and clearer gates produce more reliable output at scale than adding more agents or more credits.

What does “gates before volume” mean for AI workflows?

Gates before volume is the principle that scaling AI output requires tightening quality controls before increasing throughput. Adding more agent runs without first improving inputs, prompts, and review checkpoints multiplies bad output, not good output.

The 60-second version

The temptation when AI starts working is to run more of it. Resist that. The order that works is gates first — the inputs the agent reads, the prompts it uses, the checkpoints that catch bad output — then volume. Operators who skip the gate-tightening phase end up with high-volume slop. Operators who tighten gates first end up with high-volume quality. Same agent, same model, same credits. The difference is the gates.

What a gate actually is

What a gate actually is.

A gate is any checkpoint where output quality gets verified before it propagates downstream. In a Notion AI workflow, gates exist at five points:
1. Input gate — the data the agent reads (database hygiene)
2. Prompt gate — the instructions the agent receives (specificity)
3. Output gate — the format and quality criteria the agent produces against (rubric)
4. Review gate — the human checkpoint before downstream use
5. Distribution gate — what triggers final propagation (publish, send, file)
Each gate is a place where a small fix prevents large drift. Each missing gate is a place where bad output silently propagates.

The volume trap

The volume trap.

Without gates, scaling looks like this: agent runs once, output is mediocre but acceptable. Operator runs it 10× per week. Now there’s 10× the mediocrity. By month three, the operator has built a content factory that produces volume but nobody trusts the output enough to skip review. The “scale” never actually shipped because everything still goes through human eyes anyway.

With gates, scaling looks like this: tighten input substrate, write specific prompts, define a rubric, set a review checkpoint, then ramp volume. Each piece that ships clears the gates. Trust accrues. Eventually the review gate can be sampled rather than universal. That’s when the scale is real.

Five gates worth installing this month

Five gates worth installing this month.
1. A controlled-vocabulary tag system on the databases your agent reads from
2. A prompt template library so prompts are versioned, not improvised
3. A quality rubric for the output type (the foundry article uses a 5-dimension rubric — same idea)
4. A weekly review window where you sample 10% of agent output
5. A failure log where caught drift gets recorded so prompts can be tightened
Why this is hard

Because gates are boring. Volume is exciting. Adding a new Custom Agent feels like progress. Tightening a tag taxonomy feels like procrastination. The operators who win at AI scale are the ones who can stay with the boring work long enough that the volume is actually trustworthy.

Same agent, same model, same credits. The difference is the gates.

Sources
- Tygart Media editorial line
- Notion 3.3 release notes (February 24, 2026)
Continue the journey

This article is part of the May 3 Cliff Decision journey-pack on Tygart Media. Here’s where to go next:
April 25, 2026
Notion Workers for Agents: Code Execution for Builders
Anchor fact: Workers for Agents is in developer preview as of April 2026, accessible via the Notion API but not exposed through any consumer-facing UI yet. Workers run server-side JavaScript and TypeScript, sandboxed via Vercel Sandbox, with a 30-second execution timeout, 128MB memory limit, no persistent state, and outbound HTTP restricted to approved domains.

What is Notion Workers for Agents?

Workers for Agents is Notion’s code execution environment for AI agents, in developer preview as of April 2026. Workers run server-side JavaScript and TypeScript functions that an agent calls when it needs to compute, query a database, transform data, or call an approved external API. Workers are sandboxed (30-second timeout, 128MB memory, no persistent state) and run on Vercel Sandbox infrastructure.

The 60-second version

Workers turn Notion AI from a text layer into a compute layer. Before Workers, Notion AI could read pages and write text. It couldn’t run code, couldn’t transform data, couldn’t reliably call external APIs. With Workers, an agent can offload computational tasks to a sandboxed JavaScript or TypeScript function — running for up to 30 seconds in 128MB of memory, with outbound HTTP restricted to approved domains. It’s the upgrade that makes Notion agents capable of real workflow automation, not just document assistance.

Why Workers matter

Why Workers matter.

Three things change when agents can call code:

1. Real database queries. Before Workers, an agent could read pages but couldn’t reliably do “give me all rows where date is in the next 7 days and owner is unassigned.” With Workers, that’s a one-line query that returns structured data the agent uses in its response.

2. Approved external API calls. An agent can fetch live exchange rates, look up shipping status, query an internal CRM, or pull from any service exposed through an approved domain. The agent doesn’t make the call directly — it delegates to a Worker that does the call and returns the result.

3. Multi-step transformation chains. Read CSV → transform → enrich → write back to a database. Each step is a Worker. The agent orchestrates the chain. This is the pattern that lets agents handle real ops workflows that previously required Zapier, n8n, or custom code.

The technical constraints worth knowing

Workers are not Lambda. They have intentional limits:
- 30-second execution timeout. Anything longer needs to be split into smaller Workers or moved off-platform. No long-running batch jobs.
- 128MB memory limit. Streams and chunked processing only for large data. No loading 500MB CSVs into memory.
- No persistent state between calls. Each Worker invocation is fresh. State lives in Notion databases or external services, not in the Worker.
- Outbound HTTP restricted to approved domains. You declare which domains a Worker can reach. This is a security feature, not a limitation to fight.
- Sandboxed via Vercel Sandbox. Workers run on Vercel’s untrusted-code infrastructure. Performance is solid; cold starts exist.
What you need to use Workers

This is not a point-and-click feature. Requirements:
- A Notion developer account
- A Notion integration set up
- Familiarity with the agent configuration format
- API access — Workers are API-only as of April 2026
If you’ve never built on the Notion API, Workers aren’t your starting point. Standard agents and skills are. Workers are the next step once those don’t go far enough.

Three Worker patterns to start with

Three Worker patterns to start with.

1. The data-fetch Worker. Agent says “I need the current value of X.” Worker calls an approved external API, parses the response, returns a structured value. Common pattern: looking up live data the agent doesn’t have access to natively.

2. The transform-and-write Worker. Agent passes structured input to a Worker. Worker reshapes the data — formatting dates, normalizing strings, computing derived fields — and writes the result to a Notion database row. Common pattern: cleaning incoming form submissions before they land in the CRM.

3. The chain-orchestration Worker. A Worker that calls other Workers in sequence, collecting results and returning a synthesized output. Common pattern: a multi-step intake process where each step needs different logic.

Why this is the more interesting story than May 3

The May 3 credit cliff is the news story. Workers are the strategic story. Workers are why credits exist — Notion can’t ship “an agent that calls any code you want and any API you want” on a flat fee. Credits make Workers viable as a product. The pricing news is the boring infrastructure that supports the interesting capability.

If you’re a developer or an agency building on Notion, Workers reshape what’s possible. A custom Notion deployment for a client used to mean “we set up databases and trained the team.” Now it can mean “we set up databases, trained the team, and built five Workers that handle their specific workflows.”

What’s still missing

What’s still missing.

Three gaps in the current developer preview worth tracking:
- No consumer UI. Workers are API-only. End users can’t build them in the Notion app. This will change.
- Limited debugging. Errors in Workers surface as agent errors. Better tooling for inspecting Worker execution is on the roadmap.
- Sandbox boundaries are evolving. Approved domain lists, memory limits, and timeout limits are likely to relax over time. Build with current limits; don’t bet on them staying fixed.
Workers turn Notion AI from a text layer into a compute layer.

Sources
- Notion 3.4 part 2 release notes (April 14, 2026)
- Vercel blog — How Notion Workers run untrusted code at scale with Vercel Sandbox
- Notion API documentation — Workers for Agents (developer preview)
Continue the journey

This article is part of the May 3 Cliff Decision journey-pack on Tygart Media. Here’s where to go next:
April 25, 2026
When Not to Use a Notion AI Agent (What to Keep Manual)
Anchor fact: Custom Agents are powerful but inappropriate for tasks involving novel judgment, regulated content, sensitive personnel matters, or work where the cost of being wrong exceeds the cost of doing it manually.

When should you not use a Notion AI agent?

Don’t use Notion agents for tasks requiring novel judgment about people, compliance-sensitive output (legal, medical, financial guidance), one-off work that won’t repeat, or any decision where the cost of being wrong is higher than the cost of doing the work manually.

The 60-second version

Notion agents are a hammer. Not everything is a nail. The honest list of tasks that should stay manual is longer than most operators want to admit. Performance reviews. Hiring decisions. Compliance-sensitive drafting. Anything that gets sent to a regulator or a lawyer. One-off work. Anything where the value of doing it yourself is the thinking, not the output. The discipline of saying “not this one” is what separates operators who use AI from operators who use AI badly.

Five categories that stay manual

Five categories that stay manual.

1. Decisions about specific humans. Performance reviews, hiring choices, conflict mediation, layoff decisions. The agent can summarize and surface evidence; it shouldn’t draft the decision. The risk isn’t that the output is wrong — it’s that the decision-maker outsources the moral weight of the call. Don’t.

2. Regulated or compliance-sensitive output. Legal language, medical guidance, financial advice, anything that gets reviewed by a regulator. Use AI to draft inputs to a human reviewer. Never ship the AI output as final.

3. Novel work without precedent. “Plan our entry into a new market.” “Write our crisis response if X happens.” Agents synthesize from existing patterns. They struggle when the situation has no analog in your workspace.

4. One-off tasks. Building a Custom Agent for a task you’ll do once is more work than just doing the task. The investment in setup (prompt, scope, rubric, review) only pays back across many repetitions.

5. Work where doing it is the point. Strategic thinking. Writing meant to clarify your own ideas. Reflection journals. The output isn’t the value; the doing is. AI shortcuts the doing, which destroys the value.

The dangerous middle category

The dangerous middle category.

Worse than tasks that obviously shouldn’t be agent work are tasks that look like agent work but aren’t. Examples:
- “Draft client emails” — sounds like a clear agent task, but the relationship cost of off-tone email outweighs the time saved
- “Summarize our team’s wins for the board” — looks easy, but framing matters and an agent’s framing is generic
- “Write our company values” — agents can produce values; only humans can mean them
The test: if the value of the output depends on being recognizably yours, agent involvement should be limited to research and drafting, not production.

How to decide

How to decide.

Three questions before launching a new Custom Agent:
1. Will I do this task at least 20 times in the next year? (No → don’t build an agent.)
2. Is the cost of a wrong output bounded? (No → don’t automate it.)
3. Is the value in the output, not the doing? (No → don’t outsource the doing.)
If any answer is no, the task stays manual. That’s not a failure of AI. That’s discipline.

AI shortcuts the doing, which destroys the value.

Sources
- Tygart Media editorial line
- Operator practice notes
Continue the journey

This article is part of the May 3 Cliff Decision journey-pack on Tygart Media. Here’s where to go next:
April 25, 2026
Notion Custom Agent ROI: Calculating Your Time Reclaimed
Anchor fact: Notion Custom Agents cost $10 per 1,000 credits starting May 4, 2026. Credits reset monthly with no rollover. Simple agent runs use a handful of credits; complex multi-step runs can use dozens to hundreds.

How do you calculate ROI on a Notion Custom Agent?

Multiply the human-equivalent time saved per agent run by the dollar value of that time, subtract the credit cost per run (at $10/1000 credits starting May 4, 2026), then multiply by run frequency. An agent that saves 30 minutes of work per run at $50/hour, costs 5 credits ($0.05) per run, and runs daily produces ~$700/month in net value.

The 60-second version

Most operators don’t do the math because the math feels small. It isn’t. A Custom Agent that runs daily and saves 30 minutes of $50-an-hour work produces about $750/month in time savings and costs maybe $1.50 in credits. The ratio is so favorable for the right agents that the real ROI question isn’t whether agents pay back — it’s which agents to retire because the math doesn’t clear. After May 4, the bottom of the agent fleet stops being free. That’s good. That’s how you stop running agents that weren’t earning their keep.

The simple formula

The simple formula.

For any Custom Agent:
- Time saved per run (minutes) × frequency (runs per month) × hourly value ($/hour ÷ 60) = monthly value
- Credits per run × frequency × $0.01 (since $10/1000 = $0.01/credit) = monthly cost
- Monthly value − monthly cost = net ROI
Three worked examples:

Example 1 — The weekly digest agent.
Saves 45 minutes/run, runs 4×/month, your hourly value is $75. Monthly value: 45 × 4 × ($75/60) = $225. Credits: ~20/run × 4 × $0.01 = $0.80. Net: $224.20/month. Keep it.

Example 2 — The lead enrichment agent.
Saves 5 minutes/run, runs 200×/month (every new lead), hourly value $50. Monthly value: 5 × 200 × ($50/60) = $833. Credits: ~3/run × 200 × $0.01 = $6. Net: $827/month. Keep it.

Example 3 — The exploratory analysis agent.
Saves 15 minutes/run, runs 2×/month, complex multi-step (~80 credits). Monthly value: 15 × 2 × ($50/60) = $25. Credits: 80 × 2 × $0.01 = $1.60. Net: $23.40/month. Keep it, but barely. If credit cost rises or run complexity grows, retire it.

Where the math turns negative

Where the math turns negative.

Three patterns where the ROI math fails:
1. The fancy agent that runs occasionally. Complex agents cost dozens to hundreds of credits per run. Low frequency means the per-month cost is small but so is the value. Net is small. Better as a manual prompt.
2. The agent that needs human review on every output. If you review 100% of the output anyway, the time saved is partial. Reduce the apparent monthly value by 40-60%. Many agents stop clearing the bar with that haircut.
3. The agent that runs but the output isn’t used. This is the silent killer. Credits consumed, no value extracted. The fix is monthly observation: which agent outputs do you actually open?
The portfolio approach

Treat your Custom Agents as a portfolio. Three categories:
- Anchors (top 3-5 agents producing outsized ROI). Protect their credit budget first.
- Earners (agents producing positive but modest ROI). Watch monthly. Retire if drift.
- Experiments (agents under evaluation). Cap at 20% of credit budget.
Anything outside those three categories is waste.

The monthly review ritual

The monthly review ritual.

Once a month, look at:
- Credits consumed per agent (Notion’s dashboard will show this)
- Outputs produced per agent
- Outputs you actually used per agent
- Time saved estimate per agent
The gap between “outputs produced” and “outputs used” is where the budget goes to die. Close that gap or retire the agent.

Treat your Custom Agents as a portfolio. Anchors, earners, experiments. Anything outside those three is waste.

Sources
- Notion Help Center — Custom Agent pricing
- Notion 3.3 release notes (February 24, 2026)
Continue the journey

This article is part of the May 3 Cliff Decision journey-pack on Tygart Media. Here’s where to go next:
April 25, 2026
Notion Custom Agents vs Basic AI: Is the Upgrade Worth It?
Anchor fact: Custom Agents are available on Business and Enterprise plans only. They run autonomously on triggers or schedules, can work for up to 20 minutes per task across hundreds of pages, and starting May 4, 2026, consume Notion Credits at $10 per 1,000.

Do you need Notion Custom Agents or is basic Notion AI enough?

Basic Notion AI handles inline drafting, summaries, and reactive prompts within a page. Custom Agents add proactive execution — running on schedules or triggers, working autonomously for up to 20 minutes, and using skills and Workers. Choose Custom Agents only if you have recurring autonomous workflows that justify Business-plan pricing and Notion Credit consumption.

The 60-second version

Most operators don’t need Custom Agents. They think they do because the marketing makes Custom Agents sound essential, but the honest answer is that basic Notion AI plus standard agent prompts cover most knowledge-work needs. Custom Agents earn their cost only when you have specific, repeating, autonomous work — things that run on a schedule or trigger without you starting them. If you don’t have that pattern in your workflow, you’re paying for capability you won’t use.

The honest comparison

The honest comparison.

Basic Notion AI (included on Plus, Business, Enterprise plans):
- Inline writing assistance — draft, rewrite, summarize, translate
- Q&A over your workspace content
- Standard AI Autofill on databases
- Meeting notes summarization
- Reactive: you prompt, it responds
Custom Agents (Business and Enterprise plans only):
- Everything above, plus:
- Runs on schedules or triggers without prompting
- Can work autonomously for up to 20 minutes per task
- Spans hundreds of pages in a single run
- Skills can be attached for repeatable workflows
- Workers integration (developer preview) for code execution
- Can integrate with Calendar, Mail, Slack at agent level
- After May 4, 2026: consumes Notion Credits at $10/1000
When Custom Agents are worth it

When Custom Agents are worth it.

Five workflow patterns where Custom Agents pay off:

1. Recurring deliverables. Weekly status reports, monthly board prep, daily standups. If you produce the same shape of document on a schedule, an agent that runs Friday at 4 PM and drops the draft in your inbox is worth real money in time saved.

2. Continuous database enrichment. A CRM that needs new leads scored, categorized, and routed within minutes of arrival. A content database that needs incoming articles tagged and summarized. An ops database that needs items checked for SLA breaches.

3. Cross-source synthesis on demand. “Pull everything from the last two weeks across Slack, Calendar, and our project pages and tell me what’s at risk.” This is a 20-minute autonomous task that would take a human two hours.

4. Multi-step workflows with handoffs. Triage incoming → route to owner → draft response → flag exceptions. The chain is what makes it agent work, not assistant work.

5. Off-hours and overnight work. If you’d benefit from work happening while you sleep, agents are the only Notion layer that can do it. Reactive AI sits idle until you arrive.

When basic Notion AI is enough

When basic Notion AI is enough.

Most knowledge workers fit here:
- Solo writers and researchers who need help drafting and summarizing
- Teams of fewer than 10 where work is mostly real-time collaborative
- Workflows where the AI is occasional, not scheduled
- Anyone on Plus plan (Custom Agents aren’t available anyway)
- Anyone whose AI usage is “I ask, it answers” — that’s reactive, not agentic
If you’re in this group, upgrading to Business for Custom Agents is paying for capacity you won’t use. Stay with basic AI and revisit when the workflow pattern changes.

The cost calculus after May 4

Before May 4, 2026, Custom Agents are free to try on Business and Enterprise. After, every run consumes credits at $10 per 1,000. Real numbers:
- A simple agent run (single-page summary): typically a handful of credits — pennies
- A complex multi-step run (synthesis across many pages, multiple skills chained): can run into the dozens or hundreds of credits — measurable dollars
- A daily scheduled agent that runs 30 days/month at moderate complexity: budget low tens of dollars per agent per month
Math gets serious when you have many agents running daily. A workspace with 10 active Custom Agents can easily consume hundreds of dollars per month in credits on top of Business-plan seat fees. That’s the ROI conversation that turns “I’m experimenting with agents” into “I run a small fleet on a budget.”

The decision framework

Walk yourself through these four questions:
1. Do you have recurring work on a schedule? No → basic AI is fine.
2. Are you on Business or Enterprise? No → Custom Agents aren’t available. Upgrade or stay with basic.
3. Does the time saved per agent run, multiplied by frequency, exceed the credit cost? No → basic AI plus manual prompts is cheaper.
4. Are you willing to manage the credit pool monthly? No → don’t take on the operational overhead.
If all four are yes, Custom Agents earn their place. If any is no, basic Notion AI is the right call.

Reactive AI sits idle until you arrive.

Sources
- Notion 3.3 Custom Agents release notes (February 24, 2026)
- Notion Help Center — Custom Agent pricing
- Notion Pricing page (April 2026)
Continue the journey

This article is part of the May 3 Cliff Decision journey-pack on Tygart Media. Here’s where to go next:
April 25, 2026
Notion Custom Agents Pricing: The May 3 Operator Checklist
Anchor fact: Custom Agents are free to try through May 3, 2026. Starting May 4, they require Notion Credits at $10 per 1,000 credits, and access stays gated to Business and Enterprise plans.

What changes for Notion Custom Agents on May 3, 2026?

Custom Agents are free to try through May 3, 2026 on Business and Enterprise plans. Starting May 4, agents require Notion Credits at $10 per 1,000 credits. Credits are workspace-shared, reset monthly, and don’t roll over. If credits hit zero, every Custom Agent in the workspace pauses until an admin tops up.

The 60-second version

If you’re running Notion Custom Agents on a free trial right now, you have until May 3, 2026 before the meter starts. On May 4, agents stop running unless your workspace admin has bought Notion Credits at $10 per 1,000 credits. Credits reset monthly. They don’t roll over. Custom Agents stay locked to Business and Enterprise plans only — Free and Plus plans don’t get them at all.

The decision in front of you isn’t “should I keep using Custom Agents.” It’s three smaller decisions stacked: whether to be on the right plan, whether to budget credits, and whether the agents you’ve already built earn their keep at the new price.

This article walks through each one in operator terms.

What actually changes on May 4

What actually changes on May 4.

Before May 3:
- Custom Agents run for free on Business and Enterprise plans (including Business trials)
- No credit accounting
- You can build, test, and run as much as your plan allows
On and after May 4:
- Custom Agents consume Notion Credits per task
- Credits cost $10 per 1,000, billed as a workspace-level add-on
- Credits are shared across the workspace, not per-seat
- Credits reset every month with no rollover
- If the credit pool empties, every Custom Agent in the workspace pauses until an admin tops up
- Agents stay on Business and Enterprise plans only — no migration path to Free or Plus
The mechanic worth pausing on: shared, non-rolling, hard-pause-on-zero. That’s not a soft throttle. If your workspace runs out mid-month, the agent that drafts your weekly board update doesn’t degrade gracefully. It stops. An admin has to log in and add credits before anything resumes.

Why this matters more than it sounds

Most of the coverage of this transition reads it as a pricing announcement. It’s actually a posture announcement. Notion is saying: agents are real infrastructure, real infrastructure has metering, and metering changes how teams use it.

Three knock-on effects worth thinking about:

1. The “leave it running and forget about it” pattern dies. Free trial behavior — point an agent at a database, walk away, come back a week later, see what it did — becomes expensive behavior. Every autonomous run consumes credits. If you’ve built agents that run on schedules or triggers, that scheduled work is now a line item.

2. Agent ROI becomes a real conversation. Up to now, the question was “does this agent save me time?” Starting May 4, the question is “does this agent save me time at a credit cost lower than what my time is worth?” That’s a much sharper test, and a fair number of trial-era agents won’t survive it.

3. The build-vs-prompt decision shifts. A one-off prompt to Notion AI inside a doc still runs on plan-included AI. A Custom Agent — even doing similar work — runs on credits. For repetitive work that’s worth automating, the agent still wins. For occasional work, you may quietly retreat to manual prompts.

What you should do this week

What you should do this week.

This is the operator’s checklist, in priority order.

1. Audit every Custom Agent you’ve built

Open your workspace’s Custom Agents list. For each one, write down four things:
- What does it do?
- How often does it run?
- Roughly how complex is each run (one step, multi-step, multi-page)?
- What’s the human equivalent — how long would the task take a person?
Anything you can’t answer is a candidate to retire on May 3.

2. Identify your top 3 keepers

Sort the list by “human equivalent time saved per month.” The top three are your ROI anchors. Those are the agents you’ll actively budget credits for. Everything below the line is provisional — keep them running only if credit headroom allows.

3. Get on the right plan if you aren’t already

Custom Agents stay on Business and Enterprise. If your workspace is on Free or Plus and you’ve been using Custom Agents on a Business trial, the trial expiry is the cutoff. After that, agents disappear entirely unless you upgrade. Business is $20 per user per month billed annually, $24 monthly. Enterprise is custom-priced.

4. Have an admin set up the credit dashboard before May 4

The credit dashboard is where admins buy and track credits. The smart move is to provision a starter pack — somewhere in the hundreds-to-low-thousands range of credits — before the cutover, so your top-three agents don’t pause on the first morning of the new pricing era. You can scale credit purchases up or down monthly based on what actually gets consumed.

5. Set up usage observation

Once credits are running, treat the first 30 days as data collection. Watch which agents burn credits fastest. Watch which agents you actually open the output of. The gap between “credits consumed” and “output used” is where the next round of agent retirement happens.

The trap to avoid

The trap to avoid.

The natural temptation between now and May 3 is to build more agents while it’s still free. Don’t. The agents you build in a free-trial mindset are precisely the ones you’ll regret budgeting credits for in May.

A better use of the remaining trial window: harden the agents you already have. Tighten their scopes. Reduce the number of pages they touch. Cut the multi-step chains that don’t need to be multi-step. Every operation you can shave off a workflow today is a credit you don’t spend tomorrow.

This is the gates-before-volume principle applied to agents. You don’t scale by adding more agents. You scale by making each agent leaner before the meter starts.

What this signals about Notion’s roadmap

Reading the tea leaves: credit-based pricing for agents is the foundation for Workers for Agents (currently in developer preview as of April 2026). Workers let agents call code and external APIs. That’s the kind of capability that needs metering — you can’t ship “an agent that calls any API you want” on a flat fee. Credits make Workers possible at scale.

If you’re a developer or an agency, this is the more interesting story. The May 3 cliff is the boring part. The Workers preview is the part to watch, and credits are the pricing rail that makes Workers viable as a product.

The operator’s bottom line

May 3 is not a problem to solve. It’s a forcing function that turns “I’m experimenting with agents” into “I run a small fleet of agents on a budget.”

That’s a healthier place to be. Free trials produce sprawl. Metered usage produces discipline.

Decide your top three. Get on the right plan. Have an admin top up credits before May 4. Spend the next week tightening, not building. That’s the entire move.

Sources
- Notion Help Center — Buy & track Notion credits for Custom Agents
- Notion 3.3 release notes (February 24, 2026)
- Notion Pricing page (April 2026 snapshot)
Continue the journey

This article is part of the May 3 Cliff Decision journey-pack on Tygart Media. Here’s where to go next:
April 25, 2026
Southern Hood Canal Frost Advisory: April 25-26, 2026
What’s Happening

The National Weather Service in Seattle issued a Frost Advisory on Saturday, April 25, 2026 at 10:02 AM PDT. Temperatures as low as 32°F are forecast overnight, which will cause frost formation and can damage or kill sensitive outdoor plants left uncovered.

Where

The advisory covers Southern Hood Canal (which includes Belfair and the North Mason shoreline along the canal), the Olympia and Southern Puget Sound area, the Lowlands of Lewis and Southern Thurston Counties, the Lowlands of Pierce and Southern King Counties, and the City of Seattle. Mason County is included via the Southern Hood Canal zone (WAZ321) and SAME code 053045.

When

In effect from 11 PM Saturday night (April 25) through 10 AM Sunday morning (April 26).

What To Do
- Cover sensitive plants — vegetables, tender annuals, anything newly planted. A sheet, frost cloth, or even a cardboard box works.
- Bring potted plants inside or move them against the south side of the house under cover.
- Drain garden hoses and disconnect them from spigots to prevent freeze damage.
- Cover outdoor faucets with insulated covers if you have them.
- Check on neighbors — especially anyone elderly or with outdoor pets.
Source

National Weather Service Seattle — Frost Advisory issued April 25, 2026 at 10:02 AM PDT, valid through April 26 at 10:00 AM PDT. weather.gov/sew
April 25, 2026
Tier-Gated Autonomy: Google Validates AI Agent Governance

Related on Tygart Media: AI operator’s stack · Claude calibration.

This article was not written by a scheduled task. It was not part of a batch pipeline. There was no cron job, no Cloud Run trigger, no automation queue. I asked Claude in chat, we picked an angle, I generated the images myself, and Claude hand-crafted what you are reading now. Custom, batch-of-one, at the desk. I’m leading with that because it is the entire point of the piece.

On April 22, Google Cloud Next ’26 turned Vertex AI into something else. The keynote rebranded it as the Gemini Enterprise Agent Platform. The new pieces are an Agent Designer, an Agent Inbox, long-running agents that can work autonomously for days inside cloud sandboxes, and Agent Observability, Agent Simulation, Agent Identity, Agent Registry. Google framed agents as managed enterprise workloads with identity, policy, observability, evaluation, and runtime controls, rather than one-off AI applications. They added Anthropic’s Claude Opus 4.7 to the Model Garden alongside Gemini 3.1. They committed $750 million to a partner program to push it through Accenture, Salesforce, SAP, and Deloitte.

That announcement is the most architecturally ambitious version of agentic infrastructure anyone has shipped. It is also enterprise-shaped, not operator-shaped. The customers in the keynote were Walmart, Citadel, Honeywell, Home Depot, Papa John’s. The framing was Agentic Enterprise. The unit of trust was a partner integrator. None of that is a criticism. It is just a different scale of problem than the one a sole operator running 20+ WordPress sites and a content automation stack actually has.

What Google announced is what we already built — at our scale

Underneath the marketing, Gemini Enterprise Agent Platform answers one specific question: how do you give an autonomous system enough leash to be useful, while keeping enough control to catch it when it fails? Google’s answer involves Agent Identity, runtime policy enforcement, observability dashboards, and evaluation harnesses. It is the right answer. It is also the answer we landed on — independently, six months earlier, at a much smaller scale — because the question is the same whether you are running a Fortune 50 supply chain or a one-person agency that publishes 200 articles a month.

Tier-gated autonomy: amber proposes and waits for approval, blue prepares but never publishes, green runs autonomously and reports anomalies.

Our version is called The Bridge. It is a top-level page in our Notion workspace, peer to the operations Command Center. Underneath it lives the Promotion Ledger, where every autonomous behavior in our stack is tracked by tier and status. Tiers are A, B, C, and Wings. Status is one of Running, Probation, Demoted, Candidate, Graduated, or Retired. The Pane of Glass is the live Cowork artifact view of the whole thing. It is the operator-scale equivalent of Google’s Agent Inbox, except it is not selling itself to me — it is reporting to me.

The three tiers, in plain language

Tier A — System proposes, operator approves. A behavior at this tier produces a recommendation, not an action. Claude flags an opportunity, drafts a structure, surfaces a candidate. I make the call. Approval happens through an elevated report, not an atomic checkbox queue. This is where everything new starts.

Tier B — Operator flies it, system prepares. The behavior is allowed to do all the preparatory work — research, drafting, formatting, staging — but the publish button stays under my hand. This is where most behaviors live for a while. Most of the trust gap is closed at Tier B because I can see exactly what the system would have done before it does it.

Tier C — System runs autonomously, reports anomalies. The behavior publishes, posts, files, schedules — without asking. It only surfaces in my inbox when something is off. The twice-daily software update monitoring pipeline that writes posts to The Machine Room category on this site is Tier C. So is the weekly digest that drafts the LinkedIn and Facebook posts off it. I do not see those running. I see them only when they fail to run.

Wings is a fourth tier — used for behaviors that are still on the candidate list, where the architecture exists but the trust does not yet.

The clock that makes it work

Promotions are not a feeling. They are a count. Seven clean days at a tier makes a behavior a candidate for promotion to the next. Any gate failure resets that clock to zero and drops the behavior down one tier. The failure is logged on the Promotion Ledger row with date and reason. Decisions to promote or demote happen on Sunday evenings — not in the middle of a panic on a Tuesday.

This is the part that most “AI agent governance” frameworks skip. They define the tiers but not the promotion mechanic. Without the clock, every promotion is a vibe call. With the clock, the question stops being do I trust this agent and becomes what does the ledger say. The answer is either there or it is not.

Trust as evidence. The Promotion Ledger reads clean — or it does not. Reassurance is not a substitute for a number on a row.

Why this article is hand-crafted, on purpose

Here is the meta-move that makes the framework legible. The system that publishes most of our content is Tier C Running — twice-daily monitoring writes posts directly to The Machine Room and Industry Signals categories without my approval, and the weekly digest drafts the social. That works because the behavior has earned its leash on the ledger.

This article is not that. This article is a one-off, custom request, hand-crafted in chat. I asked Claude what it thought of the Next ’26 announcements relative to our stack. We had a real exchange about it. I generated four sets of images on my own, picked the directions, and let Claude pick the strongest variants from each set. We agreed on the angle. Then I gave one explicit, in-conversation authorization to publish live to WordPress and LinkedIn — because publishing to LinkedIn live is not a Tier C Running behavior on the ledger right now, and the system correctly flagged that gap and asked.

That is the whole framework, working in real time. The twice-daily Tier C automation does not need to ask. The one-off LinkedIn live publish does need to ask. The system knows the difference because the difference is on a Notion page, not in a vibe.

What Google’s announcement actually changes for operators like us

Three things, all useful.

The vocabulary went mainstream. “Long-running agents,” “Agent Inbox,” “agent governance,” “agent observability” — these are now words you can say to a CFO without translating. The bar for trust-gap evidence just went up across the field, which means the operators who already have a ledger are ahead of the operators who have a vibe. Stay on the ledger.

Claude is in the Model Garden. If we ever want to run our Cowork-style behaviors inside Google’s agent runtime — using their identity, observability, and governance plumbing while keeping Claude as the model — that door is now open. We will not, because the platform overhead is more than we need. But the option being available is structurally significant.

The architectural pattern is validated. When the third-largest cloud spends a keynote arguing that agents need tier-style governance and an inbox-style observability layer, every operator running an autonomous stack should treat that as confirmation, not as a sales pitch. We are not the weird ones for running a Promotion Ledger. We were just early.

The unsexy part

The unsexy part of all of this is that none of it works without the boring discipline of writing things down. The tiers are useful because they are on a page. The promotion clock is useful because it is a number. The trust-gap protocol is useful because it points to evidence rather than to feelings. Google is building the same thing for the Fortune 500 because the discipline is the same at every scale. The only thing that changes is whether you call it a Promotion Ledger or an Agent Registry.

Build the ledger. Run the clock. Publish what is earned. Ask before you do what is not. The rest is just whose dashboard is prettier.

April 25, 2026