Faster publishing
Request a change in plain English, review it on staging, approve it and keep a complete revision history.
Website platform proposal · 23 August 2026
Rebuild the current website in clean custom code, simplify how the team publishes, and keep Wil involved after launch for support, improvement, SEO and AI visibility.
What BOI gains
The value is not a new visual layer alone. It is a simpler way for BOI to publish, translate, connect tools and keep improving the site without working around a growing plugin stack.
Request a change in plain English, review it on staging, approve it and keep a complete revision history.
Maintain one approved source, prepare market versions and keep language links, metadata and updates aligned.
Launch reports, landing pages, diagnostics, calculators and campaign experiences from one consistent component system.
Templates carry the technical SEO, expert attribution, source structure and machine readable context needed by search and AI answer systems.
Wil remains available after launch to resolve issues, guide priorities, ship improvements and connect new tools as BOI evolves.
Working prototype
The BOI homepage has been recreated as standalone custom code. It is a prototype, not the completed migration, but it demonstrates the visual reconstruction, responsive behavior and performance standard available to the full build.
Open the prototype in a new tab
Verified mobile Lighthouse 13.4.1 run, 19 August 2026. Largest Contentful Paint was 1.1 seconds.
| Measure | Public baseline | Prototype |
|---|---|---|
| Performance | 50 | 100 |
| Accessibility | 83 | 100 |
| Best practices | 54 | 100 |
| Technical SEO | 100 | 100 |
| Largest Contentful Paint | 13.3 seconds | 1.1 seconds |
The public baseline was measured on 18 August 2026. These are lab measurements, not guarantees of field performance. No BOI Search Console, Analytics or CRM data was available, so no traffic, ranking or lead claim is made.
How the team works
BOI can work through the custom CMS or an approved coding assistant such as Claude Code. Every meaningful change still follows the same controlled path.
Describe the page, translation, integration or change in normal language.
The platform assembles the content, components, metadata, links and language versions.
BOI checks a private preview, sees what changed and requests any correction.
An approved release is tested, deployed and recorded with rollback available.
Example request
“Turn the new AI operating model report into a landing page, prepare Dutch and French versions, and connect the relevant case studies.”
After launch
The monthly partnership is not only SEO and GEO. It gives BOI a direct technical and growth partner who knows the platform, can solve problems quickly and keeps turning evidence into useful improvements.
Direct access to Wil for questions, fixes, release help and urgent website issues.
Small enhancements, publishing refinements, translation setup and integration guidance.
A monthly evidence cycle covering technical health, content opportunities, AI visibility and one prioritized implementation sprint.
Monitoring, release history, dependency review and a clear recommendation for what BOI should improve next.
The working allocation is up to eight specialist hours each month. Larger features or new products are estimated and approved separately, with BOI receiving continuity and priority because the platform foundation is already in place.
Delivery plan
The rebuild runs in parallel. BOI’s current website remains available until staging has passed content, browser, accessibility, analytics and editor acceptance.
Confirm content, templates, integrations, data, languages, ownership and acceptance criteria.
Build the design system, homepage and core templates on private staging.
Complete the CMS, AI workflow, integrations, content migration, redirects and multilingual foundation.
Run BOI review, training, quality checks, rollback rehearsal and a controlled launch with no planned downtime.
Investment
Fixed launch investment, excluding VAT and third party provider fees.
Invoices are due within ten calendar days. Two consolidated BOI review rounds are included per phase. The 30 day defect warranty begins at launch.
Included foundation
Working assumptions: one primary domain, timely access, one BOI decision owner, consolidated feedback and approval within two business days.
Separate scope: secondary domains, complete editorial rewriting, more than three integrations, large translation batches, paid media and major new products.
Third parties: hosting, database, storage, monitoring, AI model, translation and integration usage remain BOI owned and billed separately.
Outcome boundaries: quality, accessibility and performance are testable. Rankings, leads, AI citations, uninterrupted service and permanent security cannot be guaranteed.