Capabilities · Fixed-scope projects
A new website. A deliberate path for everything it replaces.
For institutions moving platforms or rethinking a site: plan the content, integrations, approvals, and launch together, with scope, milestones, and price agreed in writing.
URL map
5 URL- Inventory
- Agree what moves
- Redirects
- Preserve useful links
- Acceptance
- Verify before launch
Rebuilds are fixed-price projects, separate from the monthly operations retainer. New requirements are quoted for approval before work proceeds.
Engagement details
Choose the build your team can run.
Decisions before design
Platform and publishing
WordPress, Drupal, or a static build should follow your publishing needs. Agree templates, permissions, languages, and approval steps before choosing the implementation.
Content and integrations
List pages, documents, forms, member systems, and other dependencies. State what migrates, who supplies revised content, and which vendor access is needed.
Accessibility
Set the target standard and the representative journeys to test. Include keyboard, screen-reader, and automated checks in the acceptance plan.
Ownership and continuity
Keep organizational accounts under your control. Document the repository, hosting, deployment process, and handover so the next operator can use them.
A launch needs an acceptance plan.
- Agree
Inventory and written scope
Confirm page types, content volume, integrations, responsibilities, and milestones. The quote identifies assumptions and any separately scoped discovery work.
- Build
Review working journeys
Review templates and migrated content on staging. Track exceptions in the inventory and seek approval for changes to the scope.
- Verify
Check the launch criteria
Reconcile agreed content, test redirect mappings and key forms, perform accessibility checks, and record open issues for the authorized approver.
- Launch
Switch with a recovery plan
Agree the content freeze, launch window, backup and rollback procedure. Check key journeys after launch and hand over the records and access.
Decide what happens to every agreed page.
A migration starts with an inventory. Your content owners decide what stays, what changes, and what can be retired. Each decision gets a destination and a check.
The working inventory also records source and destination URLs, owner, decision date, and test evidence. Sample format; the actual inventory follows the agreed scope.
See Leland’s experience and rolesBring the site, the deadline, and what must survive the move.
We will identify what needs to be inventoried and agreed before a rebuild can receive a useful scope and fixed quote.