A WordPress website proposal is the document that turns an engagement into scope, deliverables, and price — and it is the single best predictor of how the project will actually run. It is also, for most small-business owners, one of the harder documents to read. The vocabulary is unfamiliar, the numbers vary wildly, and two proposals that look almost identical on the cover can differ by twenty thousand dollars in what they actually deliver.
A café owner on Guadalupe Street in Santa Fe recently walked me through three proposals for a new site — $8,000, $17,500, and $34,000 — and asked, reasonably, why. The answer was in the line items. Once we lined the three up section by section, two of them dropped out on their own, and the choice became obvious. This is what I wish she had read before she started.
What a real WordPress proposal contains
Skip the cover art and look for these sections. If a proposal is missing three or more, it is not a proposal — it is a quote. That distinction matters, because a quote binds neither party to anything specific.
- Scope of work — the pages, features, and functionality being built, in enough detail to argue about later.
- Deliverables — the specific artifacts you will receive (design files, a working site, training materials).
- Line-item pricing — cost broken down by phase or component, not a single lump sum.
- Timeline — realistic milestones, with dependencies on your side called out (content delivery, feedback windows).
- Exclusions — what the proposal does not cover. This is where the surprise invoices live.
- Assumptions — what has to be true for the timeline and price to hold (existing hosting, content ready by X, etc.).
- Contract terms — payment schedule, ownership, warranty, what happens if you cancel.
Decoding the line items
Custom WordPress builds usually break down into six to eight billable components. Here is what each one actually covers.
Discovery. Interviews, competitor review, sitemap, and a written brief that turns your business goals into design decisions. On a small site this runs 5–15 percent of the total; skipping it usually costs more later. If a proposal has no discovery line at all, you are paying for a visual refresh, not a real project.
Information architecture. The sitemap and content model — how pages nest, what custom post types exist, what fields each entry needs. Often bundled into discovery on smaller sites and broken out on larger ones. Any site with a portfolio, staff directory, product catalog, or events calendar needs this work done deliberately.
Design. Homepage, key page templates, and a component system (buttons, forms, cards). Ask how many revision rounds are included and what happens if you want a second creative direction — this is where “design” line items diverge dramatically in what they actually deliver.
Development. Turning the design into a working WordPress theme. On a custom project this usually means a bespoke theme (not a customized commercial one), custom fields for editable regions, and the block patterns your team will use to add content later. If a proposal names a page-builder plugin (Elementor, Divi, WPBakery) as the whole approach, the “custom” price should reflect a template, not custom work.
Integrations. Anything that has to talk to another system — a CRM, a point-of-sale, a booking tool, an email platform, Google Analytics 4, a payment processor. Each integration is its own small project. A proposal that lists “integrations” as a single line without naming the systems is understating the work.
Content entry. Someone has to put your text and images into the CMS. Proposals differ on who does it — you, the developer, or a mix. Neither answer is wrong, but the answer must be explicit. “Content entry” on a 40-page site can be 20–30 hours of work.
QA and launch. Browser and device testing, form testing, 301 redirects from the old site, staging-to-production migration, and a launch-day plan. If the proposal treats launch as a single afternoon, ask what happens if a form does not send or the old URLs 404.
Training and handoff. A recorded session or written guide that shows your team how to edit the site. Two hours is typical; some projects need more. A site your team cannot maintain becomes a call to the developer for every small change.
What should a small-business WordPress site cost?
A professional small-business WordPress site — one with real discovery, custom design, and a bespoke theme — typically runs $8,000–$25,000 in 2026. Below $5,000 you are almost certainly getting a lightly customized template with limited discovery. Above $30,000 you should see enterprise-grade requirements in the scope: complex integrations, e-commerce with hundreds of SKUs, multilingual content, or a custom application layer. A ten-page brochure site quoted at $40,000 has padding somewhere; a boutique with a real catalog and POS sync quoted at $6,000 has cut something out.
For a concrete reference: a recent build for Two Baroque Girls, a Santa Fe luxury floral studio, included a custom theme, custom post types for portfolio and services, a WooCommerce storefront, a journal, a members area with login, and third-party integrations. The proposal reflected that scope in about a dozen line items — not one lump sum. If a similar site had come back at half the price, the missing work would have shown up during the project instead of on the proposal.
Red flags to watch for
- A single-line total with no breakdown. Every reputable proposal itemizes at least four to six components.
- No discovery line. The project will make design decisions in a vacuum and you will pay to redo them.
- No named integrations. “We’ll integrate your systems” without listing them is scope you cannot verify.
- Aggressive timelines without discovery. A 15-page custom site in three weeks is a template being repainted.
- Ownership left vague. You should own the domain, the hosting account, and the code. If a proposal implies otherwise, treat it as lock-in.
- Heavy jargon and thin answers. If you cannot understand the proposal, you cannot hold the team to it.
- A price far outside the others. A quote 60 percent below the rest is not a bargain — it is a different project.
How to compare two proposals side by side
Put them in a two-column table and line up the same rows: discovery, IA, design, development, integrations, content, QA, training. Where a section is missing from one, ask what that vendor plans to do about that work — not “did you forget it,” but “how are you covering this?” The answer tells you whether the omission was a mistake or a philosophy. Then compare the exclusions and assumptions. Two proposals with the same total often differ most in what one has quietly moved into the “not included” column.
Finally, read the payment schedule and cancellation terms. A 50-percent deposit is normal; 100-percent upfront is not. Milestone-based payments — design approval, staging site, launch — protect both sides more than a flat monthly billing that continues whether the work moves or not.
What a good proposal feels like to read
You should finish it knowing what you are getting, what the vendor is not doing, when you have to have your content ready, and what the site will cost if you add one more page or a new integration halfway through. If any of those answers are missing, ask for them in writing before you sign. The answers you get will tell you as much about the vendor as the original document did.
Patrick Iverson is a Santa Fe brand strategist and custom WordPress developer who has been writing proposals for New Mexico businesses since 2003. If you have quotes on your desk and want a second read before you sign, get in touch — comparing proposals is faster with someone who has written a few hundred of them.