ChargePoint website rebuild: discovery pack

Prepared: 25 September 2026 (V3: adds the transit side project, the hero video workstream, the "Product Pages We Like" reference set and the Figma review workflow. V2 24 Sep: team roles, WordPress and deadline provenance clarified) Prepared by: Strategy and content, for the Uprisal x ChargePoint website rebuild Working deadline: site live 30 November 2026 (roughly 9.5 weeks out; communicated verbally by Sonali) Platform: WordPress (confirmed within the team; not yet written down anywhere)

What this pack is

Every file received so far has been read: 5 strategy and messaging documents, 38 brand identity PDFs, 5 email threads, 2 migration workbooks, 3 CMS/nav CSVs, 2 HTML prototypes, 3 reference images, 3 transit side-project briefs, and the notes from the 25 Sep hero video concept meeting, plus the earlier document evaluation (21 Sep) and full website audit (21 Sep) already in this folder. This pack consolidates all of it into what the content and design team needs before execution starts.

The files in this pack

The headline finding

The raw material is unusually good. The client has supplied a page-level equity analysis of all 5,637 indexed pages, a 5,565-row redirect map, an approved homepage direction, a draft master nav, and a messaging playbook with approved headline hierarchies per segment. The measurement architecture is genuinely well thought through. Most rebuilds start with far less.

What's missing is the connective tissue. Three different navigation models are in circulation and none has been declared the winner. Three different top-line brand messages coexist without a ratified hierarchy. The brand refresh is still mid-review: the client deck and the V01 guidelines name two different typefaces. The proof-point numbers contradict each other across nearly every document, sometimes inside the same one. And nothing is written down about the schedule: the 30 November date and the WordPress decision both exist only as verbal understandings, and no document records phasing, ownership, or the migration plan from Drupal to WordPress.

None of this is fatal. All of it is fixable in one or two working sessions, if the right people are in the room. But with a 30 November go-live, every week these stay open is a week of build and content work that risks being redone.

What changed on 25 September (V3)

Three things landed after the V2 pack:

1. A transit side project. Michelle (client side) has requested, routed through Nikhil, an APTA-oriented "Transit 101" package: an 11-slide sales deck, a 60-second no-voiceover animated video, and a master storyline, all built on a ChargePoint + Eaton "Beyond the Charger" system story. It is sales collateral adjacent to the website, not part of it, but it is the deepest transit messaging we now hold, and it arrives with its own claims-approval list. Michelle's original request text and the deadline were not in the forward. Detail in file 01, section 7.
2. The hero video workstream is live. Vilasini and Noella developed homepage hero video concepts and reviewed them internally on 25 Sep. Direction agreed: roughly 70% B2B and fleet imagery, keep the charging-light and looping treatments, replace the home-centric ending with a depot, logistics or retail setting, and tie the film back to the intelligent-electrification differentiators (geographic reach, plug-and-play simplicity, operational value). Open question for Sonali: does the homepage video carry supers, or run behind a separate headline and CTA, the Tesla pattern? Revised concepts were presented to the client the same evening by Vilasini.
3. The home product pages got their reference set and review workflow. Sonali's "Product Pages We Like" email (22 Sep, forwarded to us 25 Sep) names eviqo's product-page architecture (How to Install, Reviews, FAQs in the page nav) and Tesla's charger landing page as the models, and asks that Rebecca, Xiaoshan and Sonali get Figma comment access once wireframes exist.

Who's who

ChargePoint (client)

• Sonali Sen — primary contact; sends all direction (page decisions, nav, product-page briefs)
• Rebecca Paruch, Xiaoshan Gao — feedback on the home product pages
• Prem — marked which of the "remove" pages to retain (surname and role unconfirmed)
• Jyothi — feedback already folded into Sonali's product-page mockups (role unconfirmed)
• Michelle — owner of the "Charge Where Life Happens" messaging playbook; now also the requester behind the APTA transit side project (25 Sep) and the client contact for October event coordination
• Rick Wilmer (President and CEO) and Bruce Chizen (Board Chair) appear in brand mockups

Uprisal (agency) Engaged for the website redesign and build, plus video assets — now concrete: the homepage hero video and the transit side-project deck and video.

• Nikhil Kumar — agency lead
• Vismaya MN — day-to-day PM, sent the briefing pack
• Rukmini Chatterjee — on every thread; away 2 Oct and 5–8 Oct, with cover for that window (including Michelle's event coordination) still being clarified
• Alyssa Kurian — on every thread, role not stated; flagged 25 Sep as possible design input for the hero video concepts

Vilasini's team (external contractors, onboarded to Uprisal for this project)

• Vilasini Muralidhar — leads the external team; with Noella, owns strategic comms, content and writing for the website; developed a hero video concept and presents the concepts to the client
• Noella Cresence — strategic comms, content and writing, with Vilasini; developed two hero video concepts
• Sushanth Swaminathan — leads the redesign

AFTERNOW (external brand and design agency)

• Mateo Strmotic — authored the brand refresh, and was briefed directly by Sonali for the home product pages UI/UX. This is a parallel design track the client runs herself; Uprisal receives it as forwards.

The internal split is now clear, but a written roles-and-ownership note still doesn't exist for the wider project. Rukmini and Alyssa sit on every thread with no stated function, and design authority is split three ways: Sushanth leads the redesign, Uprisal holds staged retail and investor pages and the approved homepage sections, and AFTERNOW owns the brand system and the home product pages. The boundary between Sushanth's redesign mandate and Mateo's product-page track is the sharpest edge to settle.

The timeline problem, stated plainly

The 30 November go-live was communicated verbally by Sonali and appears in none of the written material. The platform is WordPress, also unwritten. So the two most important project facts exist only as verbal understandings, and there is still no schedule, no phasing plan, no content-freeze date, and no QA window for migrating 2,206 pages from Drupal to WordPress across 9 locales. Client decisions have been arriving by email daily (21 to 25 Sep), which is good energy but not a plan, and the 25 Sep internal call flagged further client deadlines expected the following week. Meanwhile a side project (the transit package) has landed on the same team with no stated deadline of its own. Getting a written plan of record agreed, with the date and platform in it, is the single most urgent ask in file 03.

Material inventory and evaluation

Prepared: 25 September 2026 (V3: adds the transit side project, the "Product Pages We Like" reference email, the hero video meeting notes, and duplicate-file verification. V2 24 Sep: platform and deadline provenance clarified)

Everything received, grouped by what it's for. Each entry says what the file actually is (which is not always what the filename suggests), its status, and how much weight it can carry.

1. Strategy and messaging

ChargePoint-Strategy-Document.doc (August 2026)

Competitive landscape and messaging framework titled "Intelligent Electrification." Positions ChargePoint as the "Open Ecosystem Leader" serving three stakeholders (drivers, fleets, site owners), maps ten competitors, and closes with a three-message framework and a manifesto. Despite the .doc extension it's an HTML export with no named author, and none of its competitor figures (EVgo's 35% margin, Blink's revenue jump, IONNA's bay counts) carry sources. It references interactive perceptual maps "maintained as a separate artifact" that we don't have.

Trust level: use for positioning logic and competitive framing. Do not lift any number from it into site copy without a source check.

Michelle Draft, "Charge Where Life Happens" Messaging Playbook (July 2026, 42pp)

The client's own working source of truth for destination charging: five active segments (Workplace, Retail, Fueling and Convenience, Universities, Commercial Real Estate; Multifamily archived), approved rally cries and H1/H2 hierarchies per segment, 18 buyer personas with buying committees, a CTA library, and an ad index. Explicitly written for "ads, BDR sequences, landing pages and sales decks."

It is a draft and shows it: broken table of contents, a garbled sentence in the Retail section, a blank page, typos in ad IDs, many headlines marked "Test" rather than approved, and internal stat conflicts (four different dwell-time figures, two different gas-decline rates). Its cover points to a "Campaign Operating Instructions" document for usage rules, voice standards and claims governance. That document is not in our possession and is arguably the most important missing file in the whole set.

Trust level: the single most reusable input for web copy, but segment-approved lines only. Every statistic needs verification against a governed source sheet that doesn't yet exist.

Chargepoint Retail Campaign v3, 16 Sep (Uprisal, 46pp)

"The new front of store" retail campaign. Strategically careful: it nests itself under the approved hierarchy (Intelligent Electrification, then Charge Where Life Happens, then the retail chapter, then the playbook's own approved rally cry). Centrepiece is "Revenue per spot," a modelled index across five retail formats, plus an estimator tool, an annual Retail Charging Index, a podcast, and a full retail landing-page mock built on the future site's chrome.

Caveats: it's a v3 pitch, not an approved plan. Slide numbers 34-36, 42 and 48-50 are missing from the export, and the missing 48-50 sit inside the landing-page section. The index's calibration claims are half-sourced. Two "Click to see the page" buttons point to prototypes we don't have.

Trust level: the landing-page mock is our best preview of intended site chrome (nav, hero, trust bar, stat band). Treat the campaign mechanics as proposed until the client confirms what's approved.

Retail Marketer.docx (undated, unbranded, ~2pp)

Second-hand notes describing some other artifact ("the page cites..."), arguing the retailer-owned charging model against third-party operators. Contains stats found nowhere else: 38% higher spend per visit (CEBR), 4% foot traffic lift, 92.3% membership renewal, 14 countries.

Trust level: useful as a content skeleton for a retailer page. Its numbers conflict with the playbook's and must not be used until reconciled.

2. Brand identity (AFTERNOW)

"ChargePoint — Client File" folder (24 PDFs)

A brand refresh review deck by AFTERNOW, exported one PDF per Figma frame, and mid-process by its own admission. The "Next steps" slide asks for feedback on palette, typography and photography, and lists guidelines as still to be prepared. Contents:

• Refreshed identity keeps the existing lowercase "chargepoin+" wordmark and circular C icon
• Palette: Accent Orange #FF7A14, Blue #006EDB, Purple #8866CC, off-black #0F1215, a grey ramp, and signature "sunrise" gradients. One documented bug: the 50% orange tint carries the same hex as full orange, so the real tint value is nowhere on paper
• Typeface: Saans by Displaay (a paid licensed face; see the conflict below)
• Photography: editorial, motion-blur, golden-hour references only; no owned image library exists yet
• Graphic elements: gradient keylines, dotted patterns, Tabler open-source UI icons, neumorphic components, an "Ask AI agent" pill
• Applications: sales deck, conference, events, social, vertical ads, brochure, product spec modules
• Three alternative website UI directions (clear light layouts; colour pops; dark mode with soft depth) and a homepage hero direction ("Electrification that pays you back"). No direction has been chosen

The mockup copy layer is full of typos and placeholder content ("unlonck savings," "Sumer Summit," "Commercial Real State," lorem ipsum industry cards, the same product description pasted under three different products). Fine for mockups, dangerous if any of it is treated as approved copy.

"rechargepointxuprisalteam" folder (12 PDFs)

A partial export of the actual "Visual Identity Guidelines V01, September 2026" that the review deck promised. Only covers, dividers and four content pages arrived; roughly 11 pages (logo rules, colour specs, imagery guidance) were not shared. Every intro paragraph shared so far is lorem ipsum and every footer says page 31.

The one big contradiction: the review deck specifies Saans by Displaay. Guidelines V01 specifies Instrument Sans (free, Google Fonts) using the identical specimen layout. Nobody can set type or license webfonts until this is resolved.

Trust level (both folders): direction is clear and attractive, but formally unratified. No logo usage rules, clear space, minimum sizes, accessibility guidance, or written photography principles exist in anything we hold.

ChargePoint-BrandAssets (1).fig

Figma brand assets file sent by Nikhil at kickoff. Not yet opened in Figma; unknown whether it matches the AFTERNOW deck, the V01 guidelines, or neither. Worth checking early, since it may resolve (or deepen) the typeface question.

3. Migration and SEO data

ChargePoint Priority and Equity Analysis (Sep 2026, xlsx)

Page-level audit of all 5,637 Google-indexable pages, each scored on organic clicks (GSC), visits/conversions/revenue (GA4) and backlinks (Ahrefs), with a four-way verdict. Summary: 448 top pages carry 88% of landing-page visits and effectively all attributed revenue ($2.9M); 2,206 pages come to the new site; 1,427 FAQ articles consolidate into one page per language with anchors; 2,004 pages don't get rebuilt. Homepage alone: 434K organic clicks, 2.21Mattributedrevenue, 5, 022referringdomains.Thehighest − revenuepageafterthehomepageis/drivers/home(354K), which confirms home charging as the commercial heart of the site.

Trust level: high. This is professional work and should be treated as the operative content-scoping document. Two caveats: Search Console click data covers only the top ~962 pages, and the language-retirement decision it marks "pending D1" has since been made by Sonali's 24 Sep email (nine locales dropped) but should be reconciled in the workbook.

ChargePoint Redirect Mapping (Sep 2026, xlsx)

5,565 old URLs mapped: 2,915 301s, 1,626 unchanged, 1,024 gone (410). Its destination URLs reveal the planned new structure: /home-charging, /commercial-charging, /fleet-charging, /ev-chargers, /support/faqs, /incentives, /solutions, /resources, /blog, /about, /partners, /legal. It references a "URL Structure v1.1" document we don't have.

Open issues inside it: 72 "needs confirmation" URLs with real traffic and no destination (including /installer-app at 1,964 clicks, the German legal-notice page /de-de/impressum, the CEO profile, and /about/coverage in every language at ~50K combined visits); some destination rows still use old folder names; case-inconsistent duplicates. It needs a QA pass against URL Structure v1.1 before dev builds from it.

all-pages-export.csv and cp-pages-list.csv

Two Drupal CMS exports of the same dataset (11,894 and 11,256 rows; the larger is simply newer, adding job postings). Includes unpublished nodes the crawl-based audit can't see. Useful as a completeness cross-check, not as a planning document.

Information Hierachy(Master).csv (client, 24 Sep)

The client's draft master nav: Product Portfolio, Fleet, Home, Industry (with a heavy three-level Commercial Charging branch), About, Support, Partner, Contact. Contains bracketed naming alternatives still in flux ("Retail [Retailers]", "Charging Lounges [Corridor Charging Points]"), no home for blogs, case studies, customer stories or investors, and a "Residential" item nested under Industry that collides with the top-level "Home." Critically, this audience-led nav does not match the journey-led URL structure in the redirect map, and neither matches the nav in the AFTERNOW/Uprisal mockups. See file 02.

4. Home product pages workstream

The brief (email, Sonali to Mateo, 22 Sep)

Sonali briefed AFTERNOW directly for the two home product pages, naming Tesla and eviqo.io as the bar, with a six-step user journey (want a solution, see options, top features, validate fit, easy install, support) and a product-detail page that "reinforces the decision already made." The landing-page story she wants told: ratings, "top ranked on Amazon," ease of use, and guided selection of the best-suited product. The PDP needs features, accessories, "what's inside my box," compatible vehicles, easy comparison and tech specs. Jyothi's feedback is already folded into the mockups. This email reached us twice (both of Noella's inboxes); the two PDFs are the same message.

The reference set ("Product Pages We Like" — email, Sonali to Mateo, same morning; forwarded to us 25 Sep)

A companion email that sharpens the brief into named patterns. For the individual product page, eviqo's architecture is the model: How to Install, Reviews and FAQs built into the page's own nav bar. For the landing page, Sonali likes eviqo's "Which charger works for me?" selector, its compatibility testing and its comparison, and calls Tesla's charger landing page "really neat," adding that eviqo's product page and images are "exceptionally good." It also sets the review workflow: once wireframes exist, Rebecca, Xiaoshan and Sonali get Figma comment access for direct feedback.

chargepoint-home-charging.html and chargepoint-home-flex-detail.html

These are not saves of the current site. They are self-contained prototypes of the future category page and Home Flex product page, built client-side with Jyothi's feedback already in. They carry pricing ($699 Home Flex, $799 "Home Flex Plus" with NACS, a product that appears in no other document), a named competitor comparison against EVIQO with placeholder cells, "#1 Selling Home Charger," "4.5/5 (2,400+ reviews)," three placeholder testimonials, and network stats (250K+ ports, 70K locations, 16 countries) that contradict every other document's numbers.

Trust level: excellent for intent, structure and the client's taste. Zero of the claims, prices, reviews or specs can be reused without verification. The prototype's own placeholders confirm this: all three testimonials are tagged "Placeholder Review" in the markup, and two EVIQO comparison cells literally read "[PLACEHOLDER - Verify from eviqo.io]". Naming EVIQO on-page is a legal and brand decision nobody appears to have made deliberately.

The folder also holds duplicate copies of both prototypes ("copy" files); checksummed 25 Sep, all byte-identical to the originals, no variant content.

5. Approved design references

• 462646.png — full-length homepage mock ("Electrification that pays you back," B2B-led, product ecosystem, customer stories, stat band). Per Sonali's emails this direction is approved, with the second section dropped.
• background.png — a blank card UI asset.
• image 658.png — a Calendly customer-story module screenshot, sent as a testimonial-section reference.

6. Measurement

GA Architecture, Sep 15 (Uprisal)

A GA4 measurement architecture: one property, three data streams (marketing site, driver app, investor site), one GTM container, Consent Mode from day one, a 12-event taxonomy, a UTM convention, and CRM-joined closed-loop attribution. Sound, unglamorous, good work.

Three issues. The deck's own numbering skips slides 02 and 07, and the missing slide 02 almost certainly held the "roughly a dozen questions this business needs answered every month" that the whole architecture claims to be designed around. The event taxonomy is retail-B2B shaped (estimator events, revenue-per-bay parameters, store formats) and contains no consumer commerce events at all, despite the home product pages being an explicitly purchase-shaped journey. And it presumes interactive tools (estimator, power demo slider) that no other document confirms are being built. The implementation target is now known to be WordPress, which the deck predates; the GTM/data-layer spec will need a WordPress-specific implementation plan.

7. Transit side project (received 25 Sep)

A separate request routed by Nikhil on 25 Sep under the subject "APTA 101 Deck & Videos: Michelle introduction and side project request." This is sales collateral for the transit/electric-bus business — an 11-slide deck, a 60-second animated video and a master storyline built on the ChargePoint + Eaton partnership — not website scope. But it is the deepest transit messaging the project now holds, and much of it will be reusable when the website's transit pages get written. Caveat on the routing: only the internal Uprisal forward chain arrived; Michelle's original request text, her exact ask and any deadline are all missing.

Transit Full Integrated Solution Storyline.docx

The master narrative ("The Integrated ChargePoint Transit Solution"). The story: a patchwork multi-vendor depot fails at 2:00 AM and buses miss the 5:00 AM pullout while vendors point fingers; the integrated stack (Eaton power infrastructure → ChargePoint DC fast chargers → CMS Suite → ViriCiti telematics → fleet operations software) fixes it. Rich in specifics: the division of labour ("ChargePoint manages everything from the charger to the bus; Eaton manages everything from the utility to the charger"), a 30–70% peak-demand-charge reduction claim, an AI Data Assistant and an AI Installer Toolkit ("automates up to 95% of activation tasks"), an integrated-vs-mixed comparison table, and the Santa Monica Big Blue Bus proof point ($56M committed, 195-bus fleet by 2032, 130 DC ports on Express Plus, 10M+ annual rides, a $53.3M state grant, and a named quote from Anuj Gupta, Director of Transportation). Also proposes a "ChargePoint Integrated Fleet Package" bundle. Notably careful on lock-in: "ChargePoint's software is and will always be OEM agnostic."

ChargePoint_Transit_101_Deck_Design_Guidance.docx

The build brief for the 11-slide core deck ("Beyond the Charger: The System Behind Electric Transit"): fragmented depot as Point A, one connected system as Point B, one continuous depot environment evolving across the slides, business outcomes before product, real products visible by slide 3, Big Blue Bus as the proof slide, emotional close ("When everything works together, transit just works."). It carries an explicit "Items to Validate Before Design Finalization" list — product naming (Distro, Power Link, Express Solo, Express Plus, gantry, pantograph), external approval for the 30–70% claim, the "70+ transit organizations" claim, the Big Blue Bus metrics, the Anuj Gupta quote permission, approved logos and the combined Eaton+ChargePoint support/SLA language.

One internal contradiction worth holding onto: the storyline leads with "one company to call," while the deck guidance explicitly warns against broad "one company to call" claims until the commercial and support model is confirmed, preferring "coordinated visibility, accountability and support." The deck's more cautious language should govern anything customer-facing.

APTA_Transit_Animated_Video_Creative_Brief_UPDATED.docx

Production brief for the 60-second motion-graphics video: no voiceover, text and visuals only, one continuous build across ten frames following POWER → STORE → CHARGE → OPERATE, ending on the ChargePoint + Eaton lockup. Several lines are locked verbatim ("When everything works together, transit just works," "More productive fleets. Lower energy costs. Greater uptime," "Right bus. Right charge. Right time," "From the grid to fleet readiness"), the 30–70% callout is conditional on approval, and "demand charges must be stated accurately," never shortened to generic "demand." It is an enhancement of an existing video, not a rebuild; Nikhil's email links the existing Eaton ChargePoint video (on the /products/stations/next-gen page), a Dropbox animatic, and customer-story references (Gillig blog, PSTA, King County Metro, SFMTA).

Trust level (all three): strong, internally consistent messaging architecture, clearly written close to the client. But every load-bearing claim is explicitly gated on validation, the product naming ("Express Plus" vs the current portfolio) is flagged as unreconciled by the documents themselves, and nothing here is approved for external use yet. Treat as the transit messaging source of truth in waiting.

8. Meetings

Hero video concept review (internal, 25 Sep; recap + transcript on file)

Vilasini and Noella presented three homepage hero video concepts (Vilasini's "Charge While Life Happens" day-in-the-life; Noella's cinematic visual-connection treatment; Noella's sound-led "world plugs in" treatment). Direction agreed: shift to roughly 70% B2B and fleet imagery (per Nikhil, major retail, fleet, bus, delivery and logistics customers outweigh home users commercially), keep the charging-light and looping treatments, replace the home-centric ending with a depot, logistics bay, supermarket or parking setting, and tie the film to differentiators (geographic reach, plug-and-play simplicity, operational value) rather than a message a competitor could run. Two useful clarifications surfaced: the team's working model of the message hierarchy (intelligent electrification is the company positioning, not a tagline; "charge where life happens" is the consumer-facing campaign within it), and the homepage mechanics question — the video likely loops behind a separate headline and CTA (Sonali referenced the Tesla site, which overlays only a CTA), but whether it carries supers needs confirming. Also noted: Rukmini is away 2 Oct and 5–8 Oct, and client deadlines are expected the following week.

9. Prior internal outputs (already in the project folder)

• Chargepoint-Strategy-Documents-Evaluation-V1.md (21 Sep) — forensic evaluation of the five briefing documents; flagged the cross-document stat conflicts and missing deck pages first.
• Chargepoint-Website-Audit-Output (21 Sep, 6 files) — full audit of the live chargepoint.com: Drupal on Pantheon, 1,765 English pages across 17 locales, four audiences, 18 solution verticals, 155 custom pages vs 1,610 templatised, plus complete URL lists per content type. Still current and load-bearing for scoping.

Referenced but not received

These are named inside the material we hold but absent from it:

1. Campaign Operating Instructions (usage rules, voice standards, claims governance) — referenced on the playbook cover
2. URL Structure v1.1 — referenced by the redirect workbook
3. Visual Identity Guidelines V01, content pages 4-14 — logo rules, colour specs, imagery guidance
4. GA Architecture slides 02 and 07 — including the "dozen questions"
5. Retail Campaign slides 34-36, 42, 48-50 — including landing-page detail
6. The interactive perceptual maps (strategy document companion)
7. The estimator / landing-page prototypes behind the deck's "Click to see the page" buttons
8. The style guide behind the Google Drive link in Vismaya's 21 Sep email (access unverified)
9. The staged pages at chargepoint.uprisal.in/retail and /investors (not yet reviewed side-by-side)
10. Any written schedule or plan of record. The 30 November date (verbal, from Sonali) and the WordPress platform decision are both known to the team but recorded nowhere, and no document covers hosting, the multilingual setup, or the Drupal-to-WordPress migration approach
11. Michelle's original transit request — only the internal Uprisal forward arrived; her ask, its deadline and its approval path are all unstated
12. The transit reference assets behind Nikhil's links: the Dropbox animatic (091126_ChargePoint_Express_Animatic_04.mp4) and the customer-story references (Gillig blog, PSTA, King County Metro, SFMTA PR) — links received, files not in hand

Takeaways and gaps

Prepared: 25 September 2026 (V3: folds in the transit side project, the hero video direction and the product-page reference set. V2 24 Sep: platform and deadline provenance clarified)

Ten takeaways from the full material set, then the gaps. Takeaways first because the material genuinely tells us a lot; the gaps make more sense against that backdrop.

Takeaways

1. This is a full-site rebuild and migration, not a redesign of a few pages

Nikhil's kickoff email calls it "the website project" without qualification, and the artifacts back that up: a site-wide redirect map, an equity analysis of every indexed page, a master nav covering every segment, locale retirement decisions, and a measurement architecture spanning three surfaces. Scope in practice: 2,206 pages migrate, 1,427 FAQ articles consolidate, 2,004 pages die, 9 locales retire, and a set of flagship pages (homepage, home charging, retail, commercial, fleet, investors) get built new to a new brand.

2. The commercial heart of the current site is home charging, but the strategy documents barely cover it

The homepage plus the drivers/home-charging journey carry the overwhelming majority of clicks and effectively all attributed revenue ($2.21M homepage, $354K /drivers/home, plus a 21,500-conversion FAQ cluster). Yet the messaging playbook covers only five B2B destination segments and contains no driver, home or fleet messaging at all. The strategy document covers home charging only at competitive altitude. The best content guidance for the highest-value section of the site is currently a client-built HTML prototype full of placeholder claims.

The 25 Sep transit side project narrows the fleet half of this gap: transit now has a full message architecture (storyline, deck logic, locked lines, a flagship proof point) — written for sales collateral and gated on claims approval, but reusable for the transit vertical pages. Home and driver messaging remain uncovered. Meanwhile the hero video direction from the same day (roughly 70% B2B and fleet imagery, per Nikhil: retail, fleet, bus, delivery and logistics customers outweigh home users commercially) confirms the B2B tilt is deliberate, which makes the missing home messaging more pointed, not less — the revenue engine gets neither the homepage lead nor a playbook chapter.

3. Three navigation models are in circulation and they disagree

• The client's Information Hierarchy CSV (24 Sep): audience/industry-led. Product Portfolio, Fleet, Home, Industry, About, Support, Partner, Contact
• The AFTERNOW UI mocks and Uprisal's retail deck: journey-led. Electrify my fleet / Electrify my site / Electrify at home, plus Resources & Support and Partners
• The redirect map's destination URLs: journey-led but differently sliced. /home-charging, /commercial-charging, /fleet-charging, /ev-chargers, /support, /incentives...

Any of the three could work. Running all three means the IA, the URL structure and the visual design are being built against different maps. This is the single most consequential unresolved decision in the project.

4. Three top-line brand messages coexist without a ratified hierarchy

"Intelligent Electrification" (strategy document, with manifesto), "Charge Where Life Happens" (client playbook), and "Electrification that pays you back" (the approved AFTERNOW homepage hero). Only Uprisal's retail deck proposes how the first two nest, and that proposal is a v3 pitch, not a client sign-off. The approved homepage mock's hero line comes from neither of the two strategy documents. Until someone ratifies the hierarchy, every headline we write is a guess about which brand voice wins.

The 25 Sep hero video session put the team's working model on record, and it matches the retail deck's proposal: intelligent electrification is the company positioning, not a tagline; "charge where life happens" is the consumer-facing campaign inside it (fleet gets "intelligent fleet management" language instead). Useful, and still internal — it needs the client to say it back in writing before it governs headlines.

5. The brand refresh is genuinely attractive and genuinely unfinished

The visual system (orange/blue/purple palette, sunrise gradients, dotted patterns, keylines, neumorphic components, editorial photography direction) is well-developed and distinctive. It is also formally unratified: the review deck is still soliciting feedback, the guidelines are V01 with lorem ipsum and 11 unshared pages, the deck and guidelines name different typefaces (Saans vs Instrument Sans), the 50% orange tint has no documented hex, and no logo usage, accessibility or photography rules exist in writing. Three website UI directions await a decision. And there is no owned image library yet, which for a photography-led design system is a long-lead-time problem against a November deadline.

6. The proof-point numbers are in open conflict, sometimes within one document

A sample across the set: activated ports appear as 400K+, 406K+, 375K+ and 250K+; countries as 14 and 16+; Fortune penetration as "82% of the Fortune 50" and "64% of Fortune 500"; retail dwell uplift as five different figures; spend uplift as +20%, +38% and "50% more time"; gas-station decline as 1.4% and 2-4%; revenue per port as $41.6K (QSR, retail deck), $125,360 (UI mock) and $130K (homepage mock). Some of these are different metrics wearing similar clothes; most are just unreconciled. There is no claims sheet, and the document that would govern one (Campaign Operating Instructions) is missing. Nothing numeric should reach production copy until this is fixed.

The transit documents add a fresh batch to govern — 30–70% peak-demand-charge reduction (explicitly conditional on external-use approval), "70+ transit organizations," the Big Blue Bus metrics ($56M, 195 buses, 130 ports, 10M+ rides), a named customer quote pending permission — but they also model the right behaviour: they gate their own claims on validation before use. That discipline is what the claims register generalises.

7. The client is an active, opinionated participant, and has her own design channel

Sonali makes decisions daily, builds her own HTML mockups, and briefs AFTERNOW directly, with Uprisal receiving the results as forwards. That's useful (fast decisions, clear taste, Tesla and eviqo named as the bar) and risky (two agencies designing in parallel with no stated boundary, and client-authored placeholder claims that could be mistaken for approved copy). The collaboration model needs naming before the tracks collide on the same pages.

8. The migration thinking is the most mature part of the project

The equity analysis and redirect map are professional, internally documented, and largely decision-complete. The 448 top pages are individually mapped with a "confirm the new page exists before go-live" discipline. What remains is bounded: 72 needs-confirmation URLs, a QA pass on destination inconsistencies, sign-off on 1,024 hard removals, and reconciliation with the missing URL Structure v1.1 document.

9. The measurement plan is ahead of the product

The GA architecture presumes an estimator, a power-management demo, a store-format selector and a separated investor site. No other document confirms those features are in the build scope. Either the feature list needs confirming (in which case UX has significant interactive tools to design) or the taxonomy needs trimming. Meanwhile the taxonomy has no consumer commerce events despite a purchase-shaped home product journey, and while the CMS question is now answered (WordPress), the CRM and warehouse it must join to remain unnamed.

10. The two most important project facts are verbal

The 30 November go-live came from Sonali verbally, and the platform decision (WordPress) is likewise team knowledge rather than a documented brief. No received document contains a launch date, schedule, phasing, content freeze or QA window. The Drupal-to-WordPress move is a real migration, not a reskin: 2,206 pages, 9 locales (which forces a multilingual-plugin or multisite decision), 2,915 redirects, anchor-level FAQ consolidation, and a GTM data layer to rebuild. Ten weeks of runway is achievable only with aggressive sequencing, which requires a written plan of record that currently does not exist.

Gaps

Grouped by the kind of work they block. The ranked chase list with owners is in file 03; this is the full map.

Strategy and messaging gaps

• No ratified brand message hierarchy (see takeaway 4; the team's working model from 25 Sep needs client confirmation)
• No messaging for home/driver audiences, installers, utilities, CPOs, OEMs, government, or any of the 13 live site verticals outside the playbook's five. Transit is now the exception (25 Sep side-project docs), pending claims validation and confirmation the material may be reused on the website
• Multifamily is archived in the campaign but present in the nav ("Residential") and on the live site; no guidance for it
• No tone-of-voice standard; three registers exist across documents (punchy playbook, essayistic retail deck, elevated manifesto) plus a fourth in the AFTERNOW mocks (plain-spoken, proof-first)
• No approved boilerplate, about copy, legal disclaimers or pricing guidance

Brand and design gaps

• Typeface undecided (Saans vs Instrument Sans); webfont licensing blocked
• UI direction unchosen among three alternatives
• Guidelines V01 incomplete and partially unshared; no logo/photography/accessibility rules
• No owned image library; photography is references only
• The .fig brand assets file unverified against the current system

Content and data gaps

• No claims/source sheet; Campaign Operating Instructions missing
• Playbook persona "Proof needed" items still open (dwell/basket study, payback models)
• All prototype claims unverified (prices, reviews, rankings, network stats, tax credit)
• "Home Flex Plus" appears only in the prototype; is it a real, launching product?
• Time-expired claims in circulation: the Section 30C credit hook (expired 30 June 2026) and the Apple Card promo (ended 15 September)
• No case study or customer quote content beyond logo names

Structural gaps

• IA unreconciled across three models; bracketed nav labels undecided
• No home in the nav for blog (340 posts), case studies (38), customer stories, press (491 releases), incentives (456 pages), or investors
• "Home" vs "Residential" label collision
• 72 redirect destinations unconfirmed; URL Structure v1.1 not in hand
• store.chargepoint.com explicitly out of scope of the page list with no stated owner, while the prototypes' "Buy Now" CTAs presumably point at it
• Investor relations: rebuilt page exists on staging, absent from nav, treated as a separate surface by GA

Video and side-project gaps (new, 25 Sep)

• Homepage hero video mechanics unconfirmed: does it carry supers, or loop behind a separate headline and CTA (the Tesla pattern Sonali referenced)? Blocks the supers-writing task and the hero component design
• Michelle's original transit request not in hand: her exact ask, the deadline, the approval path and whether the side project is inside the engagement's scope and fees
• The transit validation list (product naming including Express Plus vs the current portfolio, the 30–70% claim, "70+ transit organizations," Big Blue Bus metrics, the Anuj Gupta quote, logo permissions, combined Eaton SLA language) is entirely open — the documents themselves say don't finalise until it closes
• Rukmini away 2 Oct and 5–8 Oct with cover unassigned, in the same window client deadlines are expected

Operational gaps

• No written schedule, phasing or content freeze against 30 November (the date itself is verbal)
• Platform is WordPress, but hosting, multilingual approach (WPML/Polylang/multisite), theme/block architecture, build owner and staging environment are all undecided or undocumented; the current site is Drupal on Pantheon, so this is a full replatform
• No roles/ownership map across ChargePoint, Uprisal, AFTERNOW and Vilasini's team (internal split now clear: Vilasini and Noella on comms/content/writing, Sushanth leading the redesign; the Sushanth/Mateo design boundary still needs naming)
• No translation workflow for the 8 retained non-English locales
• No legal review path (German Impressum currently has no redirect destination; EVIQO comparison unvetted; claims substantiation)
• No accessibility target stated for a design system leaning on gradients, glows and low-contrast greys

Priority inputs needed ASAP

Prepared: 25 September 2026 (V3: adds the hero video and transit side-project asks. V2 24 Sep: platform confirmed as WordPress, deadline confirmed as verbal from Sonali) Working backwards from: 30 November go-live

Ranked by how hard each item blocks work, not by how easy it is to get. P1 items block multiple workstreams today. P2 items block specific workstreams within a week or two. P3 items are needed before launch but don't block starting.

P1 — blocks everything, chase this week

1. A written plan of record against 30 November. From: Uprisal (Nikhil/Vismaya) with ChargePoint sign-off. The date exists only as Sonali's verbal instruction; no document records it. We need it in writing along with phasing (what launches 30 Nov vs after), a content freeze date, a QA and redirect-testing window, and locale sequencing. Every other priority call depends on this. If the honest answer is that 30 Nov means a phased launch (say, new brand + flagship pages + redirects live, long-tail migration following), better to plan that deliberately now than discover it in November.

2. The WordPress build spec. From: Uprisal (whoever is developing) with ChargePoint IT. The platform is decided: WordPress. What's undecided or undocumented is everything that makes that real ten weeks out: hosting; the multilingual approach for 9 locales (WPML vs Polylang vs multisite — this choice shapes URL prefixes, the locale switcher, translation workflow and the anchor-linked FAQ pages); theme and block architecture (the design system should be built as reusable blocks, which Sushanth and the designers need to know before componentising); migration tooling for 2,206 pages out of Drupal; redirect implementation (2,915 301s at the server or plugin level); staging environment; and who develops. Migrating a 17-locale Drupal site to WordPress is the longest lead-time job in the project and none of its sub-decisions are on paper.

3. One ratified information architecture. From: Sonali, in a working session with Uprisal, AFTERNOW and us. Three nav models are live (client CSV, AFTERNOW mocks, redirect-map URL folders). One session should settle: the top-level nav, whether nav labels and URL folders are allowed to differ (they can, if deliberate), where blog/case studies/press/incentives/investors live, the Home vs Residential naming collision, and the bracketed label choices. Until then, designers are wireframing against a moving target and the redirect map can't be finalised.

4. The typeface decision and the complete Visual Identity Guidelines V01. From: AFTERNOW (Mateo), via Sonali or Uprisal. Saans (review deck) vs Instrument Sans (guidelines) must be settled before any type is set or licensed; the two have different licensing costs and loading behaviour. At the same time request guidelines pages 4-14 (logo rules, colour specs including the missing 50%-orange hex, imagery guidance) and confirmation of which of the three website UI directions is chosen.

5. A single governed claims and stats sheet. From: ChargePoint (Michelle's team), possibly delivered as the missing Campaign Operating Instructions. Every load-bearing number currently exists in two to five conflicting versions (ports, countries, Fortune penetration, dwell, spend uplift, revenue per spot/port). We need one sheet with the approved figure, its source, its as-of date, and where it may be used. Content production at scale cannot start safely without it. If the client can't produce one quickly, we should draft it from the playbook's April 2026 proof points and have them ratify it.

P2 — blocks specific workstreams, chase within two weeks

6. Scope confirmation for interactive features. From: Uprisal + ChargePoint. Is the revenue-per-spot estimator in the 30 Nov build? The power-management demo? The store-format selector? The "Ask AI agent" component? The GA architecture assumes them; nothing else confirms them. Each is a significant design-and-build item on its own. One update: the transit documents name an AI-powered Data Assistant and an AI Installer Toolkit as real products, so the "Ask AI agent" pill likely reflects something that exists — the question is whether it's in website scope, not whether it's invented.

7. Messaging direction for home, fleet and the 13 uncovered verticals. From: ChargePoint (Michelle's team) via Uprisal. The playbook covers five B2B destination segments. The site needs copy for home charging (the revenue engine), fleet (a top-level nav item), and the other live verticals (utilities, CPOs, OEMs, government, dealerships, education...). We need either extended playbook chapters, or explicit licence to derive messaging ourselves from the strategy document plus product material, with a defined approval path. The transit storyline (25 Sep) shows chapters like this exist or can be produced fast — ask whether equivalents exist for the other verticals, and confirm the transit material may be reused on the website's transit pages once its claims clear validation.

8. The 72 unconfirmed redirect destinations and removal sign-off. From: Sonali/Prem + whoever owns URL Structure v1.1. Includes real-traffic and legally sensitive pages (/installer-app, /de-de/impressum, /about/coverage in all languages, the CEO profile, /branding). Also get URL Structure v1.1 itself, confirm the 1,024 hard removals, and commission the QA pass on destination inconsistencies flagged in file 01.

9. Home product pages: claims verification and the Home Flex Plus question. From: Sonali/Rebecca/Xiaoshan. The prototypes' prices (699/799), "#1 Selling," review counts, tax-credit framing, network stats and the EVIQO comparison all need verification or removal — the prototype itself tags its testimonials "Placeholder Review" and two EVIQO cells "[PLACEHOLDER - Verify from eviqo.io]". The "top ranked on Amazon" story Sonali wants told needs the same check. Confirm whether "Home Flex Plus" is a real launching product, whether ChargePoint wants a named competitor on its own site (legal question), and who owns store.chargepoint.com and its redirects, since the Buy Now journey presumably lands there. Process note: once wireframes exist, Rebecca, Xiaoshan and Sonali get Figma comment access (per the 22 Sep "Product Pages We Like" email) — set that project up now so the loop is ready.

10. Access pack. From: Uprisal. The Google Drive style guide link, the staged pages at chargepoint.uprisal.in/retail and /investors, the estimator/landing-page prototypes behind the retail deck's "Click to see the page" buttons, the missing deck slides (GA 02 and 07 including the "dozen questions" list; retail 34-36, 42, 48-50), the interactive perceptual maps, and the .fig file opened and checked against the brand system.

11. A roles and ownership map for the wider project. From: Nikhil. The internal split is settled (Vilasini and Noella on strategic comms, content and writing; Sushanth leading the redesign). Still open: the design boundary between Sushanth's redesign mandate and Mateo/AFTERNOW's tracks (brand system, home product pages), what Rukmini and Alyssa own, who approves copy on the client side beyond Sonali, and the escalation path. One page is enough. The parallel design tracks make this more than admin hygiene. New wrinkle from 25 Sep: Rukmini is away 2 Oct and 5–8 Oct with cover unassigned, in the same window client deadlines are expected; the roles map should name her cover.

12. Hero video mechanics and the transit side-project brief. From: Sonali (video) and Michelle via Nikhil (transit). Two asks from the 25 Sep developments. First, does the homepage hero video carry overlaid supers, or loop behind a separate headline and CTA the way Sonali's Tesla reference does? Writing timed supers is real work; don't start it until this is answered. Second, the transit side project arrived without Michelle's original message: we need her actual ask, the deadline, the approval path for the validation list (product naming, the 30–70% demand-charge claim, "70+ transit organizations," Big Blue Bus metrics, the Anuj Gupta quote, logos, combined Eaton SLA language), and a scope call from Nikhil on where this sits against the website's 30 November runway.

P3 — needed before launch, doesn't block starting

13. Photography plan. The system is photography-led and no owned library exists. Commissioning or licensing takes weeks; a decision on shoot vs stock is needed soon even if delivery lands mid-build.

14. Translation workflow for the 8 retained non-English locales. Who translates, against what schedule, and does 30 Nov include localised content or English-first with locales following.

15. Legal review path. Impressum and EU legal pages, claims substantiation, competitor naming, promo end-dates (the Apple Card mock is already expired), accessibility compliance target.

16. Case study and testimonial content. The approved designs feature customer-story modules (the Calendly reference) and a trust bar; we hold logo names but no quotes, permissions or written stories. Clearances take time.

17. Analytics implementation inputs. The named CRM, warehouse and reporting tools; the "dozen questions" list; a decision on adding consumer commerce events for the home journey.

18. Confirmation of what from the retail campaign is client-approved. The deck is a v3 pitch. Which mechanics (index, podcast, estimator, ABM tiers) are real commitments affects what the retail section of the site must support.

Questions for the client

Prepared: 25 September 2026 (V3: adds hero video and transit side-project questions. V2 24 Sep: platform and deadline questions updated now WordPress is confirmed) Route: via Uprisal (Vismaya/Nikhil) to Sonali, unless noted. Starred questions (*) are the ones to force into the next client call if time is short.

Business and strategy

1. • The 30 November date has so far been verbal. Can we confirm it in writing, and define what success on that date looks like? Full site live in all retained locales, or a phased launch? What is non-negotiable for day one?
2. • What are the site's top three commercial jobs, ranked? The data says home charging drives revenue, the campaign material says retail B2B pipeline, the approved homepage mock leads B2B. Where does the business want the site's centre of gravity?
3. Which parts of the retail campaign (estimator, Retail Charging Index, podcast, ABM programme) are approved commitments the site must support, and which are still proposals?
4. The strategy document sells the three-stakeholder model (drivers, fleets, site owners); the playbook is built on five destination segments; the live site sells 18 verticals. Which verticals must have dedicated pages on the new site, and which can consolidate?
5. Multifamily is archived in the campaign but exists in the nav as "Residential" and on the live site. What is its status for the rebuild?
6. Is the go-forward geography confirmed as: US English default plus en-gb, en-ca, fr-ca, fr-fr, de-de, nl-nl, es-es, it-it? Does 30 Nov include localised content, or English-first?
7. Who is the single decision-maker for site sign-off on the ChargePoint side? Is it Sonali alone, or do Rebecca, Xiaoshan, Prem, Jyothi and Michelle each hold a veto in their area?

Brand

8. • Please ratify the message hierarchy in writing. Where do "Intelligent Electrification," "Charge Where Life Happens" and "Electrification that pays you back" each sit, and which one leads the website?
9. • Which typeface is final: Saans or Instrument Sans? (This blocks webfont licensing and all design work.)
10. Which of the three website UI directions (clear light / colour pops / dark mode with depth) is chosen, or is the intended answer a blend, and if so on what logic (for example, dark for B2B, light for consumer)?
11. When do we get the complete Visual Identity Guidelines V01 (pages 4-14), and who signs off logo usage, accessibility and photography rules?
12. Is there a plan (and budget) for an owned image library, or do we art-direct stock to the reference style for launch?
13. Is the "chargepoin+" wordmark treatment on dark backgrounds ("point" in white vs grey) a free choice or a rule?
14. The AFTERNOW mocks show an "Ask AI agent" component and "AI Assistance" in the footer, and the transit documents name an AI Data Assistant and AI Installer Toolkit as real products. Is an AI assistant in scope for this site?

Messaging and content

15. • Where are the Campaign Operating Instructions (voice standards, claims governance) referenced on the playbook cover? If they don't exist yet, can we draft the claims sheet and have Michelle's team ratify it?
16. • Which single set of proof-point numbers is approved for the site, as of what date, and who maintains them? (Ports, sessions, countries, Fortune penetration, roaming, brands.)
17. The dwell-time and spend-uplift figures conflict across five sources. Which figure, from which study, may we publish?
18. Is there approved messaging for home charging and drivers, or do we build it from the product material with your approval? Same question for fleet.
19. Several playbook personas list "Proof needed" items (dwell/basket study, payback models). Have any of these landed since July?
20. Are the trusted-by logos (IKEA, Stanford, Stripe, Airbus, Disney, Target, VW, Porsche, Sonepar) cleared for website use? Can we get customer quotes and written case-study approvals to fill the story modules?
21. The strategy document's competitor figures and the retail deck's Revenue Per Spot inputs are unsourced. Do sources exist internally, and can they be shared for anything that reaches public copy?
22. The Section 30C tax-credit hook expired 30 June 2026 and the mocked Apple Card promo ended 15 September. What is the current, publishable incentive story for home buyers?

Home product pages (for Sonali, Rebecca, Xiaoshan)

23. • Is "Home Flex Plus" ($799, NACS) a real product launching by 30 November? If yes, we need its actual spec sheet, naming and pricing; if no, the category page needs rescoping.
24. Are the $699 price, "#1 Selling Home Charger," "4.5/5 from 2,400+ reviews," "top ranked on Amazon" and "70,000+ locations / 250K+ ports / 16 countries" claims verifiable? Several conflict with the corporate numbers elsewhere in the material, and the prototype's own testimonials are tagged as placeholders.
25. Do you genuinely want a named EVIQO comparison table on your own product page? Has legal seen it? (Naming a cheaper competitor on-page cuts both ways.)
26. Who owns store.chargepoint.com, is the buy journey staying there, and who handles its redirects? The Home Flex store page alone carries 29K+ organic clicks.
27. What is the tax-credit message we can legally run for home installation right now?

Migration and operations

28. • For the WordPress build: who develops, on what hosting, and when does the build start? What is the multilingual approach for the 9 retained locales (WPML, Polylang, or multisite), how are the 2,915 redirects implemented (server-level or plugin), and is there a staging environment plan? Does the buy journey stay on store.chargepoint.com or move into WordPress (WooCommerce)?
29. The redirect workbook references URL Structure v1.1. Please share it, and confirm the 72 "needs confirmation" URLs, especially /de-de/impressum (a German legal requirement), /installer-app, /about/coverage and the CEO profile.
30. Please sign off the 1,024 hard removals (410s), including the ~234 with residual traffic.
31. Blogs, case studies and customer stories migrate "as is" per your 24 Sep email, but have no home in the master nav. Where do they live, and does "as is" mean unedited copy even where posts carry the old brand voice and outdated facts?
32. What happens to the 456 incentive pages and 491 press releases (1,300+ referring domains ride on the press archive)? They're absent from the nav.
33. Where does investor relations live? Uprisal has a rebuilt IR page on staging, GA treats it as a separate surface, and it is absent from the nav.
34. Who implements and QAs the redirects at cutover, and is there a rollback plan?
35. What is the translation workflow and who are the approved translators for the retained locales?
36. For measurement: what CRM and data warehouse are we integrating with, and can we have the "dozen questions" list the GA architecture was designed around (missing slide 02)?
37. Is there an existing consent-management platform, or does one need selecting for the EU locales before launch?

Homepage hero video (for Sonali)

38. • Does the homepage video carry overlaid supers, or loop behind a separate headline and CTA? (The Tesla reference overlays only a CTA.) This decides whether we write timed supers or an external headline system, and it constrains the hero component design.
39. Confirm the content balance: roughly 70% B2B and fleet imagery with home charging reduced, and a B2B setting (depot, logistics bay, supermarket, parking) for the closing sequence — is that the ratified direction after the 25 Sep evening review?
40. Which differentiators must the film communicate: geographic reach, plug-and-play simplicity, operational value — all three, or a priority order?

Transit side project (for Michelle, via Uprisal)

41. • What exactly is the ask, and by when? Only the internal forward reached us; the original request, deadline and approval path aren't on paper.
42. Is the 30–70% peak-demand-charge reduction approved for external use, and with what qualification language? The video brief makes this callout conditional.
43. Please validate: "70+ transit organizations," the Big Blue Bus metrics ($56M, 195 buses by 2032, 130 DC ports, 10M+ annual rides), and permission plus wording for the Anuj Gupta quote.
44. Product naming needs reconciling before design lock: Distro, Power Link, Express Solo, and especially "Express Plus" versus the current portfolio naming. Who owns the product taxonomy?
45. What support/SLA/accountability language may we use for the combined ChargePoint + Eaton offer? The storyline says "one company to call"; the deck guidance warns against that until the commercial model is confirmed.
46. Which transit customer logos are cleared for the deck's credibility slide?
47. Once validated, may the transit storyline content be reused on the website's transit pages, or is it sales-collateral-only?

UX/UI collaboration points

Prepared: 25 September 2026 (V3: adds the hero video component, the eviqo/Tesla reference set and the Figma review workflow. V2 24 Sep: addressed to Sushanth as redesign lead; WordPress implications added) For: Sushanth (redesign lead) and the wider UX/UI team

Working agenda for our first sessions together. Organised as: decisions we need jointly, design problems the material hands us, and things worth knowing before opening Figma.

Decisions we need to make together (or force upward)

1. The navigation model

Three competing models exist (client CSV, AFTERNOW mocks, redirect-map URLs; detail in file 02). My read: the AFTERNOW "Electrify my fleet / my site / at home" nav is the strongest of the three as user-facing wayfinding, it matches the approved homepage mock, and it maps cleanly onto the URL structure's /fleet-charging, /commercial-charging, /home-charging folders. The client's CSV reads more like an internal taxonomy than a nav. But that's a recommendation to take to Sonali, not a decision we can make alone. Whatever wins, nav labels and URL folders don't have to be identical, but the mapping must be deliberate and documented.

Open sub-questions: where do Resources, Blog, Customer Stories, Incentives, Press and Investors live; is Support top-level (client CSV says yes, AFTERNOW mock nests it under "Resources & Support"); does "Partner" mean installer partners, OEM partners, or both.

2. One design system across three design sources

Uprisal has staged retail and investor pages. AFTERNOW owns the brand system and the home product pages. We're building everything else. Before any of us designs further, we need a shared component inventory reconciled against all three sources, or the site ships with three dialects of the same brand. Suggest we jointly audit: the AFTERNOW UI PDFs, the staged pages, the approved homepage mock, and the client's HTML prototypes, and extract one component list.

3. Dark/light strategy

The three AFTERNOW directions aren't really three options; they read as three registers of one system (calm light "proof" pages, light chrome with colour pops, dark neumorphic sections). A workable hypothesis: dark for B2B impact moments (homepage hero, fleet), light for consumer and content pages, the "clear light" register for finance/proof pages. Needs deciding as a system rule, not page by page.

4. Template list and content-model mapping

From the audit and equity analysis, the minimum template set is: homepage; segment/vertical page; product category page; product detail page (PDP); product spec/tour module; consolidated FAQ page (per language, anchor-linked); blog post; resource/download page; case study/customer story; press release; incentive page; corporate/about page; legal page; contact/forms. The 1,427-into-one FAQ consolidation and the 456 incentive pages mean the FAQ and incentive templates carry serious traffic; they aren't afterthoughts.

Design problems the material hands us

5. The consolidated FAQ page is a real UX challenge

1,427 support articles collapse into one FAQ page per language with anchor redirects. That's 21,500 conversions' worth of support content landing on a single template. It needs search-within-page, categorisation, deep-linkable anchors that survive translation, and a mobile pattern that doesn't become an endless accordion. This deserves early wireframe attention, not end-of-project cleanup.

6. The home product pages have an opinionated client brief

Sonali's six-step journey (want a solution → see options → top features → validate fit → easy install → support) with Tesla and eviqo as the bar, and Mateo already engaged for UI. Her "Product Pages We Like" email makes the references concrete: the PDP should carry eviqo's architecture (How to Install, Reviews, FAQs as sections in the page's own nav — the prototype already does this), and the landing page should learn from eviqo's "Which charger works for me?" selector, compatibility testing and comparison, plus Tesla's charger landing page. Our role: pressure-test the journey (the "validate fit" step is underspecified; charger-to-home compatibility checking is a genuine tool, not a content block — and now a client-referenced pattern), and rescue the good structure from the placeholder claims. Also flag: the comparison table currently names EVIQO with unverified cells; design should not bake in a legally undecided element.

Review workflow is defined: once wireframes exist, Rebecca, Xiaoshan and Sonali get Figma comment access for direct feedback. Worth setting the Figma project up for that from day one.

7. Interactive tools of unknown scope

The GA taxonomy assumes an estimator (revenue per spot), a power-management demo slider, and a store-format selector. The brand system includes an "Ask AI agent" pill. Any one of these is weeks of design and build. We need the scope answer (file 03, item 6) before wireframing pages that assume them; better to design graceful static fallbacks that upgrade later.

8. Accessibility risk in the visual system

The system leans on orange (#FF7A14) on white, grey-on-grey text pairings, thin gradient keylines, and neumorphic low-contrast depth cues. Several of these will fail WCAG AA as mocked (orange-on-white body text and grey 300/400 text almost certainly do). No accessibility guidance exists in the brand material. We should set a WCAG 2.2 AA target now, build a contrast-checked colour-usage matrix, and hand it back to AFTERNOW as a guideline contribution rather than discovering this in QA.

9. Performance of the aesthetic

Sunrise gradients as heavy rasters (the guideline divider PDFs are ~6.5MB each because of them), dotted patterns, glow effects, motion-blur photography: all lovely and all expensive on mobile. Gradients and dot patterns should ship as CSS/SVG, not images. Worth agreeing a per-template performance budget early, given the home journey is high-traffic and mobile-heavy, and given SEO equity preservation is a stated project goal (Core Web Vitals count).

10. Localisation-proof components

Eight retained non-English locales, German among them. Headline-led components sized on English ("Electrification that pays you back") need to survive German compound nouns and French length. Stat cards, pill buttons and the mega-menu all need long-string variants. Also: the anchor-linked FAQ pattern must handle translated anchor slugs.

11. Motion and interaction are explicitly undefined

The AFTERNOW next-steps slide assigns "refine graphic patterns with the UI team for interactions and animations". That's us. Scroll behaviour, hover states, the dotted-pattern animations, accordion mechanics: all unowned. Suggest we propose a small motion spec (three or four principles, reduced-motion support) rather than wait for one.

12. The homepage hero is now a video component

The hero video workstream went live 25 Sep: a looping film behind the homepage hero, most likely with the headline and CTA outside the video rather than burned in (Sonali's Tesla reference overlays only a CTA; confirmation pending). Direction: roughly 70% B2B and fleet imagery, charging-light and looping treatments retained. Design implications: the hero component needs a video slot with a poster-image fallback, reduced-motion support, a performance budget (this sits on the highest-traffic page), and no text baked into the video until the supers question is answered — text in the component keeps it localisable, text in the film doesn't.

13. Known component references worth reusing

• The approved homepage mock (462646.png): section order is client-approved with section two dropped; treat as fixed unless renegotiated
• The retail deck's landing-page mock: nav, hero, trust bar, stat band on real site chrome
• The Calendly screenshot (image 658.png): the client's taste reference for customer-story modules
• The Tech Specs PDFs: a strong configure-your-product accordion + annotated-diagram pattern for PDPs
• The mega-menu mock in "UI — Color Pops": the intended nav pattern, but its copy layer is placeholder (same description pasted under three products)

Worth knowing before opening Figma

• The build platform is WordPress. Design the system as a reusable block library (heroes, stat cards, accordions, mega-menu, FAQ anchors) rather than bespoke pages, and expect the multilingual plugin choice (WPML/Polylang/multisite, undecided) to constrain the locale switcher, URL prefixes and translated anchor slugs. Editor experience matters too: the client team will maintain 456 incentive pages and a large FAQ in this CMS.
• The typeface is undecided (Saans vs Instrument Sans). Don't set type until file 03 item 4 resolves; if we must start, wireframe in a neutral stand-in.
• The 50% orange tint has no documented hex; the palette otherwise is fully specified in file 01.
• Tabler (open-source) is the chosen UI icon library.
• No image library exists. Layouts that depend on hero photography need stock-or-shoot resolution (file 03, item 13) or should be designable with the graphic-element system alone.
• The current site runs 17 locales on Drupal; the new site keeps 9. Locale switcher design should handle the retired-locale redirect experience gracefully.
• 58 sitemap URLs currently 403; the redirect QA will catch them, but don't reference current-site URLs as canonical anywhere in design documentation.
• Mockup copy across every AFTERNOW file contains typos and placeholder stats. Nothing in a mock is approved copy. All production copy comes through the content workstream.

Brand and communications lens

Prepared: 25 September 2026 (V3: adds the 25 Sep hierarchy clarification, the hero video as brand-in-motion, and the transit side project's claims discipline. V2 24 Sep: brand-to-experience translation, launch-as-debut, transcreation, governance model, recommended sequence.)

The rebuild is also a brand migration: a new visual identity, a new campaign platform and a new voice landing on the company's biggest owned channel at the same time. On 30 November, chargepoint.com becomes the first place most of the world sees this rebrand. That framing changes what "done" means, and it runs through everything below.

Part one: what has to be resolved

1. Brand architecture: three claimants to the top line

Uprisal's retail deck proposes the reconciliation: platform → campaign → chapter → rally cry. It's a sensible structure, and it's the agency's proposal in a v3 pitch, not a client ratification. Meanwhile the approved homepage leads with a third line that answers to neither.

The practical risk isn't philosophical inconsistency; it's that copywriting decisions cascade from the top line. Whether the homepage H1 is a manifesto claim ("intelligence") or an ROI claim ("pays you back") changes the whole register of the page beneath it, the CTA logic, and what the segment pages must prove. Recommendation: put the table above in front of Sonali and Michelle, propose "Electrification that pays you back" as the site-lead expression of Intelligent Electrification (ROI language is what the approved design and the buyer personas both reward), and get one paragraph of ratified hierarchy in writing.

The 25 Sep hero video session moved this forward internally. The working model articulated there: Intelligent Electrification is the company positioning, not a tagline ("just that positioning, it's not a tagline that we can use"); "Charge Where Life Happens" is the consumer-facing campaign inside it, while B2B contexts get intelligent-X language (intelligent fleet management, and so on). That matches the retail deck's proposed nesting, and it came with a useful constraint: the hero film must carry differentiators a competitor couldn't claim — geographic reach, plug-and-play simplicity, operational value — not just the lifestyle promise. It is still an internal understanding; the recommendation above stands, now with a stronger draft to put in front of the client.

2. Voice: four registers, one standard needed

The material speaks in four voices. The playbook is punchy and commercial ("Turn Charging Time Into Store Revenue"). The retail deck is essayistic and contrarian ("Charging is a system, not a box in a car park", a line that also appears in the AFTERNOW mocks). The strategy manifesto is elevated ("Connected to the intelligence that outlives it all"). The AFTERNOW mock copy is plain-spoken and proof-first ("The numbers your finance team will ask for, in the open").

For the website the blend is actually visible in the best mocks: plain-spoken, commercially blunt, proof-forward for B2B; warmer and benefit-led for the home audience ("Charge tonight. Go anywhere tomorrow"). That split needs writing down as a one-page voice standard with per-audience examples. With the team split now clarified, this is squarely ours: Noella and Vilasini should author the standard, get Sonali and Michelle to ratify it, and hold every copy contributor to it, including mock copy coming out of the design tracks. The missing Campaign Operating Instructions were supposed to contain exactly this; if they surface, we reconcile, and if they don't, ours becomes the operating document.

3. Claims governance: the single biggest comms risk

Full conflict map in file 02, takeaway 6. The short version: ports (250K/375K/400K/406K), countries (14/16), Fortune penetration (82% of 50 vs 64% of 500), dwell time (five figures), spend uplift (three figures), revenue per port/spot (three figures an order of magnitude apart in places).

What makes this urgent rather than merely untidy:

• ChargePoint is publicly traded. Numbers on the corporate site are effectively investor-facing statements, and the GA architecture deliberately separates the investor surface, which tells us the client thinks about this too.
• The retail campaign's whole positioning is measurement honesty ("a confidence interval a finance team will find unglamorous and believable," EVgo's number dismissed as a "claim without a tool"). Shipping a site with self-contradicting stats under that campaign is self-refuting.
• Third-party stats (CEBR, Urban Land Institute, Electric Era, Plug In America) are named without links or dates. Republishing them without verification transfers their risk to ChargePoint.

Proposed mechanism, which we can run: a claims register with columns for claim, approved wording, source, as-of date, approved surfaces (site/ads/sales), expiry/review date, and owner. Seed it from the playbook's dated proof block ("as of April 30, 2026", the only properly dated stats in the whole set), have Michelle's team ratify, and make it the only permitted source for numbers in production copy.

The transit documents (25 Sep) both add to the register's workload and prove the model works. They add: the 30–70% peak-demand-charge reduction, "70+ transit organizations," the Big Blue Bus metrics and a named customer quote. And they demonstrate the discipline: the video brief makes its own headline stat conditional on approval, insists "demand charges must be stated accurately," and locks approved lines verbatim, while the deck guidance carries a formal validate-before-finalising list and pulls back the storyline's "one company to call" to "coordinated visibility, accountability and support" until the commercial model is confirmed. That is claims governance working as intended — the register generalises it to the whole site.

WordPress gives this teeth in a way a spreadsheet never will: build the register's approved stats as centrally managed reusable blocks or fields (one "ports activated" block reused everywhere), so a quarterly update propagates across the site in one edit and nobody can hand-type a stale number into a page. This should be a line item in the WordPress build spec (file 03, item 2), not an afterthought.

4. Time-bombed and legally sensitive content

• The playbook's CRE urgency hook cites the Section 30C credit expiring 30 June 2026, already past. The home prototype leans on a 30% federal tax credit. The current, publishable incentive story needs a legal-checked rewrite before any tax language ships.
• The mocked Apple Card promo ended 15 September. Fine as a mockup; must not leak into build.
• The EVIQO comparison table names a competitor with placeholder data. Comparative advertising has legal requirements in several retained locales (Germany and France are stricter than the US), and this page ships in those locales.
• /de-de/impressum currently has no redirect destination. An Impressum is legally mandatory in Germany; this is a compliance defect, not an SEO detail.
• "#1 Selling Home Charger" and "4.5/5 (2,400+ reviews)" are substantiation-required claims in most markets.
• Trusted-by logos and named customers (IKEA, Stanford, Stripe, Airbus, Disney, Target, VW, Porsche) need usage clearances we haven't seen.

5. Naming decisions hiding in the material

• "Retail" vs "Retailers"; "Charging Lounges" vs "Corridor Charging Points" — bracketed alternatives in the client's own nav CSV
• "Home" (consumer) vs "Residential" (B2B multifamily, nested under Industry) — a genuine collision that will confuse both audiences and search
• "Home Flex Plus" — a product name that exists only in a prototype
• Product naming drift in mocks: "Next-gen Express," "Express Solo" (600kW), "Depot Charging - AC," "FlexPro," "FlexPlus" — several appear nowhere in the strategy documents; the product taxonomy needs one owner
• "chargepoin+" wordmark with inconsistent "point" colour on dark backgrounds
• The company's own effect terminology wobbles ("neomorphism"/"skewmorphism") — trivial, but symptomatic of guidelines that haven't been edited

Part two: how the brand should translate into the website

This is the part V1 under-served. A brand doesn't live on a website as a logo and a palette; it lives as behaviour. The strongest thing about this particular brand material is that it already implies a behavioural idea, and nobody has named it yet.

6. The brand's core behaviour: show the math

Look at what the best material has in common. The retail campaign's whole argument is measurement honesty. The AFTERNOW "clear light" UI direction leads with "The numbers your finance team will ask for, in the open." The approved homepage hero is an ROI claim. The GA architecture refuses vanity tracking. The playbook's tone spec says "specific and credible."

That convergence is the brand idea in experience terms: ChargePoint is the company that shows the math. If we adopt that as the site's design-and-content principle, it makes dozens of downstream decisions for us:

• Proof modules (stat cards, payback figures, worked examples with visible assumptions) become the signature component family, not decoration
• The estimator stops being a nice-to-have feature and becomes the brand's central proof act; if it can't ship by 30 Nov, a transparent static version (a worked example per format, assumptions listed) holds the position
• Every segment page follows the playbook's own logic as a page structure: buyer's problem → why it matters → outcome → the ChargePoint answer, with sourced numbers at each step
• Claims hygiene (section 3) stops being compliance housekeeping and becomes brand expression; an unsourced stat on this site isn't just risky, it's off-brand
• Even microcopy carries it: CTAs like "See what a spot earns" (already in the mocks) beat "Learn more" everywhere they can

This principle needs one paragraph of client ratification, then it becomes the brief for every page. It's also the cleanest way to reconcile the three top lines: "show the math" is what "Electrification that pays you back" does, and what "Intelligent Electrification" claims.

7. Voice carried by components, not just copy

On a component-built WordPress site, the design system is the voice as much as the sentences are. Worth agreeing with Sushanth's team as a shared content-design layer:

• A CTA taxonomy: one primary verb pattern for B2B ("Talk to an expert", "See what a spot earns"), one for home ("Shop", "Find an installer"), and a rule against generic "Learn more" except in tertiary positions
• Stat cards always carry a source line and as-of date as part of the component, so the design enforces the claims register
• The accordion/configurator pattern from the Tech Specs mocks as the standard way to layer depth: confident summary first, detail on demand — that's the plain-spoken register expressed structurally
• Microcopy standards for forms, errors, empty states and cookie consent in both registers; consent UX in the EU locales is a brand touchpoint, not a legal chore
• Photography and gradient use mapped to voice: editorial motion photography where we're being human (home, drivers), charts and worked numbers where we're being commercial (B2B) — the dark/light split in file 05 and this voice split should be the same decision

8. Audience coverage and the homepage tension

The material's centre of gravity is B2B destination charging. The equity data says the site's actual traffic and revenue are dominated by drivers and home buyers. The approved homepage is B2B-led. That can be the right call — the site is being pointed at the buyer ChargePoint wants more of, while consumers arrive with high intent and can be routed fast — but it must be a decision, not an accident of mockups. The 25 Sep hero video direction makes it explicit: Nikhil's guidance was roughly 70% B2B and fleet imagery, home charging reduced, and a B2B setting for the closing sequence, because retail, fleet, bus, delivery and logistics customers matter more commercially than home users. So the B2B lead is now a stated intention, not an accident. The consequence stands, sharpened: the homepage needs an unmissable home-charging route within the first viewport, and the home journey (the revenue engine) gets flagship-level content investment even though neither the homepage nor its hero film leads with it.

The persona gap runs the same direction: 82% of the playbook's persona work covers five destination segments, while fleet and the "Industry" branch (utilities, CPOs, OEMs, government) have no message work at all. Transit is now the exception — the side-project storyline is a complete message chapter, pending claims validation and permission to reuse it on the site. The rest of those pages will be written from product sheets unless the client extends the playbook, and that extension request is already in files 03 and 04.

Worth noting how the video session resolved the lifestyle-versus-B2B tension, because it's a reusable copy principle: lifestyle shown through operational contexts — a bus fleet serving families before it returns to charge, a full parking structure rather than a single garage. "Charge where life happens" can be told at fleet scale; that's the register the site's B2B pages should borrow.

9. Global is not translation, it's transcreation

Eight non-English locales survive the cut, and the brand has never been expressed in any of them. Decisions a global comms lead would force now:

• Which brand lines translate, which stay English, and which need transcreation. "Electrify my fleet" may work in German nav space; "Electrification that pays you back" almost certainly needs a native line, not a translation. "Charge tonight. Go anywhere tomorrow" lives or dies on rhythm
• Claims differ by market: US tax credits, German comparative-advertising law, per-market network stats (a "70,000 locations" claim reads differently in the Netherlands). The claims register needs a locale column
• Who approves translated headlines — a native-speaker brand reviewer per locale, not just a translation vendor
• English-first launch with locales following is a legitimate phasing answer, but it must be chosen, scheduled and reflected in the redirect plan, not discovered in November

10. 30 November is a brand debut, not a cutover

Somebody wakes up on 1 December and sees a new ChargePoint: new identity, new voice, new architecture. Right now no received document plans that moment. Questions to put on the table early, because several have long lead times:

• Is there a coordinated reveal (press note, LinkedIn from Rick Wilmer, customer email, investor page alignment), or a quiet switch? Either is defensible; unmanaged is not
• The hero video is the debut's opening shot: the first moving expression of the new brand, on the most-visited page, looping. It should be treated as a launch asset with launch-asset review (client, brand, legal), not as a page component that happens to move
• What happens to every touchpoint that isn't the website on 1 December: sales decks, email signatures, social profiles, the driver app, signage on 400K+ physical ports that will carry the old identity for years? The old-brand/new-brand overlap needs a stated policy, because the hardware guarantees the two identities coexist in public
• The blog and press archive migrate "as is", meaning years of old-brand voice sit under the new identity from day one; the archive treatment (clear dating, no retrofitted claims) is part of the debut story
• Every migrated page needs a new-brand OG/social image at cutover, or the first thing people share from the new site renders with broken or old-brand cards
• Internal enablement: ChargePoint's own teams need the one-pager on what changed and why before their customers ask them

11. Governance: one brand, three design sources, named stewards

Design authority is currently split across Sushanth (redesign lead), Uprisal (staged retail and investor pages, approved homepage sections) and AFTERNOW (brand system, home product pages), with the client herself commissioning work directly. Without a governance rhythm, the site ships speaking three dialects of a brand that isn't finished being defined.

Proposal, using the clarified team structure:

• One named brand steward for the website (logically Sushanth for visual, Noella/Vilasini for verbal), with the authority to send work back that breaks the system
• A weekly cross-track design review while AFTERNOW, Uprisal and the redesign run in parallel; the shared component inventory from file 05 is its working artifact
• The claims register and voice standard as the two gate documents for copy; nothing publishes that doesn't clear both
• WordPress editorial roles configured to match: stat blocks and boilerplate locked to stewards, page copy editable by the wider team
• AFTERNOW's unfinished guidelines treated as upstream input, not gospel; where the website team makes rules AFTERNOW hasn't (accessibility matrix, motion spec, colour-usage ratios), we hand them back as contributions to Guidelines V02

12. What the brand system is still missing that comms needs

• Written photography principles (references exist, rules don't) and an owned image library
• Logo usage rules, clear space, minimum sizes, don'ts
• Accessibility guidance; contrast pairs and type sizes (file 05 flags likely WCAG failures in the current palette usage)
• A boilerplate kit: about paragraph, legal footer, press boilerplate, product descriptor lines
• Social/OG image templates for the new brand
• The transcreation decisions from section 9, written down per locale

Recommended sequence

How I'd run the brand-and-content side of the next ten weeks, in order, alongside the P1 chase list in file 03:

1. Ratify the top-line hierarchy and the "show the math" principle with Sonali and Michelle (one meeting, one page of minutes)
2. Draft and ratify the voice standard and the claims register (we author, client ratifies; both become gate documents)
3. Build one flagship page end to end — copy, design, data, in WordPress — as the reference standard. The retail landing page is the obvious candidate: it has the most complete material behind it and a staged Uprisal version to beat. Every argument about voice, components and claims gets settled once, concretely, on this page
4. Scale by system: templates and block library carry the decisions to the other pages; segment copy written playbook-first, home journey written against the ratified claims register
5. Plan the debut (section 10) in parallel from mid-October, so launch comms aren't invented in the last week
6. Localization pass per the transcreation decisions, phased if the plan of record says English-first

The thing to hold onto: this project's biggest brand risk isn't bad material, it's unratified material shipped at speed by three design sources and four voices. Everything above is a mechanism for turning good-but-loose inputs into one governed system before ten weeks of production locks them in.

ChargePoint: company and industry briefing

Prepared: 25 September 2026 (V3: adds transit specifics from the 25 Sep side-project documents — the Eaton division of labour, the Big Blue Bus deployment, the AI tooling. 24 Sep: revised twice same day; dug deeper into financial arc, corporate history, leadership, strategic position and risks) Purpose: everything the website team needs to understand about ChargePoint's business and its industry to write, design and build credibly for them. Read this before touching a page. Sources: the project's full briefing material set, SEC filings, company releases and industry reporting. Where internal documents disagree on a number, this file uses the only properly dated figures and says so.

One paragraph

ChargePoint is one of the world's largest electric vehicle charging networks, founded in 2007 in Silicon Valley and publicly listed since 2021. It mostly doesn't own chargers and doesn't primarily sell electricity. It sells the picks and shovels: charging hardware, the recurring software that runs it, and support services, to businesses and property owners who install charging on their own sites and keep the revenue. Around that sits a driver-facing network and app connecting hundreds of thousands of ports across North America and Europe. The company is mid-turnaround: after riding the 2021 EV boom to a $507M revenue peak, it has been through a CEO change, three rounds of layoffs, a reverse stock split to protect its NYSE listing, and a deliberate pivot from selling boxes to selling software — and it is launching its biggest product cycle in years (the Eaton-powered Express platform) in the same window as this website. The rebuild is not cosmetic; it's part of the relaunch of the company.

Corporate facts

The fiscal year runs February to January, so "FY2026" mostly describes calendar 2025.

The company's arc, and why it matters for this project

The trajectory in one table:

Read that arc and the briefing material snaps into focus. The company over-expanded into a demand curve that flattened, then spent two years cutting costs, protecting the balance sheet and pushing the revenue mix toward software (hardware shrinking, subscriptions growing 13% with rising margins — the installed base of 400K+ ports is the annuity the whole equity story now rests on). The current management's turnaround narrative is: costs controlled, margins rising, losses narrowing, next-generation products arriving, path to profitability.

Three practical consequences for the website team:

1. The ROI-first messaging isn't a stylistic choice, it's the corporate strategy speaking. "Electrification that pays you back," Revenue Per Spot, "the numbers your finance team will ask for" — a company selling a profitability story to Wall Street sells a payback story to customers. Every page should assume a skeptical, spreadsheet-holding reader, because that's who ChargePoint itself now answers to.
2. The site launches into an investor-sensitive moment. A recently reverse-split, loss-making public company gets zero benefit of the doubt on inflated claims. The claims-register discipline (file 06) is not pedantry; unsupported numbers on this site carry real securities-adjacent risk.
3. The rebrand plus the website plus the product cycle are one event. The Eaton-powered Express platform opens orders in early 2026 with deliveries in the second half of 2026 — essentially alongside this site going live. The new site is the launch vehicle for the company's next act, which raises the stakes and argues for product pages built to carry a major launch, not just migrated content.

Corporate history in brief

Founded as Coulomb Technologies in 2007 by Richard Lowenthal and colleagues, before there was a meaningful EV market; the earliest press releases in the company's own archive still carry the Coulomb name. Renamed ChargePoint in 2011 under Pasquale Romano, who ran the company for twelve years through its growth phase and 2021 listing. Went public in February 2021 via SPAC merger.

The 2021 European acquisitions built the EU business and still shape it:

• has·to·be (Austria, ~€250M, October 2021) — brought be.ENERGISED, a white-label charging-management platform used by European charge point operators. This is why ChargePoint has a real CPO-software business in Europe that doesn't exist in its North American model, and why the German be.ENERGISED page is one of the site's biggest backlink assets (605 referring domains).
• ViriCiti (Netherlands, ~€75M, August 2021) — eBus and commercial-fleet telematics and electrification monitoring. This is the origin of the fleet telematics offering and much of the transit/bus credibility (pantograph charging, depot management).

Rick Wilmer arrived as COO in July 2022, became CEO in November 2023 when the board asked Romano to step down, and has run the retrenchment since. In 2025 the company announced the Eaton partnership — an industry-first pairing of EV charging with intelligent power management, co-developing vehicle-to-everything (V2X) technology and giving ChargePoint access to Eaton's distribution channels across North America and Europe.

What's new in the product pipeline (and landing alongside the website)

The 2025-2026 announcements define what the new site will actually have to sell:

• A new AC architecture with bidirectional charging built in, underpinning future AC models across commercial, residential and fleet variants in both regions — the eventual successor generation to CT4000/CP6000/Home Flex
• ChargePoint Express Grid, powered by Eaton — V2X-capable DC platform delivering up to 600 kW for passenger EVs and megawatt-class charging for heavy commercial vehicles, integrating charging with storage, solar and demand response
• Express availability: orders for select customers from Q1 2026, deliveries beginning H2 2026 — i.e., the launch window of this website

This explains details in the brand mocks that otherwise look like fiction: the "Express Solo — 600 kW" announcement bar, "Next-gen Express — partnership with Eaton" in the mega-menu, V2G and "AI Assistance" in the footer. They're previews of the pipeline. The open question for us is which of these are announced and sellable by 30 November — the product-naming confusion flagged in file 06 (Express Solo vs Express Grid vs Express Plus, "FlexPlus", "Home Flex Plus") is really a question about how much of the 2026 roadmap the site launches with.

The industry, explained

You can't write this website well without understanding how the charging business works. This section is the industry from a standing start.

Where charging happens, and why that shapes everything

Roughly 80% of EV charging happens at home, overnight. Another slice happens at workplaces. Public charging is the minority of sessions, and for most drivers a preference or top-up, not a necessity. ChargePoint's own retail deck is unusually honest about this: "public charging is a preference, not a need... A preference gets met at the place that earns it."

That single fact structures the market:

• Home is the volume game: a Level 2 charger for every EV buyer.
• Workplace and destination charging (retail, hotels, campuses, apartments) works because the car is parked there for hours anyway. The charger attracts and holds customers, tenants and staff, and earns on the side. Speed matters less; the car has time.
• En-route fast charging (highway corridors, fueling stations) is the only segment where charging is the destination. Speed is everything, utilization is the business model, capital costs are brutal.
• Fleet is its own world: depot charging on predictable duty cycles, route top-ups, and (ChargePoint's angle) reimbursed charging at the driver's home.

The internal material splits public charging into two modes worth memorising because the messaging depends on them: destination ("they were coming anyway; charging decides where") and en route ("the charge is the reason the stop happens at all").

The technology tiers

• Level 1: a wall socket, ~5 miles of range per hour. Commercially irrelevant.
• Level 2 (AC): 7 to 19.2 kW. The workhorse for home, workplace and destination; full charge overnight or across a workday. CT4000, CP6000, CPF50 and Home Flex live here. Relatively cheap to install, gentle on the grid.
• DC fast charging (DCFC): 50 to 600+ kW. Minutes, not hours; the highway and depot tier. The Express family lives here. DC stations cost an order of magnitude more, often need utility upgrades, and only pay back with high utilization.

kW is charging speed; kWh is energy delivered. Site economics turn on utilization and on avoiding electrical upgrades — which is why power management is ChargePoint's most repeated proof point: 30 to 40+ chargers on a panel that would otherwise support 8 to 10, avoiding a $200K-500K panel upgrade. "The single biggest cost objection killer in destination charging."

The connector wars, mostly over

North America spent a decade with competing plugs: J1772 (AC), CCS (DC), and Tesla's connector. In 2023-2025 the industry standardised on Tesla's design as NACS; Ford, GM, Toyota, Hyundai, Kia, BMW, Rivian and others now ship or have committed to NACS vehicles, and Tesla's Superchargers have progressively opened to all EVs. For ChargePoint this cuts both ways: Tesla's exclusivity moat erodes (good), but its famously reliable network now competes for every driver (bad). ChargePoint's answer is Omni Port — J1772/CCS and NACS on one station, so a site owner never bets on a connector. Europe standardised earlier (Type 2/CCS2); no equivalent war.

Behind the plugs sit software standards that surface in B2B buying conversations: OCPP (charger-to-software protocol, the basis of "works with hardware that isn't ours"), OCPI/roaming (network interconnection, the basis of "992,000+ additional places to charge"), and Plug & Charge / ISO 15118 (the car authenticates itself).

Who's who in the value chain

• Hardware manufacturers build chargers (Alpitronic, ABB, ChargePoint itself)
• CPOs (charge point operators) own/operate stations and sell electricity (EVgo, Electrify America, IONNA, Tesla)
• eMSPs (e-mobility service providers) own the driver relationship: app, account, payment
• Software enablers sell white-label charging platforms (AMPECO, Monta, Driivz; ChargePoint's be.ENERGISED plays here in Europe)
• Site hosts own the real estate and, in ChargePoint's model, the chargers too
• Installers deploy everything; a certified channel in its own right
• Utilities supply power, fund make-ready infrastructure, offer rebates

ChargePoint spans four roles at once — hardware maker, software platform, eMSP, services provider — while deliberately not being a CPO at scale. That's the "vertically integrated but open" positioning, and the asset-light choice is why its balance sheet looks nothing like EVgo's.

The two business models, and the fight between them

• Owner model (ChargePoint's): the site host buys the hardware, subscribes to the software, sets prices, keeps 100% of charging revenue, owns the customer data and brand experience. ChargePoint gets equipment margin plus recurring SaaS either way.
• Third-party operator model: an operator (EVgo, EA) installs and runs chargers on the host's land, typically free to the host, keeping the revenue and the customer relationship.

ChargePoint's retail material names the operator model, not any single company, as "the real competitor," and the Retail Marketer document sharpens it: retailers who own their gas stations already understand owning the fuel relationship; surrendering EV charging to an operator surrenders pricing, revenue, brand and data. Expect this argument to structure most B2B pages.

Money from governments: the incentive layer

• NEVI (the US federal highway-charging program, $5B) froze in 2025, then rebooted with new guidance; the FY2026 apportionment of $885M is flowing to states again, with 97% uptime and 150 kW minimums attached.
• Section 30C federal tax credit (up to 30% of install cost) had its expiration moved up to 30 June 2026 — already dead as an urgency hook, though it still appears in the playbook and the home-page prototype. The current publishable incentive story needs legal confirmation.
• State and utility programs: hundreds of rebate and make-ready schemes — the reason the current site maintains 456 incentive pages, a genuine SEO moat and a real buyer service (incentives can cover 50-80% of install costs in some segments).
• Europe: the AFIR regulation drives buildout with payment-transparency rules; GDPR governs the site experience itself in EU locales.

Industry weather, September 2026

US EV sales growth has slowed from the 2021-2023 pace: EVs took 8.1% of new US light-vehicle sales in 2024, volumes rose through 2025, but share slumped to 5.7% in Q4 2025 after federal purchase incentives shifted — the clearest single signal of the demand wobble pressuring the whole sector. Charging infrastructure still grows fast regardless (US public ports past 253,000 by mid-2026, up ~17% in a year). NACS consolidation is nearly complete. Electrify America has been reported up for sale; IONNA (the eight-automaker joint venture) is scaling toward a claimed 30,000 bays by 2030. Bidirectional charging (V2G/V2H) is crossing into commercial reality — the reason Eaton, solar and storage keep appearing in ChargePoint's material. ChargePoint's posture in this weather: costs cut, margins up, software-led, new product cycle incoming.

ChargePoint's business, in detail

The commercial engine

The core insight: ChargePoint's paying customer is usually not the driver. The customer is the business that installs charging on its property. Three revenue layers sit on that relationship:

1. Hardware — stations bought outright ($216.5M in FY2026, declining as competition bites and the mix shifts)
2. Software subscriptions — pricing, access control, power management, reporting ($162.4M, growing 13% a year; the margin engine, the moat, and the part of the business investors are told to watch)
3. Services — the Assure and Care warranty/support families, turnkey deployment, installer certification

The network wraps around the B2B engine: the driver app, roaming, Plug & Charge. Drivers cost little to serve and make every port more valuable to the next site owner. The flywheel: more sites attract more drivers; more drivers make sites pay back faster; faster payback sells more sites. The company reports across three verticals — commercial, fleet, residential — in North America and Europe.

The offer, product by product

AC hardware (Level 2): CT4000 (the long-serving commercial workhorse), CP6000 (current flagship commercial AC, up to 19.2 kW, 50A/80A, the hero product of the new brand material), CPF50 (entry/multifamily), Home Flex (residential, up to 50A). A next-generation bidirectional AC architecture is announced and will succeed these. Mocks reference "Home Flex Plus" with NACS — unconfirmed as a launching product; flagged to the client.

DC hardware: Express 250 and 280, Express Plus (bannered at 500 kW), and the Eaton-era platform: Express Grid (V2X, up to 600 kW passenger / megawatt heavy-duty, integrated with storage and solar), with pantograph charging for transit and a Megawatt Charging System for trucks. "Express Solo" (600 kW standalone) appears in mocks; verify its announcement status before it appears on the site.

Software: station and network management (CMS suite), power management, dynamic pricing and member rates, waitlist, telematics (the ViriCiti inheritance), utilization/revenue reporting, and be.ENERGISED serving European CPOs white-label (the has·to·be inheritance).

Services: Assure, Assure Pro, Assure Assist, Safeguard Care, Premier Care, Premier Deployment — tiered warranty, monitoring and deployment offerings pitched by risk appetite. Plus installer training and certification ("certified in all 50 states"; consumer material claims 2,000+ certified installers).

Scale, with a health warning

The only properly dated figures in the material (messaging playbook, "as of April 30, 2026"):

• 406,000+ activated ChargePoint ports
• 453 million+ charges delivered
• 992,000+ additional roaming ports accessible to drivers
• 82% of the Fortune 50 are customers

Other documents circulate 400K, 375K and 250K ports, "5,000+ brands," "64% of Fortune 500," "23 billion electric miles," "19 years." The conflicts are unresolved, the company is publicly traded and freshly reverse-split, and no scale figure should reach production copy without the claims register (file 06).

Who ChargePoint speaks to, in depth

This is the section to internalise if you'll be writing or designing pages. Five audiences use the website. Two of them buy, one of them drives the traffic, and two are watching.

How a B2B charging deal actually happens

Before the personas, the shape of the sale, because the website has a job at every stage:

1. Trigger — an executive mandate (sustainability pledge, tenant demand, a competitor's install, fleet electrification order), or an incentive program with a deadline
2. Research — a mid-level owner (facilities, real estate, operations) is told to "look into charging." This is the website's biggest B2B moment: this person needs to understand the category, the models (own vs operator), the costs, and come back with a credible recommendation
3. The committee forms — typically real estate/leasing, facilities/energy, finance, sustainability, operations, IT/security, sometimes HR and legal. Each holds a partial veto; each needs different proof
4. Site assessment — electrical capacity survey, utility engagement, make-ready applications. This is where the panel-upgrade fear lives and where power management wins deals
5. Incentive hunting — federal, state and utility money can cover 50 to 80% of install costs in some segments; buyers expect the vendor to navigate this (which is why 456 incentive pages exist)
6. Procurement and install — certified installers deploy; timeline months, not weeks
7. Operation — the subscription relationship: pricing, access rules, reporting, support. Renewal and expansion is where ChargePoint's economics actually live

Total cycle: months to well over a year for portfolio deals. The website's B2B role is stages 2 and 3: arm the internal champion, then give every committee member their proof. That's why the playbook's message logic is "lead with the buyer's business problem, prove why it matters, show the outcome, then the ChargePoint answer."

The people in the room: recurring B2B buyer roles

The playbook maps 18 personas across its segments, but the same roles recur in nearly every committee regardless of vertical. Content should be written to these people, because they are who actually reads the pages. For each: what they own, what keeps them up at night, and what wins them.

Two production notes on these roles. First, the playbook already carries approved one-line value messages and CTAs per role (its "Value messages by buyer role" tables) — use those as the starting point rather than inventing new ones. Second, several personas list "Proof needed" items that are still open (a dwell/basket-size study, a 3-year payback model, a CSRD reporting template); where a page's argument depends on missing proof, that's a flag for the client, not a licence to improvise.

The five active campaign segments, one by one

These are the segments with ratified messaging in the "Charge Where Life Happens" playbook. For each: the approved rally cry, the market logic, who's in the room, and what they need to believe.

Workplace — "A New Reason to Drive In: EV Charging." The logic: 68% of charging happens at home or work; the office is the second-biggest charging location in a driver's life, and return-to-office gives employers a reason to sweeten commutes. The playbook's stat: 98% of employees without workplace charging want it. Buyers: heads of workplace/facilities, HR (charging as a benefit), sustainability officers, finance. Their questions: cost per employee served, panel capacity, who pays for the electricity, fairness (waitlists when demand exceeds ports — a real workplace politics issue ChargePoint's waitlist software addresses). Charging here is an amenity and retention tool, not a revenue line.

Retail — "Turn Charging Time Into Store Revenue." The commercial heart of the current campaign. The logic: a charging customer is captive for 30 to 50 minutes, and that dwell converts to basket size; grocery-adjacent chargers average 42 sessions a day, 41% of drivers prefer charging at supermarkets and shopping centres, yet only 6.7% of fast chargers sit near a grocery store. The gap between driver preference and charger placement is the pitch. Buyers: VPs of real estate, retail marketing leads, operations, finance. Account-level FOMO is approved messaging ("Target and Walmart Are Building the EV Shopping Habit. Are You?"). The campaign's proprietary metric, Revenue Per Spot, models $5.1K/year per spot (malls) up to $41.6K (QSR), and the segment offer is a "Retail EV Revenue and Site Opportunity Map." Caution: the dwell and spend-uplift numbers conflict across documents; only the claims register version ships.

Fueling and Convenience — "The Fuel Changed. The Customer Is Still Yours." The existential segment: gas stations are declining ~1.4% a year and fuel margins are pennies, while a 20-minute DC fast charge creates an $8-12 c-store transaction at 50%+ gross margin, against roughly $0.05/gallon profit on gasoline. C-stores sit within 10 minutes of 90% of US households — the real-estate advantage nobody else has. Buyers: fuel retail operators, VPs of operations, category managers. Their mindset: fuel people who understand throughput and margin, being asked to bet on a new fuel. This segment overlaps awkwardly with the retail campaign's QSR-on-the-interstate framing — a scope conflict flagged in file 02.

Universities — "One Campus. Not Five Charging Networks." The logic: campuses accrete point solutions (a few chargers from one vendor per building or parking structure) and end up managing five networks badly. 82% of universities hold a carbon-neutrality pledge, AASHE STARS scoring rewards charging, and grants can cover 50 to 80% of install costs. Buyers: facilities and transportation directors, sustainability officers, finance/administration. The offer: a "Campus EV Charging Master Plan." Long procurement cycles, RFP-driven, consensus-heavy.

Commercial Real Estate — "The Charger Is Easy. The Portfolio Model Is Hard." The most sophisticated buyer. The logic: a single install is trivial; a defensible model across a 40-building portfolio (which sites first, what tenants pay, how it appears in NOI and GRESB reporting) is the hard part, and the pitch is that ChargePoint brings the model, not just hardware. Claims in play: 3 to 8% rent premiums for charging-equipped properties. Buyers: CRE investment and asset managers, leasing, sustainability, building operations. Note: the playbook's urgency hook here (the Section 30C deadline) has already expired and must not ship.

Multifamily is archived from the campaign but alive on the site and in the nav ("Residential" under Industry). The underlying story is strong — roughly 5% of multifamily properties offer charging against massive renter demand — so expect the client to revive it; the brand mocks already use the 80%-home/5%-multifamily stat.

The other thirteen verticals

Live on the current site with dedicated pages but no current campaign messaging: healthcare, hospitality, entertainment and stadiums, cities and towns, federal and state agencies, parking operators, auto dealerships, automakers (OEM partnerships), utilities, HR, and education below university level. They cluster into four content families — property-adjacent (borrow from CRE/retail logic), public sector (procurement- and grant-led, uptime-mandate sensitive), auto trade (dealerships need charging to sell EVs; automakers are partners more than customers), and utilities (simultaneously customer, funder and channel). Until the client extends the playbook, copy for these pages gets derived from the strategy document plus product material — a defined gap in files 02 and 03.

Fleet buyers

A different species from site owners: they charge their own vehicles, and the money question is total cost per mile, not revenue per spot. Three sub-audiences in the new nav: delivery and logistics fleets (depot charging on duty cycles, uptime is everything — a van that can't charge doesn't earn), transit (buses, pantograph charging, the ViriCiti telematics inheritance), and motor pools/company vehicles (the quiet one — reimbursed home charging via Home Flex, "company managed, reimbursement automated"). Autonomous-vehicle fleets appear in the new nav as a fourth. Roles: fleet operations directors, procurement, sustainability, finance, and the drivers themselves (whose home charging becomes an HR/payroll matter). ChargePoint's claimed edge: the only player covering depot, en-route and driver-home in one platform. Fleet content must speak operations language — duty cycles, uptime SLAs, energy cost management — not amenity language.

The 25 Sep transit documents put flesh on this. The transit pitch is a system story ("Beyond the Charger"): Eaton power infrastructure → ChargePoint DC fast chargers → CMS Suite → ViriCiti telematics → fleet operations software, sold on the 2:00 AM problem (a charger faults overnight, buses miss the 5:00 AM pullout, vendors point fingers) and on energy economics (a claimed 30–70% reduction in peak demand charges through managed charging — conditional on approval for external use). The flagship deployment is Santa Monica's Big Blue Bus: $56M committed to electrify a 195-bus fleet by 2032, 130 DC fast-charging ports on the Express Plus platform with overhead gantries, 10M+ annual rides, largely funded by a $53.3M state grant — which also illustrates how transit deals get financed. Supporting claims in circulation, all pending validation: "70+ transit organizations," an AI Data Assistant, and an AI Installer Toolkit said to automate up to 95% of activation tasks. None of this is approved for external use yet, but it is the best picture of the fleet/transit business the project holds.

Drivers and home buyers: who actually is the 2026 EV driver

The audience that generates most of the site's traffic and its direct revenue. Worth being precise about who they are, because the picture is shifting:

• The installed base skews affluent, educated, suburban homeowners — multi-car households with a garage. Research consistently shows homeownership is a stronger predictor than income alone: among $75-100K households, homeowners are roughly three times likelier than renters to own an EV. This is ChargePoint Home's natural customer: they have a driveway, a panel, and a tax accountant.
• The market is mainstreaming. EVs passed ~8% of new US registrations in 2024 and adoption is diversifying. The next buyer is more pragmatic and less forgiving than the early adopter: less willing to tinker, more anxious about compatibility and installation, more price-sensitive, more likely to comparison-shop against a $429 EVIQO on Amazon. This is exactly why the client's product-page brief obsesses over ratings, "top ranked on Amazon," ease, and decision reinforcement.
• The renter/apartment driver is the structurally underserved group — can't install a home charger, depends on workplace, public and multifamily charging. They're simultaneously a driver-support audience today and the demand argument behind the multifamily and workplace B2B pitches.

Distinct driver mindsets the site serves, each with different content needs:

1. The home-charger shopper — consumer-electronics buying behaviour: which charger fits my car (NACS vs J1772 anxiety), what does installation involve and cost, what rebates exist, will it survive outdoors, what do reviews say. Journey per the client's brief: want a solution → see options → top features → validate fit → easy install → support. High purchase intent; the site's second-biggest revenue engine after the homepage.
2. The new EV owner onboarding — just bought the car, often arriving via OEM co-branded pages (Toyota, BMW, etc.); needs charging-101, app setup, activation. Retention content, and the top consolidated-FAQ queries prove it ("how do I start a charging session," "how do I charge my Tesla").
3. The network user — an app-first relationship; the website is their support desk (pricing policies, session problems, etiquette, connector questions). 21,500 conversions a year ride on this content.
4. The incentive hunter — arrives from search on rebate queries into the incentive pages; often a shopper one step earlier in the funnel.

Installers and channel partners

Electricians and contractors who deploy everything. Small audience, outsized leverage: the consumer's installation experience is ChargePoint's brand in their garage, and B2B deployment timelines depend on certified capacity. The training/certification track is their hub (and carries real organic traffic — 8,869 clicks). The unresolved /installer-app redirect (1,964 clicks, no destination) belongs to this audience.

The watchers: investors, press, job seekers

Not buyers, but a company that has been through a reverse split, layoffs and a CEO change is watched closely. Investors get a separate surface (deliberately excluded from marketing analytics), but everything public-facing feeds the turnaround narrative — which is the deeper reason claims discipline matters. Press and analysts use the 491-release archive and 63 leadership profiles (profiles currently slated to redirect to /about, with the CEO's own profile among the unconfirmed redirects). Job seekers are a real audience too: the careers section carries 10K+ organic clicks, and a company rebuilding morale after three layoff rounds needs its employer story intact.

One table to keep on the wall

The recurring anxieties across all B2B buyers, for quick reference: ROI and payback; electrical capacity (the $200K-500K panel-upgrade fear, answered by power management); ownership and control versus the operator model; reliability and uptime; future-proofing (connectors, V2X-readiness, stranded assets); sustainability reporting (GRESB, AASHE STARS, CSRD); and, for retail specifically, dwell and spend uplift — whose figures conflict across documents and must come from the claims register.

Competition

Claimed position: the "Open Ecosystem Leader" — the only company serving drivers, fleets and site owners at once, vertically integrated like Tesla but open. In actual deals the enemy is usually the third-party operator model, not a logo.

ChargePoint vs Tesla: the comparison that matters

Tesla deserves more than a row in the table, because it's the comparison every buyer and every driver silently makes, and because Tesla's strategy shifted in a way that lands directly on ChargePoint's turf.

Two opposite architectures. Tesla runs a closed, vertically integrated network it owns and operates: 8,182 stations at the end of 2025 by Tesla's own count, tracking toward ~8,700 stations and 80,000+ stalls by mid-2026 per network trackers (Tesla's official round number is 75,000+ Superchargers). Its famous 99.95% uptime is self-reported, from Tesla's Impact Report, and measured as the share of sites with at least half their chargers functional — site-level availability, not per-charger reliability. Still the industry's best number, but a softer claim than it sounds. ChargePoint runs the opposite model: 406K+ ports owned by its customers, spread across vastly more locations, mostly AC destination and workplace charging rather than DC corridors. On paper they barely compete — Tesla owns highway fast charging, ChargePoint owns the parking lot where the car sits for hours. In practice the lines are collapsing from both sides.

Tesla is coming into ChargePoint's market. Two moves matter. Tesla started selling its charging hardware to other operators with a $100M order from bp pulse in 2023 — bp brands, installs and operates those chargers itself, with NACS and CCS connectors — and has since reportedly opened Supercharger sales to businesses generally, with the host branding the stations and keeping the revenue while Tesla handles operation. And "Wall Connector for Business" puts Tesla AC hardware into commercial destination sites, adding over a thousand chargers at commercial locations in recent months. Both are direct moves onto the owner model that is ChargePoint's core pitch, from the one brand with a stronger charging reputation.

Where Tesla is genuinely stronger, and copy shouldn't pretend otherwise: reliability reputation (its self-reported 99.95% site uptime is the industry benchmark, and "every buyer has seen a broken charger" mostly means a non-Tesla one); driver experience (native plug-and-charge seamlessness); brand gravity with consumers; and now the NACS standard itself, which is Tesla's connector in everyone else's car.

Where ChargePoint wins, and the site should press:

• Neutrality. A retailer, employer or municipality installing Tesla-managed infrastructure hands its charging experience, and its data relationship, to another consumer brand — one whose CEO is a polarising public figure, which is a real (if unspoken) factor in corporate procurement. ChargePoint white-labels to the host's brand and hands over the data.
• Universality by design. Omni Port serves NACS and J1772/CCS natively; nobody's employee or customer is turned away, no adapter politics.
• Software depth for the operator. Pricing controls, access rules, waitlists, power management across mixed hardware fleets, ESG-grade reporting — the management layer Tesla's host offering doesn't attempt.
• The full estate. Tesla covers fast charging and a wall box; ChargePoint covers AC + DC + fleet depot + telematics + driver-home reimbursement + roaming under one platform and one support contract.
• Fleet and Europe. Depot operations, transit/pantograph, the ViriCiti telematics layer, and the be.ENERGISED CPO business have no Tesla equivalent.

The website implication: "why not just get Tesla?" is now a live objection on B2B pages, not a hypothetical. The answer the material supports is ownership, neutrality, universality and software depth — never a reliability comparison, which ChargePoint loses. On the consumer side, Home Flex vs Tesla Wall Connector is fought on universality (any EV, both connectors) and network/app integration; on the driver side, roaming and NACS compatibility mean the honest message is "we work alongside the Superchargers," not against them.

Where ChargePoint is going: focus, targets and growth areas

What management has actually said and guided, as of the 9 September 2026 earnings call — useful because the website launches into this exact narrative:

The stated focus is operating leverage on a stabilised cost base: pricing discipline, a revenue mix shifting to higher-margin software, and a "path toward positive adjusted EBITDA" — deliberately without a committed date. Wilmer also claims software engineering productivity has doubled through AI adoption, which is management shorthand for: more product, flat costs.

The scoreboard they're pointing to: adjusted EBITDA loss down to $4.8M in Q2 FY2027 (from $22.1M a year earlier), the adjusted quarterly loss cut 72%, and Q3 revenue guided to $105-115M — roughly 4% growth at the midpoint, the return to top-line growth after two shrinking years. The market has noticed (the stock rallied ~70% around the results). No formal long-range targets are published; guidance is quarterly, and profitability remains a direction, not a date.

The growth vectors, ranked by how visible they are in the material:

1. Subscription attach on the installed base — 400K+ ports already in the field, each a candidate for more software and higher service tiers. This is the margin story and the moat.
2. The Eaton-era DC product cycle — Express Grid and the 600 kW platform (demonstrated moving a passenger EV from 10% to 80% in 11 minutes) take ChargePoint upmarket into fast charging, where it has historically been weak, with orders from Q1 2026 and deliveries from H2 2026. This is the headline launch the website will carry.
3. V2X and energy management — bidirectional charging, storage and solar integration via Eaton; positions charging as grid infrastructure, a story utilities and CFOs both like.
4. Fleet electrification — commercial fleet conversion is early and contractual (multi-year, high-attach); the depot-route-home triangle is the wedge.
5. Europe — AFIR-driven buildout plus the be.ENERGISED CPO platform; a structural tailwind ChargePoint is already positioned for.
6. Whitespace segments the campaign is aimed at — retail (the entire Revenue Per Spot push) and, sooner or later, multifamily (~5% penetration against massive renter demand; archived from the campaign today, unlikely to stay archived).
7. The NACS transition itself — every site owner with legacy-connector hardware eventually refreshes; Omni Port makes ChargePoint the safe refresh choice.

The website implication: the site launches into a "turnaround taking hold" moment — there is real momentum to draw on (growth returning, losses collapsing, a flagship product cycle) and a management team highly sensitive to overclaiming while the story is still fragile. Momentum framing: yes. Victory laps and unsourced superlatives: no. Same claims-register rule as everything else.

Strategic risks a briefing should be honest about

• Demand: EV adoption growth has slowed in ChargePoint's biggest market, and hardware revenue is contracting
• Commoditisation: chargers are becoming interchangeable boxes; the defensible layer is software and network, which is exactly where Monta and AMPECO attack
• Tesla: the open Supercharger network competes for drivers, and Tesla now sells and manages charging for businesses — a direct move onto ChargePoint's owner-model turf (see the dedicated comparison above)
• Financial: still loss-making with a history of layoffs and a reverse split behind it; every public claim is scrutinised
• Execution: the Eaton product cycle has to land on time; the website will be selling some products before they ship

None of this is secret — it's in the filings — but it explains the company's tone: disciplined, ROI-obsessed, proof-first. The website should sound like a company that has been through the fire and knows its numbers, because that is literally the corporate story.

Partners and ecosystem

• Eaton — the defining partnership: co-developed V2X charging and power infrastructure, plus access to Eaton's electrical-distribution channels in both regions. The transit documents (25 Sep) state the division of labour cleanly: "ChargePoint manages everything from the charger to the bus; Eaton manages everything from the utility to the charger" — Eaton supplies the medium-voltage switchgear, switchboards, panelboards and engineering. The combined support/SLA language for the joint offer is not yet confirmed; avoid "one company to call" claims until it is
• Automaker (OEM) programs — co-branded driver onboarding and offers (Toyota, Nissan, Chevrolet, Honda, BMW historically; co-branded pages for Mazda, Harley-Davidson, Motortrend, Evergy)
• Roaming partners — the interconnection agreements behind the 992K+ figure
• Utilities — make-ready funding and rebates; a channel as much as a segment
• Certified installers — the deployment arm, all 50 states
• Consumer partnerships — an Apple Card cashback promo appears in brand mocks (expired September 2026; do not reuse)
• Named customers in circulating material — IKEA, Target, VW, Porsche, Sonepar, Stanford, Stripe, Airbus, Disney (logo clearances unverified)

Geography and languages

Operating markets: North America and Europe (14 or 16 countries per conflicting internal documents), with Europe built substantially on the 2021 acquisitions. The current website runs 17 locales; the rebuild keeps 9 — US English, en-gb, en-ca, fr-ca, fr-fr, de-de, nl-nl, es-es, it-it — together 99.4% of organic clicks. Germany is the strongest non-English digital market (the be.ENERGISED page holds 605 referring domains) and brings hard legal requirements (Impressum, strict comparative-advertising law). EU locales need GDPR-grade consent from day one.

Digital estate

• chargepoint.com — 5,637 indexed pages on Drupal/Pantheon today, rebuilding to WordPress for 30 November 2026. Traffic and revenue concentrate in the homepage and home-charging journey; content mass sits in press (491 releases back to the Coulomb era), incentives (456 pages), blog (340 posts) and support FAQs (1,427 articles, consolidating to one page per language)
• store.chargepoint.com — consumer commerce (Home Flex, accessories); outside the rebuild's page list, migration ownership unconfirmed
• Driver app (iOS/Android) — find/start/pay charging, home-charger control; its own analytics surface
• Investor site — a separate surface, and given the reverse split and turnaround story, one the company treats with care; Uprisal holds a rebuilt IR page on staging
• Engineering blog — small engineering-culture publication on the main domain

Glossary

• Port vs station vs spot — a station (physical unit) can have multiple ports (plugs charging simultaneously); a spot is the parking space. ChargePoint counts scale in ports; the retail campaign monetises spots. Don't mix them in copy.
• Level 2 / L2 — AC charging, 7-19.2 kW, hours to full
• DCFC — DC fast charging, 50-600+ kW, minutes to substantially full
• kW / kWh — speed / amount of energy delivered
• NACS / CCS / J1772 — connector standards; NACS (Tesla's design) has won North America
• Omni Port — ChargePoint's dual-connector answer
• CPO / eMSP — charge point operator (owns/runs stations) / e-mobility service provider (owns the driver relationship)
• OCPP / OCPI — open protocols: charger-to-software / network-to-network roaming
• Plug & Charge (ISO 15118) — the car authenticates itself; no app or card at the plug
• Make-ready — utility programs funding electrical infrastructure up to the charger
• NEVI — the US federal highway fast-charging program, rebooted 2026
• Section 30C — the (now-expired) US federal charging-infrastructure tax credit
• AFIR — EU charging-infrastructure regulation (payment transparency, card terminals)
• V2G / V2H / V2X — vehicle-to-grid / home / everything: bidirectional charging, the Eaton partnership's core
• Utilization — share of time a port is dispensing; the driver of DC economics
• Dwell time — how long a charging customer stays at a destination; the driver of retail's business case
• Power management / load management — software sharing a site's electrical capacity across chargers
• be.ENERGISED — ChargePoint's European white-label charging platform (via the has·to·be acquisition)
• Destination vs en-route — charging where you were going anyway vs stopping in order to charge

What all this means for the website, in seven lines

The business is shifting from hardware to software, so the site must sell a platform and a relationship, not a catalogue of boxes. The company is mid-turnaround and investor-watched, so every claim must be sourced and every number governed. The buyer is a committee with a spreadsheet, so proof, payback and worked numbers beat adjectives. The real competitor is a business model, so "own it" is an argument pages must actually make. The traffic is consumers, the strategy is B2B, so the home journey must be excellent and one click from a B2B-led homepage. Incentives and FAQs are unglamorous traffic machines whose templates deserve first-class treatment. And a major product cycle (Eaton-era Express, next-gen AC) lands in the launch window, so product pages must be built to carry announcements, not just migrate history.

Where each fact comes from

Corporate financials and history: ChargePoint FY2026 results, IR release, SEC 8-K FY2026, 8-K on CEO transition, Nov 2023, 10-K FY2024 (restructurings), SF Chronicle on the 2024 layoffs, reverse-split announcement, Fast Company on the reverse split. Acquisitions: electrive on ViriCiti and has·to·be, Silicon Canals on ViriCiti (€75M), Sustainable Bus on has·to·be. Eaton partnership and product pipeline: Eaton/ChargePoint launch release, ChargePoint V2G announcement, Q2 FY2026 results. Revenue history: S-1/FY2021 filings, FY2023 8-K. FY2027 momentum, targets and management commentary: Q2 FY2027 8-K, Q2 FY2027 earnings call transcript (Motley Fool), StockTitan on the 72% loss reduction, Yahoo Finance on the rally. Tesla comparison: EV Charging Stations Q2 2026 Supercharger report, Not a Tesla App on Supercharger business sales, Tesla commercial charging, Destination Charged on network reliability 2026. Industry status: GreenCars on the NEVI reboot, EV Range NEVI 2026 guide, U.S. News on NACS vs CCS, Paren US fast-charging Q2 2026. Everything else: the project briefing material as evaluated in files 01 and 02. Transit detail (Eaton division of labour, Big Blue Bus deployment, 30–70% demand-charge claim, "70+ transit organizations," AI Data Assistant and Installer Toolkit): the 25 Sep side-project documents — internal, pre-validation, not approved for external use. Scale figures use the playbook's dated April 2026 block; treat all others as unverified. Verification pass (24 Sep 2026): FY2022 revenue confirmed at $242.3M against the company's FY2022 results release; the bp/Tesla deal confirmed as a $100M hardware order that bp brands and operates itself, per bp's own release and Electrek; Tesla's 99.95% uptime confirmed as its own Impact Report figure measured at site level (The Driven); 2024 US EV share of 8.1% and the Q4 2025 dip to 5.7% per CarEdge/Cox data and CNBC; 253,319 US public ports (June 2026) per DOE-derived counts and the Joint Office. Facts sourced only from single blog-tier trackers (mid-2026 Supercharger stall counts, the "Tesla manages business Superchargers" program detail) are attributed as "reported" in the text and should not be republished on the website without a primary source.

ChargePoint Document Set: Evaluation

Reviewed: 21 September 2026 Files covered: 5 documents received from Uprisal (agency) via email, 21 September 2026 Scope note: a separate folder of roughly 24 brand and design assets ("ChargePoint — Client File") landed in the working directory partway through this review. It isn't covered here; see the note at the end.

What these files actually are

The routing email (Noella Cresence Mail - Chargepoint | Briefing Documents.pdf) is what makes sense of everything else. Vismaya MN at Uprisal sent four attachments to Noella and Vilasini Muralidhar on 21 September 2026 at 12:38pm, describing them as "everything we discussed," ahead of a same-day client meeting. So this isn't four independent documents. It's one agency's briefing package, built at least partly on a client-supplied source-of-truth playbook. A fifth attachment named in the email, Retail Marketer.docx, isn't in the folder. That's worth chasing before the meeting: it's the one file the email lists that nobody can currently open.

The email also links to a style guide and two live pages, chargepoint.uprisal.in/retail and /investors, which sit outside this review. Decks and shipped pages tend to drift apart fast, so those are worth a side-by-side check.

File by file

1. Messaging Playbook — Michelle Draft_Charge_Where_Life_Happens_Messaging_Playbook.pdf

Created: 11 September 2026, 15:12 PDT. Tool: Microsoft Word (confirmed in the embedded xmp:CreatorTool field), printed to PDF. Author field blank. The filename suggests a working draft attributed to someone named Michelle, most likely on the ChargePoint side rather than Uprisal's.

This is the client's own source-of-truth document: a large, structured playbook covering six segments (Workplace, Retail, Fueling and Convenience, Universities, Commercial Real Estate, and an archived Multifamily), each with approved rally cries, message hierarchies, buying committees, and 18 buyer personas. It's also the most heavily cited document in the set, pulling from Plug In America (2025), CBRE, J.D. Power, Electric Era (Q4 2025), Oliver Wyman (2025), Numerator, and Consumer Reports (2024). None of these are linked or footnoted, just named inline, so every stat still needs a source check before it goes in front of the client. At least there's a name attached to check against.

Strong on citation density, weak on citation traceability. Nothing in the metadata points to an AI tool; this reads as manually authored in Word.

2. Strategy Document — ChargePoint-Strategy-Document.doc

Created (this file): 11 September 2026, 15:12 PDT, the same minute as the Playbook above. That's more likely a coincidence of file transfer timestamps than genuinely simultaneous authorship. Content dated: August 2026, per the document's own title page, so the material itself is roughly a month older than this export.

Despite the .doc extension, this isn't a Word binary file. It's MHTML, a single-file "Save As Web Page" export, confirmed by inspecting the file header. The embedded CSS is tuned to an unusual degree for a Word export: precise hex colors, named classes like .insight-adv and .insight-risk, a deliberate type scale. That reads more like an HTML artifact generated by an AI coding tool or browser-based writer than something built inside Word's own formatting menus and saved out. The dc:creator field just says "Un-named." Treat this as AI-assisted synthesis wearing a Word-document extension, not a verified Word deliverable.

The content is a competitive landscape (ChargePoint plus ten named competitors across network operators, energy company networks, hardware makers, and software enablers), three perceptual-map insight summaries, and a three-message "Intelligent Electrification" brand platform with a closing manifesto. It cites specific competitor figures, EVgo's "35% charging gross margin" and "37% YoY" revenue growth, Blink's "$2.6M to $140M in four years," IONNA's "~1,000 bays live... targeting 30,000 by 2030," with no sourcing at all. They read as plausible. Plausible isn't the same as checked.

It also references "interactive perceptual maps (2×2 quadrant views)" as "maintained as a separate interactive artifact." That companion piece isn't in this folder either.

3. GA Architecture — GA Architecture - Sep 15.pdf

Created: 15 September 2026, 17:36 UTC. Author (embedded): Uprisal. Description (embedded): "PptxGenJS Presentation."

That description is a real fingerprint, not a guess. PptxGenJS is a code library for generating PowerPoint files programmatically. This deck wasn't built by hand in PowerPoint, Keynote, or Canva; it was generated by a script, almost certainly with AI assistance given how polished the copy is next to the templated visual structure. The garbled letter spacing running through the extracted text ("P repar ed by U pri sa l") comes from how PptxGenJS embeds fonts in its PDF output, not from a content problem, but it's a tell for the production method.

The content itself is a Google Analytics 4 measurement architecture: one property, three data streams (marketing, driver app, investor site), a documented event taxonomy, a UTM convention, and a closed-loop attribution model built on a CRM-linked client ID and offline conversion import. It's sound GA4 practice and internally consistent. One gap: the page numbering jumps from 06 to 08, skipping page 07 entirely. Something was cut from this deck without renumbering, or a slide failed to export.

This is methodology, not a claims document, so there's little to fact-check here. The risk is completeness, not accuracy.

4. Retail Campaign — Chargepoint Retail Campaign v3_Sep16.pdf

Created: 16 September 2026, 12:36 UTC. Author (embedded): Uprisal. Description (embedded): "PptxGenJS Presentation," the same script-generated production method as the GA Architecture deck, which means both likely came out of the same internal build pipeline.

This is the centerpiece creative document: "The New Front of Store," a retail campaign built on the idea that a parking lot is unmonetized retail space. Strategically it's well put together. It nests cleanly under the approved brand hierarchy: Intelligent Electrification (brand) leads to Charge Where Life Happens (campaign) leads to The New Front of Store (retail chapter) leads to "Turn charging time into store revenue," which is the Messaging Playbook's own approved Retail rally cry, reused correctly rather than reinvented.

It gets shakier at the centerpiece metric: Revenue Per Spot, a "proprietary" index with headline numbers of $41,639 for QSR, $15,321 for warehouse clubs, $11,007 for home improvement, $10,955 for supercenters, and $5,111 for malls. The deck justifies the index's credibility by citing ChargePoint's real-world scale: "453M+ charging sessions... 406,000+ activated ports... 19 years of history... 4,000+ commercial and fleet customers." Two of those four figures, the 453M+ sessions and the 406,000+ ports, do show up in the Messaging Playbook, so they trace back to the client's own numbers. The other two, 19 years of history and 4,000+ commercial and fleet customers, appear nowhere else in this document set. They may well be accurate (ChargePoint was founded in 2007, so 19 years checks out arithmetically by 2026), but as written they're unsourced additions bolted onto client-supplied figures, and the whole index's credibility argument depends on all four holding up.

Beyond the "we have enough data to calibrate this" claim, there's no visible methodology behind the index itself: no disclosed sample size, formula, or confidence interval, despite the deck's own copy promising "a confidence interval a finance team will find unglamorous and believable." That promise is aspirational here, not delivered.

A few more things worth flagging in this file specifically. Page numbering breaks in three places: 15 to 17 (16 is missing), 33 to 37 (34 through 36 missing), and 47 to 51 (48 through 50 missing), so something was pulled from each of the deck's four major sections without the numbering getting cleaned up. Section VI, "The landing page," contains only the placeholder text "Click to see the page," with no actual screenshots or mockups embedded, so the section meant to show the campaign "standing up on its own" doesn't currently exist in this file. And the competitor table on page 44 (Electric Era, NACS, PowerFlex, EVgo) is useful due diligence, but like the Strategy Document's competitor claims, none of it is sourced.

5. Briefing email — Noella Cresence Mail - Chargepoint | Briefing Documents.pdf

Created: 21 September 2026, 16:02 IST (Safari print-to-PDF, confirmed by Producer: macOS Quartz PDFContext and Creator: Safari). This is just the Gmail thread saved as a PDF, genuine correspondence rather than a strategy artifact, but it's the only place in the set that says who made these documents, why, and what's still missing.

Cross-document contradictions and inconsistencies

Retail dwell-time numbers don't agree with each other, inside the same document. The Messaging Playbook alone gives four different figures for how much longer an EV-charging customer stays in a retail store: "25 to 40 minutes" (the Retail pains table), "dwell time increase by an average of 50 minutes" (Retail market situation), "45-60 min vs. 20-30 min" (the VP of Real Estate/Marketing persona), and "30 minutes longer per visit" (that same persona's own headline, two lines below the 45-60 range). The Uprisal retail deck adds a fifth figure, "forty to ninety minutes" for destination-mode visits generally. None of these are flagged as measuring different things, say, total visit time versus incremental time. They read as the same claim, stated five different ways.

Gas station decline rate: 1.4% versus 2-4%, in the same Playbook. The Fueling and Convenience segment's Market Situation section says stations are "declining ~1.4% annually." The VP of Operations persona sheet two pages later says "Gas volumes declining 2-4% annually." These aren't two different metrics being confused for one; both are presented as the same trend.

Port-count rounding drifts across documents. The Strategy Document says "400K+ charge points" three separate times. The Messaging Playbook and the Retail Campaign both say "406K+ activated ports." A 6,000-port gap between 400K+ and 406K+ doesn't matter much on its own, but it suggests the Strategy Document wasn't checked against the Playbook's own numbers when it was written. Two documents that are supposedly aligned, citing the same live figure, not pulled from the same source at the same time.

Three top-line messaging architectures that never reference each other. The Strategy Document's own Messaging Framework section presents three key messages (pathos, logos, ethos, built around "a charger powers a vehicle, an intelligent network powers e-mobility") and a closing manifesto as the top-line message "across every audience, every journey, every touchpoint." None of that language, the pathos/logos/ethos structure, the manifesto copy, the "400,000 drivers, revenue, and grid intelligence" line, shows up anywhere in the Messaging Playbook or the Retail Campaign deck. Those two run entirely on the Playbook's own segment rally cries and the Retail deck's "New Front of Store" idea instead. That's not necessarily a problem; a brand platform and a campaign hierarchy can coexist fine. But nothing in the file set explains how the Strategy Document's manifesto is meant to sit alongside "Charge Where Life Happens." As written, they read as two separate creative territories that happen to share the "Intelligent Electrification" label at the top.

Where the documents hold up

A gaps list can end up reading more damning than it should, so it's worth naming what's solid. The campaign hierarchy claimed in the Retail deck is real: Intelligent Electrification (brand), Charge Where Life Happens (campaign), The New Front of Store (retail chapter), and "Turn charging time into store revenue" (working line, taken verbatim from the Playbook's approved Retail rally cry) is a clean, correctly nested structure. It's the one place in the Retail deck that actually shows its work rather than just asserting it. The GA Architecture deck's measurement design, one property, three separated streams, a CRM-joined client ID for closed-loop attribution, is sound, unglamorous, engineering-grade work with nothing overclaimed. And a quick public check on ChargePoint's current scale (roughly 385,000 active ports, roaming access above a million points, session growth in the double digits year over year) lands close enough to the "406K+ ports / 453M+ sessions / 992K+ roaming" figures used throughout this set that the base numbers look real, even without a citation trail inside the documents themselves.

Gaps to close before the client meeting

1. Retail Marketer.docx is listed in the routing email but isn't present in the folder.
2. The interactive perceptual maps referenced by the Strategy Document as a separate artifact aren't present either.
3. Section VI of the Retail Campaign deck is a placeholder, "Click to see the page," not the actual landing page content, despite the email linking to a live page at chargepoint.uprisal.in/retail.
4. Pages are missing from two decks without renumbering: page 07 in GA Architecture, and pages 16, 34 through 36, and 48 through 50 in the Retail Campaign.
5. Revenue Per Spot, the index anchoring the entire retail campaign (podcast, content calendar, paid media, the campaign's own name for itself), has a marketing description of its inputs but no visible calculation, sample size, or confidence interval, despite the deck promising one exists.
6. Two of the four calibration figures behind that index ("19 years of history," "4,000+ commercial and fleet customers") aren't sourced anywhere else in the set, sitting in the same sentence as two figures that are. There's no way to tell which is which without asking Uprisal directly.
7. The dwell-time and gas-decline figures inside the client's own Messaging Playbook disagree with themselves. Worth resolving with Michelle's team before those numbers get baked into ads and BDR scripts across five segments.

One more thing

A new folder, "ChargePoint — Client File," appeared in this directory partway through this review: roughly 24 files covering brochure, color system, typography, UI mockups, product diagrams, and event and social assets. It looks like the brand and design source material the briefing email points to, but it wasn't part of the original four-file request, and reviewing it properly would mean a different kind of pass (visual and brand-system, not strategic-document). Flagging it here rather than folding it in. Let me know if it needs its own review.

chargepoint.com: overview, platform, and history

Audited: 21 September 2026 Method: HTTP header inspection, robots.txt and sitemap.xml analysis, homepage source inspection, WHOIS lookup, live page spot-checks. No CMS admin access, so platform identification is based on public technical fingerprints, not confirmed internally.

How old is the site

Two different ages apply here, and they answer different questions.

Domain age: 19 years. WHOIS shows chargepoint.com was registered on 15 May 2007, through Network Solutions, currently pointed at AWS Route 53 nameservers. That lines up with ChargePoint's own founding year.

Current platform/content structure: at least 8 years old. The oldest lastmod timestamp found anywhere in the live sitemap is February 2018 (/about/what-we-offer, /drivers/offers/toyota/faq). That's the earliest evidence the current Drupal-based URL structure has been running continuously. It doesn't rule out an earlier version of the site existing before 2018, but nothing from before that date survives in the current sitemap. The press release archive under /about/news/ contains articles dating back to 2015 (CES 2016 coverage, a COP21 recap), so historical content has been carried forward through at least one platform migration.

I wasn't able to confirm an exact "last full redesign" date. The Wayback Machine's API was returning outage errors (429/504) at the time of this audit, so I couldn't cross-check archived snapshots for a specific relaunch date. Worth a follow-up check if that timing matters.

When was it last updated

Most recent content edit: 16 September 2026, five days before this audit, on the node that renders as the homepage across multiple locales. The homepage's social-share image was last replaced in May 2026 (visible in its filename path, /sites/default/files/2026-05/...). The footer copyright reads "© 2026 ChargePoint, Inc." Site maintenance is clearly continuous, not dormant.

Looking at lastmod dates across all 1,773 default-locale (English/US) pages in the sitemap:

The jump from roughly 50 pages a year (2020-2023) to nearly a thousand in 2025 is real, but it's mostly volume from two high-frequency sections, not a site-wide overhaul: the 491-page press release archive and the 456-page state/utility incentive library. Both are the kind of section that can get bulk-touched by a scheduled rebuild or a content-freshness sweep without an editor manually opening each page, so treat "956 pages updated in 2025" as upper-bound evidence of an active CMS pipeline, not confirmation that 956 pages were individually rewritten.

What platform it's built on

Drupal, self-hosted on Pantheon (a managed Drupal/WordPress hosting platform), confirmed by several independent signals:

• robots.txt disallows /node/add/, /user/register, /filter/tips, /admin/ — all default Drupal paths, not WordPress or a custom stack.
• sitemap.xml is explicitly generated by "the Simple XML Sitemap Drupal module."
• Response headers carry x-pantheon-styx-hostname and x-styx-req-id, Pantheon's routing layer signature.
• Homepage source references drupal-settings-json, drupal-selector, and a custom theme named chargepoint (theme=chargepoint in asset URLs, /themes/chargepoint/favicon.ico).
• Core JS asset path is /core/assets/vendor/jquery/, standard for Drupal 9/10.

The front end is server-rendered (no React/Vue/Next.js signals in the page source) and layered with jQuery, Swiper.js (carousels), ScrollMagic (scroll-triggered animation), and Lottie (animated illustrations, used on the "why-chargepoint" animated map). This is a traditional Drupal theme with progressive JS enhancement, not a headless/JAMstack build.

Multi-language setup: 17 locale variants run in parallel off the same content structure (en-gb, en-ca, fr-ca, fr-fr, fr-be, de-de, at-de, nl-nl, nl-be, es-es, it-it, sv-se, no-no, da-dk, pt-pt, cs-cz, pl-pl), each mirroring the default (US English) page structure via Drupal's native multilingual system rather than separate microsites.

One technical gap worth flagging

58 URLs in the site's own sitemap point to raw, unaliased Drupal node IDs (/node/3317, /node/81571, etc.) instead of clean URLs. Spot-checking four of them returned an "Access denied" 403 response on every one, including the single most recently-modified URL in the entire sitemap (/node/81571, edited 16 September 2026). These are either orphaned entries that should have been pruned from the sitemap, or a caching/access-control misconfiguration blocking direct node access. Either way, it's 58 URLs Google (and anyone else) is being pointed to that currently return an error.

chargepoint.com: page inventory

Source: sitemap.xml (two-part sitemap index, pulled 21 September 2026), cross-checked against the live main navigation.

Headline numbers

So the "how many pages" answer depends on what's being counted. If the question is "how big is the sitemap," it's 5,282. If it's "how many actual pages of content does the English site have," it's 1,765. The gap between those two numbers is almost entirely translation coverage, not extra content: two-thirds of every URL on the domain exists only because the same page structure is replicated across 17 locales.

Note on the 8 duplicates: the sitemap lists bare locale-root URLs (/de-de, /en-gb, /fr-fr, etc.) alongside the full locale-prefixed page trees. These are just the localized homepage and got miscounted in the raw base-URL pull; they're not separate content.

Breakdown by section (default locale, 1,773 URLs)

Locale coverage

17 locale variants run alongside the default (US English) site, each mirroring the same page structure:

en-gb (393) · de-de (395) · fr-fr (340) · fr-ca (310) · en-ca (310) · nl-nl (226) · es-es (224) · it-it (223) · sv-se (195) · no-no (189) · da-dk (185) · pt-pt (176) · cs-cz (160) · pl-pl (158) · fr-be (11) · nl-be (11) · at-de (11)

The steep drop-off for fr-be, nl-be, and at-de (11 pages each, versus 150-400 for the other locales) suggests those three are thin/minimal-viable localizations, most likely a handful of core pages translated rather than the full site.

chargepoint.com: target personas

Method: derived from the primary navigation structure, the /solutions/ segment pages, and the buyer-facing language on each (headlines, CTAs, proof points). Cross-referenced against the "Charge Where Life Happens" Messaging Playbook, since that document names buying committees for several of the same segments.

Four top-level audiences

The site's main navigation is organized around four distinct audiences, each with its own entry point and content track.

1. Drivers — individual EV owners. Served by the /drivers/ section: home charging setup, the driver app, charging etiquette ("charging-101"), OEM-specific onboarding (Tesla, Nissan Leaf, Chevy Bolt/Volt, Honda Clarity, BMW i3), and support. This is the only persona cluster not buying anything — it's a self-serve help and retention track for people who already have access to a ChargePoint station somewhere.

2. Businesses / site hosts — by far the largest and most segmented audience. This is everyone deciding whether to install charging on property they own or manage. The /solutions/ section breaks this single audience into 18 named verticals:

• Workplace
• Retail
• Fueling and convenience
• Commercial real estate
• Apartments / Condos (the live site's equivalent of the Playbook's archived "Multifamily" segment — active here, not archived)
• Cities and towns
• Education
• Federal and state agencies
• Healthcare
• Hospitality
• Entertainment and stadiums
• Parking operators
• Auto dealerships
• Automakers (OEM partnerships, a different relationship than "auto dealerships")
• Utilities
• HR (charging as an employee benefit — overlaps with Workplace but pitched to a different buyer)
• Logistics/delivery fleet
• Passenger transportation fleet
• Company vehicle / motor pool fleet

3. Installers and contractors — the /partners/training-certification/ track exists specifically to certify the electricians and installation contractors who deploy ChargePoint hardware. A narrow but operationally essential audience.

4. Press and job seekers — /about/news/ (491 press releases) targets media and industry press directly, and /about/opportunities/ targets prospective employees. Neither is a sales audience, but both get dedicated site real estate.

No investor-facing content found on this domain. ChargePoint is publicly traded, and the Uprisal retail campaign materials reference a "reimagined investor relations page," but nothing under chargepoint.com in this sitemap serves that audience. It's most likely hosted on a separate investor relations subdomain or a third-party IR platform (common for public companies) rather than missing outright — worth confirming rather than assuming either way.

How this compares to the Messaging Playbook

The Messaging Playbook you reviewed earlier (Michelle Draft_Charge_Where_Life_Happens_Messaging_Playbook.pdf) names five active campaign segments: Workplace, Retail, Fueling and Convenience, Universities, and Commercial Real Estate, with Multifamily archived out of the current campaign.

The live website supports all five of those, but runs 13 additional segments the campaign playbook doesn't currently address: Apartments/Condos (active on-site despite being archived in the campaign), Cities and Towns, Federal and State Agencies, Healthcare, Hospitality, Entertainment and Stadiums, Parking Operators, Auto Dealerships, Automakers, Utilities, HR, and three separate fleet types (logistics/delivery, passenger transportation, company vehicle/motor pool).

That's a real gap between what the campaign is built to say and who the website is actually built to sell to. Worth flagging to Uprisal: either those 13 segments are being deliberately left out of the current campaign wave (fine, if intentional), or the campaign's segment coverage hasn't caught up to what Sales already has live pages for.

Buying-committee detail (where available)

For the five segments that overlap with the Messaging Playbook, that document already names specific buyer roles per segment (Head of Workplace, VP of Real Estate, Facilities/Energy, Finance/CFO, IT/Security, and so on — see the Playbook's "Buying Committee" tables). Rather than duplicate that here, treat this persona list as the segment-level map and the Playbook as the role-level detail underneath it.

chargepoint.com: custom-designed pages

Count: 155 (default locale)

Methodology

Custom = a unique, individually-authored page: one URL, one purpose, not one instance of a repeating content type applied across many similar records. This was determined remotely, without CMS admin access, from URL structure and live spot-checks, not from Drupal's internal content-type field. Two solutions pages were fetched and compared directly (/solutions/retail and /solutions/workplace): both draw from the same component library (hero, benefit grid, feature highlight, testimonial, logo wall, stats footer) but arrange and populate those components differently per page. That makes them custom-assembled rather than templatised, even though they share underlying design components. See file 01 for the templatised-page spot-checks that this list is being contrasted against.

Within "custom," the pages range from genuinely bespoke marketing pages (segment/solution pages, product hub pages) down to simple one-off utility pages (FAQs, confirmation pages, legal notices). All are unique URLs serving a distinct purpose, but not all represent the same level of design investment — flagged inline below.

Marketing and product pages (highest design investment)

Homepage, product hubs, and the segment/solutions pages are where custom design work is concentrated:

• https://www.chargepoint.com/
• https://www.chargepoint.com/why-chargepoint
• https://www.chargepoint.com/solutions
• https://www.chargepoint.com/solutions/workplace
• https://www.chargepoint.com/solutions/retail
• https://www.chargepoint.com/solutions/fueling-convenience
• https://www.chargepoint.com/solutions/commercial-real-estate
• https://www.chargepoint.com/solutions/education
• https://www.chargepoint.com/solutions/apartments
• https://www.chargepoint.com/solutions/condos
• https://www.chargepoint.com/solutions/cities-and-towns
• https://www.chargepoint.com/solutions/federal-and-state-agencies
• https://www.chargepoint.com/solutions/healthcare
• https://www.chargepoint.com/solutions/hospitality
• https://www.chargepoint.com/solutions/entertainment-and-stadiums
• https://www.chargepoint.com/solutions/parking-operators
• https://www.chargepoint.com/solutions/auto-dealerships
• https://www.chargepoint.com/solutions/automakers
• https://www.chargepoint.com/solutions/utilities
• https://www.chargepoint.com/solutions/hr
• https://www.chargepoint.com/solutions/logistics-delivery-fleet
• https://www.chargepoint.com/solutions/passenger-transportation-fleet
• https://www.chargepoint.com/solutions/passenger-transportation-fleet-0
• https://www.chargepoint.com/solutions/company-vehicle-motor-pool-fleet
• https://www.chargepoint.com/solutions/improve-tco
• https://www.chargepoint.com/solutions/improve-tco-fleet
• https://www.chargepoint.com/solutions/attract-retain
• https://www.chargepoint.com/solutions/build-and-install
• https://www.chargepoint.com/solutions/bidding-and-buyout
• https://www.chargepoint.com/solutions/pre-construction
• https://www.chargepoint.com/solutions/site-host
• https://www.chargepoint.com/solutions/sustainability
• https://www.chargepoint.com/solutions/specifications
• https://www.chargepoint.com/solutions/customer-stories
• https://www.chargepoint.com/solutions/voyager-faq
• https://www.chargepoint.com/products/stations
• https://www.chargepoint.com/products/stations/cp6000
• https://www.chargepoint.com/products/stations/cp6000-0
• https://www.chargepoint.com/products/stations/cp6000-fleet-old
• https://www.chargepoint.com/products/stations/cp6000-fleet-old-0
• https://www.chargepoint.com/products/stations/cpf50
• https://www.chargepoint.com/products/stations/ct4000
• https://www.chargepoint.com/products/stations/express
• https://www.chargepoint.com/products/stations/express-280
• https://www.chargepoint.com/products/stations/express-plus
• https://www.chargepoint.com/products/stations/next-gen
• https://www.chargepoint.com/products/stations/pantograph
• https://www.chargepoint.com/products/stations/megawatt-charging-system
• https://www.chargepoint.com/products/stations/branding
• https://www.chargepoint.com/products/stations/chargepoint-compatible
• https://www.chargepoint.com/products/software
• https://www.chargepoint.com/products/software/cms-suite
• https://www.chargepoint.com/products/software/power-management
• https://www.chargepoint.com/products/software/telematics
• https://www.chargepoint.com/products/services
• https://www.chargepoint.com/products/services/driver-experience-network
• https://www.chargepoint.com/products/eol
• https://www.chargepoint.com/products/customers
• https://www.chargepoint.com/products/how-to-choose
• https://www.chargepoint.com/3dtour/cp6000
• https://www.chargepoint.com/branding

Corporate / about

• https://www.chargepoint.com/about
• https://www.chargepoint.com/about/contact
• https://www.chargepoint.com/about/sustainability
• https://www.chargepoint.com/about/media
• https://www.chargepoint.com/about/coverage
• https://www.chargepoint.com/about/press-media-gallery
• https://www.chargepoint.com/about/awards
• https://www.chargepoint.com/about/opportunities
• https://www.chargepoint.com/about/opportunities/job
• https://www.chargepoint.com/about/webinars-events
• https://www.chargepoint.com/about/what-we-offer
• https://www.chargepoint.com/about/news (archive index/landing, distinct from the individual press-release template — see file 05)

Driver hub and account pages

• https://www.chargepoint.com/drivers
• https://www.chargepoint.com/drivers/home
• https://www.chargepoint.com/drivers/activate
• https://www.chargepoint.com/drivers/installation
• https://www.chargepoint.com/drivers/charging-101
• https://www.chargepoint.com/drivers/home-charging-101
• https://www.chargepoint.com/drivers/apartments-and-condos
• https://www.chargepoint.com/drivers/condos
• https://www.chargepoint.com/drivers/support
• https://www.chargepoint.com/drivers/support/faqs
• https://www.chargepoint.com/drivers/waitlist-faq
• https://www.chargepoint.com/drivers/valet-faq
• https://www.chargepoint.com/drivers/nacs-connector-faq
• https://www.chargepoint.com/drivers/sms-notifications-rollback-faq
• https://www.chargepoint.com/drivers/home/general
• https://www.chargepoint.com/drivers/home/before-you-buy
• https://www.chargepoint.com/drivers/home/installation
• https://www.chargepoint.com/drivers/home/installation/25
• https://www.chargepoint.com/drivers/home/installation/flex
• https://www.chargepoint.com/drivers/home/settings/25
• https://www.chargepoint.com/drivers/home/settings/flex
• https://www.chargepoint.com/drivers/home/troubleshooting/25
• https://www.chargepoint.com/drivers/home/troubleshooting/flex
• https://www.chargepoint.com/drivers/home/resource
• https://www.chargepoint.com/drivers/home/tax-credit
• https://www.chargepoint.com/install
• https://www.chargepoint.com/homeinstall

Partners and installers

• https://www.chargepoint.com/partners
• https://www.chargepoint.com/partners/training-certification
• https://www.chargepoint.com/partners/training-certification/faq
• https://www.chargepoint.com/partners/training-certification/installer-onboarding

OEM/partner co-branded landing pages

• https://www.chargepoint.com/mazda/home
• https://www.chargepoint.com/mazda/credit
• https://www.chargepoint.com/evergy
• https://www.chargepoint.com/evergy/connect
• https://www.chargepoint.com/harley-davidson
• https://www.chargepoint.com/motortrend

Incentives (federal-level, custom pages — not the state-level template series)

• https://www.chargepoint.com/incentives
• https://www.chargepoint.com/incentives/federal-charging-incentives
• https://www.chargepoint.com/incentives/federal-tax-credit
• https://www.chargepoint.com/incentives/federal-tax-credit-home-ev
• https://www.chargepoint.com/incentives/nevi
• https://www.chargepoint.com/policy/iija

EU-specific

• https://www.chargepoint.com/eu/activate
• https://www.chargepoint.com/eu/installers
• https://www.chargepoint.com/eu/guides
• https://www.chargepoint.com/eu/support/guides

Billing / operations FAQs

• https://www.chargepoint.com/businesses/electrical
• https://www.chargepoint.com/businesses/services/assure
• https://www.chargepoint.com/businesses/payment-methods-faq
• https://www.chargepoint.com/businesses/weights-measures
• https://www.chargepoint.com/businesses/weights-measures/faq
• https://www.chargepoint.com/businesses/sucuring-approval-to-bill-by-kilowatt-hour
• https://www.chargepoint.com/products/guides
• https://www.chargepoint.com/products/guides/eos-eol-policy
• https://www.chargepoint.com/products/support-faq
• https://www.chargepoint.com/products/sustainability-host-faq
• https://www.chargepoint.com/products/software/waitlist-faq
• https://www.chargepoint.com/products/certifications
• https://www.chargepoint.com/products/cpe100-installation-video
• https://www.chargepoint.com/products/cpe200-installation-video

Legal, policy, and site utility (lowest design investment — functional pages)

• https://www.chargepoint.com/terms-of-use
• https://www.chargepoint.com/tax-policy
• https://www.chargepoint.com/accessibility-statement
• https://www.chargepoint.com/supplier-code-of-conduct
• https://www.chargepoint.com/regulatory-api-license
• https://www.chargepoint.com/store-maintenance
• https://www.chargepoint.com/error404
• https://www.chargepoint.com/search
• https://www.chargepoint.com/locale
• https://www.chargepoint.com/labels
• https://www.chargepoint.com/blog (index/landing page, distinct from individual blog post template — see file 05)
• https://www.chargepoint.com/engineering (index/landing page, distinct from individual engineering post template)
• https://www.chargepoint.com/resource-library
• https://www.chargepoint.com/guides
• https://www.chargepoint.com/support
• https://www.chargepoint.com/rental-host-resources
• https://www.chargepoint.com/auto-customer-resources
• https://www.chargepoint.com/fleet/solutions
• https://www.chargepoint.com/ca/activate
• https://www.chargepoint.com/charging-forward/popular-times
• https://www.chargepoint.com/offers/20/confirmation

chargepoint.com: templatised pages

Count: 1,610 (default locale)

Methodology

Templatised = one instance of a repeating content type, applied across many records that share the same field structure and layout, where only the data changes. Confirmed by spot-checking one page from each of the three biggest groups against the requested URL directly:

• /incentive/illinois-ev-rebate — a fixed template: title, one-line subheading, a decorative icon, and a details area, structurally identical to every other state incentive page.
• /about/news/chargepoint-hires-colleen-jansen-chief-marketing-officer — a standard press-release template: headline, dateline, opening paragraph, executive quote, boilerplate footer, repeated across all 490 press releases.
• Blog posts follow the same pattern based on URL structure and metadata consistency (not individually spot-checked beyond the above two).

Full URL lists for every group below are in the full-url-lists/ subfolder next to this file, since several of these run into the hundreds and aren't readable as inline lists.

By group, largest to smallest

Representative samples (first 8 of each large group)

Press releases:

• https://www.chargepoint.com/about/news/350green-install-more-400-chargepoint-network-charging-stations-electric-vehicles-across
• https://www.chargepoint.com/about/news/365-energy-brings-coulomb-technologies-intelligent-charging-stations-e-mobility-norway
• https://www.chargepoint.com/about/news/365-energy-installs-first-coulomb-chargepoint-networked-charging-stations-irelands
• https://www.chargepoint.com/about/news/365-energy-selected-provider-chargepoint-networked-charging-stations-poland
• https://www.chargepoint.com/about/news/3m-worldwide-headquarters-installs-coulomb-technologies-chargepoint-stations-electric
• https://www.chargepoint.com/about/news/ald-automotive-and-chargepoint-create-new-ev-charging-business-accelerate
• https://www.chargepoint.com/about/news/alfen-showcase-chargepoint-enabled-charging-stations-electric-vehicles-ecomobiel-show
• https://www.chargepoint.com/about/news/aloha-ev-coulomb-technologies-installs-solar-powered-chargepoint-networked-charging (482 more in the full list — note the "Coulomb Technologies" branding in early URLs: that's ChargePoint's pre-2011 company name, preserved in the archive since the earliest press releases.)

State/utility incentive pages:

• https://www.chargepoint.com/incentive/126-corridor-ev-chargers-incentive-program
• https://www.chargepoint.com/incentive/2026-clean-air-grants-program
• https://www.chargepoint.com/incentive/3ce-electrify-your-ride-program
• https://www.chargepoint.com/incentive/3ce-electrify-your-ride-residential
• https://www.chargepoint.com/incentive/access-energy-coop-electric-vehicle-charging-station-rebate
• https://www.chargepoint.com/incentive/access-energy-electric-vehicle-level-2-charging-station-rebate
• https://www.chargepoint.com/incentive/aes-indiana-commercial-fleet-ev-charging-rebate
• https://www.chargepoint.com/incentive/alabama-power-ev-home-charger-rebate (448 more in the full list)

Blog posts:

• https://www.chargepoint.com/blog/10-notable-new-electric-vehicles-coming-your-way-2019
• https://www.chargepoint.com/blog/11-college-campuses-wander-while-charging-your-ev
• https://www.chargepoint.com/blog/13-beaches-where-you-can-recharge-while-you-charge-your-ev
• https://www.chargepoint.com/blog/13-things-you-didnt-know-you-could-do-chargepoint-app
• https://www.chargepoint.com/blog/2021-year-electric-pickup-trucks
• https://www.chargepoint.com/blog/2022-epa-school-bus-rebate-program-everything-you-need-know
• https://www.chargepoint.com/blog/3-actions-you-must-take-now-support-your-ev-drivers
• https://www.chargepoint.com/blog/3-myths-about-millennials-and-evs-are-costing-you-money (331 more in the full list)

Resource library detail pages:

• https://www.chargepoint.com/resources/10-steps-success-chargepoint-ev-charging-employees
• https://www.chargepoint.com/resources/4-reasons-speed-your-electrification-efforts
• https://www.chargepoint.com/resources/7-considerations-successful-ev-charging-site-design-fuel-and-convenience-retail
• https://www.chargepoint.com/resources/achieve-your-business-goals-ev-charging
• https://www.chargepoint.com/resources/activating-your-chargepoint-home
• https://www.chargepoint.com/resources/beginners-guide-providing-ev-charging-work
• https://www.chargepoint.com/resources/best-practices-reducing-emissions-electric-vehicle-charging-workplace
• https://www.chargepoint.com/resources/brochure-chargepoint-home-32a-cph25 (104 more in the full list)

Leadership/spokesperson profiles:

• https://www.chargepoint.com/profile/adam-cook
• https://www.chargepoint.com/profile/adam-hart
• https://www.chargepoint.com/profile/ajay-agrawal
• https://www.chargepoint.com/profile/alexander-schabert
• https://www.chargepoint.com/profile/andre-ten-bloemendal
• https://www.chargepoint.com/profile/anne-smart
• https://www.chargepoint.com/profile/axel-harries
• https://www.chargepoint.com/profile/bill-loewenthal (55 more in the full list)

Small groups, shown in full here

OEM co-branded driver join pages (7): bmw-i3 · chevy-bolt · chevy-volt · honda-clarity · nissan-leaf · tesla · toyota-prius-prime (all under /drivers/join/)

Product spec sheet pages (6): cp6000, cpf50, ct4000, express, express-280, express-plus (all under /products/stations/[model]/specs)

Product tour pages (5): cp6000, ct4000, express, express-280, express-plus (all under /products/stations/[model]/tour)

OEM driver offer pages (2): /drivers/offers/toyota and /drivers/offers/toyota/faq

Single-instance templates (1 each): /products/software/tour, /products/software/power-management/faq