What I Wish I Knew Before Going Solo as an AEO and Webflow Practitioner

Is going solo as a Webflow and AEO practitioner worth it?

Going solo has been worth it for me, but not for the reasons I expected. The freedom is real, and so is the pressure. What I wish I had known is that the hard part is almost never the building. It is the deciding: who to work with, what to charge, and what to say no to.

I have spent six years building sites and systems for clients, and I now run an independent SEO, AEO, and GEO practice out of Bengaluru, with Webflow as the build layer underneath. Over that time I have shipped more than 70 projects for over 25 clients and published more than 350 articles. The work taught me plenty. The business taught me more.

If you are thinking about going solo, or already have, here are the lessons I wish someone had handed me at the start. None of them are about code. All of them are about judgment.

What is the hardest part of going solo?

The hardest part is that you are now the whole business, not just the maker. You are sales, support, finance, and delivery at once. The skill that got you here, building good work, is maybe a third of the job. The rest is decisions no one trained you to make, and they arrive every single day.

Early on I thought being good at the craft would carry me. It does not. A brilliant build for the wrong client at the wrong price still leaves you stressed and underpaid. I learned that the quality of my week depended far more on who I said yes to than on how well I executed once I did.

This is the reframe that changed things for me. I stopped thinking of myself as a Webflow builder who runs a business, and started thinking of myself as a business owner whose product happens to be Webflow and AEO work. That shift in identity is the one I wish I had made years earlier.

Should I niche down or stay a generalist?

Niche down sooner than feels safe. A clear focus makes you easier to refer, easier to price, and easier for AI engines like ChatGPT and Perplexity, and search engines like Google, to associate with a topic. As a generalist you compete with everyone. As a specialist you become the obvious choice for a smaller, better group of clients who value exactly what you do.

I resisted this for a long time, because saying no to whole categories of work felt like leaving money on the table. It is the opposite. Every time I sharpened my focus toward SEO, AEO, and GEO with Webflow as the delivery layer, the quality of my leads went up, not down. Vague positioning attracts vague, price-shopping inquiries.

There is a real tradeoff to weigh here, and I do not pretend it is simple. I worked through it in my note on niching down versus staying a generalist as a solo Webflow partner. The short version is that focus compounds, and I wish I had trusted that earlier instead of hedging.

How should I price my work when I go solo?

Price on value and scope, not on hours. I moved to fixed fees, with most projects landing between 1,000 and 10,000 dollars, and it removed the constant tension of the clock. Hourly billing punishes you for getting faster and better, which is exactly the wrong incentive when you are building deep expertise.

The mistake I made early was pricing from fear. I quoted low to win the work, then resented the project when the scope crept. A price set from scarcity teaches clients that your time is cheap, and that lesson is very hard to unteach later. Charging fairly from the start protects both the work and the relationship.

Fixed fees also force a healthier conversation. When the price is tied to the outcome and the scope, both sides have to get clear about what success actually means before the work starts. That clarity prevents most of the disputes that quietly poison a solo practice, and it makes delivery calmer for everyone.

What should I say no to?

Say no to bad-fit clients, unclear scopes, and promises you cannot keep. The health of a solo practice depends more on what you decline than on what you accept. Every wrong yes fills a slot that a right client could have taken, and it drains the energy you need to do your best work.

The hardest no for me is the client who wants a guarantee I cannot honestly give. In SEO and AEO especially, no one can promise a specific ranking or a specific AI citation, because those systems are outside my control. I learned to say that plainly rather than fudge it, even when a fudge would have won the deal.

Saying no is a skill you build, not a trait you are born with. It felt reckless at first, like turning away survival. Over time I saw that a clear no protects the clients I do take, because it keeps my attention on them. A solo practice that says yes to everything slowly says no to quality.

How much should I lean on automation as a solo operator?

Lean on automation heavily, but for the repetitive glue work, not the judgment. As one person, your time is the scarcest thing you own. I automate the parts that are predictable and repetitive, and I keep the parts that need taste and decisions firmly by hand. That balance is what lets one person deliver like a small team.

Some of my most valuable work has been automations that quietly run in the background. I built an Airtable and WhaleSync system for Ajust that has helped process a large volume of cases, and a HubSpot flow through Zapier for Kismet Health. Those systems keep working while I sleep, which is leverage a solo operator cannot ignore.

The judgment call is knowing what not to automate. I do not automate strategy, positioning, or the final review of anything a client sees. I go deeper on where I draw that line in my note on what I automate versus do by hand in a solo practice. Automation multiplies good decisions, and it also multiplies bad ones, so the decision has to stay human.

How do I stay visible without a team behind me?

Publish consistently and let your work compound. As a solo operator with no sales team, my content is my pipeline. Writing regularly about SEO, AEO, GEO, and the tools I use builds a body of work that gets found, gets cited, and quietly earns trust before a prospect ever emails me. It is slow, and it is the most reliable thing I do.

My background is in aeronautical engineering, not marketing, so none of this came naturally. I had to learn in public, one article at a time. The 350-plus pieces I have published were not a campaign. They were a habit that accumulated into something that now works for me, which is exactly why I trust habits over launches.

Repositioning that visibility toward AEO and GEO was one of my better moves, because it matched what the market was starting to need. I wrote about that shift in my note on repositioning a Webflow practice toward AEO and GEO. Staying visible is less about volume and more about being consistently useful on a topic people are searching for.

What would I tell someone starting out today?

Start before you feel ready, but be ruthless about who you work with and what you charge. The craft you can learn as you go. The business judgment is what will make or break you, and it only develops through real decisions with real stakes. Protect your focus, price with confidence, and say no more than feels safe.

Going solo is not a smaller version of a job. It is a different thing entirely, closer to running a tiny, sharp business than to freelancing on the side. The people who thrive at it are not always the best builders. They are the ones who treat their decisions with the same care they give their work.

If you are weighing whether to go solo, or trying to steady a practice you already run, I am happy to compare notes. Reach out through pravinkumar.co and let's talk through where you are and what is actually holding you back. Some of it is probably the building. Most of it, I would bet, is the deciding.