Going Solo: How a One-Person Web Practice Runs Client Sites Without an Ops Team

Going solo does not fail on craft. The people who leave a studio to run their own practice can nearly always build the sites. What breaks them is everything attached to the sites: the hosting that needs watching, the platform updates that arrive on someone else's schedule, the plugin that stops working on a Friday, the invoice nobody sent, the client who wants a small change on a site you last opened eleven months ago.

One person cannot carry a delivery team, a sysadmin and an account manager at the same time. So the platform choice is not a preference question when you are on your own — it decides how many client sites you can hold before the maintenance load eats the week you were going to sell in. This is what that looks like on WebinOne, with the mechanics named and every claim pointed at the page it comes from.

What actually ends a one-person web practice?

Maintenance that grows faster than revenue. Every site you take on adds a permanent, unpaid subscription of small obligations: platform updates, dependency updates, certificate renewals, backups you hope are running, a hosting account with its own billing and its own support queue. Ten sites on ten stacks is not ten times one site — it is ten different failure modes, and you are the only person on call for all of them. The practices that survive are usually the ones that made every client site look the same from the inside.

What does one platform for every client site remove from your week?

The switching. On WebinOne the content management, the Ecommerce, the CRM, the forms, the member areas and the workflow notifications are parts of the same product rather than parts you assemble. Our platform overview states it directly: "All features are native extensions built and maintained by the WebinOne team." That is the difference between a stack you maintain and a platform that maintains itself under you.

The second thing it removes is the tab sprawl. Every client site you build sits in one Portal — the same page-overview publishes that "Partners manage all client sites from a single centralized portal", with trial sites, live sites, client billing and support tickets in that one place. For a solo operator that is not a convenience feature. It is the difference between knowing the state of your whole book of business in one screen and reconstructing it from memory every Monday.

Who patches the platform when you are the only developer?

Not you. Our security overview publishes the split in plain language: "AWS operates, manages, and controls the components from the hypervisor virtualization layer down to the physical security of the facilities in which WebinOne operates. In turn, WebinOne assumes responsibility and management of the guest operating system (including updates and security patches) and application software, as well as the configuration of the AWS-provided security group firewall."

Read that as a job description you are not doing. Nobody is asking you to size an instance, apply a kernel patch, renew a certificate by hand or work out why a shared host started throttling. Our support FAQ puts the same fact from the operator's side: "All sites are supported and maintained by WebinOne team on AWS servers." Backups are ours too — we publish that platform data is stored in Amazon EBS and backed up via snapshot lifecycle policies every 12 hours.

Where the site physically lives is still your decision, per site rather than per account: the data centre is chosen for each website you create, which is what makes a client with a data-residency requirement a normal project instead of a special one. The choice is listed on the platform overview and in the support FAQ.

Where does the margin come from when you are both the agency and the account manager?

From the gap between what you pay and what you invoice, and the programme is built around that gap rather than around a rate card you have to work past. Our pricing page says the published plan pricing "is designated for web design resellers" and that "site owners and free users expect at least 2x markup". You are buying at the reseller line and selling at your own.

Three mechanics matter more than the numbers. Plans are modular — you choose a content plan per site and add Ecommerce only on the sites that sell something, so a brochure site never carries the cost of a store. Ecommerce carries no transaction fees: the platform overview publishes "zero transaction fees on all Ecommerce plans, regardless of sales volume", which means a client's good quarter does not quietly become a platform bill. And the reseller programme is white-label — "White-label all of the sites under your brand", with granular white-labeling, branded subdomains and, in its own words, "direct billing is available".

WebinOne does not publish a fixed commission rate, and that is the point: what you charge for hosting, care plans and changes is your pricing decision, not a percentage handed to you.

What happens when a project is bigger than one person?

You subcontract it to the team that built the platform instead of turning it down or hiring. TeamOne is our in-house development, design and QA bench, and it is available to Partners as fixed packages with the price published on the page: template adaptation to a brief, design-to-implementation from Figma or PSD, migrations by site size, WCAG audits, and prepaid credits you spend on whatever comes up. Its own published record is on that page — founded 2009, more than 1,700 projects delivered, agencies in 16 countries.

The operational value for a solo practice is narrower and more useful than "we have a team". It is that you can say yes to a project whose middle you cannot staff, quote it from a published price rather than a guess, and keep the client relationship and the invoice. The bench is also the answer to the thing that actually frightens people about going solo: what happens to your clients during the two weeks you are away or ill.

What does the AI layer actually give a one-person practice?

Leverage in the two places a solo operator has none: repetition and coverage. AgentOne is the platform's own agent system, in Partner Beta and available to licensed Partners, and it runs inside the WebinOne admin rather than as another tool with another login and another way of thinking about your work.

It is built in three layers, and the middle one is the one that matters most if you are on your own. System Agents ship with every site and are trained by our team: they know the platform natively — every component, module, Liquid pattern, custom property and API — rather than generic code patterns. Partner Agents are your layer, where your own skills, design patterns and preferred configurations live; build a pattern once and deploy it across every client site, so your methodology becomes a reusable asset instead of tribal knowledge in one head. Site Agents sit on individual sites for specialised work — SEO, content, operations — and when you decide the client is ready, they can be given limited self-service inside boundaries you define. Your call, your rules.

The control model is the part I would read first, because for one person an unsupervised agent is a liability rather than a colleague. That distinction is the whole of what we call Managed Vibe Coding: the agent operates directly on a managed platform, inside the live infrastructure that will still be running the site next year, instead of generating code files somebody then has to host, secure and maintain alone. Everything runs in draft mode: nothing publishes without your approval. The boundaries are yours to configure — what the AI may and may not touch, your design system, your patterns. A backup is taken before every modification with one-click rollback, and the activity log records what changed, when and why.

Where this goes is a self-operating website: a site that updates content, optimises SEO and manages its own data inside the boundaries the practice that built it has set, instead of sitting still until someone bills an hour to maintain it. That is the direction of the product, not a description of a finished one — AgentOne is in Partner Beta today and early access to the next version opens to Partners. Two commercial consequences are worth planning for now: AI workspace configuration is something you can sell as a service, and a well-built Partner Agent is a product in its own right, alongside recurring management fees rather than one-off build fees.

Why do clients stay, and what happens if the platform does not?

Clients stay because there is nothing to escape from. A site that keeps working, keeps being editable and never demands a migration project generates no reason to shop around, and recurring platform-plus-care revenue is what turns a solo practice into a business with a floor under it rather than a sequence of builds.

The harder version of that question is what happens if we stop. Our Terms of Service answers it in writing, under End of Life Immunity: "In case of an unlikely event of the Service being closed or discontinued for any reason, we commit to open-source the WebinOne platform to the level that every Reseller would be able to host their trial and live sites, WebinOne Portal, and SSO service without our support." The same document is equally plain about whose work it is: "Customer Content is and remains your exclusive property, and we claim no rights whatsoever to the Customer Content except to the extent explicitly granted herein." Read both before you commit a client book to any platform, ours included — the absence of that clause elsewhere is worth noticing.

What does the platform not do for you?

It does not find clients, write proposals or chase invoices. Removing the operations load gives you the hours back; what you sell in them is still on you, and no platform choice fixes a pipeline.

Three more limits worth knowing before you plan around them. TeamOne is paid delivery work, not a free bench — the packages are priced, and the page states that the final price may vary for custom, non-standard projects. The On-Site Editor lets a client edit front-end content without admin access, and it is worth setting up per site and walking through with the client at handover rather than assuming every layout suits it. And if you are arriving with existing client sites, treat that as a rebuild rather than a copy: our migration page says so in our own words — "Our team rebuilds your site on WebinOne" — and what transfers and what gets rebuilt is worth reading before you promise a date, which is the subject of a separate piece on inheriting a client site.

How does a solo operator actually start?

Free, and without a sales conversation. The reseller programme's own description of the model is that Partners sign up for a free account and get immediate access to the admin portal; you build on trial sites, activate a site to live when the client signs, and every live site includes an SSL certificate. Branding the Portal under your own name and switching on direct billing are settings, not a negotiation.

The order that works for a one-person practice: build one real client site end to end before you move anything else, put the second one on the same platform so the first has company rather than an exception, and only then decide whether to migrate the back catalogue. The reseller programme page is where the Partner tiers and the white-label mechanics live, and it is the page to read next. If you want the delivery mechanics — Portal structure, admin roles, environments — how delivery works on WebinOne covers them at the level a working practitioner needs.