Bondens WebbyråWEB THAT BRINGS MORE INQUIRIESSVENBook 15-min intro →
Case study

grusflak.se

Focused product site for dump bodies and side-board bodies direct from the factory

We built a premium, host-friendly microsite with clear product tracks, a knowledge hub and a quote start for a narrow B2B offer in the transport body segment.

WebB2BSEO

3

Product tracks

5

Knowledge articles

API

Separate lead flow

Book 15-min needs check →Send a short briefVisit grusflak.se→
Relevant servicesWeb developmentSEOServer management
No. 02 — Project in brief

Goal, solution and results

GOAL

The case

  • ✦Make the difference between dump bodies, side-board bodies and custom bodies clear immediately.
  • ✦Capture better quote briefs from the first contact.
  • ✦Build SEO surfaces around pricing, delivery, materials and buying guidance.
  • ✦Keep the front end fast and the deployment easy to host.
SOLUTION

What we did

  • ✦We built an Astro-based information architecture with a homepage, three product tracks, pricing, delivery, knowledge hub and quote flow.
  • ✦The product logic became editorial with a comparison table, product-near guides and CTAs that move users to the right next step.
  • ✦The quote flow was connected to a separate Node-based form API with SMTP delivery and a clear brief from the first request.
  • ✦The SEO foundation was handled through metadata, schema, sitemap, internal linking and articles close to commercial questions.
RESULTS

What changed

3 clear entry points

Product tracks

5 guides close to the sale

Knowledge articles

Separate API and a better brief

Quote route

No. 03 — Scope

What was delivered, broken down

SCOPE 01

Products & navigation

  • ✦Three clear product tracks in the main navigation
  • ✦Comparison table and product-near copy
  • ✦CTAs from guide to product and quote
SCOPE 02

SEO & content

  • ✦Knowledge hub around pricing, material and delivery
  • ✦Semantic metadata, schema and sitemap
  • ✦Internal linking between guides, products and quote
SCOPE 03

Quote & operations

  • ✦Node-based form API separated from the front end
  • ✦Host-friendly static Astro output
  • ✦Matomo for follow-up on key steps
No. 04 — How we drove it forward

Working in clear steps

STEP 011

Positioning & current state

We started with how a narrow B2B offer could feel more premium while becoming easier to understand.

STEP 022

Information architecture

Product tracks, guides, pricing and delivery were structured so the right questions are answered before quote.

STEP 033

Quote flow & technology

The front end stayed static and fast while lead handling lived in a separate API track.

STEP 044

SEO & release

Sitemap, schema, Matomo and a host-friendly build were set up for simple operations and further growth.

No. 05 — What it meant in practice

Outcomes that customers felt

OUTCOME

Better decision support before quote

Visitors can now compare tracks, understand materials and read guides before first contact.

OUTCOME

A stronger premium feel in a niche category

The site feels more considered and more appropriate for a narrow B2B offer.

OUTCOME

Easier to continue improving

Static output, a separate form API and a clean content model make future improvements easier to keep shipping.

No. 06 — Decisions and priorities

What we prioritized in the delivery

PRIORITIES

Take-aways

Clear route from guide to product to quote.Static Astro front end with a separate lead API.Knowledge hub that supports both SEO and buying-near questions.
Key decisions

Keep the front end fully static for fast loading and low operational complexity.

Let product tracks carry the navigation instead of hiding them behind generic company copy.

Split out quote logic into a separate API so lead handling can evolve without making the site heavier.

No. 07 — Selected views

Screens that show the solution in context

grusflak.se
1 / 6
1 / 6

Homepage

Next step

Want a similar clarity in your next project?

Book a short call and we'll walk through what would create impact at your company.

Book 15-min needs check →See selected projects
← Prev: bmcontainer.nuNext: gödselomrörare.se→
  • One team — design + tech + ops.
  • Clear priorities, not vague proposals.
  • Ownership after launch too.