A custom WordPress website runs through four stages: agree on the content structure, build the page templates, load the content and connections, then test and hand over. Its price depends on how many page types and integrations you need, far more than on the page count. Done well, you finish with a site your staff can edit and with code you own.
To keep this concrete, follow a hypothetical training provider. It runs courses on set dates in several towns. Staff want to add a course once and see it appear on the course page, the calendar and the town pages. A generic setup would turn that into copying and pasting. That is the kind of need a custom build answers.
Milestone one: the brief and the content model
No design tools open yet. The key output of this stage is a plain list of what kinds of content exist and how they relate.
For our training provider, that list looks like this:
- Course: title, summary, level, price, instructor.
- Session: a course on a date, in a town, with seats left.
- Instructor: name, photo, short bio.
- Town: a page that lists upcoming sessions there.
In WordPress terms, these become custom post types, taxonomies and custom fields, often built with a tool such as Advanced Custom Fields. Get this wrong, and every later stage costs more. So take the time to walk through real examples together.
Milestone two: templates and the editing experience
Now the visual side takes shape. Designs are turned into a theme, or a child theme, with a template for each content type. Reusable blocks handle sections that editors can mix on normal pages.
Ask to see the admin screens at this stage, not only the public pages. When the office manager adds a session, she should see a short form with clear labels. She should not see a page builder with a hundred options. A review at this point catches problems that are cheap to change.
Milestone three: content and connections
This stage feeds real content into the site and connects it to outside services. For the training provider, that means course data, a payment or booking step, and a link to its email list.
Importing data deserves a separate check. If the old content lives in spreadsheets or a prior site, someone must map fields and clean up the mess. Each integration also needs agreement on what happens when the other service goes down.
Milestone four: testing and launch
Real testing goes beyond clicking through pages. It includes staff performing their usual tasks, form and payment tests, phone checks, keyboard use, speed checks and redirects from any old addresses. Launch happens only after a final backup, and on a day when someone can react if something misbehaves.
What moves the price of a custom WordPress website
Wooprex quotes a fixed price before work starts. Expect a figure from $1,000 for a build of this size, based on your brief, with progress reviewed in weekly milestones. These are the things that move a quote most.
- Number of content types. Each one needs its fields, templates and admin screens.
- Integrations. A form that emails you is simple. A two-way sync with a booking system is not.
- Custom logic. Rules like “hide a session when the seats run out” must be built and tested.
- Content migration. Clean data costs little, while messy data costs much more.
- Number of languages and roles. Each one multiplies the testing.
What moves it less than you might expect? Sheer page count. Fifty town pages from one template are far less work than five pages that each need a unique layout.
If you find that nothing on that list applies, you may not need a custom build. A one-page WordPress website starts at $199, and our pricing page lists other standard options.
Plugin or custom code?
Reasonable developers will disagree here. A sound rule: use a maintained plugin for a common and well-understood need, such as SEO fields, caching or forms. Write custom code for what makes your business different, such as the session rules above. Our Plugin Development team packages that code as a small plugin of its own, so a future redesign does not remove it.
The handover list
On the last day, you should hold all of the following. Ask for it in the contract.
- Administrator access, and hosting and domain logins in your own name.
- All custom code in a repository you control, or at least a full copy.
- Licenses for paid plugins, registered to you.
- A short guide, written or on video, on how to do the common edits.
- A list of which plugins are installed, and why.
- A note on how backups run and how to restore one.
- A written statement that you own the custom work once it is paid for.
Then decide who looks after the site afterward. WordPress and its plugins need regular updates. You can do it yourself, retain the builder, or use Maintenance & Optimization.
How the AI and the expert split a build
Much of this work follows patterns. AI drafts field groups, template code and first-pass content and tests, which is why timelines can be short. A WordPress expert owns what a pattern cannot settle. That includes the content model, security checks on any input or database query, how the code behaves with real data, and whether the admin screens make sense to your staff. See Custom WordPress for the service itself.
FAQ
Will a custom site lock me in to one developer?
It should not. Standard post types, documented code and a repository you control mean another developer can take over. Ask how they handle this before you sign.
Do I have to design everything from scratch?
No. A build can adapt your existing brand or a ready-made design, and the custom work can focus on content structure and logic. That often keeps the cost lower.
How much of this can my team do themselves?
Writing and gathering content is the part most teams can take on. Doing it well can reduce the milestone three work, but agree on the format early.
Have a content type or a process that keeps forcing copy and paste? Explain it in Start a Task. The price and schedule are settled before anyone writes code.
