EstimateForge

Sample estimate: City of Hidden Hills, California website RFP

This is the unedited output EstimateForge produced on 2026-10-28 from a public request for proposals, “Website Redesign and Development Services (Request for Proposals)” (PDF, 7 pages). Upload your own RFP and you get the same structure: 26 tasks and 8 risks here, 601–1,244 hours in total.

Overview

The City of Hidden Hills seeks a vendor to redesign, develop, host, and maintain its municipal website (up to 50 pages) on a CMS (preferably WordPress), with standard municipal features, WCAG 2.1 AA accessibility, and future integration capability for an AI Digital Library Initiative. Scope includes training, 30-day post-launch bug fixing, and ongoing hosting/maintenance billed separately.

Total: 601–1,244 hours · $105,175–$217,700 at $175/hr blended.

Hour ranges are industry-typical estimates, not calibrated to your agency's historical actuals. Adjust to your reality.

Risk register

Each risk lists the tasks it affects. Those tasks carry padding for the risk type; tasks with no risk carry none.

  1. R1Vague scope+25% padding

    Digital library integration is described only as 'where applicable' with no platform, data, or API specified, making T19 unscopeable until the 2026 initiative is defined.

    Affects T19. Scope only a generic placeholder/landing page now; require a separate change order once the digital library platform is selected.

  2. R2Third-party API+30% padding

    E-newsletter integration names MailChimp 'or equivalent' without confirming the actual provider or existing account, risking rework if provider differs from assumptions.

    Affects T16. Confirm exact ESP and API credentials/account ownership during discovery before integration work begins.

  3. R3Vague scope+25% padding

    'Up to 50 pages' and feature list give no detail on page complexity, custom layouts, or data-heavy pages (agendas/documents), so page build effort is highly variable.

    Affects T5, T8, T17, T18. Request a detailed content inventory and page-type breakdown from the City during discovery to firm up per-page effort.

  4. R4Data migration+25% padding

    Content migration scope and condition of existing static site content (volume, format, structure) is not described, risking underestimated migration effort.

    Affects T9. Audit existing site content volume and formats before finalizing fixed-price migration estimate.

  5. R5Security review required+15% padding

    WCAG 2.1 AA compliance is required but no baseline audit of current site or acceptance testing method (automated vs manual/AT) is defined.

    Affects T20. Clarify accessibility testing/certification method and remediation responsibility with the City before fixed-price commitment.

  6. R6Vague scope+25% padding

    Fixed-price fee is required for 'complete' scope despite several undefined elements (library integration, exact page count, content volume), creating margin risk for a fixed bid.

    Affects T5, T8, T9, T19. Define a clear change-order process and itemize assumptions explicitly in the proposal to protect against scope creep on a fixed fee.

  7. R7Third-party dependency+20% padding

    CMS is only 'preferably WordPress,' leaving platform choice open; different CMS choices materially change backend/build hours and training content.

    Affects T6, T7, T24. Confirm CMS platform decision with City early in discovery phase before committing to build approach and hours.

  8. R8Unknown scale / load+20% padding

    No traffic, concurrency, or performance expectations are specified for hosting, risking under- or over-provisioning of infrastructure for a small 1,700-resident city site.

    Affects T25. Confirm expected traffic levels and any peak-load scenarios (e.g., emergency bulletins) to right-size hosting plan.

Task breakdown

TaskTitleCategoryRisksHours
T1Kick-off & discoveryKick-off meeting, requirements confirmation, content strategy sessionpm-overhead—8–16
T2Sitemap & information architectureDevelop sitemap and site architecture for approvalfrontend—8–16
T3Wireframes for key page typesWireframes for all key page layouts prior to designfrontend—16–30
T4Homepage design compsTwo homepage comps with one revision round eachfrontend—16–30
T5Secondary page template designDesign templates for secondary content page types with revisionsfrontendR3, R638–78
T6CMS setup (WordPress)Install/configure CMS platform, roles, permissions, base themebackendR724–48
T7Theme/front-end buildBuild responsive front-end templates from approved designsfrontendR772–144
T8Page build-out (up to 50 pages)Implement up to 50 content pages in CMS with one revision roundfrontendR3, R678–188
T9Content migrationTransfer/migrate existing static content per approved sitemapbackendR4, R638–94
T10SSL certificate setupProcure, install, configure SSL certificateinfra—2–6
T11Site search featureImplement site-wide search functionalitybackend—8–20
T12Image/photo gallery with video embedBuild gallery module supporting images and embedded videofrontend—12–24
T13Homepage slider/banner & bulletinBuild featured content slider and urgent news bulletin modulefrontend—10–20
T14News/events feed & community calendarBuild news feed and calendar modules with admin managementbackend—20–40
T15Contact formBuild and configure contact form with spam protectionfrontend—4–10
T16E-newsletter signup integrationIntegrate signup form with third-party ESP (e.g., MailChimp)integrationR28–21
T17Agendas/minutes portal & directoryBuild Council agendas/minutes portal and staff/council directory pagebackendR320–45
T18Document organizer moduleBuild document library/organizer for City documentsbackendR313–30
T19Digital library integration placeholderBuild landing page/widget placeholder for future digital library integrationintegrationR1, R613–38
T20Accessibility (WCAG 2.1 AA) implementation & auditBuild and audit site to meet WCAG 2.1 AA complianceqaR523–58
T21Pre-live environment & review cyclesStand up staging environment; two rounds of changes per pageqa—20–50
T22Cross-browser/device QA testingResponsive and functional QA across browsers/devicesqa—16–36
T23Launch & 30-day warranty supportLaunch site and provide 30-day post-launch bug fixingqa—10–30
T24Staff training & documentationConduct 3-hour CMS training; produce written user guidesqaR710–19
T25Hosting setup & backup configurationConfigure hosting environment and quarterly backup scheduleinfraR810–24
PMProject management overheadPM, client communication, sprint ceremonies, status reporting.pm-overhead—107–131

Requirements read from the RFP