How Much Website Does a Solo Business Actually Need?
A practical guide for solo founders: what to build, what to skip, and how to keep ownership of your site.
For a solo business owner, a website is a business card, a salesperson, and a monthly chore all at once. That's why the real question isn't "should I build one?" but "how far should I build, and where should I stop?" This guide collects the decision points we at SAENRU run into repeatedly while building sites and doing AI search optimization work, framed for people running a business alone.
What's the minimum a solo business website needs?
Four or five pages are enough to start: home, services and pricing, case studies or portfolio, about, and contact. Without these, visitors can't tell what you sell or what it costs, so they leave. Adding more pages beyond this rarely moves conversion much.
The two things solo founders most often omit are pricing information and multiple ways to reach you. A page that only says "contact us for a quote" fails to filter inquiries, and you end up spending hours on people who were only price-shopping. Even a starting price or a range changes the quality of the messages you receive.
- Home: a one-sentence definition (for whom, what, how), three sample cases, and a contact button
- Services and pricing: package names, what's included, starting price or range, timeline
- Cases: industry, problem, outcome — one paragraph each. Text alone works fine
- About: real name, background, business registration details, and a photo of your face (it meaningfully helps trust)
- Contact: a form plus at least two of email, messenger, or phone
Should you build it yourself or hire someone?
The deciding factor isn't budget — it's how often you plan to edit the site yourself. If you'll publish content weekly, a no-code builder you control is better. If you'll touch it two or three times a year, building it properly once and stepping away usually costs less overall.
No-code builders start fast but tend to limit fine control over HTML structure, structured data, and file-level assets. Custom development gives more freedom, but if you don't check source code ownership and handover terms in the contract, you're locked in when you want to switch vendors. The smaller your team, the more urgently you should ask: can I walk away with this asset intact?
- Is the domain registered under your own name?
- Can you receive the source code and repository (a GitHub handover, for example)?
- Do you own the hosting account, analytics, and search console properties?
- Does the site keep running if the vendor relationship ends?
- Can the monthly retainer be explained line by line as actual work?
What does SAENRU offer a solo business?
SAENRU runs an open launch stage for AI builders alongside its production and consulting services. Depending on your budget and stage, there's a free path and a hire-us path. Since this is our own blog, we'll state it plainly.
- If you built it yourself: register your AI-built web or app project for free on Launch to get exposure, votes, and feedback. We encourage open launching on GitHub, and code ownership stays with the builder. The weekly vote winner gets a free week on the main banner plus an interview feature.
- If you'd rather hire: SAENRU Studio builds through an AI pipeline — websites from 2.7M KRW (about 2 weeks), web app MVPs from 8.7M KRW (4–6 weeks). You see a first prototype within 48 hours, and the finished work is handed over as the full GitHub repository.
- If AI search visibility is urgent: AEO/GEO consulting starts with a measured diagnostic report across ChatGPT, Gemini, and Claude for 190,000 KRW, delivered in five business days. Build packages start at 3.6M KRW and monthly operations at 1.47M KRW per month; the diagnostic fee is fully credited if you sign a build contract. All prices exclude VAT.
For reference, the SAENRU homepage itself is an AEO implementation case — raw HTML with embedded JSON-LD and llms.txt. If you're running a business alone, we'd suggest building something yourself first, checking the response, and then spending money only where it's clearly needed.
What mistakes do solo founders make most often?
The most common one is spending all the time on design and writing the copy last. Visitors aren't judging your font — they're deciding whether you can solve their problem. The second most common is refusing to publish until it's "finished," when shipping something incomplete and collecting feedback improves it far faster.
- Launching a blog and abandoning it after three months — better not to have one
- Putting contact details in an image so they can't be searched or copied
- A contact button pushed off-screen on mobile
- A case page with only unverifiable phrases like "many clients" and no concrete examples
- Hiring a vendor and never receiving the domain or account credentials
A website isn't something you finish once — it's an asset you keep revising. Start with four or five pages, watch which path actually produces inquiries, and expand from there. For a solo business, that sequence is usually enough.