For most community, marketplace and directory sites, the sensible first move is to start from a ready-made theme and pay a developer only for the parts that are truly yours. A from-scratch build is the right call in a narrower set of cases, listed below, and this guide gives you a fair way to tell which side your project falls on before you sign a quote.
In this guide:
- What “hire a theme developer” usually means in a quote, and what it often leaves out
- What a from-scratch build must include, and what each part costs to own later
- What a ready theme plus add-ons gives you on day one (Reign facts, checked)
- A side-by-side comparison in words
- When custom work is the right call
- The middle path: a ready theme with a developer for the parts that are yours
- How to brief that developer, and questions to ask before hiring anyone
- Questions people ask
This is written for a business owner who is about to ask for quotes and is not a developer. Each technical term is explained the first time it appears. We make the Reign theme, so we have a view, and we say so. We also say plainly when a custom build is the better answer. Nothing here is legal or financial advice, and we give no figures for what a custom build costs, because any number we invented would mislead you. We give you a way to compare quotes instead.
What does “hire a theme developer” actually mean in a quote?
It usually means someone will write the code that controls how your site looks and where things appear, but the quote rarely says how much of the rest of the job is included. A theme is, in WordPress’s own words, the design of your website: it can control everything from colours to fonts to the entire layout. WordPress’s theme handbook adds the key division of labour: themes control the presentation of content, while plugins control the behaviours and features of your site (WordPress Theme Handbook, “What is a theme?”).
That division matters for a community, marketplace or directory site, because the hard parts of those sites are behaviours: members who can sign up and message each other, sellers who list products and get paid, businesses who submit listings that visitors can search. Those come from plugins. The theme’s job is to make every screen those plugins produce look like one product. A quote for “a custom theme” can therefore mean very different things:
- A design and templates only. The developer builds the look. You still have to choose, install and configure the plugins, and nobody is responsible for making the plugin screens match the design.
- Design plus styling of every plugin screen. This is the expensive version, and it is the one most owners assume they are buying.
- Design, plugins and custom logic. The developer also writes the member, listing or vendor behaviour. This is closer to building a product than building a theme.
If a quote says only “custom WordPress theme development” and a price, treat it as the first kind until the developer confirms otherwise in writing. The gap between what you imagined and what the first kind delivers is where most budget arguments start.
What does a quote often leave out?
Check the quote against this list. Anything missing is either excluded, which you should know now, or assumed, which is how scope disputes begin.
- Templates for every screen a visitor or member can reach, not just the home page and a blog post. A community site has profile pages, group pages, activity streams, message inboxes, settings screens and empty states (what a screen shows before anyone has added anything).
- Styling for the screens your plugins create, including the ones only logged-in members see.
- Accessibility, meaning that people using a keyboard, a screen reader or large text can use the site. The Web Content Accessibility Guidelines are the usual yardstick, and a quote should name the level it aims for.
- Email templates, because a community site sends many emails and they are part of the brand.
- Testing across the plugins you will actually run, on the PHP and WordPress versions your host uses.
- Documentation and a handover, so someone other than the original developer can change things later.
- Maintenance after launch. WordPress, PHP and every plugin keep changing, and a theme written once does not stay working on its own.
None of these is a trick. They are normal parts of the work. The problem is only when a price is compared with another price without asking which of them are inside each one.
What must a from-scratch build include, and what does each part cost to own?
A from-scratch build must include every item below, and each one keeps costing time after launch. Use this as a checklist when you read a quote or plan your own budget.
1. Design
What it covers: brand, colours, type, spacing, and the look of buttons, forms, cards and menus, decided once so every screen agrees.
The cost to own later: every new feature needs design decisions. If the design lives only in a developer’s head or a one-off design file, each addition means asking the same person again.
2. Templates for every screen
What it covers: the page layouts: home, archives, single items, search results, member areas, checkout, error pages.
The cost to own later: plugins update, and when a plugin changes its own markup, your custom templates can stop matching. Someone must notice, test and repair. The more screens you override, the more there is to repair.
3. Member, listing or vendor logic
What it covers: who can post, who can see what, how a listing is approved, how a vendor is paid.
The cost to own later: the most hidden work sits here, and every rule is one more thing to test when anything changes. Ask whether the developer writes this logic or uses a plugin that thousands of sites already run. Shared logic has been tested by many sites.
4. Payments
What it covers: taking money, refunds, receipts, tax handling, payouts to sellers if you run a marketplace.
The cost to own later: payment providers change their requirements, and mistakes here cost real money and trust.
5. Email
What it covers: welcome messages, notifications, receipts, password resets.
The cost to own later: delivery rules change, and messages that worked last year can land in spam. Someone must own the sending setup, not just the templates.
6. Accessibility
What it covers: keyboard use, screen reader labels, colour contrast, readable text sizes.
The cost to own later: every new screen needs the same care.
7. Testing
What it covers: trying the site as a visitor, a member, a seller and an admin, on phones and desktops, with the plugins you will run.
The cost to own later: each update repeats part of this. If nobody tests updates before they reach your live site, your members find the breakage for you.
8. Documentation
What it covers: a written description of what was built, where the code lives, how to change a setting, how to restore a backup.
The cost to own later: without it, every future developer has to read the whole codebase first, and you pay for that reading each time. Insist on it in the quote.
9. Handover
What it covers: access to the code repository, the hosting and any accounts, plus a walkthrough for whoever will run the site.
The cost to own later: if the code and accounts sit with the developer, you depend on that one person. That is a business risk, and it should be a deliberate choice, not a surprise.
What does it cost to own the finished build?
A site you build is a site you maintain, and the ongoing work falls into four buckets:
- Updates. WordPress releases updates, and every plugin you use releases its own. Each one needs to be tried on a copy of your site before it reaches your live one.
- Security. Code written for one site gets no outside review. A theme or plugin used by many sites gets bug reports and security fixes from a wider group of people. Ask who will watch for security notices about the plugins you run, and who will act on them.
- PHP and WordPress changes. PHP is the programming language WordPress runs on, and hosts retire old versions. Code that worked on one version can show warnings or stop on a newer one. A developer-maintained theme needs someone to keep it current.
- Changes you want. A year after launch you will want something different. A custom build means paying for design and development of each change. A ready theme often already has an option for it.
The practical test: ask the developer, “If you stopped working with me tomorrow, who would update this, and how long would it take them to learn it?” The answer tells you more about the real price than the quote does.
What does a ready theme plus add-ons give you on day one?
A ready theme gives you finished design and templates for the screens your plugins produce, so the first week goes into your content and rules instead of into building screens. Here is exactly what the Reign theme provides, based on its own pages, which we read on 8 October 2026. We list only what those pages state.
On its Reign theme page, the theme is described as the design layer for a whole community, with the features coming from plugins. In concrete terms:
- Community. Member profiles, activity feeds, groups and messages are styled for BuddyNext, our own community engine, which is free to install. Reign also styles BuddyPress, BuddyBoss Platform and PeepSo if you already run one of those.
- Marketplace. WooCommerce, Dokan, WC Vendors and WCFM marketplace screens are covered. Dokan, WC Vendors and WCFM each have a matching Reign add-on.
- Directory. GeoDirectory layouts are covered through a Reign add-on. Our own directory plugin, Listora, is styled by the theme itself, with no add-on in between.
- Job board. WP Job Manager layouts are covered through a Reign add-on. Our own job plugin, WP Career Board, is styled by the theme itself.
- Courses. LearnDash, LifterLMS, Tutor LMS and Sensei course archives, focus mode and student dashboards come through the matching Reign add-on. Our own course plugin, Learnomy, is styled by the theme.
- Brand controls. Custom colour tokens (named colour settings you change in one place), dark mode and five header layouts, with no code edits required.
The page states the model plainly: an add-on styles one third-party plugin so it looks native inside Reign, and you only need one if you run that plugin. Plugins from our own family need no add-on.
What does it cost, as listed today?
Read on the Reign pricing page on 8 October 2026: the Reign theme for one site is $99 a year or $249 once (lifetime). Each third-party add-on for one site is $39 a year or $79 once. A licence covers one production site, and staging and local development copies do not count. The page also lists a 30-day money-back guarantee and a free demo installer, with more than thirty demo sites. Prices can change, so check the pricing page before you budget. We do not list prices for our plugins’ paid plans here, because we want you to read the current ones yourself.
That is the licence cost only. Content, configuration and developer time to make the site yours exist on any route.
What do you still have to do yourself?
You still choose your plugins, write your pages, set your membership or listing rules, configure payments and moderate your community. A ready theme also reflects its makers’ choices and limits. If your project needs something outside them, the middle path below shows how to pay for changes safely.
If you want to see what the same theme looks like across different kinds of site, we covered that in One Theme, Many Sites You Own: What You Can Build With Reign, so we do not repeat it here.
How do the two routes compare, side by side?
Here is the comparison in words, across the four things that matter most to an owner. We use no invented numbers, because every project differs. Use these as questions for your own quotes.
Time to launch
Custom build: the design, every template, the logic and the testing all happen before you can show a member anything real. The calendar depends on how many screens you need and how fast decisions get made.
Ready theme plus add-ons: the screens exist on day one. You can import a demo, replace its content with yours and show a working version quickly. Your time goes into content, rules and polish. The risk is that you reach the end of what the theme’s options can do and need customisation, which is what the middle path covers.
Who maintains it
Custom build: you do, or the developer you keep on retainer. Every update to WordPress or a plugin is your responsibility to test. If the original developer leaves, the knowledge leaves with them unless it was documented.
Ready theme plus add-ons: the theme’s maker maintains the theme and its add-ons, and licences typically include updates and support for the licence period (Reign’s pricing page states this for both annual and lifetime licences). You still maintain your content, your plugins and your own customisations. A theme maker serving many sites can spread the cost of keeping up with WordPress and PHP changes, which one site cannot.
What you can change
Custom build: anything, at a price per change. Nothing is off the table, because the code is yours.
Ready theme plus add-ons: everything the theme’s options expose, which for colours, headers and layouts is a lot, plus anything a developer adds on top in a child theme or small plugin. What you cannot do is change the theme’s core without making updates harder.
Risk
Custom build: the main risks are dependence on one developer, scope growth, and a long tail of maintenance you did not budget for.
Ready theme plus add-ons: the main risks are fit (the theme may not suit an unusual brand or workflow) and dependence on the vendor’s continued work.
Is the new default WordPress theme enough for a community site?
No. The next default WordPress theme is a blank canvas for blogging, and a community, marketplace or directory site needs much more. In a post on make.wordpress.org dated 16 September 2026, the core team introduces Ipsum as the proposal for the next default theme, planned to be bundled in WordPress 7.2, and describes it as “an intentionally minimal blog theme that centers on a blank canvas” (Introducing Ipsum, the new default theme, read 8 October 2026). That is the right job for a default theme, which should be a simple starting point for the widest range of sites. It is not designed to give you member profiles, vendor dashboards or listing pages. Those still need either a purpose-built theme or a developer to build the screens. Starting from it and building the rest is the from-scratch build described above.
When is custom work the right call?
Custom work is the right call when what you need cannot be reached by choosing, configuring and lightly extending something that exists. Be honest with yourself against each of these, because they are narrower than most owners first think.
- An unusual workflow. Your core process is one that no existing plugin matches, and it is the thing customers pay you for. For example, a matching or booking process with rules specific to your industry. If the workflow is your business, building it is not a cost to avoid. It is the product.
- A brand system the theme cannot carry. You have a strict, established identity (a design system, with rules a regulator or a parent company enforces) and a ready theme’s options cannot reach it. A child theme can go a long way, so test that first. Where it truly cannot, a custom theme is justified.
- Heavy integrations. The site must connect deeply with systems you already run, such as a membership database, a CRM, a booking system or an internal API, and the connection is complex. Most of that work lives in plugins or integration code, not the theme, which means it is custom work even when the theme is ready-made.
- A product you will sell. You plan to resell or white-label the site to many customers, or the software is the thing you sell. Then you need to own and control the code, and the cost of building it is part of building a business.
What is the middle path: a ready theme and a developer for the parts that are yours?
The middle path is to start from a ready theme, then pay a developer to add only what is unique to you, in a way that does not break when the theme updates. For most owners reading this, it is the best balance, because it spends developer time where it creates value that no one else has.
WordPress has a standard, documented mechanism for this: the child theme. The WordPress developer handbook lists the reasons to use one: to make your modifications portable and replicable, to keep customisations separate from the parent theme, and to allow the parent theme to be updated without losing your modifications (WordPress Theme Handbook, “Child Themes”). A child theme needs, at minimum, a stylesheet that names its parent. Its functions file adds to the parent’s instead of replacing it. The same page warns that extensive customisation from within a child theme can become a headache, and at that point it suggests thinking about a separate theme. That gives you a rule for your brief: a child theme is for changes, not for rebuilding the theme.
For behaviour rather than appearance, the right home is a small plugin written for your site. Because the WordPress handbook assigns behaviours and features to plugins, a rule such as “listings from this category need manual approval” belongs in a small plugin, not in the theme. That way, if you ever change themes, the rule goes with you.
How do you brief a developer for this?
A clear brief protects you more than any contract clause. Include these points, and put them in writing.
- State the starting point. “We are using this theme and these plugins. Customisations go in a child theme or a small plugin. We do not edit the theme or plugin files.”
- List what must be unique, and why. Three to ten items, each with the reason it cannot be done with existing options. If the reason is weak, the developer should tell you.
- Insist on staging. A staging site is a private copy of your site where changes are tried before they reach the live one. No change should go to the live site without being checked on staging first.
- Insist on version control. Version control (usually Git) records every change to the code, who made it and why, and lets you undo a mistake. Ask that the repository is in an account you own or can access, not only the developer’s.
- Insist on handover notes. A short document: what was built, where it lives, how to update it, what to test after each WordPress or plugin update, and which accounts and licences it depends on.
- Agree what happens at update time. When the theme or a plugin updates, who tests your customisations, and is that inside the price or billed separately?
- Agree how success is checked. A list of screens and tasks (sign up, post a listing, buy something, reset a password) that must work on a phone and a desktop before the work counts as done.
What should you ask any developer before hiring?
These questions work for a freelancer, an agency, or a company like ours. Good answers are specific. Vague answers are information too.
- “Which parts of this need to be built, and which can use something that exists?” A good developer will happily name existing options even when it reduces their work. One who always says “custom” deserves a follow-up.
- “What exactly does your quote include?” Ask for the list from earlier in this guide: templates for every screen, plugin screen styling, mobile, accessibility, testing, documentation, handover.
- “What will you do about updates after launch, and what does that cost?” Look for a clear answer on who tests, how often and at what charge.
- “Who owns the code and the accounts at the end?” The answer should be you.
- “What would make you recommend a ready theme instead?” The reply tells you whether you are being advised or sold to.
For a broader checklist on vetting a developer, including the types of engagement on offer, see our companion guide on the Wbcom Designs site, How to Hire a WordPress Developer in 2026 Without Getting Burned. We keep this post to the theme-versus-custom decision so we do not repeat it.
Questions people ask
Is a ready theme always cheaper than hiring a developer?
Not always, and we will not claim it is. A ready theme usually costs less to start and less to maintain, because the design and templates are shared across many sites. But a ready theme with extensive custom changes can cost more than a tight custom build, and a project with an unusual workflow may need custom work whatever theme you pick. Compare the total over the first couple of years, including upkeep, rather than the launch price alone.
Will a site on a ready theme look like everyone else’s?
Only if you leave every setting alone. Colours, type, logo, header layout and your own images and content do most of the work of making a site look like yours. Reign, for example, lists custom colour tokens, dark mode and five header layouts as brand controls. If you need more than that, a child theme adds it without touching the parent.
What is the difference between a child theme and a custom theme?
A child theme sits on top of an existing parent theme and changes only what you specify, so the parent can keep receiving updates. A custom theme is built whole, and you own all of it, including the maintenance. WordPress’s own handbook recommends child themes for modifying an existing theme and suggests a separate theme only when the customisation becomes extensive.
Do you need a developer at all with a ready theme?
Many owners launch without one, using the demo importer, the theme options and the plugins’ settings. You are more likely to need one for custom rules, integrations with other systems, performance work on a large site, or a one-off look that the options do not reach. Hire for those specific jobs and agree the scope in writing.
Is the new default WordPress theme a good base for a community site?
It is a good base for a blog. The core team describes Ipsum as an intentionally minimal blog theme and a blank canvas. A community, marketplace or directory still needs screens for members, sellers and listings, from either a purpose-built theme or a developer.
If you want to see how a ready community theme handles the screens in this guide, the Reign theme page lists what it styles, the plugins it works with, and the current price, and you can try the free demo installer before deciding. If your project is one of the cases where custom work is right, the same page shows what you would be building on top of.