Your New Library Website: What to Expect at Every Step

About 8 weeks start to launch, depending on how quickly feedback and approvals come back from your team. The fastest way to keep your project on schedule is to return homework and feedback within the timeframes listed above.

Our project timeline includes set windows for review, feedback, and approvals. Staying within those windows helps keep the project on schedule, within scope, and on budget. If your team has known scheduling conflicts, board meetings, vacations, or other timing considerations that could interrupt this timeline, let us know! Our team is happy to plan or postpone your kick-off date around your team's needs. Once the project begins, we’ll follow the timeline tied to your selected service level to avoid delays or overages. If more time is critical for your time, we can always discuss an addendum for a project extension.

Less than you'd think. Across the whole project, plan for: the initial questionnaire and homework, a Loom design review, one training meeting (1–1.5 hours), a few days of design feedback, and a review window where you explore the preview site at your own pace. Everything else is on us.

Depends on your budget. However our team will outline the process for you and help you decide if you want to do it yourself or hire us to do it. Content migration is included in the build phase (Step 5) - up to a certain amount of content.

You can request a quote for content migration at any time before launch - we recommend doing this after training so you can see the site and understand the process (including how easy it is to update content).

No. The CMS is designed so anyone on your staff can update content, and we train your whole team before launch (Step 6).

At the Big Design Reveal (Step 2), about 1–2 weeks into the project. You'll receive a Loom video with the full design and sitemap — not rough sketches — so you can react to something that looks and feels like the real thing.

The design approval (Step 4) is what allows our developers to begin building, so significant design changes after that point can affect the timeline. That's why we build in a dedicated feedback window (Step 3) — take the time you need there.

Almost certainly not! During the build (Step 5, typically 4–6 weeks), our developers are heads-down and no action is needed from you. We'll reach out when it's time for your sneak peek and training.

During training we'll show you a simple page-by-page way to submit requests. Using it (rather than email) keeps every piece of feedback tracked and ensures nothing slips through the cracks.

Note: This is only applicable if you have a scoped revision period (add-on).

Yes — the site is fully responsive and mobile-friendly, and our QA team tests it on all devices and browsers before launch (Step 9).

Yes. We verify the site meets ADA and WCAG accessibility standards as part of our quality assurance process.

You do, together with your account manager, during the launch countdown (Step 10). Launch itself usually takes just 1–2 hours.

Your old site stays live throughout the project — your patrons won't notice a thing until the new site launches in its place.

You get 1–2 weeks of dedicated post-launch support while your team settles in. After that, ask us about our month-to-month ongoing support program for maintenance and upgrades.

Yes — we offer optional community surveys, heat mapping, and wireframe testing early in the project (Phases 1–2). Just mention it when you return your questionnaire, or earlier.

As part of Phase 1, we'll ask you to work with your current hosting provider or IT team to create a complete backup (ZIP archive) of your existing website (for you to keep for your own records). This ensures you have a copy of the site before any work begins.

Before launch, we'll confirm that this backup has been completed. If you're unable to obtain one yourself, our team can typically create a backup for you, provided we have the necessary access to your website and hosting environment.