Tag: Productivity

  • Why I Judge AI Deliverables by Outcomes, Not Effort

    Why I Judge AI Deliverables by Outcomes, Not Effort

    When I think about AI deliverables, I keep coming back to a simple scenario: a client receives two pieces of work.

    Both deliverables solve the problem they were hired to solve. Both are accurate, useful, and tied to the same business outcome. The client is happy, and from the outside, there is no meaningful difference in the results.

    Then the client learns that one took 20 hours to create, while the other took 20 minutes. That is when the uncomfortable questions begin.

    Was AI involved? Should the faster deliverable cost less? Is the person who completed it less skilled because they found a faster, more efficient way to reach the same result?

    What I find most interesting is how differently many of us react to AI depending on which side of the transaction we are on. I love using AI when it saves me time, but I also understand why customers can feel uneasy when they discover AI helped create something they paid for.

    I recently ran a LinkedIn poll asking a simple question: if the outcome is great, do we really care how it was made?

    The responses reinforced something I have been thinking about for a while. Many of the strongest objections people have to AI are not really about quality at all.

    The Time vs. Value Fallacy

    I think part of the discomfort comes from the fact that we have spent decades tying value to effort.

    Long hours feel valuable. Fast work feels suspicious. Struggle often gets mistaken for expertise.

    The harder something appears to be, the easier it becomes to justify the price attached to it.

    There is an old story about a ship engine that stopped working. After multiple failed attempts to repair it, the owners brought in an engineer with decades of experience. He inspected the engine, tapped it once with a small hammer, and the machine roared back to life.

    His invoice was $10,000.

    Image

    The owners were furious and demanded an itemized bill. The response was simple: hammer tap, $2. Knowing where to tap, $9,998.

    People debate whether that story is true or just a useful tale for people like me who believe in value-based pricing. But whether it really happened almost does not matter. The lesson still holds.

    People are not paying for the tap. They are paying for the expertise behind it.

    That is what makes AI such an important topic for me. It forces us to confront a question many of us have avoided for years: are we paying for expertise, or are we paying for visible effort?

    Those are not always the same thing.

    The Objections That Actually Matter

    To be clear, I do not think every objection to AI is unreasonable. I have shared plenty of my own concerns, and some of them are serious.

    In fact, I think the strongest arguments against AI have very little to do with how quickly something was created.

    Risk matters. Hallucinations matter. Bad recommendations matter. Compliance, privacy, and security concerns matter. Accountability matters.

    Those are legitimate concerns. What stands out to me is that none of them has much to do with how long it took to create the deliverable.

    They are questions of trust.

    Can the output be trusted? Can the recommendation be defended? Can someone confidently stand behind the work if it is questioned six months from now?

    ```json
{
  "alt": "SEO For Lunch Newsletter by Nick Leroy, featuring actionable SEO insights.",
  "caption": "Join Nick Leroy's SEO For Lunch: Your go-to source for actionable SEO insights served directly to your inbox.",
  "description": "This image promotes Nick Leroy's 'SEO For Lunch' newsletter, emphasizing actionable SEO insights. It features a smiling person against a dark blue background with the newsletter's branding, '#SEOFORLUNCH,' and website details. The design includes graphic elements like a fork and knife, alongside the tagline 'Not Your Average Table Talk.'"
}
```

    Because when something goes wrong, nobody gets to blame the AI. The employee is accountable. The consultant is accountable. The company is accountable.

    That is why I have always found the quality debate to be the least interesting part of the conversation. The more important question is not whether AI was involved. It is whether the outcome is trustworthy enough for someone to put their name behind it.

    The Outcome Test

    The more I think about AI, the less interested I become in whether it was used.

    Instead, I find myself asking a different set of questions. Was the outcome accurate? Was it useful? Was it better than the alternative? Would I be willing to stand behind it with my name, reputation, and credentials on the line?

    If the answer to all of those questions is yes, then I have a hard time arguing that the production method matters more than the result.

    I suspect this is where many people become uncomfortable because it shifts the conversation away from tools and back toward results.

    Ironically, this is also where humans become more important, not less.

    The future is not machines versus humans. I know, "The Terminator" and "I, Robot" movies will never feel the same. The real shift is humans using AI versus humans who refuse to adapt.

    The premium will not come from avoiding AI. It will come from judgment, taste, decision-making, communication, and accountability.

    AI can accelerate execution, but people still decide what should be built, what should be published, and what risks are acceptable. More importantly, people are still responsible for the outcome.

    The people who lose to AI will not be the ones using it. They will be the ones still evaluating effort while everyone else is measuring outcomes.

    This post first appeared on the author’s website and is republished here with permission.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Why I Stop Positioning AI as a People Replacement

    Why I Stop Positioning AI as a People Replacement

    I think one of the biggest mistakes in AI marketing is positioning a product as a replacement for people. That message can win attention in the short term, but I believe it quietly drains trust over time.

    This is a little different from what I usually write about, but it matters. The way we talk about AI shapes how customers, employees, executives, and markets respond to it.

    In this memo, I want to focus on three things: why “substitution positioning” feels powerful at first but weakens a brand later, what the data says about whether AI is actually replacing people, and how I think companies should position AI instead.

    Image

    The cardinal sin of positioning in the AI era is replacement. I call it substitution positioning. It is tempting because it sounds bold, efficient, and disruptive. But over time, it creates anxiety, skepticism, and credibility problems.

    We have seen this pattern already. Anthropic CEO Dario Amodei predicted that software engineering jobs could disappear within 6 to 12 months as models began doing most or all of what software engineers do end to end. Yet demand for software engineers has continued to look strong.

    Image

    OpenAI CEO Sam Altman also predicted that many customer support jobs would go away because AI could handle that work better. Soon after, customer service hiring began outpacing the broader job market.

    I understand why fear works as a marketing tool. The fear of being replaced gets attention fast. It got me, too. When powerful AI models gained traction, I worried about my own future. But when I still see AI companies hiring copywriters, SEOs, engineers, and support teams, I sleep better.

    Image

    Fear sells because it taps into fight-or-flight. Layoffs make that story even louder. They let companies frame cost-cutting as innovation and make the replacement narrative feel more real than it may actually be.

    But I do not think the facts support the clean replacement story. In New York, companies can indicate when mass layoffs are caused by technological innovation or automation. In one reported period, more than 160 companies filed mass layoffs affecting roughly 28,300 workers, and not one chose AI as the reason. That list included companies such as Amazon and Goldman Sachs.

    Image

    Researchers at Yale also studied employment data from the Current Population Survey over 33 months and found no evidence of job displacement from AI. To me, the pattern looks less like instant replacement and more like the earlier waves of computers and the internet changing how work gets done.

    That is why I keep coming back to this point: stop trying to make replacement happen. It is not happening in the simple, dramatic way many AI narratives suggest.

    Image

    AI is powerful, but it is also inconsistent. In its current form, it can do some tasks better than humans and fail badly at others. That paradox is often called the Jagged Frontier.

    The Jagged Frontier idea matters because it explains why some people see AI as transformative while others remain lukewarm. A BCG and Harvard study of 758 knowledge workers found that people get the most value from AI when they understand what it is good at and where it breaks down.

    Image

    Microsoft reached a similar conclusion in its 2026 Work Trend Index Annual Report. The company found that a small group of advanced AI users, described as Frontier Professionals, were not simply using AI more often. They also knew which mode of AI use fit each task.

    That distinction is important. The best AI users are not handing everything over blindly. They are applying judgment. They know when to use AI as a helper, when to use it as a collaborator, when to use agents for multi-step workflows, and when to keep a human firmly in control.

    Image

    I still do not trust most AI workflows enough to leave them running with no maintenance, review, or quality assurance. The question I ask is simple: would I bet my brand, customer experience, or revenue on a fully automated workflow with no human oversight?

    Klarna is a useful warning here. The company publicly promoted the idea that AI was doing the work of hundreds of agents and helping reduce headcount. Later, it reversed course and rehired humans after leadership acknowledged that aggressive cost-cutting had lowered quality and that customers still wanted a human option.

    Image

    That is the tradeoff I see with substitution positioning. It creates immediate attention, but it can damage long-term credibility. The words often do not match the operational reality.

    Replacement positioning could work if customers truly wanted full replacement and if the technology were consistently ready for it. I do not think either condition is true.

    Image

    Cost reduction is a strong AI argument because it shows up quickly on the P&L. Productivity gains usually take longer. They build inside companies over time and often take even longer to appear across the broader economy.

    But when replacement positioning goes beyond cost-cutting and becomes people-cutting, I believe it starts to antagonize the very people companies need to win over.

    Image

    We have already seen backlash. Duolingo’s AI-first memo drew heavy criticism before the company reframed AI as a tool to accelerate work rather than replace contractors. Surveys have found that some workers refuse to use AI tools because they fear job loss. Pew has reported that many U.S. adults are more concerned than excited about AI in daily life. Reuters/Ipsos polling has shown widespread fear that AI will permanently displace workers.

    There is also a quality problem. When employees believe the purpose of AI is to replace them, they may disengage or produce lower-quality work. In my view, that is not just an adoption issue. It is a positioning failure.

    Image

    Executives often feel more excited about AI than the employees asked to use it every day. That gap matters. If leadership talks about AI as a replacement engine, employees hear a threat. If leadership talks about AI as leverage, employees have a reason to learn.

    Token economics also complicate the replacement story. Some companies have bragged about massive AI usage, but token costs are still a real business variable. As those costs normalize, the math may make junior employees look interesting again, especially when human judgment, context, and accountability are part of the output.

    So what should replace replacement? I think the answer is enhancement. Instead of positioning AI as a way to remove people, I would position it as a way to make capable people more effective.

    AI can be used in two broad ways. A company can try to reduce the number of people, or it can grow output with the same number of people. The data I have seen suggests that productivity gains often create the stronger return.

    A National Bureau of Economic Research paper surveyed 750 executives about AI’s impact on productivity and labor markets. Larger firms showed more interest in replacing labor costs, but the highest ROI came from productivity growth.

    That is the lesson I take from the research: doing more with the talent you already have is often stronger than trying to remove the talent that knows what good work looks like.

    Building products has become easier, but distribution has not. When supply explodes, the scarce thing is not output. The scarce thing is being the product, brand, or service that actually gets chosen.

    That is why positioning matters more than ever. Product quality still matters, but the way I frame AI use can determine whether people see it as empowering or threatening.

    My takeaway is simple: I would stop selling AI as a people replacement. I would sell it as judgment leverage, workflow acceleration, and creative expansion. Fear can get attention, but empowerment is a better long-term strategy.

    This post first appeared on the author’s website and is republished here with permission.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Effortlessly Integrate External Tools into Profound with MCP

    Effortlessly Integrate External Tools into Profound with MCP

    I’m thrilled to introduce the latest addition to Profound: the External MCP Connectors. With these, I’ve found it incredibly easy to link my favorite CMS tools, project trackers, and team communication platforms directly to Profound via MCP.

    This seamless integration has transformed the way I manage projects, allowing me to streamline workflows and enhance team collaboration. Now, all my critical tools are accessible from one central hub, boosting my productivity like never before.

    Try it out and see how Profound can help you connect everything you need in one cohesive system. It’s a game-changer for efficiency and team synergy.


    Inspired by this post on Try Profound Blog.


    crushpress.ai community screenshot
  • Harness Claude Code: Build a Second Brain for Agencies

    Harness Claude Code: Build a Second Brain for Agencies

    How to build a Claude Code-powered second brain for agency work
    Understanding how memory, search, MCP integrations, and AI skills come together to streamline agency workflows and eliminate context-switching.

    If you work in an agency or manage clients, you probably know how quickly your morning can disappear into Gmail, Slack, and CRMs just to recall what mattered yesterday.

    In the past, I would juggle decisions like pricing for my team, roadmap calls for our app, Slack threads, and urgent sales follow-ups, all before my first coffee.

    Those hectic days are now behind me. About six months ago, I rebuilt my workflow using Claude Code as my second brain, and my Monday morning catch-up now takes just a minute.

    Let me share what I built, why it’s been transformative, and how you can do the same.

    Why Most Second-Brain Setups Break Down

    The concept of a “second brain” isn’t new. Tiago Forte’s “Building a Second Brain,” PARA method, Notion, and Obsidian all capitalize on the same idea: externalizing memory.

    Catching information is effective. The recall? Mostly. The real value lies in transforming recalled data into actionable tasks.

    Most implementations fail in three ways:

    • Passive storage. Information enters but doesn’t exit without a manual search and personal memory, especially meeting notes.
    • Context-switching tax. Finding the right note involves copy-pasting and additional prompting before it becomes useful.
    • No action layer. Without drafting or executing tasks, it becomes a burden of excess notes, leading to cognitive overload.

    The issue isn’t documenting tasks but having those scattered in myriad apps without a unifying layer to read across them.

    What truly saves time is a layer that can amalgamate all of this and turn it into action.

    Dig deeper: How to turn Claude Code into your SEO command center

    How Claude Code Changes the Equation

    General AI assistants can answer queries but aren’t seamless with file systems or past interactions. Claude Code changes this with:

    • Native file system access: It reads and writes within project folders, accessing local files directly.
    • Persistent, structured memory: Remembers session data stored in curated Markdown files.
    • MCP integrations: Directly connects with Gmail, Slack, Google Drive, HubSpot, Scoro, without altering workflows.
    • An action layer: Drafts documents, analyzes data, and handles repeatable tasks in my workflow.

    The most advantageous aspect is moving from mere storage to actionable insights, saving immense time.

    The Four Layers of an AI Second Brain

    I structured my second brain using four fundamental layers.

    1. Memory

    Stored in a small collection of Markdown files. They cover my work details, client preferences, decision-making data, and my desired AI persona.

    These automatically load, eliminating the need to reintroduce context every session.

    Memory self-expands, converting daily logs into long-term memory selectively for accurate client models.

    2. Search

    Minimizing memory size keeps daily logs indexed in a local database for quick retrieval of past conversations with full context.

    3. Skills

    Focused capabilities like drafting a brief or proposal, replying in my voice, or summarizing meetings. Small, purposeful, and memory-inherited.

    Not an all-encompassing agent, but an adaptable assistant, growing daily with specific skills.

    ```json
{
  "alt": "The CapmatchOne logo with a gradient circle and bold text.",
  "caption": "Discover innovation with the CapmatchOne logo, featuring sleek typography and a modern gradient circle.",
  "description": "The CapmatchOne logo features bold, modern typography coupled with a gradient circle, symbolizing connection and innovation. The sleek design conveys a sense of progress and creativity. This image can be used for branding or promotional purposes, appealing to audiences interested in innovative solutions and forward-thinking designs."
}
```

    4. A Heartbeat

    An hourly process checks emails, calendar, Slack, and pipeline activities, alerting me if intervention is needed with a summarized Slack ping and draft.

    Dig deeper: How a ‘client brain’ gives AI the context SEO work needs

    Where It Pays Back Hours Every Week

    Here’s how it saves time:

    Faster Context-Gathering for Client Work

    When clients request updates, my second brain already compiles all relevant transcripts, threads, and notes, reducing my prep time dramatically.

    Faster Data Analysis

    From analytics to rank-tracking data, the second brain swiftly compiles the necessary context for review.

    Discovery to Scope

    New engagements once required lengthy exchanges. Now, the second brain formulates a scope based on past discoveries, reducing my workload.

    Overall, this system enhances efficiency and service by ensuring critical information isn’t overlooked.

    Get the newsletter search marketers rely on.


    The Guardrails That Make This Work

    Such powerful tools need proper guidelines to prevent unintended actions by the agent.

    Read-only by Default

    Integrations begin read-only, seeing and drafting in tools like Slack and Gmail, without sending or committing.

    Write access is carefully granted after evaluating its performance, reducing the risk of undesirable actions.

    Memory Hygiene Matters

    Resist storing everything. Long-term memory should affect agent actions—like pricing or preferred workflows.

    Trust the Draft, Verify the Action

    Always review drafts before sending them out. It’s not about removing yourself from the process but leveraging a head start with your expertise.

    Dig deeper: How to train Claude to sound like your brand

    How to Build Your Own Second Brain

    You can customize your setup with preferred tools. Here’s the process I followed:

    • Identify key decision-making tools—email, calendar, messaging, CRM, task tool.
    • Incorporate a transcript layer for calls where essential context is discussed.
    • Create a memory foundation with a ‘this is me’ file and a distilled daily log. Communicate until it feels familiar with your business.
    • Add skills incrementally, starting with the most repetitive task.
    • Integrate the heartbeat once retrieval and skills are working, starting with notification capabilities, then slowly adding write permissions.

    This is a Second Brain, But Don’t Let It Replace Your Actual One

    The aim is not to replace your brain but to enhance efficiency in daily operations, creating more value for teams and clients.

    These tools were non-existent 18 months ago, but now, they pay off setup efforts quickly.

    Dig deeper: How to build custom SEO reports with Claude Code and Google Search Console


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Maximize Productivity with Google Suite Integration for Agents

    Maximize Productivity with Google Suite Integration for Agents

    Managing tasks efficiently is essential for anyone in the fast-paced world of agency work. With the introduction of Google Suite nodes, I now have the power to seamlessly integrate Google Suite into my workflow. This enhancement allows me to send emails, create and retrieve documents, and delve into spreadsheet data with ease.

    What excites me the most is having the ability to pull context from any deck effortlessly. This means all my presentation materials are at my fingertips, ready to help me deliver stellar pitches and presentations.

    Incorporating these tools not only streamlines my daily activities but also boosts my productivity significantly, allowing me to focus on creative and strategic aspects of my role rather than getting bogged down by logistical details.


    Inspired by this post on Try Profound Blog.


    crushpress.ai community screenshot