Every way to pay for HighLevel AI, explained

You are a senior web designer, front end engineer, and conversion copywriter working as one. Build a lead generation landing page for [business name], a [business type]. Aim for the standard of a custom agency build, not a template.

AUDIENCE AND GOAL
The ideal customer is [ideal customer]. The main offer is [main offer]. Every section should move the visitor toward one action: [primary button text].

PAGE STRUCTURE, IN THIS ORDER
1. Hero: a headline under ten words that states the main outcome for the visitor, one supporting sentence, the primary button, and a row of three short trust signals directly under the button. Text on one side, a large image on the other.
2. Services: a grid of matching cards, three or six. Each card has an icon, a plain name, one sentence on the result, exactly three short bullet points, and a text link.
3. How it works: three or four numbered steps from first contact to finished result, shown as a stepper joined by a line, each with a short title and one sentence. Not a bullet list.
4. Social proof: three matching testimonial cards with a star row, a quote slot, and name and role slots, plus one row for ratings or logos. Use only the real facts I gave you and mark everything else as a slot.
5. FAQ: five to seven real objections as an accordion, answered plainly in two or three sentences each.
6. Final call to action: a bold full width band in the dark brand tone that restates the main outcome, with the primary button and one line that lowers the risk of acting.

DESIGN SYSTEM
Set these once as shared tokens and reuse them everywhere. Do not style sections one at a time.
Style: Clean and modern. Lots of whitespace, a crisp sans serif type pairing, soft rounded corners, subtle shadows, and one confident accent color.
Color: [brand colors]. Build a small system from them: one primary, one accent, one dark tone for contrast sections, and neutral tints for backgrounds and borders.
Type: one display typeface for headings and one clean typeface for body text, with a clear size scale and comfortable line height.
Shape and depth: one corner radius, one border color, and one soft shadow style, used everywhere.
Spacing: one vertical rhythm between sections and one padding size inside cards.
Buttons: one primary style and one secondary style, used the same way in every section.

LAYOUT AND ALIGNMENT
1. Every set of cards in a row is the same height. Titles, body text, and buttons start on the same lines across the row.
2. Cards in a set carry the same number of bullet points, of similar length.
3. Grids are always even: two, three, four, or six across. Never leave one card alone on a row.
4. No narrow columns that force text into tall thin blocks. If text needs room, give it a wider row.
5. Nothing is stretched to fill space. No empty padding inside a card.
6. One clear focal point per section. Alternate white, tinted, and dark sections so the page has rhythm as you scroll.
7. Tags and chips sit in an ordered row or grid, never scattered.

SHOW IT, DO NOT LIST IT
Visitors scan. They do not read. Numbers become large stat figures. A process becomes a numbered stepper. A comparison becomes two panels side by side. Features become icon cards. Never use a plain table or a long bullet list where a visual would do. Keep every paragraph to three lines or fewer on desktop.

INTERACTION AND MOTION
Build every item on this list. Use CSS transitions and the browser's IntersectionObserver. Do not add an animation library.
1. Sections and cards fade and rise into view as they scroll in, staggered left to right, and only once.
2. Every large number counts up from zero when it scrolls into view.
3. The steps in How it works light up in order, first to last, when the stepper scrolls into view, and the line between them fills as they do.
4. Cards lift slightly with a soft shadow on hover. Buttons have clear hover, focus, and pressed states.
5. The header stays pinned to the top, and gains a solid background and a soft shadow after the first scroll.
6. The FAQ opens and closes smoothly, one item at a time, with a rotating icon.
7. The hero image has a very slow, subtle zoom.
Rules: nothing loops forever except the slow hero zoom. No particles, floating dots, or animated backgrounds. No motion that shifts the layout or delays reading. When a visitor has reduced motion turned on, show everything in its finished state. Nothing may ever cause sideways scrolling.

COPY RULES
Tone: confident and plain spoken. Write specific, benefit led copy for this exact business and this exact customer. Short sentences. Headlines under ten words. No filler phrases, no em dashes, and no small generic label above each heading.
I have not given you facts yet, so do not state any numbers, years, ratings, or guarantees. Never invent reviews, statistics, awards, client names, or guarantees. Where a fact is missing, write a clearly marked slot in square brackets for me to fill in.

IMAGES
Do not generate any images in this pass. Leave clearly sized image slots with a short note describing the ideal photo. I will add imagery in a later step. Do not add photo credits or stock photo notes anywhere on the page.

FUNCTION
The primary button appears in the header, in the hero, after the proof section, and at the end of the page. Prepare the page to connect to [your form or calendar]. I will confirm the connection myself after the build. Include a footer with the business name, service area, contact slots, and the main links.

QUALITY BAR
Design mobile first, then scale up to tablet and desktop. No sideways scrolling at 390 pixels wide. Tap targets are easy to hit. Text contrast meets accessibility standards. Use semantic headings in order, with one H1 only. Every image or image slot has descriptive alt text. Keyboard focus is always visible.

PROCESS
Build the full structure, design, copy, and motion in this single pass. Do not ask me questions unless something truly blocks the build. Do not publish. When you finish, report three things: what you built, section by section. Every interaction you actually implemented, and where it lives in the code. Every square bracket slot I need to fill. If you could not build something on this list, say so plainly instead of saying it is done.