AI agents now read your docs almost as much as humans do.
Mintlify analyzed 790 million requests across its documentation platform. The finding: AI coding agents account for 45.3% of all traffic, nearly tied with traditional browsers at 45.8%.
Two tools are driving almost all of it:
Claude Code: 25.2% of total traffic, more requests than Chrome on Windows
Cursor: 18% of total traffic
Together they account for 95.6% of all identified AI agent traffic
The rest of the field, OpenCode, Trae, ChatGPT, and NotebookLM, is showing up but nowhere close.
One caveat: OpenAI's Codex doesn't send an identifiable user-agent header, so the real agent percentage is likely even higher.
The takeaway for anyone maintaining developer docs: your documentation now serves two audiences. Structure and machine-readability matter as much as clarity for human readers.
Sunday is the thinking day. Monday through Saturday I hand you tactics. Today we pull back and design something you can actually execute for the next three months.
If you run a one person business, or a small business that feels like a one person business because everyone is wearing seven hats, this plan is for you. I am not going to pretend you have a dedicated operations team. I am going to assume you are the CEO, the head of sales, the head of marketing, and the head of delivery, all running on the same twenty four hours everyone else has.
The question I get most from operators in your position is not “what should I do with AI.” It is “how do I prioritize what to do with AI when I only have a few hours a week to spare.” Fair question. Here is the answer. Ninety days. Three phases of thirty days each. Each phase has one primary objective and one supporting one. No more. That constraint is the entire point.
Let us build it.
Phase one, days one through thirty, reclaim time
The first thirty days are not about revenue. They are about reclaiming hours. This is counterintuitive for most operators because they want to see dollars in the door immediately. I understand the impulse. Resist it.
Here is why. If you try to build revenue generating AI systems on a calendar that is already overstuffed, the new work competes with your current work and loses. The only way to build durable AI infrastructure as a solo operator is to first create slack in your week. Then fill that slack with strategic work.
Phase one primary objective. Reclaim ten hours a week of administrative time.
Ten hours is not arbitrary. It is roughly the weekly overhead an average one person business burns on repetitive administrative tasks. Meeting notes, follow up emails, calendar scheduling, invoice creation, client status updates, content scheduling, social monitoring. Individually each is small. Stacked together, it is a full work day a week.
How you do this. Deploy three specific automations by the end of week four.
Week one. Install automated meeting recording and summarization using Fathom. Every call gets recorded, transcribed, summarized automatically. You stop taking notes during calls. You spend the last two minutes of every call confirming next steps verbally instead of typing. At end of day, you review summaries and ship follow ups in one batch session, not throughout the day.
Week two. Build a simple automation in Make.com that takes meeting transcripts and generates a draft follow up email. You review and send, but the drafting work is gone. This alone saves a few hours a week once it is running.
Week three. Consolidate your AI tool subscriptions into Galaxy.ai or similar aggregator. This saves money, but more importantly it saves the cognitive overhead of remembering which tool does what.
Week four. Audit your content production. Shift to a batched weekly production model. Three hours on Monday, content shipped all week. You are not starting new content work. You are compressing what you already do into a single block.
Phase one supporting objective. Get to a one page operating stack. List every tool, every cost, every owner, every business outcome. By end of month one, this document exists and is accurate. It will be the reference point for everything that follows.
Phase one output. You now have roughly ten hours a week back that used to go to administrative overhead. That time is sacred. It is the budget for phase two.
Phase two, days thirty one through sixty, build pipeline infrastructure
Now that you have time, spend it on the highest leverage system a small business can build. Pipeline infrastructure.
Phase two primary objective. Deploy a consistent lead generation system that produces at least a few qualified conversations per week without daily manual effort.
This is the single most important build in the ninety day plan. Most one person businesses die not because the founder is bad at delivery but because they are inconsistent at generating new conversations. When delivery is heavy, sales goes quiet. Three months later the pipeline is empty and the founder is back to scrambling. Breaking that cycle requires a system that generates conversations even during your busy weeks.
How you do this. Pick one pipeline motion and go deep.
If your audience reads newsletters, your motion is publish and nurture. Build the content engine from Wednesday’s issue. Publish weekly. Convert readers to conversations through targeted calls to action in each issue. Use Beehiiv or a similar modern platform. Ship something useful every week for eight weeks straight. That is eight data points. Then measure what is converting.
If your audience lives on social platforms, your motion is publish, engage, and reach out. Use Buffer for distribution. Spend thirty minutes a day on genuine engagement with your target audience. Use a simple lead tracking sheet to note who engages repeatedly. Reach out to the top engagers with a direct message monthly.
If your motion is outbound, build a clean, targeted outbound system. Enrich your list with Clay. Write the three email sequence from Thursday’s prompt vault. Send a manageable volume, perhaps fifty to one hundred sends per week, for the full thirty days.
The specific motion matters less than the consistency. Pick one. Do it every week for thirty days. Measure what happens. Do not bounce between three motions hoping one will catch. Depth in one motion beats shallowness across three.
Phase two supporting objective. Install the inbound lead triage automation from Tuesday’s issue. Every lead that does enter the pipeline, from any source, gets scored and routed. No lead sits in your inbox for six hours while you finish a client deliverable. Fast response times compound over months.
Phase two output. By end of month two you have a repeatable pipeline motion with real data on conversion rates, and the infrastructure to handle inbound without dropping anyone. This is when most operators stop feeling like they are barely keeping up and start feeling like they are actually running a business.
Phase three, days sixty one through ninety, compound your best work
Now the fun part. You have time. You have pipeline. Month three is about turning both into compounding advantage.
Phase three primary objective. Productize or systematize one offer so that it can be delivered with substantially less of your personal time.
Every one person business has the same ceiling. Your time. You can only take so many calls, run so many projects, or produce so much custom work in a week. The only path past that ceiling is to package something so that additional revenue does not require proportional additional hours from you.
How you do this depends on your business. A consultant might productize a diagnostic into a fixed scope engagement that used to take four weeks of custom work. A coach might package a program that runs in cohorts rather than one on one. A service provider might build a templated starter project that handles the first thirty percent of most engagements. An ecommerce operator might automate customer service for the most common inquiries using a trained chatbot on their product catalog.
The common thread. Find the work you do over and over that currently requires you, and build a system that lets it happen without you. The AI tooling is a means to that end, not the end itself. The output is a business that does not require you to be present every hour it is generating revenue.
Phase three supporting objective. Build a feedback loop. Every week in month three, you run a fifteen minute review. What worked, what did not, what to adjust. No more, no less. Small, frequent corrections beat large quarterly overhauls every time.
Phase three output. By end of month three you have an offer that can scale without scaling you. You have a pipeline that feeds it. You have time in your week to operate the business instead of being operated by it.
What this plan is not
Let me be specific about what I am not promising.
I am not promising you will double your revenue in ninety days. Some operators will. Most will not. Revenue growth comes from the systems you build during these ninety days. Those systems compound over the following six to twelve months. If you execute well, the ninety days set up a much better year. If you measure the plan by ninety day revenue change, you will likely be disappointed and underestimate what you actually built.
I am not promising the plan is easy. The framework is simple. The execution requires consistent weekly hours. Most operators will fall off around week three. The ones who finish will have built more in ninety days than most of their peers will build in a year.
I am not promising every tactic works for every business. The phases and objectives are universal for small operators. The specific tools and motions vary by industry. Adapt the implementation. Hold the structure.
How to stay on track
One, write the plan down. Not in your head. In a document you open every Monday morning. List the phase you are in, the primary objective, the supporting objective, and the specific week within the phase.
Two, pick one weekly success metric per phase. Phase one, hours reclaimed. Phase two, qualified conversations generated. Phase three, offer delivery hours per unit of revenue. Track them every week. Fifteen minutes.
Three, find one accountability partner. Another operator. Someone who will ask you what you did this week. Even a text thread with a former colleague works. The social contract is half the discipline.
Four, do not add a fourth thing. No optimization hobby. No new tool you heard about. No side quest. The plan has two objectives per phase for a reason. Adding a third breaks the plan.
Five, rest on Sunday. Not optional. If you run seven days a week for ninety days you will be broken by day sixty. The plan assumes you are rested enough to execute six days a week and off on the seventh. The rest days are part of the build.
The mindset shift
Here is the one thing that separates the operators who finish this plan from the ones who do not. It is not skill. It is not budget. It is willingness to build systems before you feel like you need them.
Most small business owners wait until they are drowning before they invest in infrastructure. By then they have no time to build it and no energy to think clearly. The operators who compound over years build infrastructure while things are stable or slightly slow, so that when demand surges they have capacity to absorb it.
Phase one is the gift you give yourself. Phase two is the gift you give next quarter. Phase three is the gift you give next year.
If you are reading this wondering whether it is the right time, the answer is always yes. The right time to build systems is before you need them. That is the whole game.
One last thing
If this plan feels overwhelming, cut it in half. Thirty days per phase becomes sixty. Ninety becomes one eighty. That is fine. The structure survives. The key is not the speed. The key is the order. Time first. Pipeline second. Productize third. Never the other direction.
You have a plan now. Print it. Mark the calendar. Set the Monday block. Show up tomorrow morning and take the first step.
That is how ninety day plans become businesses.
If you want the full ninety day plan with templates, prompts, and the exact build sequence I use for clients, reply BLUEPRINT. The AI Workflow Blueprint is forty seven dollars and walks through every week of this plan in detail. If you want implementation support with live office hours and a small community of operators running the same plan, reply ACCELERATOR for the AI Business Accelerator.
Next week we start a new cycle. New anchor, new frameworks, same principles. Thanks for reading this week. Rest today. Ship tomorrow.
Jordan Hale
The AI Newsroom
Turn AI into Your Income Engine
Ready to transform artificial intelligence from a buzzword into your personal revenue generator?
HubSpot’s groundbreaking guide "200+ AI-Powered Income Ideas" is your gateway to financial innovation in the digital age.
Inside you'll discover:
A curated collection of 200+ profitable opportunities spanning content creation, e-commerce, gaming, and emerging digital markets—each vetted for real-world potential
Step-by-step implementation guides designed for beginners, making AI accessible regardless of your technical background
Cutting-edge strategies aligned with current market trends, ensuring your ventures stay ahead of the curve
Download your guide today and unlock a future where artificial intelligence powers your success. Your next income stream is waiting.




