Marketing Proposal Project
De-Centraalweb-developer2026-04-08
Slide 01Why this now

De Verzetswinkel / De-Centraal landing page refresh

A sample web-developer proposal showing how De-Centraal can sharpen the first impression, separate reader and author journeys, and make the landing experience easier to act on.

Strongest assetReal origin story
Main issueBlurred hierarchy
Proposal typeSample deck

De-Centraal already has a strong story asset, but the current experience still asks visitors to assemble the value on their own.

The goal of this refresh is simple:

  • make the reader path unmistakable
  • make the author path unmistakable
  • make the first screen easier to trust and easier to act on

This is not a brand reset. It is a sharper first impression so the existing story converts more cleanly.

De-Centraal · web-developer1 / 6
Slide 02Current problem

The current page asks too much from the visitor

Audience splitReader + author
Mobile pressureHigh

The project has two audiences, readers and authors, but the experience does not yet separate their motivations strongly enough.

  • the real origin story behind De Verzetswinkel is powerful enough to lead the page, but it is not always framed as the primary conversion driver
  • CTA language and hierarchy are still softer than they should be
  • on mobile, the page has less room to explain itself, so weak hierarchy costs more
De-Centraal · web-developer2 / 6
Slide 03Proposed direction

Rebuild the top of the page around one dominant path

Hero patternProof-first
CTA modelSingle-primary

The best refresh direction is:

  • one dominant message
  • one dominant image
  • one dominant action

Lead with authenticity and proof first, then support it with a clear next step.

Create a cleaner branching model:

  • Bestel nu for readers
  • Stuur je manuscript or Neem contact op for authors
De-Centraal · web-developer3 / 6
Slide 04Refresh scope

What changes in the actual implementation

ScopeFocused
ReusabilityHigh

This proposal changes the page at the structural level, not just at the sentence level.

  • refresh the hero into a proof-first layout with a stronger headline, subhead, and CTA
  • raise trust signals higher, including story proof, reviews, and publisher credibility
  • simplify supporting sections so the page feels intentional instead of content-heavy
  • tighten mobile behavior so the primary action stays visible and usable
De-Centraal · web-developer4 / 6
Slide 05Technical approach

Build it as a reusable page system

Build styleModular
Future useCross-site

The refresh should be implemented as reusable sections, not as a one-off page rewrite.

  • use modular Gatsby sections that can be reused across de-centraal.nl and deverzetswinkel.nl
  • keep the structure flexible for future campaign pages and landing page variants
  • align the page architecture with measurement so future tests compare cleanly by path and source

This turns one refresh into a better system for future marketing work.

De-Centraal · web-developer5 / 6
Slide 06Success criteria

What success looks like after the refresh

Reader clarityFaster
Path confidenceHigher

Success is not just a prettier page. It should change behavior.

  • more visitors understand what the book is and why it matters within the first screen
  • more visitors choose the right path without hesitation
  • reader intent and author intent become easier to separate
  • the page becomes easier to test, improve, and reuse over time

The strongest asset remains the same: the real Bodegraven resistance origin story. The refresh simply puts that asset in the lead position.

De-Centraal · web-developer6 / 6