Building online without boxing yourself in.

I thought I was simply building two websites. Instead, I learned how much the platform beneath a website determines what you can do next.

A website can look beautiful and still be static. It may tell people who you are, but it cannot necessarily manage customers, payments, memberships, documents, enquiries or the everyday work behind the business.

This is where I share what I am learning from building real websites, encountering their limits and asking better questions about what an online business actually needs.

Your website may look good—but do you own a business asset?

Most entrepreneurs choose a website based on what they need today: a professional-looking page, photographs, contact details and perhaps a form. That feels sufficient—until the business begins to grow.

Then they need bookings, payments, customer records, memberships, digital products, automated follow-ups or a client portal. Suddenly, the beautiful website is no longer supporting the business. It has become something the business must work around.

I understood this more clearly while helping to build two very different websites: Cape Town Blogger and the website for GRAPA, a community organisation. Google Sites was a practical choice for both. It gave each project an accessible online home without unnecessary complexity. It also showed me, through lived experience, where a publishing website ends and a business platform needs to begin.

The problem is not that a simple website is bad. The problem is choosing one without understanding the limits—and discovering those limits only after your customers, content and processes have become tied to it.

The shiny object is only the front door.

A website is often treated as the finished product. In reality, it may be only the front door. Behind it, the business still needs somewhere to manage enquiries, customer information, payments, communication, content, services and the work that follows every click.

If all of that happens across disconnected tools, spreadsheets, inboxes and manual messages, the business owner has not really built one system. They have built a collection of workarounds. Each new requirement adds another subscription, another login and another place where important information can be lost.

A platform can also look easy to leave until the day you try. The domain may belong to you, but what about the design, customer data, forms, automations, transaction history and content structure? Can they be exported in a useful format? Can they move with you? What must be rebuilt by hand? That is when many owners discover that the website they paid for is not the portable business asset they assumed it was.

I now understand what my husband has been building.

These two website projects gave me a clearer understanding of my husband’s work. His focus has never been only on producing a polished website. He has been building a configurable foundation that can support the work behind it: customer management, payments, forms, email, automation, client areas, online selling and room to add what a business needs as it develops.

That distinction is easy to miss when all we can see is the website. We compare colours, layouts and templates because those are visible. The real value, however, may be in what happens after a person makes contact, becomes a customer or needs to return.

I am still learning. I am also asking better questions now—not only, “Does this website look good?” but, “What will this platform allow the business to become?”

Questions worth asking before you build

• Do I own and control my domain?

• Can I export my content and customer data in a useful format?

• Can the platform manage the work behind the website?

• Can it add payments, memberships, bookings or a client area when I need them?

• Will new features connect to one customer record, or create another information silo?

• What will have to be rebuilt if I move?

• Am I choosing for the business I have today, or leaving room for the business I am trying to build?

The right answer will not be the same for every project. Cape Town Blogger and GRAPA do not currently need a complex operating platform. Their websites are doing the job they were built to do. The lesson is to make that choice knowingly—and to recognise when a website is an online presence and when a growing business needs something more.

Cloud does not automatically mean organised.

A few years ago, we helped an NPO migrate its files from Dropbox to its own server. It was a nightmare.

The organisation did not have one shared filing architecture. Every user had created a personal system, so the location and naming of documents depended on who had saved them. Institutional records sat beside personal files. Folders had grown around individuals instead of the organisation, and there was no reliable organisation-wide structure to move.

The migration exposed a risk that had been easy to ignore while everything appeared to be safely stored in the cloud: storing information is not the same as governing it.

Google Drive can become the same kind of problem. It is easy to keep adding files and folders because there always seems to be somewhere to put them. Without agreed naming conventions, permissions, ownership and one official location for each type of record, the clutter grows quietly. By the time an organisation needs to migrate, audit its records or hand responsibility to someone new, nobody is entirely certain what is current, duplicated, personal or missing.

Ask me how I know! Organising GRAPA’s Drive has made the lesson very real again.

The cloud is a tool, not an information strategy.

Cloud services can make collaboration, access and backup much easier. The risk begins when an organisation assumes the platform will create order on its behalf. It will not.

A sustainable system needs an organisation-wide folder architecture, clear file-naming rules, appropriate access permissions, institutional ownership and a process for archiving outdated records. It should be built around roles and business functions—not around the preferences of whichever individual happens to be using it today.

This is also part of building online. A business can be trapped not only by its website platform, but by years of unmanaged information scattered across accounts and tools. The earlier the structure is created, the easier the organisation is to run, protect and eventually move.