A website is either an asset or an expense. There is very little middle ground.
Built properly, it earns its keep over time. Built badly, it absorbs time, rebuild cycles and subscription costs without returning proportionate income.
I have rebuilt enough sites, and closed enough projects, to understand that instability costs more than annual renewals.
This page documents how I run this site as part of my overall income structure, and why I keep it deliberately contained. It also explains the infrastructure decisions behind the site: the tools, structure and constraints that keep it stable.
Why the Website Matters
Marketplaces provide buyers. Digital products provide leverage. A website provides control.
It gives you a place to direct traffic you do not rent, explain what you sell clearly, and route visitors between income layers without relying entirely on external platforms.
Without a controlled website, pricing, positioning and visibility are shaped by someone else’s rules. That may work for a period of time. It does not protect margin over the long term.
Control reduces structural risk. That is the role of the website.
Structure Before Traffic
Traffic does not fix a weak setup. It exposes it.
Before focusing on growth, I prioritise clarity of structure. That means defined sections, simple navigation, and pages that each have a specific commercial job.
If structure is messy, traffic magnifies confusion. If structure is tight, traffic compounds into something useful.
I no longer redesign for novelty. Earlier in my online work, I rebuilt sites chasing layout improvements or perceived design upgrades. The time cost of those rebuilds exceeded several years of hosting fees. The disruption rarely improved income proportionately.
Now I build for reliability and ease of publishing.
Stability costs less than experimentation.
Tools Cost Money
Websites are not free, even when the software is inexpensive.
Hosting costs money. Email systems cost money. Themes and plugins cost money. The visible costs are obvious. The hidden costs show up later in migration time, plugin conflicts, SEO disruption and lost publishing momentum.
Very cheap setups often become expensive through rebuild cycles. Rebuilding a site once usually costs more than several years of solid tools.
The goal is not to run the cheapest stack possible. The goal is to run a stack that remains proportionate to turnover and does not introduce fragility.
If complexity begins to grow faster than income, I apply the same test outlined in When to Stop.
Proof of Stability
The current structure of this site has remained stable for years without redesign cycles or forced migrations.
Tools are added only when income structure justifies them, and removed when they no longer serve a clear role.
I have not rebuilt this site to chase trends, experiment with heavy page builders or layer unnecessary automation. The focus has remained on publishing, routing and income support.
Stability compounds quietly. It rarely looks impressive, but it prevents structural drag.
The Core Stack That Runs This Site
This site runs on a deliberately small stack:
Member videos are hosted on Bunny. Public videos are embedded directly from YouTube.
Hosting is chosen with renewal stability and margin protection in mind. I compare proportionate hosting options in Best WordPress Hosting for Small UK Digital Product Businesses.
There is no page builder, no heavy optimisation framework and no layered plugin stack.
Total annual paid tool cost sits roughly between £250 and £300 depending on renewals and usage. For infrastructure designed to support income over years rather than months, that is a reasonable operating expense.
Each tool exists because it supports margin or stability. None exist for novelty.
If you are starting from scratch, begin with GeneratePress Premium and GenerateBlocks. Everything else improves performance. Those two define the foundation.
Stability is cheaper than rebuilding.
What Would Make Me Rebuild This Site
I am not attached to any setup.
I would reconsider the structure if income model changed materially, if renewals became disproportionate to turnover, or if plugin stacking began to increase maintenance load beyond what the revenue justified.
Rebuild decisions should follow income shifts, not design preference.
So far, the current structure has remained proportionate to both revenue and workload. If that changes, I would simplify before expanding.
Content With a Defined Role
Not every page exists to rank.
Each page on this site serves one of four roles inside the income system:
- Income
- Infrastructure
- Documentation
- Routing
If a post or page does not generate income, support it, document it or route it, it does not remain.
Clarity compounds over time. Excess pages dilute attention and increase maintenance overhead.
How This Supports Income
Reselling and digital products operate differently, but both rely on control.
This website captures traffic I can direct, explains what I sell clearly, routes visitors between income layers, and supports affiliate revenue without turning into a marketing machine.
Without a stable website, everything depends on eBay, Etsy, email platforms or social media. That increases platform exposure and reduces pricing control.
A controlled site provides pricing freedom, clearer positioning and a base that I own.
The website is not the main event. It exists to protect what I build on top of it.
Where to Start if You Are Building a Site Like This
If you are rebuilding a site or starting fresh, begin with the foundation: GeneratePress & GenerateBlocks.
If you are building marketplace income, see How I Make Money on eBay, Vinted and Etsy.
If you are building digital products, see How I Make Money With Digital Products.