Adhvanik homepage: copy changes
Page: adhvanik-preview.stacc.workers.dev · Prepared 4 Nov 2026 · 30 changes
Summary
The homepage reads as AI-written. The cause is not the body text, which is specific: real clients, a sourced CO₂ estimate, response times honestly called "targets". The cause is three patterns:
- Section headings written as slogans ("Solar you can measure", "Four phases, one team") that would fit any competitor's site.
- Sentence and layout templates: the "X, not Y" contrast and exactly three bullets in almost every block.
- The same stats repeated: 85%, 170+, 110 MW, the 2040/2051 PPAs and 120% IRR each appear 2–3 times.
Each fix below either replaces a generic line with a specific fact or deletes it. Swapping words without adding facts doesn't remove the AI feel.
Dev notes (read first)
- Accent words. Headings use
<span class="accent"> inside data-split. The highlighted word in each "After" is our suggestion. Change it if the animation needs a different word.
- FAQ changes go in two places: the visible accordion and the
FAQPage JSON-LD in <script type="application/ld+json">. Keep them identical.
- Hero subhead text is also in the footer. Change only the hero (
p.sub). Leave the footer.
- Removing the "Preferred model" field: check the form handler / CRM mapping doesn't require
preferred_model.
- [CONFIRM] items need facts from Adhvanik. Do not ship placeholder text. Until a figure arrives, ship the rest of the change and leave that line out (see the list below).
- Selectors were taken from the live HTML on 4 Nov. Search the source for the "Before" text if a selector has changed.
Changes, top to bottom
Highlighted = accent word · green ship now · amber needs a fact from Adhvanik · red delete
Hero
#1h1#hero-titleRewrite
Before
Solar that improves IRRs.
After
Rooftop solar for factories, sized to the power you use during the day.
Why: Every solar company could claim to improve IRRs, so the line says nothing about Adhvanik. The one specific claim Adhvanik makes, sizing plants to daytime load, was buried in section 2. It moves to the headline as a plain statement. Our first draft used the 'X, not Y' contrast from the live section-2 heading, and that pattern is itself an AI tell, so it's gone.
#2section.hero-wrap p.subRewrite · needs client data
Before
Adhvanik Energy designs, finances, builds and maintains rooftop solar plants for India's manufacturers.
After
Units you use on site replace grid power at your full tariff. Units exported to the grid earn much less [CONFIRM: export rate / state rule]. So we size the plant to your daytime load.
Why: The subhead should explain why the headline claim pays off. The four-verb company description says nothing about the buyer. Keep the footer copy of this sentence; only the hero one changes.
#3section.hero-wrap, below the primary CTAAdd
Before
(nothing below the button; the 'Top 10 in India' badge sits above the H1)
After
Under the button: "Free · 14 days · no commitment". Next to it: "25%+ IRR if you buy the plant, or no upfront cost on a PPA · Top 10 in India, JMK Research FY 2025-26". Move the Top 10 badge from above the H1 to this line.
Why: Visitors hesitate at the moment they click. The facts that settle it (it's free, how long it takes, the outside ranking) should sit right at the button, not elsewhere on the page.
Why Adhvanik
#4section#why h2#why-titleReplace
Before
We size every plant to your factory's daytime load, not to the size of the roof.
After
Why Adhvanik (promote the existing eyebrow to the H2 and remove the eyebrow)
Why: This claim now leads the hero, so repeating it would duplicate it. It's also the 'X, not Y' contrast, the most common AI sentence shape.
#5section#why, card 1 (h3 + p)Rewrite · needs client data
Before
h3: Proven industrial credibility
p: Trusted by Britannia, Hindustan Unilever, Dabur and other leading manufacturers.
After
h3: [CONFIRM what 85% measures], e.g. "85% of our clients have built a second plant with us"
p: delete
Why: "Proven credibility" asserts credibility without showing any. The p repeats the logo strip directly above it. The 85% figure is real proof, but the site says "repeat business", which could mean share of revenue or share of clients. Use whichever is true.
#6section#why, card 2 (h3 + p)Rewrite
Before
h3: A partner for 25 years
p: We invest our own capital and stay responsible for the full PPA term, with PPAs running to 2040 (Dabur) and 2051 (Sterlite Electric).
After
h3: We pay for PPA plants and run them for the full contract
p: Our longest PPAs run to 2040 (Dabur) and 2051 (Sterlite Electric).
Why: "A partner for 25 years" reads as if the company is 25 years old, which contradicts "since 2013" in the FAQ. The new heading states what Adhvanik actually does.
#7section#why, card 3 (h3 + ul)Rewrite · needs client data
Before
h3: Safety by design
ul: Dedicated safety department / Site-level safety inspections / Mandatory walkways and safety lines
After
h3: Walkways and safety lines on every roof
p: Our safety department inspects each site. [CONFIRM: a figure, e.g. incident-free hours or audits per year]
Why: "X by design" is a stock phrase. The three bullets are the same idea split three ways, and an even three-item list is another AI pattern.
Solutions
#8section#solutions h2#sol-title + p.ledeRewrite
Before
h2: One partner for every site you run
p.lede: Every installation type, designed and built by us, and maintained by our own O&M team.
After
h2: Solutions (remove the duplicate eyebrow)
p.lede: Our own O&M team maintains every plant we build. We also take over plants other companies built.
Why: The slogan heading would work for any competitor. The new lede states two facts, one of which (taking over plants built by other companies) sets Adhvanik apart.
#9section#solutions, card eyebrowsDelete
Before
"Installation" label on cards 01–05
After
Keep the numbers, drop the repeated word
Why: The same label five times in a row is noise.
#10section#solutions, card p (5 cards)Rewrite
Before
RCC: Ballasted or anchored structures.
Ground: Uses unused land inside the boundary.
Carports: Shade + generation.
O&M (ours): In-house O&M team.
After
RCC: Ballasted or anchored, depending on what your roof slab can carry. [CONFIRM]
Ground: For factories with spare land inside the boundary wall.
Carports: For plants with a parking lot: power, shade for vehicles and built-in EV chargers.
O&M (ours): Maintained by the same team that built it.
Why: The fragments are uneven, and some read like notes rather than copy. Each line now says which factory the option suits.
How it works
#11section#how h2#how-title + p.ledeRewrite
Before
h2: From your first bill to your first unit
p.lede: Four phases, one team.
After
h2: Feasibility takes 14 days. Building takes 90 to 100.
p.lede: delete
Why: Two slogans with matching rhythm. The timeline is the useful fact, and it was hidden in small labels.
#12section#how, step 01 Feasibility ul.ptsExtend
Before
3 bullets: CAPEX vs PPA / IRR and payback / Structural and shadow feasibility
After
All 5 deliverables, matching the FAQ: + indicative PPA tariff (₹/kWh) + net-metering / policy sensitivity for your state
Why: Every step has exactly three bullets because of the template, not because the content has three items. The FAQ already lists five deliverables.
#13section#how, step 02 Design p.lineDelete · needs client data
Before
Every roof engineered on its own.
After
(delete) Add a duration to match the other steps: [CONFIRM] days
Why: The line is filler. Design is the only step with no duration.
#14section#how, step 03 Build p.line + ul.ptsRewrite · needs client data
Before
p: We procure, build and commission the plant, and stay accountable for it.
li: Dedicated safety department
After
p: We buy the equipment, build the plant and commission it. [CONFIRM: what 'accountable' means, e.g. workmanship warranty of N years]
li: delete (already in the Why section)
Why: "Stay accountable" is a promise with no content. Say what it means, or cut it.
#15section#how, step 04 Operate ul.ptsMerge
Before
li: 95% uptime guarantee + PR guarantee
li: 99% average asset uptime
After
li: Guaranteed uptime is 95%, plus a performance-ratio guarantee. Across the plants we maintain, the average is 99%.
Why: The gap between the guarantee and the actual result is the strongest proof in this section. It only lands when the two figures sit side by side.
#16section#how, the 'Runs on <strong>…</strong>' linesExplain or delete · needs client data
Before
Runs on GreenAdhvanik / Runs on AdhvanikCentral / Runs on Asset Connect
After
Add 3–5 words each, e.g. "Runs on Asset Connect, our plant-monitoring system". [CONFIRM what GreenAdhvanik and AdhvanikCentral do] Otherwise delete.
Why: Internal product names mean nothing to a first-time visitor.
Financing
#17section#financing p.ledeDelete
Before
Four ways to fund the same plant.
Why: Filler. The four cards already show it.
#18section#financing, CAPEX cardAdd · needs client data
Before
25%+ IRR · A Vapi plant returned 120% IRR and paid back in under 2 years.
After
Keep, and add: "Most CAPEX plants pay back in [CONFIRM] years." Name the Vapi client or link its case study.
Why: Shown alone, the 120% outlier can look unbelievable. A typical figure next to it gives buyers a result they can expect for their own plant.
#19section#financing, EMI card (and Lease)Fill or merge · needs client data
Before
EMI card has no figure; Lease shows only "3–10 years"
After
Give EMI a figure (tenure or rate) [CONFIRM], or merge Lease and EMI into one card.
Why: An empty card looks unfinished.
Impact
#20section#impact h2#impact-title + dl.numsRewrite + trim
Before
h2: Solar you can measure
4 tiles: 110 MW / 170+ / 1.33 lakh t CO₂ / 99%
After
h2: Results (remove the duplicate eyebrow)
Tiles: keep CO₂ and 99% uptime only (110 MW and 170+ already appear in the hero). Add a real Asset Connect monthly-report screenshot. Keep the CO₂ footnote.
Why: Slogan heading, and the stats repeat. A real report screenshot proves the monthly-reporting claim better than another tile.
Projects
#21section#projects figcaption 'Site photo' (×4)Replace assets
Before
Placeholder: "Site photo"
After
Real photos of each plant
Why: Placeholders make the page look like a template more than anything else on it.
#22section#projects, each card descriptionAdd · needs client data
Before
e.g. "Rooftop solar plant, commissioned Jul 2026."
After
Add one result per plant: annual kWh or ₹ saved [CONFIRM]
Why: Capacity and date describe the plant but don't show any result.
Case studies
#23section#case-studies h2#cs-titleRewrite
Before
Manufacturers who chose to build with us
After
Case studies (remove the duplicate eyebrow)
Why: Slogan heading. The cards do the work.
#24section#case-studies p.big-text / small-card textAdd · needs client data
Before
Mounting and model details only
After
Add one outcome figure per card (₹ saved/yr, IRR or payback) [CONFIRM]
Why: Case studies should lead with the result. Right now they lead with engineering details.
FAQ
#25section#faq p.ledeDelete
Before
Straight answers from our engineers.
Why: "Straight answers" is a stock phrase.
#26section#faq, 'Who is responsible…' answer + FAQPage JSON-LDRewrite
Before
…so performance is our problem, not yours.
After
…so we carry the cost if the plant underperforms.
Why: 'X, not Y' contrast. The new line is a plain statement and is more specific.
#27section#faq, ROI answer + FAQPage JSON-LDTrim
Before
…A Vapi plant returned 120% IRR and paid back in under 2 years…
After
Replace the repeated figure with a link to the Vapi case study.
Why: Third appearance of the same figure on the page.
Contact
#28section#contact h2#contact-title + p.ledeRewrite
Before
h2: Have a factory roof that could cut your power bill?
p.lede: Send your location and monthly bill. An engineer replies within 48 hours.
After
h2: Send us a recent electricity bill and we'll compare buying the plant against a PPA for your site within 14 days.
p.lede: An engineer replies within 48 hours.
Why: The rhetorical-question opener is a filler pattern. The new heading says exactly what the visitor sends and what they get back.
#29form: #home-enquiry-preferred_model (label + select)Delete field
Before
Preferred model (optional)
After
Remove the field. Check that the form handler / CRM mapping doesn't require it.
Why: The feasibility study compares the models anyway, so asking up front only adds a field. Keep the bill-range field: it qualifies leads, and sales probably wants that filter. If they'd rather have more leads, remove it too.
#30form, next to the submit buttonAdd
Before
(no proof at the button)
After
"Top 10 in India (JMK Research FY 2025-26) · 85% repeat business"
Why: Same reason as the hero CTA: proof at the moment of clicking.
Where each stat should appear (once)
| Stat | Appears now in | Keep only in |
|---|
| 110 MW commissioned | Hero, Impact | Hero only |
| 170+ factories maintained | Hero, Impact, FAQ | Hero only (FAQ: keep the AMC answer, drop the count) |
| 85% repeat business | Hero, Why heading badge, FAQ | Why card 1 + contact proof line |
| PPAs to 2040 / 2051 | Why card 2, Financing PPA card, FAQ | Why card 2 only |
| 120% IRR Vapi | Financing, FAQ | Financing only (FAQ links to it) |
Facts needed from Adhvanik
| Where | What we need |
|---|
| Hero subhead | Grid export rate / state net-metering rule, so the 'exported units earn less' line is accurate |
| Why card 1 | What 85% 'repeat business' measures: clients or revenue |
| Why card 3 | A safety figure (incident-free hours, audits per year), if one exists |
| Solutions RCC card | Is the ballast/anchor choice driven by slab load capacity? |
| How it works · Design | Design phase duration |
| How it works · Build | What 'stay accountable' means (warranty terms) |
| How it works | What GreenAdhvanik and AdhvanikCentral do |
| Financing CAPEX | Typical CAPEX payback, and whether the Vapi client can be named |
| Financing EMI | EMI tenure or rate |
| Projects + Case studies | One result figure per plant / case |
How we got there
- Captured the live page. Fetched the preview URL and extracted every visible heading, paragraph, card and form label in page order, with its HTML element and section ID.
- Ran a landing-page teardown using our growth-marketing reference library (conversion playbooks and page teardowns). It tests whether a visitor understands in five seconds what is sold and to whom, whether each section answers the visitor's next question, whether proof sits beside every big claim, and whether the CTA settles doubts at the click.
- Ran the positioning "swap test" on every heading: replace "Adhvanik" with a competitor's name. If the line still works, it's generic. "Solar that improves IRRs", "One partner for every site you run" and the other slogan headings failed. Sizing plants to daytime load was the one claim that passed, so it became the headline.
- Ran an anti-AI writing pass on both the live copy and our own replacements. It flags known AI patterns: "X, not Y" contrasts, groups of three, slogan pairs, puffery and filler. It caught our first headline draft ("…sized to daytime load, not your roof"), which copied the live page's own "not X but Y" sentence. We rewrote it.
- Fixed substance, not words. Every change either adds a checkable fact or removes a line. Where the right fact isn't on the site, we marked it [CONFIRM] instead of inventing a number.
- Checked against the live HTML before handoff. This removed two false alarms from the first pass: the duplicate logo list is already hidden from screen readers, and the case-study text sits above the client name by design.
Not covered: visual design, page speed, SEO. This pass is copy only.