Thank you to everyone who tuned into our live discussion! Join me for my next live video in the Substack app.
The tools required to build a website, an app, or a full digital platform are no longer the barrier they used to be. That shift is real, and it is worth taking seriously, both for what it makes possible and for what it now requires of you.
I talked through this with my friend James Hicks, who has spent decades in enterprise technology and has since built a suite of AI-powered products of his own, including Kuehub and TekSync. Here is what stood out from that conversation, and what it means if you are trying to turn your own expertise into something people can actually use.
Key Takeaways
The barriers that used to stand between an idea and a built product are mostly gone. That is not the same as saying every idea deserves to be built.
James built two very different products, Kuehub and TekSync, and both came out of a real problem he was living with himself, not a “what can AI do” experiment.
Treat AI as one voice in the room, never the final decision-maker. James has literally trained his prompts to argue with him.
Own your infrastructure. Own your platform. Do not build your business on top of someone else’s closed container.
Knowing when to pivot away from an idea is not failure. It is clarity, and nobody else can hand you that answer but you.
Access Is Not the Same as Discernment
For a long time, a good idea came with a long list of barriers. You needed a developer, or the budget to hire one. You needed to interview and manage a contractor, often overseas because that was the only way to make it affordable. Most of that friction is now optional.
James put it plainly:
“There is now nothing in your way from doing whatever the thing is that you have wanted to do.”
If you can prompt a tool and shape it into something that looks and sounds like you, brand and all, the technical excuse no longer holds.
That access comes with a catch. If everyone has the same tools, a lot of what gets built is going to be noise. James does not soften this part: “The real ones know when something is not built to be premium, when something is not built with security in mind, without scalability in mind, without protections for authentication.” If you are asking someone for a phone number, an email, a home address, or a credit card number, you had better have real protections behind that request. Anything less does not last, no matter how fast the first sale came in.
Build With Intent, Not Because You Can
James’s own rule is simple: build to eliminate steps in somebody’s workflow, not to add another thing to the pile. If an idea buys back time, makes someone more effective, or solves a problem people have actually told him they have, he builds it. If it does not clear that bar, he lets it go, even after he has already sketched it out.
Two of his own products came directly out of that filter. Kuehub grew out of the real headache of running multiple live shows and managing guests himself. It bundles the parts of a production that have nothing to do with the actual conversation, overlays, lower thirds, tickers, merch integrations, into one branded environment, so the host can stay present with the guest instead of managing the backend in real time.
TekSync grew out of an earlier project of his and answers a question worth asking honestly: is a downloadable PDF still enough? James built it in tiers, from a lighter entry point up to inner-circle access with live sessions, and included asynchronous audio and video communication on purpose, because not everyone finds it easiest to get their thoughts onto a page.
Neither tool started as a business plan. Both started as a problem he was tired of solving by hand, and both were shaped by real feedback from people he trusts enough to let break the thing before it goes public.
Use AI as a Member of the Team, Not the Whole Team
AI works best as a whiteboard, not a decision-maker. James asks the same question across OpenAI, Anthropic, and Google, then measures what comes back against his own experience and real conversations with real people. “I use it as a member of the team,” he said. “Not the team.”
He has gone a step further and trained his own prompts to disagree with him. Part of his default prompt, across every platform, instructs the tool to be confrontational and offer criticism, modeled after a friend who used to call him at odd hours to say the overlays needed tightening up. The point is friction, not agreement.
Choose Infrastructure You Actually Own
James builds on industry-standard infrastructure, GitHub, Netlify, Supabase, specifically so he is never trapped inside one company’s closed system. He pointed to all-in-one platforms like Manus as an example of a contained environment worth watching closely, and noted how quickly the ground can shift, from YouTube changing platform requirements to Anthropic adding watermarking to AI-generated text.
He also walked back his own past enthusiasm for lifetime-deal software. About a year ago he pulled way back from promoting those deals once he watched several of them fall behind the pace of AI, without a real plan for the recurring revenue they needed to survive.
The rule underneath all of it: own your real estate. Your website, your list, your customer relationships should not live only on land you are renting from somebody else.
Digital Authority Requires Receipts
“People pay attention to what they pay for,” James said, and that has been true in my own work for years. You can only fake expertise for so long before someone looks under the hood.
Research is not hard for anyone to do anymore. If you are the coach, the consultant, the trusted advisor, you need to be able to explain why your systems were built the way they were built, and you need somewhere people can go to verify it. James keeps his own receipts at links.hicksnewmedia.com. If you are going to claim the authority, you need to be able to point to the proof.
Know When to Pivot
Not every build deserves to become a business, and knowing the difference is its own skill. During our conversation, a woman in the audience shared that she had built an app, spent real time and credits on it, then stopped herself and wrote down: “I am not in the SaaS business. I am in the career practitioner space.” James called that exactly what it was: clarity, not failure.
I have my own version of that lesson. I went deep down the rabbit hole with an AI website-building tool a while back, building far more than I needed, before I stepped back and asked what my own audience was actually asking for. Respecting the process does not mean finishing every road you start down. It means knowing when the road you are on was never actually yours.
Where This Leaves Us
You do not have to be an architect, a solutions engineer, or a coder to build something real right now. You need to be able to prompt these tools, hold a conversation with them, start broad and get specific, and write your actual plan down before you touch a prompt window, pen and paper, not a notes app.
But access is not the same as responsibility. Build for value. Build for scale. Build with real security in mind. And build with a servant’s heart, because that is what separates something that lasts from something that was only ever noise.
Find more of his work at hicksnewmedia.com, and his tools and resources at links.hicksnewmedia.com.
Your Guide: Tanya Smith is a digital branding strategist who helps experienced professionals turn earned expertise into a trusted presence people can find, trust, and hire. Off the clock, she’s a wife, a soon-to-be empty nester, and mom to two daughters, plus one very mischievous Shih-Poo named Koda.
