A Q&A FOR SOLO FOUNDERS · 10 QUESTIONS
In 2026 one person with the right AI tools can ship what used to take a studio. The real question isn't can you build it. It's who owns it when you do.
Start reading ↓
Q.01
Social profiles are rented land. A website is the one address on the internet you actually own.
Social platforms are great places to be found. They're shaky places to live. The algorithm decides who sees your posts this week. The format changes when the platform says it changes. And if your account gets flagged by mistake, your storefront can disappear with a support ticket as your only way back.
None of that means you should leave social media. It means you should be clear about what each place is for. Think of it as home base and outposts. LinkedIn, Instagram, YouTube and your newsletter platform are outposts: busy places where people bump into you. Your website is home base: the place every outpost points back to, where the rules are yours.
For a solo business, home base does four jobs no profile does well:
Credibility for bigger tickets. If you sell financial planning, consulting or a multi-month program, people check you out before they book a call. A clear site with your name, your method and your terms reads as “real business.” A profile alone often reads as “side project.”
A home for proof. Case studies, testimonials, a sample lesson, a portfolio. On social, your best work scrolls away in a week. On your site, it stays where you put it.
Leads you keep. A contact form or booking page on your own site sends inquiries to your inbox and your list. No algorithm sits between you and the person who raised their hand.
Being findable when people ask. People still type “tax advisor near me” into search. More and more of them also ask an AI assistant “who can help me with X?” Both reward clear, specific pages that live at a stable address and say plainly what you do and for whom.
Q.02
There are five, and they work like levels in a game. Each one trades a little hand-holding for a little more power.
None of these is the “wrong” answer. Each level is the right starting point for somebody. What changes as you go up is how much of the site is really yours, and how much you have to know to run it.
LEVEL 1
HTML, CSS, JavaScript and a framework, written by you. Total control and nothing to export, because you already have everything. The catch: the learning curve is steep, and for a non-developer it's a slow way to get a business online.
Good for: people who want to learn web development for its own sake.
Watch out for: spending months on the site instead of the business.
CONTROL · 5/5
PORTABILITY · 5/5
LEARNING CURVE · 5/5
SPEED TO LAUNCH · 1/5
COST AS YOU GROW · 1/5
LEVEL 2
Pick a beautiful template, swap in your words and photos, and launch the same week. Hosting, security and updates are handled for you. The trade-offs: you work inside the platform's limits, the site itself mostly can't leave the platform, and the monthly bill tends to grow as you add features.
Good for: testing an idea fast with zero technical setup.
Watch out for: discovering, two years in, that “moving” means rebuilding.
CONTROL · 2/5
PORTABILITY · 1/5
LEARNING CURVE · 1/5
SPEED TO LAUNCH · 5/5
COST AS YOU GROW · 4/5
LEVEL 3
Describe what you want in plain words and watch a working site or app appear. It's genuinely astonishing, and for prototypes it's often the fastest route there is. The question is what comes with you if you leave. Many of these tools let you sync or download the code, but the database, logins, hosting and secret keys often live on their side. Pricing is usually credits or tokens, so heavy iteration costs more.
Good for: prototypes, internal tools, campaign landing pages, testing an idea before you commit.
Watch out for: building a whole business on one before you've read the exit terms.
CONTROL · 3/5
PORTABILITY · 3/5
LEARNING CURVE · 2/5
SPEED TO LAUNCH · 5/5
COST AS YOU GROW · 4/5
LEVEL 4 · HOW THIS ARTICLE WAS BUILT
This is how this article was built. WordPress (the open-source system behind roughly four in ten websites) with the Elementor visual editor, on hosting you control, driven by an AI assistant through MCP (more on that in Q.04). You own the files, the database and the domain. Non-technical founders keep a visual editor they can use by hand. Tinkerers get full access when they want it.
Good for: most solo businesses that want to own their home base and still move fast.
Watch out for: you, or someone you trust, still need to keep hosting, updates and backups in order.
CONTROL · 4/5
PORTABILITY · 5/5
LEARNING CURVE · 3/5
SPEED TO LAUNCH · 4/5
COST AS YOU GROW · 2/5
LEVEL 5
Tools like Claude Code and similar AI coding harnesses can now help one person build what used to need a dev team: logins, dashboards, automations, integrations, a client portal. Maximum power. It's best suited to an almost-CTO profile, because you're now responsible for servers, security, backups and updates.
Good for: founders whose product is software, or who need custom workflows no plugin covers.
Watch out for: becoming your own unpaid IT department.
CONTROL · 5/5
PORTABILITY · 5/5
LEARNING CURVE · 5/5
SPEED TO LAUNCH · 3/5
COST AS YOU GROW · 2/5
Q.03
Lock-in is what you find out when you try to move house: can you pack your furniture, or is it bolted to the walls?
On day one, every platform feels like home. Lock-in only shows up later: when prices change, when you outgrow a feature, when you want to hire a developer who doesn't work on that platform. By then your content, design, contacts and search history all live inside one company's walls. Moving them is a project, not a weekend.
Here's what that looks like in practice, and why it's worth checking before you build:
Traditional builders. Wix's own help center says sites must be hosted on Wix's servers, so you can't move a Wix site to another host. You can keep your domain, and Wix's terms say your content belongs to you. In practice, though, leaving means rebuilding. Squarespace offers a WordPress export, but it only carries part of a site (basic pages and one blog). Your design and many page types stay behind.
AI app builders. Most now let you sync or download your code, which is a real step forward. But the code is often only half the story. Databases, user logins, stored files, secret keys and hosting setup may live on the builder's side and need a separate move.
Open-source setups. WordPress content exports in a standard format, the software is free to install anywhere, and your files sit on a server you can copy. Moving is still work, but it's packing boxes, not demolition.
Ask these about any platform before you build your business on it. If you can't answer them from the help docs in ten minutes, that's an answer too.
01
Can I export my content? Pages, posts, images, in a format another tool can read.
02
Can I export my design? Or would I be recreating every page by hand?
03
Can I export my data and contacts? Leads, form entries, customers, email subscribers.
04
Can I move my domain? Is it registered in my name, and can I transfer it out?
05
Can I host it elsewhere without rebuilding? The real test. “Yes” means you own a website. “No” means you rent one.
Q.04
It's a USB-C port for AI: one standard plug that lets an AI assistant safely connect to your tools.
Before MCP, connecting an AI assistant to a tool meant custom, one-off integrations. MCP turns that into a standard. A tool exposes an MCP server (a list of things it lets the AI do), and any assistant that speaks MCP can plug in.
For your website, that means your AI assistant can read a page, add a section, fix a typo or restyle a button using the same building blocks you'd use by hand in the editor. Nothing is hidden in mystery code. If you open the page in the editor afterwards, you'll see ordinary headings, paragraphs, images and buttons you can change yourself. WordPress now has an official MCP adapter, and page builders like Elementor are adding MCP support of their own.
Here's the meta moment: this article was built this way. An AI assistant, connected to this site through MCP, laid out every section you're reading. A human wrote the brief, reviewed each step, and pressed publish.
HOW THIS ARTICLE WAS BUILT
01
YOU
Describe what you want.
02
AI ASSISTANT
Plans the change, asks before acting.
03
MCP SERVER
The plug: only the actions you've allowed.
04
YOUR WORDPRESS SITE
Native blocks you can edit by hand.
Q.05
It's as safe as the permissions you hand it, and you decide those.
An AI assistant connected through MCP can't do anything the account it uses can't do. So safety isn't about trusting the AI. It's about the same habits you'd use with a freelancer you just hired:
Give it its own key. WordPress has application passwords: separate passwords for apps, which you can revoke with one click without touching your own login.
Use the least access that does the job. An account that can edit pages doesn't need to install plugins or manage users. Grant the smallest role that works.
Work in drafts. Let the AI build in a draft or an unpublished revision, then look at a preview link before anything goes live.
Keep backups. Automatic daily backups on your hosting are cheap insurance against any mistake, human or AI.
Keep a human on the publish button. Anything that faces customers gets your eyes first. That's how this article was handled.
Q.06
Control comes in four layers. You don't need to own all four on day one, but you should know which ones you're renting.
01
Your domain. The address itself. Register it in your name, on an account you log into. This one is cheap and non-negotiable: if the domain is yours, every other layer can be swapped.
02
Your content. Your words, images, case studies and pages. Can you get them out in a usable format, or only as screenshots?
03
Your data. Leads, form entries, email subscribers, client records. For financial advisors and consultants this is also a compliance question: you should know where it's stored and be able to export it.
04
Your infrastructure. The server and software the site runs on. Renting this is fine; most people should rent hosting. What matters is whether you could pick it up and move it to a different host.
A useful habit: write the four layers on a sticky note and next to each one write “own” or “rent.” Renting isn't failure. Not knowing is the risk.
Q.07
Portability means you can change your host, your agency or your AI tool without starting over.
Portability comes from two things: open formats and open-source software. When your site runs on software anyone can install, like WordPress, any host can run it and any developer who knows it can work on it. When your content is stored in standard formats, other tools can read it. That's what turns “we're switching providers” from a rebuild into a moving day.
The same logic now applies to AI. Because MCP is an open standard and not one company's feature, the assistant you use today isn't the only one that can plug into your site. If a better or cheaper assistant shows up next year, you switch the assistant, not the website.
Q.08
Ask two questions: can the site grow without a restart, and does the bill grow faster than the business?
Technically, a solo business site tends to grow in stages: a simple brochure site, then a blog or resource library, then bookings or payments, and maybe one day a client portal or course area. The question is whether each stage is an addition or a migration. On a flexible, open stack, you add a booking plugin or connect a payment tool to the site you already have. On a closed platform, you're limited to what that platform offers, and when you outgrow it you start again somewhere else.
Financially, there are two shapes to watch:
Subscription stacking. Every feature is an add-on, priced per month, per seat or per credit. Bookings, email, memberships, extra AI generations. Each one is small. Together they climb in steps every time you grow.
Owning the stack. You pay for hosting you control and a domain, and open-source software does most of the rest. You pay for AI usage when you actually use it. It takes a bit more setup up front, and then the line tends to stay flatter.
THE COST CURVE AS YOU GROW · ILLUSTRATIVE
Subscription stack: starts low, steps up with every add-on, seat and credit.
Owned stack: a bit more setup up front, flatter as you grow.
BROCHURE
BLOG
BOOKINGS
CLIENT PORTAL
Neither shape is always cheaper. If you'll never need more than a brochure site, a builder subscription can be the simplest, cheapest path for years. The point is to pick the curve on purpose.
Q.09
It depends less on how technical you are and more on what your site needs to do in the next two years.
Here's where we'd start for four common solo businesses:
START AT: LEVEL 4
Your site sells trust. You need clear service pages, disclosures and compliance pages you can update the moment the rules change, and enquiries that land in systems you control. Owning the stack makes all three easier.
START AT: LEVEL 4 · L3 FOR PROTOTYPES
Your portfolio is your pitch, and you'll change it constantly. Own the home base on Level 4. When a client needs a quick campaign microsite or prototype, an AI app builder is a great sketchpad.
START AT: LEVEL 4 · GROW TOWARD 5
You need bookings and a content library first, both of which open-source tools handle well. If you later add a student portal with logins and progress tracking, that's when Level 5 starts to make sense.
LEVEL 2 TO TEST · LEVEL 4 TO OWN
Early on, you're testing a positioning, and a builder gets you there this week. Once the offer works, move your authority content and lead capture to ground you own, before there's too much to move.
Q.10
Five steps. You can do the first two today, and none of them needs code.
01
Buy your domain in your own name. Use an account you control, with your own email. If someone else registers it for you, make sure it's transferred to you.
02
Choose hosting you control. Managed WordPress hosting is a good middle ground: they handle the server, you keep the keys, and you can leave.
03
Install an open-source CMS. WordPress is the most common choice, and most hosts install it in one click. Add a visual editor like Elementor if you'd rather design by dragging than by typing.
04
Connect an AI assistant via MCP. Create a dedicated application password, give it the least access it needs, and keep publishing in your own hands.
05
Publish one page that sells one service. Not a whole site. One clear page: who it's for, what you do, what it costs or how to start, and one button to get in touch. Then improve it every week.
GAME SAVED · WHAT'S NEXT
Tools are the easy part now. Knowing what to build first, what to own and what to skip is where most solo founders lose months. That's what the Makr program is for: hands-on advisory built for founders working solo.
