From a product form to a B2B enquiry journey that starts with context.
JobOutfit’s previous enquiry paths could prepare a quote. What they lacked was shared business context: who is enquiring, from which industry, at what scale — and which procurement route fits? Leadforge designed and delivered the new joboutfit.de experience, from offer structure and information architecture to migration and measurement.
Before, the website primarily asked what should be quoted. Today, it first clarifies who is enquiring and what that business needs.
- LIVE ON JOBOUTFIT.DE
- LEAD VERIFIED INTO THE REAL INBOX
- GA4 + ADS, NO DUPLICATE IN THE TEST
PROJECT SNAPSHOT
- Client
- JobOutfit
- Market
- B2B workwear
- Brief
- Restructure the website and the enquiry journey into one connected lead system
- Leadforge scope
- Strategy · Information architecture · UX/UI · Copy · Build · SEO migration · Consent · Analytics
- Status
- Live · production-verified
- Evidence as of
- September 2026
The shop remained a separate system. Leadforge’s brief was the new lead-generation site on joboutfit.de and the connection between offer, orientation, enquiry journey, migration and measurement.
STARTING POINT
The problem was not simply “an old website”.
JobOutfit already had a modern shop. At the same time, the lean main site and the enquiry paths existed as separate parts running on different logic.
The previous forms were usable and did capture product-level detail for a quote. They asked about garment types, quantities, decoration and logo. What they never captured were the shared signals a business case needs: industry, team size and the procurement route that fits.
So the real brief was not cosmetic modernisation. Several touchpoints had to become one understandable B2B entry: clear enough for prospects, useful for the sales conversation, and robust enough for real operation.
THE CENTRAL DECISION
The decisive change was a question.
BEFORE
What should we quote?
The former shop enquiry path opened with product detail: eleven garment categories, quantities, decoration, logo upload and free text. That could prepare a quote. It said little about who was enquiring and which commercial route fitted.
TODAY
Who is enquiring — and what does this business need?
The new enquiry journey first distinguishes between individual outfitting, a defined team package and an employee ordering system. It then places industry, scale and context. The conversation starts with the business case instead of a long product list.
Specific items, quantities and logo files deliberately move into the follow-up conversation — a different order of information, not simply more fields.
VERIFIED PRODUCTION STATE
What is proven today.
- Defined migration cases verified
- 28/28Defined migration cases verified13 redirects and one 410 path, each in both slash variants.
- Documented measurement checks passed
- 33/33Documented measurement checks passedTag manager state, GA4 event and Google Ads path, checked live.
- Checked entry URLs indexed by Google
- 3Checked entry URLs indexed by GoogleHome and enquiry page on www, plus the shop home page.
- Third-party requests before consent
- 0Third-party requests before consentAcross 59 checked calls, every request was first-party.
Google loaded both sitemaps with 0 errors and 0 warnings. A controlled production test lead reached the real JobOutfit inbox; GA4 and the intended Ads conversion path fired without a duplicate conversion.
Does this sound like your starting point?
Then it is worth looking at where offer, enquiry journey and measurement currently fall apart on your side.
STRATEGY AND UX
Not more pages. One connected lead system.
Three commercial entry points
Prospects do not start by picking individual products; they pick the procurement route that fits: individual outfitting, a defined team package, or an employee ordering system.
Activate the existing industry logic
JobOutfit’s existing five-industry taxonomy was not invented by Leadforge. Leadforge connected it consistently to navigation, content and the enquiry journey, so orientation and qualification speak the same language.
One clear next step
Instead of competing calls to action, the site leads repeatedly into the same, initially unbiased enquiry journey.
Only claims that can be evidenced
Performance and process claims were tied to existing proof. Unevidenced historical figures and newly invented technical promises stayed out.
PRODUCTION PROOF
A lead journey is only real once it survives production.
A submitted form and a visible thank-you page are not proof. For acceptance, the entire chain was verified in production.
THE VERIFIED CHAIN, ONE CONTROLLED TEST LEAD
- 1Enquiry submitted on joboutfit.de
- 2The API confirms the request successfully
- 3The real email reaches the JobOutfit inbox
- 4GA4 records the intended event
- 5The intended Google Ads conversion path fires
- 6No duplicate conversion occurs in the controlled test
A “thank you” that means nothing is not a small bug
In staging, Leadforge found a defect of its own: the enquiry journey could show success even though the backend had not confirmed it. It never reached the production website. The logic was hardened so that only a genuine successful server response produces the success state — timeouts and errors stay errors.
Consent first, measured rather than asserted
Before consent, all 59 checked requests stayed first-party. The default is deny-all; granting, revoking and exactly one intended tag manager load were verified. The checked events carried no personal data, and no email leakage to Google was found.
+ Further verified detail– Further verified detail
- 21/21 checked pages with a unique title, canonical, description and H1
- Sitemaps of 19 and 1,013 URLs, documented with 0 errors and 0 warnings
- Tag manager live on version 3, six tags, no pending changes
- The conversion goal holds exactly the two intended actions, no legacy shop conversions
- Search Console set up as a domain property covering both hosts
- The form’s existing spam hardening carried over untouched
- The client’s existing API watchdog kept working to the same contract
- The live build is uniquely identifiable through a version file
TECHNICAL GROUNDWORK
A finding nobody was looking for.
During the relaunch SEO check it emerged that every checked page of the then digital presence carried noindex, nofollow: the one-pager of the time, five legacy landing pages and 25 representatively checked shop pages. The uniform value points to a site-wide setting.
Leadforge identified the finding; the technical fix was made on the client side. The shop was not part of the brief and was neither built nor repaired.
Migration and metadata were fully verified against defined rules, and Google read both sitemaps without error. That is the technical precondition for organic visibility — and explicitly not yet a ranking result.
DELIVERED STATE
What JobOutfit has today.
A named B2B presence that explains the offer and the industries more clearly. Three understandable procurement routes. An enquiry process that orders the business context first. A delivery path verified for real. A verified measurement and consent base. Fully checked migration logic. And a starting point indexed by Google for the next stage of evidence.
EVIDENCE STATE · SEPTEMBER 2026
What is proven — and what operation still has to show.
What is proven is the delivered state: the enquiry journey through to the real client inbox, measurement and consent verified against a documented check, fully verified migration, and indexing of the checked entry URLs. The individual records are one click away above.
Commercial effect — enquiry volume, conversion rate, cost per enquiry, revenue, rankings — will only be published once a dependable operating period and a comparable data basis exist. For organic visibility there will be no before-and-after: the Search Console property was created after the relaunch.
Is your website collecting product detail but not business context yet?
We look together at where offer, orientation, enquiry journey and measurement currently fall apart — and what would turn them into a dependable B2B lead system.