GTM PeopleConcept by ProdCraft — not affiliated with GTM People
For Ian — three cuts, one recommendation
Ian, this is an unsolicited redesign of gtm-people.com, built from your live copy and your 25 public roles. Every sentence on the concept is yours, verbatim; nothing is invented. Three cuts exist so you can compare; this page explains why I recommend the third.
The problem with brochure pages
Your live homepage is 4,373 words over 17,828 px on desktop (36,490 px on a phone). A founder who lands with one intent — "Series A, London, need a founding AE" — has to scroll 4,450 px to reach the roles, 8,682 px to reach pricing, and read a median of 190 words per screen on the way. The content is strong; the page makes the visitor do the work of finding it. Two of my own cuts had the same flaw in different clothes: the compact deck was still a brochure, only denser, and the scroll-story was a brochure stretched over 52,000 px.
Brief it — in five lines
- One input at the top: the visitor types the hire ("Series A, London, founding AE") or taps a stage; a demo brief types itself on load so the idea is obvious in five seconds.
- The page assembles itself under the input in about 300 ms: roles in play, market rate, your fee (with the £15,000-vs-£30,000 calculator), a dated five-day plan, why it works at that stage, the two FAQs that matter, next step.
- Every tile is a one-line header and a short answer; "Open" expands it in place to your full copy. One open at a time; no page navigation.
- "Looking for a role" flips the same board to the candidate side: roles first, your four candidate steps, JobSearchBud, register.
- Everything else — specialisms, 28 partners, insights, legal — sits in an index at the bottom, one tap from view, so nothing you publish is lost.
Measured: today vs the concept
| Measure (desktop 1440×900) | Live gtm-people.com | Brief it (v3) |
|---|---|---|
| Scroll to the first role matching "Series A London AE" | 4,450 px (jobs grid; then filter by hand) | 0 px — first matching role at 582 px, inside the first screen |
| Interactions to see pricing for your stage | Scroll 8,682 px, read four tiers, pick one | 0 — the recommended tier and calculator are on screen |
| Words visible by default | 4,373 | ≈ 710 on the page (board ≈ 400); all 4,373 one tap away |
| Default page height (desktop / mobile) | 17,828 / 36,490 px | 2,857 / 4,553 px (board 1,124 / 2,366 px) |
| Visible words per screen, median / max | 190 / 392 | 287 / 432 on desktop (one dense answer screen, then almost nothing); 108 / 158 on mobile |
| Third-party scripts | 3 (GTM, Cloudflare Insights, jsDelivr) | 0 (one Google Fonts stylesheet) |
| Weight (HTML + CSS + JS) | 1,004 KB / 41 requests | 113 KB / 6 requests |
The honest caveat is in row five: the answer board is denser per screen than your current page, because it is one screen of answers rather than many screens of prose. The visitor reads it once instead of scrolling for it.
The two other cuts
Everything on 1,773 px with tab panels. Median 224 words per screen — your content, compressed. Verdict: too dense.
A pinned film over 52,167 px. Median 35 words per screen, but the roles were 20 screens down. Verdict: too much scrolling.
What this unlocks for the agency
- Shareable brief links. "Copy link to this brief" writes
/#b=Series+A+London+AE&m=hiring; paste it in a LinkedIn DM and the founder opens a board already answering their question. - Agency view. A toggle overlays, on every tile, the live sentence or data row it came from — the honesty layer, and proof the page is built from your content rather than mine.
- A real model, when you want one.
worker/ask.jsis a Cloudflare Worker that sends the brief to Claude with your facts as the only allowed source and returns a one-line summary; setting one attribute on the page turns it on. Not deployed. - The roles feed. The 25 roles are a snapshot in the page today; the same tile reads a JSON feed from your ATS tomorrow, and the dots, counts and matches follow.
Next steps
- Open the concept on your phone and type a brief you had this week; tell me where the answer is wrong or thin.
- If it earns a conversation: a 30-minute call to decide what the board should answer that it cannot today (availability, time-to-fill by role, your own case studies).
- Then: wire the form, the roles feed and the Worker, and ship it at gtm-people.com — the build is static, zero-dependency and deploys to Cloudflare Pages in a minute.
Debanjan, Founder, ProdCraft · debanjan@prodcraft.fyi
Concept by ProdCraft — not affiliated with GTM People. All copy, prices and guarantees quoted are from gtm-people.com as of 2026-10-06.