You described your business, the site came out, and it is live. Now you want it to be yours.
Most advice for this stage is a list of settings, which is the least useful version of the answer. The hard part was never finding the colour picker. It is knowing which of your changes belong in which tool, which ones a generator can help with, which ones only you can make, and which ones need a person. Four different jobs, in four different places, and they get confused with each other constantly.
Start from the generated site, not a blank one#
This sounds obvious and it is still where the money goes. What a generator hands you is a first draft of an entire website: the pages a business of your type needs, a layout for each, copy in every section, and the components those sections are built from. Editing that is a different activity from commissioning it.
So customizing means changing what is already there. If your reaction to the first version is that none of it fits, the cheap fix is usually a more precise description and another generation, not a hand-built site started from nothing.
Where each kind of change lives#
Sitebefy builds a real WordPress site and you hold the WordPress credentials, so you have two editors rather than one. They are not competing for the same work.
| The change | Where you make it | Why there |
|---|---|---|
| A typo, a phone number, a rewritten paragraph | The Sitebefy editor | It is the shortest path to a word on a page. |
| Logo, colours, typefaces, spacing | WordPress | Theme settings, and they apply everywhere at once. |
| New pages, menus, site structure | WordPress | The Sitebefy editor is for words, not architecture. |
| Plugins, users, permissions, settings | WordPress | Ordinary WordPress administration, on an ordinary WordPress site. |
| Anything driven by how your company operates | A developer | No generator finishes these. They are covered further down. |
The third row is the one to memorise. Sitebefy is quicker for changing text on a page, and WordPress gives you everything else.
Branding, UX and content#
Every guide groups these three together, this article's own banner included. They are wildly different amounts of work.
Branding is the cheapest and the most visible. Logo, palette, typefaces, the spacing that decides whether a page feels expensive or cramped. It is theme configuration, it applies site-wide, and an afternoon usually covers it. Do it early, because seeing your own colours changes how you read everything else on the page.
UX is the order things appear in and how short the next step is. Which section opens the home page. Whether the phone number survives without scrolling. How many clicks separate a service page from a contact form. Those are structural edits, so they happen in WordPress, and they are worth more than the colours are.
Content is where the real work sits, and it is the one part nobody can do on your behalf.
It has your description and nothing else. It does not know the client you rescued on a Sunday, the guarantee you actually honour, what you charge, why you turned a job down last month, or what your work looks like in a photograph. Every sentence in the generated copy that would be equally true of a competitor is a sentence waiting to be replaced by one that could only be about you.
In practice: read each page and mark every claim that your competitors could also make. Those marked lines are the work. A generated draft is doing its job when it gives you something to disagree with, which is a great deal easier than an empty page.
The change that quietly undoes the others#
One action deserves its own warning, because it sits right next to the others in the interface and it does not ask twice.
Regenerating with AI writes the site again from a fresh description, and it replaces the current content. Anything you changed by hand goes with it. That is correct behaviour for a site nobody has customized yet, and an unpleasant surprise on one you have spent a week on. Take a backup first, or copy out what you want to keep. It also spends one AI request from your monthly allowance, the same as a build.
The two safety nets are not interchangeable, and reaching for the wrong one costs an afternoon. Version history tracks changes as they happen, so it answers what changed and can I undo it. A backup is a deliberate snapshot of the whole site, so it answers put everything back to Tuesday. Use history for edits. Take a backup before anything you would call risky, which in practice means regenerating, installing an unfamiliar plugin, changing PHP version, or any large restructure.
Telling the generic parts from the parts that are yours#
Before you commission anything, sort what you want into two piles. One pile holds everything a business in a different industry would want, built the same way: responsive layout, a contact form, SEO tags, a blog, image handling, accounts, a cookie banner. Those are solved. They ship with the site or install in minutes, and paying to have them built again buys a private copy of something public, with nobody else fixing its bugs.
The other pile holds anything whose requirements come out of how your company operates. For most businesses that pile is short, and it is the only one worth a quote. The money side of the same split is worked through in the development costs guide.
Specialized business features#
Some things no generator finishes. It is worth naming them, because "custom development" is otherwise a phrase anyone can talk you into.
- A booking system that knows real staff availability, takes deposits, and enforces your cancellation rules.
- Membership tiers with gated content and renewals.
- A customer portal where people sign in and see their own data.
- An integration with the CRM or ERP you already run the business on, so the website stops being an island.
- Workflow automation that follows how your company actually works, which exists in no plugin because nobody else works that way.
The requirements for these live in your operations and in your head, not in any training data. That is why they need a person, and it is why the scoping conversation matters more than the code. Vague requirements are the usual reason software projects go over.
One honest note. Sometimes an existing WordPress plugin already does the thing you are about to pay for. A good answer to a custom request is occasionally "install this instead", and you should expect to hear it from anyone worth hiring.
Why none of this means rebuilding#
This is the part that surprises people, and it is the reason the whole sequence works.
On a closed platform, whatever the vendor supports is the ceiling. Outgrowing the product means rebuilding somewhere else, and the money saved at the start gets spent a second time. A generated Sitebefy site is an ordinary WordPress installation, so a developer extends it the way they would extend any WordPress site: custom plugins, custom post types, custom templates, real server-side code. The work lands on the site you already have. No migration, no second website, and the URL your customers know does not change. The two routes are compared here.
The order that keeps this cheap#
Sequence does more for a budget than any single decision inside it.
- Generate, then read it as a stranger would, before changing anything. Half of what you were going to fix turns out not to need fixing.
- Do the branding. It is fast, it is site-wide, and it changes how you judge everything after it.
- Replace the generic sentences with true ones. This is the bulk of the work and it belongs to you alone.
- Run the business on the site. A few months of real visitors will tell you what is missing.
- Then quote the custom piece, if you still want it by that point.
Paying for custom functionality before launch means paying against a guess about what customers will want, made before there were any customers on the site to watch. What people are certain they need on day one is usually different from what they need on day ninety.
That is the whole mindset. A generator builds the foundation, and it is genuinely good at that, because a foundation is a solved problem repeated across millions of sites. A developer should be spending their hours on the part of your business that exists nowhere else. Anyone billing developer time for a contact form has the split backwards.
Generate the foundation, then make it yours
Describe what you do and Sitebefy builds a real WordPress site you own, with the pages, layouts, content and SEO already in place. Edit the words from Sitebefy, everything else in WordPress, and bring in a developer later for the parts only your business needs. Look at the result before creating an account, and every plan carries a 14-day money-back guarantee.
Build my siteWhat to do this week#
- Read the home page out loud and mark every sentence a competitor could have written.
- Set the logo, colours and typefaces in WordPress. One sitting is enough.
- Take a backup, then make the one structural change you have been putting off.
- Write down the thing your business does that the site cannot do yet. That sentence is the beginning of a scope, or the discovery that you do not need one.
None of this is a project with an end date. The generated site is a starting position rather than a commitment: a site written by AI can be rewritten by hand, a site written by hand can be regenerated, and a site with no custom code can get some in a year without moving anywhere.
Which leaves one small decision to get right now. Change the sentences that are not yet true. The rest can wait until the business tells you what it needs, and it will.
