The Ideas Guy Isn't a Slur Anymore. Here's What Changed.

I am, by traditional measures, an ideas guy. I have never been the engineer in the room. The dev teams I worked with at hCentive a decade ago and at SmartCue until last year wrote the code. I described what I wanted built and they built it. The dynamic was honest, and old. The labor of building was the expensive part. The ideas were cheap.

A while back, the dev agency I'd worked with at SmartCue for years had a cycle time, between here is what I want and the feature is in production, on the order of weeks. I knew this was the cost of being an ideas guy with no shipping muscle. I had paid that cost for fifteen years and stopped questioning it. Then, fairly recently, I let them go and started maintaining the codebase myself, with Claude. The cycle time collapsed from weeks to hours. The customers did not notice. The product still ships. The thing I had been paying for, for fifteen years, quietly became free.

Fifteen years ago, calling someone an ideas guy was a quiet insult. Today it might be the most underrated job description in tech.

This is my attempt to write down what I think has actually changed, and what I think most people, including a lot of very smart people, are still missing.

What an "ideas guy" used to be

I am old enough to remember when ideas are cheap, execution is everything was the operator gospel. The 2010s startup canon. The whole point was that the bottleneck was the building. The hard work. The shipping. The integration nobody wanted to write. The marketing nobody wanted to do.

Anybody could pitch you on a marketplace for cats and a delivery app for groceries. Almost nobody could actually build either of them. The market reward went to the people who closed the gap between the pitch and the working thing. The pitch itself was worth nothing without the closer.

I internalized this. I spent most of my twenties and early thirties trying to recruit better builders, sit closer to them, learn enough to talk to them, and stay out of their way. I did not consider that the bottleneck might move.

Where I noticed it had moved

The first time I noticed something had structurally shifted was in late 2024, on the side, with Mark IT.

Mark IT is the family business. My mother started it in 1999, ran it for eighteen months solo, and then convinced my Dad to leave a stable job to join her. He ran it for two decades. My brother runs it now. It is a Tally partner in Mumbai, the kind of business that survives on word-of-mouth, on relationships, on patience. For most of its life Mark IT's website was an afterthought.

We had been paying a web development team and an SEO agency for years to do something to it. The results were what you would expect. Three thousand monthly visitors. Slow page loads. A blog written by someone who clearly had a template and no opinion. Forms that worked sometimes. I had been telling my brother for years that we should fix the site. We never did, because fixing it required hiring people who would also need to be managed, and managing them was a job, and the job was not worth the upside.

In a few hours, across two or three weekends, with maybe ten hours of total focused work, I rebuilt the entire site. I thought through what the site should actually do, who should land on which page, what the content layer looked like, what the SEO strategy should be. I described it. I tinkered. I corrected. I read the AI's output and pushed back where it was wrong. I tested the result. We fired the web team. We fired the SEO agency.

Three and a half months later the site was doing sixteen thousand visitors a month.

The bottleneck had not been time or talent or budget. It had been my willingness to describe what I actually wanted clearly enough for someone, or something, to execute against. The agency had been failing in part because I had never made them work to a brief. The AI did not fail, because the AI did the thing the brief said.

This is the part that surprised me. The labor of building was no longer the expensive part. The labor of describing was.

The eight properties as a curriculum

After Mark IT, I started running this on purpose.

Snaplife was the test of whether one operator could ship and run an AI-under-the-hood B2C product without engineering hires. Audio2TextPro was the proof of concept that came before, and is mostly retired now. RoastMasterRick was the test of whether you could build a Chrome extension end-to-end on the side. Shrtfrm tests whether brand-driven media is a viable wedge. SmartCue had been my real business since 2020 and quietly became the test of whether you can run a real B2B SaaS company solo. Gramms is the test of whether just AI and an ideas guy can build a production-grade, high-quality, commercially viable iOS app. And this site is where I note down how my experiences pan out.

Eight properties is not a portfolio. It is a curriculum. Each one tests a specific AI now makes this possible claim. Each one teaches me whether the claim is true, half-true, or fashionable hand-waving. Some are alive. Some are barely alive. One is basically dead. I prefer this to the I will know once I have built one perfect thing posture, because the lesson lives in the spread, not in any individual property.

What I did not appreciate when I started is that the curriculum was secretly teaching me one thing across all eight: how much output an articulate operator can extract from current AI. The answer is a lot more than the trade publications are saying, and the limiting factor is almost never the AI.

The limiting factor is whether you actually know what you want.

The smart people who do not get this

The thing that surprises me, week after week, is who does not see it.

Some of the most credentialed people in my professional life will tell me, when I ask, that AI is fine but unreliable. That it hallucinates. That it takes too much coaxing. That after the third or fourth time they corrected something obvious, they gave up and went back to doing the work themselves. These are people whose careers were built on being the sharpest analytic mind in the meeting. By every measure I can verify, they are sharper than I am.

In my own experience working with the same tools, the AI is rarely the limiting factor in those conversations. The brief is.

I will not say this to their faces, because it is rude and because I might be wrong. But I have started to suspect that the people who dismiss AI as too-error-prone-to-be-useful are sometimes describing the quality of the conversation they had with it, not the ceiling of the tool. The model can only ship what you can describe. If your description is fuzzy, the model's output is fuzzy. If your description is sharp, the output is shockingly close to what you imagined.

This used to be an asymmetric advantage of senior engineers. They could translate vague product asks into specific build instructions, because translation was their craft. Now the translation has been collapsed into the user. If the user can do it, the model can do it. If the user cannot, no model picks up the slack.

Twenty years of operator wisdom was that the idea is worth nothing without the closer. The closer used to be a person. The closer is now a process that anyone with a clear head and a willingness to be patient can run. The idea is back.

What this actually means for "ideas guys"

I am not arguing that pedigree is dead, or that builders are obsolete, or that you can think your way into anything. The world still has hard problems that require deep technical expertise, careful systems thinking, hard-won taste. Building anything with stakes still requires someone who can tell when the AI's output is wrong, which is itself a skill that comes from having built things.

But the entry-level bar to shipping at all has moved. A clear thinker who has never written code can now do many things that used to require a small team. They can build a working website. They can run real ad campaigns. They can run customer outreach. They can rebuild a family business's online presence on a couple of weekends. They can launch an iOS app. They can run a portfolio of side properties one person could not have run a decade ago.

Most of the people I know who are doing this well started off being called ideas guys by people meaning it as a criticism. I include myself in this. I consider myself, in the most operational sense of the word, mediocre. I am not the most disciplined engineer or the most charismatic founder in the rooms I am in. What I have learned, slowly, is that articulating is itself a craft, and that the craft is having a moment.

What I am worried about

I do not think this advantage holds forever. The current generation of tools rewards clear thinkers because they are the only ones who can drive the tools effectively. As the tools improve, the articulation moat shrinks. Eventually the model will infer intent from less and less input. The premium on clarity of thought goes down again.

I also worry about a generation of operators who never have to learn the underlying craft because the tools paper over the gap. I am one of them. I am directly downstream of years of working with great builders who taught me what good looks like, even though I am not one. I do not yet know whether someone who skips that entirely can build durable things.

So I hold this opinion contingently. The ideas guy is not a slur anymore right now. Whether this is permanent or a window, I cannot say.

Closing

I am an ideas guy who can now ship. That used to be a contradiction. The contradiction died sometime around late 2023, and many of the smartest people I know are still operating like it did not.

That is the part I keep being surprised by, even though I am the person watching it happen on three different tabs every weekend. I am still figuring out what to do with the surprise. This site is part of figuring it out.

I really hope it stays this way for a while longer. I have a lot left I want to build.