Three proposals sit on your desk. They come in at $14,000, $38,000, and $71,000. All three promise a mobile-friendly redesign, all three include a homepage mockup you like, and not one of them explains why the top bid costs five times the bottom one.
That is where a school web design agency comparison usually falls apart. The committee stops evaluating and starts arguing about taste, and taste has no scoring column. Most independent schools then pick the proposal that felt best in the room, which is another way of saying they picked the best presenter.
The money makes that a real problem. NAIS and Metric Marketing reported in the 2024-2025 State of Independent School Marketing survey that "Fifty-four percent of all schools have annual marketing budgets of more than $70,000, while an additional 28% have budgets over $120,000." A website rebuild eats a visible share of that. Your board will ask how you chose.
This post gives you the scoring framework, the RFP questions, the answers that should worry you, realistic cost bands, and the ownership terms to demand. Families already run a predictable sequence before they ever reach your inquiry form. The firm you hire decides whether your site survives it.
What Should a School Web Design Agency Comparison Measure?
A school web design agency comparison should measure five things on a fixed scale: technical approach, relevant school experience, total cost of ownership, timeline, and post-launch support. Agree on the weights before any proposal arrives. A committee that scores against a rubric it wrote first will not reverse-engineer a case for the firm it already liked.
Shane Larrabee, with FatLab Web Support, noted that buyers should "Set and share evaluation criteria before you receive proposals," using weights like "30% technical approach, 25% relevant experience, 20% cost, 15% timeline, 10% ongoing support." The reason is blunt: fixed weights prevent "post hoc rationalization, where the committee reverse-engineers a justification for whoever they already liked."
Write a definition for each score level, not just each category. A rubric that says what a 3 looks like versus a 5 gets two evaluators closer to the same number, which is the whole point of scoring at all.
Then adjust the weights for your school rather than copying them. A school with one marketing coordinator should weight ongoing support well above 10%, because nobody on staff will be patching the site in March. A school with an in-house developer can push that weight into technical approach instead.
What Questions Belong in a School Website RFP?
A school website RFP should ask who owns the code, the templates, and the content when the contract ends; what documentation and training come with handover; how accessibility gets tested; and which named people do the work. Design questions sort themselves out in a portfolio review. These do not.
Put these in writing and require written answers:
- Who owns the custom code, templates, configurations, and design files when we part ways?
- Can the finished site move to another host without a rebuild, and will we have full administrative access?
- What documentation do we receive at handover, and who on our staff gets trained?
- How is accessibility tested, by whom, and is it priced as its own line item?
- What integrates with our student information system and our inquiry follow-up, and who owns that data?
- Which named team members do the work, and are they the people in this pitch?
- Can we speak with two school clients who launched more than 18 months ago?
The Answers That Should Worry You
Vague answers from a web design firm to specific ownership and handover questions are the finding, not a communication problem. Socialectric's report documents that the warning signs are: "no clear process for post-launch handover and training, reluctance to specify what documentation they will provide, proposals that respond primarily to aesthetic requirements while ignoring governance requirements, inability to provide references from nonprofit clients more than 18 months post-launch, pricing that excludes testing, documentation, and training as separate line items, and lack of familiarity with WCAG compliance testing processes."
Read that list again as a school. Every item describes a firm that plans to be finished at launch. Your website is not finished at launch. It has to hold five admissions cycles.
How Do You Compare School Web Design Proposals on Price?
Compare proposals on scope, not on totals. Ask every finalist to price the same line items separately: build, content migration, accessibility testing, documentation, training, and the first year of hosting and maintenance. A small school site runs $8,000 to $25,000. Add a parent portal and integrations and the range climbs past $30,000.
Qrolic Technologies data indicates that a small school or preschool site costs $8,000 to $25,000 to build, plus $150 to $400 a month to maintain, while a mid-sized build with multi-department structure, parent portals, and student-information-system integration runs $30,000 to $85,000, plus $500 to $1,500 a month. Those are vendor market estimates rather than survey data, so treat them as the outer walls of a reasonable conversation.
The low bid deserves the hardest questions. Leo Carnes, with ArcStone, concluded, "A proposal priced 40 percent below the field either reflects a misunderstood scope or a business model built on change orders." Ask the cheapest firm what is not included, in writing, before anyone gets excited.
Accessibility is the line item most proposals bury. Evidence from Accessibility. Works points to $8,000 to $15,000 for a full audit of a small marketing or informational site, or roughly $5,000 to $10,000 for a focused key-page audit, and an added "10%-20% on top of typical web design costs for an accessible site" when it is designed in from the start. Retrofitting later costs more than building it right. Private schools are public accommodations under ADA Title III, where expectations come from case law and settlements rather than a published compliance deadline, so this is risk management, not a date on a calendar.
What Should the Ownership and Exit Terms Say?
Your contract should state that the school owns the content, the custom code, the templates, the configurations, and the design files, and that the site can move to another host without a rebuild. An export of your text is not ownership. Ask for full administrative access in writing before you sign anything.
Ask the Egghead stated the standard for public buyers in one sentence, and it transfers cleanly to schools: "The government owns its content and all custom code, themes, templates, configurations, and other work created under the contract." The same guidance draws the distinction that matters at renewal time: you should own a working website, not merely an export of its content.
Lock-in rarely announces itself. Many proprietary platforms will happily export your pages, documents, and images. What stays behind is the site itself, including templates, navigation, custom functionality, and the CMS. Three years later, leaving means rebuilding.
Why the CMS Choice Sets Your Maintenance Bill
The platform under your site decides how much patching your staff inherits. Ask which CMS a firm builds on, whether it is proprietary, and who applies security updates. Then ask what that costs in year three, not year one.
WordPress holds the largest market share, and it earns a plain-spoken assessment. Patchstack research demonstrates that "Overall 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025," which is "a 42% increase compared to 2024." The concentration matters more than the count: "91% of new vulnerabilities were found in plugins," and "46% of vulnerabilities were not fixed in time for public disclosure." The core software is not the exposure. The plugin stack you assemble to make it do what a school needs is the exposure, and each plugin is a separate maintenance dependency.
We build on Joomla for school sites because features WordPress reaches through third-party plugins ship with the platform, which leaves a smaller surface to patch. The historical knock on Joomla was manual updates, and the project closed that gap. David Jardin, writing in Joomla Community Magazine, reported that "With the release of Joomla 5.4 and Joomla 6.0 on 14 October 2025, the Joomla project introduces a significant innovation: automatic updates for the core system." His reason for building it should focus any school's attention: for easily exploited security issues, "we are talking about a time window of 10-12 hours." Joomla is also open source, so there is no license fee and nothing proprietary holding your site hostage at renewal.
How Does Cube Creative Design Answer These Criteria?
Cube Creative Design has built websites since 2005 and works on an open platform rather than a proprietary one. Everything we build for a school is that school's property. Pricing is published instead of quoted case by case, and a new school website takes about eight weeks from kickoff.
Here are our answers to the questions above, so you can score us on the same rubric you score everyone else on.
Ownership: everything we build for you is your property. Platform: Joomla, open source, no license fee, no proprietary CMS to leave behind. Hosting: managed, with 99.9% uptime. Timeline: about eight weeks for a new site, one week for CRM integration.
Cost: our school plans are published on our site at $1,500 a month for schools of roughly 100 to 300 students, $2,400 a month for 300 to 600 students, and $4,000 a month for 600 or more students or multiple programs. Each plan bundles the website with hosting, maintenance, SEO, a 12-month content plan, social posting, Google Business Profile management, a HubSpot CRM, and monthly reporting. That is a different shape from a one-time build fee, and you should compare the shapes before you compare the numbers.
What we do not do is bid a rock-bottom build fee and recover it through change orders. Ask us for the line items. Ask everyone for the line items.
What This Looks Like at a 260-Student College Prep
A principal at a 260-student independent college prep, tuition in the high teens to mid-$20,000s, running a $30,000 to $75,000 marketing budget with a small team wearing several hats, has a board of trustees that will want a defensible recommendation in late spring. Before the RFP goes out, this school runs a website conversion audit to find out which pages are already losing families, so the new site fixes real problems instead of guessing at them.
Winter is when the work happens. The scorecard gets built in January, before proposals arrive, and the weights get adjusted for a school with no in-house developer: ongoing support moves to 25%, technical approach drops to 25%, relevant school experience holds at 20%, cost sits at 20%, and timeline takes the remaining 10%.
Three firms respond. The cheapest bid comes in 40% under the other two, and the line-item request reveals why: no content migration, no accessibility testing, no training. It scores 2 out of 5 on ongoing support and drops out on the math, not on a hunch.
The reference calls decide the rest. Two schools that launched two years ago get the same four questions: How did the firm handle problems? Did the people in the pitch do the work? Was it on time and on budget? Would you hire them again? One firm's references hesitate on the second question.
What the board sees in May is a scored matrix, a written ownership clause, and a cost per year over the site's five-year life. What it does not see is a debate about the homepage photo. That is the whole difference.
Conclusion: Score the Process, Not the Pitch Deck
The best-looking proposal and the best proposal are different documents, and only one of them still works in year three. Build the scorecard first. Weight ongoing support for the staff you actually have. Ask who owns the code, the templates, and the configurations, and get the answer in writing.
Then do the two things committees skip because they feel awkward: request line-item pricing from every finalist, and call references from schools that launched more than 18 months ago. Those two steps cost you a week and catch nearly everything a portfolio review misses.
If you have proposals in front of you and want an outside read on what they are actually promising, send me a message. I will tell you if the low bid is a bargain or a bill you have not seen yet.
Frequently Asked Questions
How Long Does a School Website RFP Process Take?
Plan on three to four months from writing the RFP to signing a contract. Allow two weeks to build the scorecard and draft the RFP, three to four weeks for firms to respond, two weeks for scoring and finalist interviews, and two weeks for reference calls and contract review. Schools that start this during winter budget planning have a recommendation ready for a spring board vote and a summer build window that misses the admissions rush.
Who Should Sit on the Website Selection Committee?
Keep it to four or five people: the head of school or principal, whoever owns admissions and marketing, one person who will maintain the site day to day, and a board member with budget oversight. The staff member who updates content after launch is the one most often left out and most affected by the choice.
What Should a School Ask an Agency's References?
Ask how the firm handled problems, whether the team in the pitch did the actual work, whether the project came in on time and on budget, and whether they would hire the firm again. Then ask what the relationship looks like now. That is why the reference has to come from a launch more than 18 months old. A school that went live last month cannot answer it.
Is the Lowest Bid Ever the Right Choice for a School Website?
Sometimes, but only after you know why it is the lowest. A bid 40% under the field usually signals a misread scope or a plan to bill the gap back through change orders. Ask for the same line items from every finalist. If the cheap proposal still holds up with content migration, accessibility testing, documentation, and training priced in, it is a real number.
What Accessibility Work Should Appear in a Web Design Proposal?
Look for testing named as its own line item, a stated standard such as WCAG 2.1 Level AA, and the name of whoever does the testing. Private schools sit under ADA Title III as public accommodations, where expectations come from case law rather than a fixed federal deadline, so accessibility is a risk decision your board should make on purpose rather than inherit.
