Rebuilds and projects
Rebuild without losing what works.
Every page, document, form, and link accounted for. One fixed price, approved before work begins.
Sample URL map for a fictional site. You receive yours at migration.
From scope to launch.
Four steps, each ending with something you can check.
- Step 1 Inventory Every page, document, and form gets an owner and a decision: keep, rewrite, merge, or retire. The inventory
- Step 2 Design and build Your design system, built as a custom theme: shared components and color and type tokens, tested against the accessibility standard you chose on a staging site. A working staging site and the design system's documentation
- Step 3 Migration Content moves, old links redirect, and each item is checked against your acceptance list. The URL map
- Step 4 Launch Edits freeze, the site switches over, and key pages and forms are checked right after. The launch record
Decided before design starts.
Four questions settled in writing, so the build has no surprises.
-
Platform and publishing
Which system the site runs on, who edits each section, and who approves a page.
-
Content and integrations
What moves as it is, what gets rewritten, and which systems the site connects to.
-
Accessibility standard
The standard the new site is tested against, such as WCAG 2.1 AA, and who signs off.
-
Accounts and access
Who holds the hosting, domain, and administrator accounts, in your organization’s name.
New features
New features and applications.
Added to the site you have, or built beside it. No rebuild or retainer needed first.
- Portals and directories Sign-in areas for members or residents, and searchable directories fed from the system you already use.
- Charts and maps from your data Public dashboards and maps built from your own spreadsheets and databases, with a text version for screen readers.
- Intake and application forms Membership applications, permit requests, and inquiries that reach the right person, with a record of each.
- Events, registration, and booking Calendars, registration, and booking on standard tools such as The Events Calendar, set up for your staff to run.
AI is optional. When a feature uses it, the written scope states its running cost before you approve anything. The Client Portal, the booking page, and the free audit on LFW.com are applications we built and run ourselves.
Try the Client PortalQuestions.
What does a rebuild cost?
It depends on how many pages, documents, and integrations move, and how much content is rewritten. After reviewing your site, we quote one fixed price. If the scope changes, the change is quoted for your approval first. We do not bill hourly.
Do you respond to RFPs?
Yes. Send the RFP or a link to it. We read the whole package, send questions during its question period, and respond the way it asks.
Who owns the work and the accounts?
Your hosting account and code repository are in your organization’s name from the first day. The work we build for you is yours once it is paid for. Open-source parts such as WordPress keep their own licenses.
Can you move us off a hosted platform or site builder?
Yes. If your site runs on a vendor’s proprietary system or a site builder, we plan the move to WordPress and redirect your old links so they keep working.
When does the launch happen?
On a weekday you approve, during business hours, so your staff and ours are both at work if anything needs attention.
Can you maintain the site after launch?
Yes. After launch, the site can move to the Web Operations Retainer: one monthly fee for updates, small changes, and daily checks.
What the retainer coversDo you build on Drupal?
We take on Drupal work. Leland’s own record is on WordPress.
Send the site you need to replace.
A website address, an RFP, or the feature you need. We reply within one business day.
See everything we can do