Company Logo

Upvista Digital

Solutions

AON Corporate Website Case Study

AON is a Japanese agency specializing in Webflow website development, SEO optimization, and AI automation using n8n and Zapier. They required a corporate website that reflected a reliable, precise, and scalable brand presence. From the client perspective, the website was to be implemented in Webflow for speed, maintainability, and CMS-driven content operations.

Live site: a-o-n.net

Objectives

  • Deliver a corporate website with clear structure, authoritative tone, and frictionless navigation.
  • Implement Webflow CMS for non-technical content management.
  • Establish SEO fundamentals: information architecture, technical hygiene, and performance.
  • Integrate marketing and operations automation via n8n and Zapier.
  • Provide a maintainable system with straightforward governance and release cadence.

Approach and Platform

The site was delivered in Webflow using a component-driven methodology. We defined a reusable design system (typography, spacing, grids, and modular sections), then instantiated these components across pages. Webflow CMS collections were used for case studies, blog posts, services, and team profiles. Where required, custom code blocks extended Webflow interactions for controlled behavior while preserving editorial flexibility.

Team and Collaboration

The internal delivery team operated as a compact cross-functional unit:

  • Engagement Lead: scope, timeline, governance, and stakeholder alignment.
  • UX Designer: information architecture, wireframes, content hierarchy.
  • UI Designer: design system, component library, responsive specifications.
  • Webflow Developer: template engineering, CMS modeling, interactions.
  • Automation Engineer: n8n and Zapier workflows, lead routing, notifications.
  • SEO Specialist: technical SEO, schema, content formatting, search console setup.
  • QA Engineer: accessibility, responsiveness, and regression testing.

Process and Sprints

The delivery was structured into time-boxed sprints with clear stage gates and review rituals. Each sprint ended with a working increment, a stakeholder review, and an integrated QA pass.

Sprint 0: Discovery and Foundations (1 week)

  • Stakeholder interviews and requirements consolidation.
  • Competitive scan and content inventory.
  • Information architecture, sitemap, and URL strategy.
  • Definition of success metrics and analytics plan.

Sprint 1: IA, Wireframes, and CMS Model (2 weeks)

  • Low-fidelity wireframes for all primary templates.
  • Webflow CMS collections designed for posts, case studies, services, and team.
  • Content types, fields, relationships, and slugs defined for SEO.

Sprint 2: Design System and Templates (2 weeks)

  • Typography scale, spacing units, grid, and components documented.
  • Page templates implemented in Webflow with reusable sections.
  • Accessibility checks on color contrast, semantics, and focus states.

Sprint 3: Build, Interactions, and Content (2 weeks)

  • Template population through CMS collections and content migration.
  • Controlled interactions using Webflow interactions and custom code blocks where necessary.
  • Localization readiness and content formatting for search.

Sprint 4: SEO, Automation, and QA (1–2 weeks)

  • Technical SEO: metadata, schema.org, canonical tags, and sitemap submission.
  • Performance tuning: image strategy, lazy loading, and asset hygiene.
  • n8n and Zapier: lead capture routing, notifications, and CRM handoffs.
  • Comprehensive QA: functional, responsive, and regression testing.

Launch and Handover

  • Staging review, content freeze, and production cutover.
  • Analytics, goals, and Search Console verification.
  • Editorial training on CMS workflows and governance checklist.

Technical Details

  • Platform: Webflow with CMS collections for structured content.
  • Design: Component library with documented usage and responsive breakpoints.
  • Automation: n8n and Zapier workflows for lead routing, notifications, and enrichment.
  • Analytics: GA4 events, Search Console integration, and UTM tracking standards.
  • SEO: XML sitemap, robots directives, schema, canonical and hreflang readiness.
  • Performance: media optimization, caching strategy, and controlled third-party scripts.

Outcomes

  • Clean, authoritative corporate presence aligned with AON’s positioning.
  • Editorial independence through CMS with consistent component usage.
  • Improved crawlability, metadata hygiene, and baseline search performance.
  • Streamlined lead handling through automation, reducing manual follow-ups.
  • Operational clarity through governance, release cadence, and training.

Visit

The corporate website is available at a-o-n.net.