In a recent LinkedIn post, Janna Bastow discusses the rise of AI-generated internal tools and the questions of ownership and upkeep that can follow when more employees can build software quickly. This article covers Bastow’s post and her reported observations; it is not written by or on behalf of Bastow.
She connects the topic to Brighton’s weathered West Pier and to her own experience of navigating change:
“Brighton’s West Pier lost a few more pieces in last week’s storm.”
The image sets up a broader reflection on resilience, but Bastow’s central concern comes from a customer conversation. She says a software veteran at a customer company had noticed teams building internal tools with AI and questioned what would happen after those tools were created.
Building quickly does not answer who owns the tool
According to Bastow, the customer’s concern was not whether teams could produce a working tool. It was whether anyone would maintain it, improve it or take responsibility for it if its creator moved on. Bastow highlights this as a potential weakness in efforts that focus on making creation easy without assigning ongoing ownership.
“sure, you can spin it up fast, but who iterates on it? Who owns it when the builder leaves?”
The questions point to practical issues companies may need to address as AI-assisted development spreads internally: who handles changes, who understands how a tool works, and who is accountable when it stops meeting a team’s needs. Bastow’s post frames those questions as part of product work, rather than as concerns that disappear once a prototype is built.
Why the purpose matters as access expands
Bastow links the customer’s experience to the theme of her SimplyProduct newsletter for the week: what happens when building becomes more accessible. In her view, broader access increases the importance of deciding why a tool should exist and what problem it is meant to solve.
“why that makes the why more important, not less.”
That argument shifts attention from the speed of AI-assisted creation to the decisions that guide it. If many teams can produce tools independently, a clear purpose can help organizations judge which tools are useful, who should support them and whether they should continue to evolve.
A call for companies to examine their practices
Bastow invites readers to consider how their own companies are responding to AI-built internal tools. She also points to a live session scheduled for November 18, titled “Put AI to work in your product process,” where she says she will explore the subject further.
Her post offers no universal policy for managing these tools. Instead, Bastow uses a customer’s questions to draw attention to a challenge that can accompany rapid building: ensuring that a tool has a clear reason to exist and someone prepared to look after it.
📝 About This Content
This article is based on insights shared by Janna Bastow on LinkedIn.
📅 Originally posted on November 4, 2026 | View original post on LinkedIn →