PlanGrid | Autodesk Forma website analysis
A detailed critique of the homepage's craft, originality, usability, and ability to move visitors toward its intended goal.
Our observations
A strong and commercially useful support-transition page with clear actions and polished enterprise presentation, held back by a crowded information architecture and several correctable accessibility defects.
Best practices
The page has one H1, coherent heading progression, semantic navigation and footer regions, clear button/link treatments, and no reported contrast failures. The audit still identifies serious naming and image-alt issues, along with widespread duplicate IDs.
What works
- Single H1 and no detected heading skips.
- Clear primary actions for login, support, and product adoption.
- Strong contrast sampling result with zero reported contrast failures.
- Semantic navigation, main content, and footer landmarks are present.
Opportunities
- Add meaningful alternative text to the identified image.
- Provide an accessible name for the logo link.
- Resolve the 42 duplicate-ID findings, including repeated navigation and SVG IDs.
- Verify keyboard focus visibility and accordion semantics in an interactive audit.
Design
A cohesive enterprise design with strong hierarchy, disciplined contrast, and credible construction imagery. The visual language is effective but familiar, and the long FAQ section limits rhythm and distinctiveness.
What works
- The hero immediately establishes PlanGrid context and presents two relevant actions.
- The black, white, and iris palette aligns the page with Autodesk Forma branding.
- The Forma Build section balances explanatory copy, checklist content, CTA, and product imagery.
- FAQ borders and spacing make a large amount of support content scannable.
Opportunities
- Reduce visual repetition in the FAQ area through stronger grouping or progressive disclosure.
- Clarify the distinction between PlanGrid support content and Forma Build acquisition content.
- Use a more distinctive visual device or customer proof point to make the page less template-like.
Uniqueness
The migration-and-support purpose gives the page a specific use case, and the construction imagery is relevant. However, the overall pattern—hero, product upsell, FAQ, black enterprise footer—is common among large B2B software sites.
What works
- The PlanGrid-to-Forma transition is a meaningful and specific content context.
- Product imagery connects the software proposition to real construction work.
- The page combines operational support with a carefully placed migration path.
Opportunities
- Make the transition narrative more explicit and easier to understand at a glance.
- Add distinctive evidence such as adoption outcomes, user roles, or a concise migration timeline if available.
- Differentiate the FAQ experience from standard enterprise accordion patterns.
User experience
The page supports the most likely existing-user tasks quickly, especially login and support. The broad navigation and competing product-promotion path may introduce uncertainty for visitors who only need account access or troubleshooting.
What works
- Login and support actions are visible in the hero rather than buried in the page.
- Mobile access is surfaced alongside the primary PlanGrid message.
- FAQ topics cover practical account, platform, pricing, support, and product questions.
- The content order moves from immediate actions to transition information and then self-service answers.
Opportunities
- Label the page more explicitly as a PlanGrid access and support destination.
- Keep the most urgent support paths persistently available without requiring navigation through a long page.
- Test the FAQ on small screens and with keyboard navigation; responsive and interaction behavior was not directly observed.
- Consider separating existing-user support from prospective Forma Build content more clearly.
Conversion optimization
For a transition/support page, conversion is appropriately defined as successful login, support contact, app access, or movement toward Forma Build. The page offers all four routes, though the number of competing actions weakens prioritization.
What works
- The hero includes direct login and support CTAs with clear action labels.
- The Forma Build section provides a concrete free-trial action after explaining product expansion.
- App-store routes serve mobile users without distracting from the primary hero actions.
- The footer repeats login and support routes for visitors who reach the end of the page.
Opportunities
- Choose one clearly primary hero action for returning users and visually subordinate the secondary route.
- Explain the relationship between PlanGrid and Forma Build immediately before the free-trial CTA.
- Add reassurance near login and support actions, such as destination expectations or account-state guidance, if accurate.
- Measure whether visitors engage more with FAQ answers, support, or the Forma Build trial and adjust prominence accordingly.
What we'd improve
- 01high
Repair the identified accessibility defects
Add accurate alternative text to the missing image, give the logo link an accessible name, and eliminate duplicate IDs across navigation and SVG elements. Re-run keyboard, screen-reader, and focus-state checks afterward.
- 02high
Clarify the page’s primary task
Make the hero explicitly distinguish returning PlanGrid users from visitors evaluating Forma Build, and assign a clearer visual priority to login versus support versus trial conversion.
- 03medium
Reduce FAQ fatigue
Group questions by access, platform availability, product status, and support, or use progressive disclosure so the 11-item list feels less repetitive while retaining self-service coverage.
- 04medium
Strengthen the transition narrative
Explain the PlanGrid-to-Forma relationship in one concise, prominent statement before introducing Forma Build, avoiding any implication that existing users must immediately migrate.
- 05low
Validate responsive and interactive states
Review the sticky navigation, wrapped CTA groups, accordion controls, and footer columns at narrow widths, with keyboard focus and reduced-motion settings enabled.
