IC-track economics. Twelve years of compounding leverage.

In September 2017, I watched a Grant Cardone video. "Dominate, don't compete." The framing was seductive, and I almost kept it. Until I wrote a public post walking it back. That walk-back, which probably twelve people read, turned out to be the first expression of a career operating system I've been refining across six companies since.

The management track is not the only legitimate destination for a senior PM. It is the most visible one. Visibility is not the same as value. Twelve years across six companies, from co-founded startup through enterprise AI deployment, produced one consistent observation: the IC who compounds domain depth, learning method, and market posture builds leverage that headcount does not produce. The AI era raised the ceiling on that leverage, not lowered it.

Market posture: expand the field, do not extract from it

The earliest career decision landed September 2017, not as a strategy but as a public walk-back.

After the Cardone video came the reframe: "Would you rather just kill everyone out there and crush your market after you are number one? Or would you help the market flourish while you try to make your healthy share?" The prior default named and dropped in one post. The reasoning visible.

One year later, the V2-to-FarEye transition compressed it into a working mnemonic: "Go increase the size of the pie if you want a bigger share." By 2019 it had become a register: "Value over revenue. Humans over resources. Trust over contracts." By 2026, agamarora.com, second-brain v1, luna-monitor, and ai-resume shipped as open-source MIT-licensed tools. The 2017 instinct that rejected the Cardone frame is the same instinct that publishes personal builds publicly nine years later. The through-line is visible.

Help-market-flourish is not a rule applied selectively. It is an operating posture. The BD framework and the open-source repos are outputs of the same question: am I expanding the field or extracting from it?

The IC path: legitimate, not consolation

IC track is a destination. Not a way-station for PMs who could not manage people.

In October 2021, five years into a PM career, I published a claim that broke a prior default: "People management is a critical skill but it's not for everyone." Not a personal confession. A universal claim about two equally valid growth axes. The supersession was public. Four years later, in June 2024: "It is a wonderful opportunity to be a product manager. I wouldn't trade it for anything." The conviction held across companies and roles. The AIonOS Senior AI Product Manager title is IC-track, chosen deliberately.

The AI era has made the IC claim more important, not less. An IC with AI agents now produces throughput closer to a small team than individual contribution historically allowed. Fifteen-plus enterprise POCs at AIonOS, $1.5M+ enterprise pipeline, 60-day to 7-day data onboarding compression at FarEye, 3.6 to 4.7 NPS improvement and $1M ARR in 18 months: these were IC contributions. No headcount required to validate the ROI.

The altitude ceiling for the IC path is now defined by thinking altitude, not org-chart altitude. "Growth as a product manager is moving from 'we are building the best product' to 'we are building a profitable and valuable business.'" That reframe is available to any IC. It requires no direct reports.

The two-roles-ahead heuristic enforces this over time: "I would recommend looking at the two roles ahead when joining a new company. Where you start is only 5% important versus where you land eventually." The IC who selects environments that stretch the thinking altitude two roles forward compounds faster than the IC who optimizes for present-tense title. Room selection follows the same logic: never be the smartest person in the room. If you are, change the room.

The learning thesis: concepts, not tools

The drivers are being automated. The engineers are not.

The driver, mechanic, and engineer frame arrived December 2019, three years before ChatGPT launched publicly: "A driver is adept in using a tool. A mechanic can repair it. An engineer knows it inside-out and can create similar tools based on the concept. The world does not need more drivers. AI will make you redundant if not now but soon. Strive to learn concepts and not tools." Written in 2019, the prediction has aged into literal accuracy. Prompt engineering frameworks from 2023 were superseded within 18 months. The frameworks still in rotation are 20 to 60 years old: STP, JTBD, MVP, AARRR, NFR. Concepts compound. Tool implementations expire.

The evidence track is the densest in 12 years of public writing: 24 documented instances across five years of applying the same principle at different altitudes. The frameworks taught through are the same ones that were in use at V2 Games in 2014. They are still load-bearing.

The practice-level complement arrived December 2025: "To get this into my muscle memory. I would recommend most PMs and even general business practitioners to do this as well. Use this man's writing/talks as not just one-offs, but commit to them." Not "learn concepts" as a declarative. "Absorb concepts to instinct level via deliberate repetition" as an operational instruction. The lowest common denominator for mastery is hours put in. You cannot skim on it.

Certifications are collectibles. Three sentences, no hedging, November 2024: "They are in no shape or means a validation of what you can and cannot do." Steve Jobs did not take a PM course to build the iPhone. The LinkedIn Top Voice PM badge, earned in February 2024, was immediately diagnosed correctly: "This kind of feedback, from not just any human but humans that are experts in their fields, is more valuable than any badge." The badge was earned. The mechanism that produced it was ranked accurately.

What these three add up to

The three decisions are the same decision restated at three altitudes.

Market posture: operate as an expander, not an extractor. The network compounds, the reputation compounds, the open-source record compounds. Learning method: invest in the conceptual substrate, not the implementation surface. Tools expire, frameworks compound, instinct-level mastery requires deliberate repetition. IC-track stance: depth of thinking is the altitude ceiling, not depth of org. The AI era raised the return on thinking depth and lowered the return on headcount-as-proof-of-seniority.

The compound is not accidental. Each decision reinforces the others. The IC who helps the market flourish builds the network that provides the rooms worth being in. The IC who learns concepts survives the tool-cycle that eliminates the driver. The IC who selects for thinking altitude two roles ahead arrives at the business-building conversation. Not the roadmap conversation. As the default operating mode.

Forward question: twelve years in, the thing I find genuinely unresolved is the altitude question in an AI-agent era specifically. If an IC with AI agents can produce small-team throughput, the traditional argument for management track (leverage through people) narrows. But the coordination problems that management solves don't disappear. They move. Where do they land, and what does the IC need to do differently to work at that layer without a team? I don't have a closed answer. If you're navigating it, I'd like to think it through together.