What GEOKERT wants, and what the three variants must prove

Prepared October 3, 2026. This is a source-grounded working explanation for Matt and the design builders. It distinguishes direct client requirements, older superseded ideas, implementation decisions and outstanding production inputs.

The actual business goal

Tamás is not trying to maximise the number of leads. He wants more of the work he enjoys, with less time spent preparing quotations for unsuitable projects. The September 19 call makes this unusually explicit: he would prefer three enquiries with one suitable job to one hundred enquiries with three jobs. The client explicitly wants visitors to invest effort in understanding the work before requesting his time. Our implementation decision is to make browsing prominent and useful, with no stopwatch or arbitrary click quota. The later email permits a secondary generic enquiry route, so direct contact stays available.

His existing online identity overemphasises winter gardens. He now prefers terrace roofs because they are less complicated and suit the current business. Glass terrace roofs should lead. Winter gardens remain possible, but they must not own the headline or dominate the first viewport. A new visitor should understand within seconds that GEOKERT makes individual terrace roofs and should be able to recognise the kind of work before being asked for personal details.

This changes the design's success criterion. An attractive page that instantly pushes every visitor into a quote funnel would miss the brief. A page that hides contact information or frustrates informed visitors would also miss it. The intended balance is browse first, recognise fit, then enquire on purpose.

Sources and how conflicts are resolved

1. Latest relevant Wispr call: September 23, 17:29–17:38 Budapest. Full transcript read, not just the summary. Its title misspells the client's surname as Puchener. The email signature verifies Puchreiner Tamás.
2. Client edit email: September 23, 16:25 Budapest. Full plain-text body read. The client's own new paragraphs override the older September 21 proposal quoted below them.
3. Original design discussion: September 19, 16:30 Budapest. The entire transcript was retrieved across two character ranges. Another recording with the same title is unrelated accidental audio and was excluded.
4. Six local HTML references in GEOKERT HTMLs. They show previous design experiments, not approval of every word, number or control they contain.
5. The requested historic Codex chat was restored byte-exact from the October 2 backup, with complete JSONL and embedded-ID checks plus a successful Codex app readback. Its old decisions are historical context and cannot override September 23 corrections.
6. The client photo-upload folder and each of its four service subfolders were checked live. All four returned no files on October 3. Therefore the new variants use existing genuine GEOKERT imagery, and cannot be described as using newly selected client photos.

Wispr recency was checked with searches for geokert, telikert and Puchreiner, then by actual meeting start date. The most recently modified result is not necessarily the most recent call. The latest relevant captured call found is September 23. Gmail search from info@geokert.hu found the same September 23 edit email as the latest matching inbound message. These are scoped source findings, not a claim that every communication channel was searched.

What must appear, and in what order

The first view must say terrace roofs. Four immediately understandable topic links should take the visitor to the matching content on the same page:

Do not create separate main categories for every combination of timber/aluminium and glass/polycarbonate. The client explicitly settled on grouping by covering and describing the structure inside each roof group. Do not promote steel as the main structure. Do not offer bioclimatic pergolas or sliding glass curtains. Their presence in the old site or an old prototype does not establish current willingness to undertake them.

Each group needs a short description, meaningful real-project images, larger image viewing, and an enquiry action that remembers the group. The client also asks for optional deeper technical reading for visitors who like to learn. A same-page Műszaki tudnivalók disclosure can retain verified planning/material information without burdening the main introduction. The final discussion settled on one page without additional service pages. Anchors, expanded galleries and image overlays satisfy this without inventing new commercial scope. The visitor can browse in a normal scroll or jump directly to a topic. A clear phone/email route should remain available throughout.

The September 19 conversation describes contact details and a questionnaire appearing during scrolling, plus service content further down. It also repeatedly stresses that a visitor should see the work before personal interrogation. This is not a sufficiently precise wireframe to justify rigidly forcing one physical section order. The implementation must preserve the intent: service links lead to work, the enquiry form appears by deliberate action, and contact is easy to find.

The questionnaire: the corrections are specific

The email corrects the earlier proposal on both sequence and content. First ask what the person wants, approximate size, where they live or where the work is, and how they can be contacted. Only after that ask what they consider most important.

The exact priority choices are:

• Ár-érték arány
• Prémium minőség
• Funkcionalitás

This is one explicit choice, not a slider, percentage weighting or ranking of all three. Nothing should be selected by default. The client explains that leaving a slider in the middle supplies no meaningful answer. That criticism applies equally to a preselected radio button. All three answers should receive equal visual dignity. Choosing value for money must not trigger an invented rejection or shame the visitor.

Remove the budget question completely. The email says to take out how much the visitor intends to spend. The later call confirms the decision after explaining why fixed price bands confuse very different projects. Therefore do not replace the bands with an optional budget field, an estimate calculator, a hidden budget value, a project-price headline or a budget slider. These would resurrect a requirement the client removed.

There are two entry routes. A generic enquiry action may ask the service because it is unknown. A button inside a service's image/details section already knows the answer, so it should skip the redundant choice and go straight to describing that project. The service should still be visible and editable, so a misclick is recoverable without discarding the rest of the enquiry.

The email's mention of a second page is interpreted as a stage of the enquiry interaction, not a request to add a separate website page. The surrounding agreement is one page. Both routes must converge on the same fields and preserve information when moving backward. These review prototypes should explain their final action truthfully. A local prepared enquiry can be inspected or downloaded, with real phone/email links for contact. They must not display a fake successful delivery or send tests to the client.

The requested visual character

Keep the white, black and green brand. The client rejects purple and does not ask for a new brand identity. He finds the previous dark, tiled presentation gloomy and likens it to Microsoft's starting screen. A slightly different colour on the same equal-card grid would not answer that criticism.

The correction is more photographic life, better composition and less uniform boxing. In the latest call he asks for a softened image on the left, with a terrace roof or winter garden visible. It should look inward, bringing the eye into the page. A colour photograph can supply warmth through foliage, sunlight and materials without adding unrelated neon accent colours. The image should remain readable as a real project, not be washed away beneath an opaque overlay.

Three variants can explore materially different composition, typography, density and rhythms while holding these facts fixed. Each needs a visible green identity, generous readable text, more luminous areas, strong actual photographs and careful image crops. The dark/light alternation suggested in the call is one permissible implementation, not an order to paint every other section black. The underlying requirement is a page with life and coherent pacing.

Avoid generic premium slogans as the main proof. The client himself calls out how every business uses superlatives. Use the real projects, individual design, material choices, a transparent identity and a direct human contact to carry trust. Do not invent reviews, star ratings, project counts, construction guarantees, nationwide availability, response times or installation timelines.

Photos, identity and content that still need care

The client explicitly sets a maximum of fifteen distinct selected project photographs per topic, not an unlimited gallery. Fewer authentic images are acceptable in these review versions while the curated selection is unavailable. He also says some older winter-garden photographs remain useful. The uploaded selections are not currently present in the designated folders. Existing authentic photographs can make the variants complete and reviewable now. Actual available image counts must be stated, and images must not be duplicated merely to reach fifteen. The final curated set can replace the catalogue later.

Photo captions need extra caution. The client says some old captions were written by people who did not understand the work. An existing picture is evidence of a visible project, not reliable proof of an exact city, material specification or performance claim unless verified separately. Use restrained descriptive captions and retain origin metadata for replacements.

The requested contact email is info@geokert.hu, replacing info@telikert.hu. The client's email signature verifies +36 30 544 8384 and Puchreiner Tamás. He wants the actual company name, registered address and tax number visible, because he values transparent identity. Verified company identity is Geokert Építő és Kereskedelmi Betéti Társaság, registered headquarters 1063 Budapest, Szondi utca 60., tax number 24511573-2-42 and registration 01-06-787370. The prior official-registry verification and current company listing agree. Headquarters must not be presented as a walk-in showroom without evidence.

Hosting and email are separate matters. The call discusses a future website hosting move, while retaining company email. None of this authorises cancelling the current hosting contract, changing DNS/MX records, editing live client prices or deploying these variants onto the current business domain. The present output is three openly accessible review versions.

Critique: keep the goal, improve the implementation

The client's strongest insight is that an unsuitable enquiry has a real workload cost. Showing projects and asking for useful details is a sound response. The risk is interpreting browsing preference as an enforced obstacle. A five-minute timer, disabled contact button, forced gallery clicks or scroll lock would frustrate informed visitors and would not prove genuine intent. Build natural informed choice instead.

The single-priority question captures a conversation starter rather than a full purchasing model. Real customers may value all three. Preserve the requested single choice, use a prompt such as which matters most, and do not use the answer as an automatic acceptance decision. Optional description gives room for nuance.

Removing budget screening reduces one qualification signal. The replacement should be concrete project information, material/category context and a readable expectation of individual quotation, not covert price screening. This is a deliberate business preference, not a defect to optimise away.

The four groups are understandable, but roof covering and use case are different classification axes. A carport might use glass or polycarbonate. Short explanatory copy and visible chosen service can handle overlap, without multiplying categories into a confusing catalogue. Service-scoped calls to action must still permit changing the group.

Automatic picture changes can enliven the page, but fast rotation competes with careful browsing. Use a slow optional presentation with manual controls and a pause, or a static lead image with an obvious gallery. Motion must not obscure content, and reduced-motion preferences must be respected. The older proposal's three-second interval is not a binding client specification.

The variants should be judged by requirement fidelity, natural browse-to-enquiry behavior, real-photo quality, Hungarian copy, responsiveness, contact clarity and visual coherence. Distinctiveness is useful only when it helps this client's work. Two independent critics checked the explanation before the three builder assignments. The final decision record below explains how their material criticisms were handled.

Acceptance checks for all three builds

• One Hungarian page, terrace-roof-led hero, four correct service anchors, green brand and brighter genuine project photography.
• Service exploration precedes involuntary data collection. Every category supports correct larger gallery viewing and a contextual enquiry.
• Generic entry asks a service. Contextual entry retains it and skips repeat selection. Back/change routes preserve input.
• Project, size, location and contact fields precede the three exact priority choices. No default priority, numerical/proportional questionnaire sliders or money question. Manual photo galleries and slow optional picture carousels are permitted. Opening category actions lead to actual work, and optional technical reading is available.
• Real email/phone and verified company identity. No excluded service, unsupported promise or fabricated testimonial.
• Final review form action is honest and does not claim a lead was sent. No live test message or client email.
• Public bare review URLs, persistent comment document identities, preserved unrelated host routes, no automatic user-facing previews.
• Functional checks plus actual desktop/mobile section screenshots, multi-section runs and postdeployment QA. Missing evidence must be called unverified.

What the six supplied HTML references contribute

The file names express previous impressions, but none is a complete current specification. The source inventory checked their headings, sections, controls, images, links and scripts. The useful ideas can be retained while their older qualification logic and unsupported copy are replaced.

The new variants are independent redesigns, rather than copies of one reference with colours changed. They carry forward the useful terrace emphasis, imagery and project browsing while applying the latest client's corrections consistently.

Independent critique decisions

The requirements critic identified four important ambiguities. We resolved them by checking the complete original call, retaining explicit same-page technical reading, treating the image limit as up to fifteen distinct images per topic, and distinguishing permitted manual photo controls from the rejected questionnaire sliders. The client asks for browsing effort, but the resulting interface uses clear work galleries and deliberate enquiry actions without an arbitrary time or click requirement.

The UX critic tested the browse-to-enquiry journeys and proposed three different compositions. Its useful objections led to a visible, editable contextual service, retained input when moving backwards, equal priority choices without a default, honest prepared-enquiry wording, direct contact, and quiet technical disclosures. We kept the client's requested single-priority choice and removed all budget screening instead of silently changing these business decisions.

The final photo set contains 24 distinct project photographs: 10 glass roofs, 5 polycarbonate roofs, 3 actual carports and 6 winter gardens. Five carport renderings were excluded. Carport-07 was excluded after actual hosted image inspection established that it duplicates the view in carport-06. A further glass-category photograph, glass-08, was excluded conservatively after independent visual QA because completed glazing was not unmistakable in the image. No available photograph is labelled as a sandwich-panel project. All three variants share the same verified factual and interaction contract.

Three directions were built by the requested executors: architectural editorial by Astra High, garden-side photographic narrative by Sol 6.1 Max, and a numbered project catalogue by Sol 6.1 XHigh. Their layout and rhythm differ while the client requirements remain fixed. These are review prototypes and implementation judgments, not a claim of client approval or new commercial commitments.

Return to the three variants →