Three proposed approaches

How should the new
Joblogic site be structured?

Based on your content strategy, persona documentation, and the workshop outcome — entry must be problem-based, not role-based. Below are three structural approaches, each with a different philosophy. Click any option to explore the full prototype.

3 structural options click any card to open the interactive prototype
Jump to: User journeys ↓
Workshop outcomes

What we know going in

These three principles apply to all options. They are non-negotiable based on the workshop outcome and client documentation.

Workshop outcome
The entry point must be problem-based — challenge-led ("I need to increase profit margin") — not role-based. Visitors identify with their challenge before they identify with a job title.
Two stakeholder types
Strategic decision makers (MDs, FDs) and operational influencers (Service Managers, Ops Managers). Content and tone differs at the destination — the entry point can be shared.
Client preference
Not many wildly different journeys. Only differentiate where the user need genuinely demands it. One coherent site, not a choose-your-own-adventure.
Inputs used

How we applied your documentation

Both documents you shared directly shaped the structure, language, and journey logic of each option below. Here is specifically what we took from each.

📄
Work Settings & Personas document
Provided by Joblogic · Completed by Iqra Manzoor
What we took from it
Two primary customer types — Contractors and Estate/Facilities Managers — confirmed the two distinct audiences the site needs to serve. This informed the two stakeholder tiers (strategic decision makers and operational influencers) that run through all three options.
Nine internal roles (Contract Manager, Service Delivery, Finance, Project Manager, Office Manager, HR, Marketing, Fleet) — used to populate the Roles nav dropdown and the role/persona inner pages in the prototype. Finance Team and Contract Manager mapped directly to strategic decision maker journeys; Service Delivery and Office Manager mapped to operational influencer journeys.
Six work settings (Contracts, Ad-Hoc Works, Equipment Sales, Projects, Subcontractor Works, CAFM) — confirmed the range of job types the platform handles. Contracts, Ad-Hoc, and CAFM informed the challenge page topics and the "Win and manage contracts" and "Scale across multiple sites" challenge categories.
Finance Team responsibilities (P&L, job costing, contract performance, invoicing) — used as the basis for the "Increase profit margin" challenge and the MD/FD strategic journey in all three options.
Service Delivery Team responsibilities (scheduling, dispatch, mobile, job recording) — used as the basis for the "Dispatch engineers faster" and "Reduce admin overhead" challenges, and the operational influencer journeys.
🗂
Notion content strategy
Provided by Joblogic · Referenced in workshop
What we took from it
Problem-based entry confirmed — the content strategy's own framing of audience pain points reinforced the workshop decision that entry must be challenge-led, not role-led. Visitors identify with "I need to increase profit margin" before they identify as "a Finance Director."
Pain points mapped to challenges — the six challenge categories used across all three options (increase margin, reduce admin, stay compliant, win contracts, dispatch faster, scale multi-site) were drawn directly from the pain points documented in the content strategy across small, medium, and enterprise segments.
Segment structure — SMB, mid-market, and enterprise segmentation from the content strategy confirmed that journey differentiation should happen at the destination page level (tone, product tier recommendation) rather than at the homepage entry point — supporting the single shared entry approach in Options 2 and 3.
Content pillars informed nav groupings — the Operate / Oversee / Grow framework in the content strategy directly shaped the Resources dropdown structure and the "Run the job / Manage the business / Scale the operation" three-part framework used in Option 3's homepage.
Navigation structure at a glance

How each option reshapes the top-level nav

What stays, what's new, what's changed, and what's removed — across all three options.

Note on "Customers": The current live site has a "Customers" nav item. Option 1 retains it as-is. Option 2 proposes merging its content into the Challenges section — case studies and testimonials becoming proof points within each challenge page rather than a standalone destination. Option 3 elevates it to a top-level "Case studies" item, giving social proof more prominence in the nav.
Persona mapping

Who lands where

How each of the four key persona types finds their path in each option — and how clearly the site serves them. For full step-by-step journeys, see the section below.

Persona Option 1 — Evolved Option 2 — Problem-first Option 3 — Single journey
MD / Financial Director
Strategic decision maker
Medium clarity
Clicks "Solutions" → job costing or reporting feature → pricing → demo. Journey works but feature framing may not resonate emotionally for an FD evaluating ROI.
High clarity
Clicks "Increase profit margin" challenge card → challenge page written in their language → Enterprise/Premium tier → demo. Most direct path for this persona.
Medium clarity
Hero statement resonates ("stop losing money") → scrolls "Manage the business" section → case study by company size → pricing → demo. Relies on scroll behaviour.
Service Manager
Operational influencer
High clarity
Clicks "Solutions" → scheduling or dispatch use case → Standard/Premium → free trial. Well served by existing feature-led nav they are comfortable navigating.
High clarity
Clicks "Dispatch engineers faster" card → challenge page in operational language → Standard tier → free trial. Challenge cards map precisely to their day-to-day pain.
Medium clarity
Hero statement less specific to them → "Run the job" section resonates → pricing → free trial. Journey is clear once they reach the right section but takes longer.
Contract Manager
Operational influencer
Medium clarity
Clicks "Solutions" → contract management use case → products → demo. Reasonable path but contract management is one of many features listed, easy to miss.
High clarity
Clicks "Win and manage contracts" challenge → dedicated page → Premium/Enterprise → demo. Only option with an explicit contract-focused entry point.
Lower clarity
Must scroll to find relevant content. No explicit contract management hook on the homepage. Likely navigates to Industries or Resources instead.
Office Manager
Operational influencer
Medium clarity
Clicks "Solutions" → admin or scheduling → products → trial. Served adequately but the feature framing is not explicitly about reducing their workload.
High clarity
Clicks "Reduce admin overhead" challenge → page addressing their exact frustration (paperless, automation) → Standard → trial. Best served by this option.
Medium clarity
"Run the job" section covers their territory. No specific hook for them but they can identify through the scheduling and job management content.
Per-option user journeys

How each persona gets to "yes"

Select an option, then a persona, to see the exact path through the site from first click to conversion. This expands on the "who lands where" table above with the full step-by-step journey for each audience type.

Option 1 entry logic: Visitors arrive at a homepage with three router cards — “Find your role”, “Find your use case”, “Explore products”. The new “Solutions” nav item provides direct problem-based access, layered on top of the existing site structure.
Strategic decision maker
MD / Financial Director
ROI-driven evaluator. Cares about margin, compliance risk, and operational visibility. Not interested in feature lists.
01 — Lands on
Homepage — “Solutions” nav
Clicks the highlighted “Solutions” nav item — the only new top-level item — and selects “Increase profit margin” from the dropdown.
02 — Gathers information
Job costing feature page
Explores job-level P&L, margin by contract, and invoice delay reduction. Feature framing — may not carry full ROI emotional resonance for an FD.
03 — Key decision point
Premium vs Enterprise comparison
Reviews feature differences between tiers. This is where they evaluate whether the investment is justified at their scale.
04 — End page
Pricing page
Lands on pricing with enough context to evaluate per-user cost against operational ROI. Tier recommendations help guide the choice.
05 — Conversion
Book a demo
Opts for a sales conversation — high-value evaluation, needs tailored walkthrough from the Joblogic team.
Journey assessment for this persona in Option 1: Medium clarity The path works, but feature framing doesn’t speak natively to FD concerns. ROI language is buried inside use case pages rather than leading the experience.
The three approaches

Choose your prototype

Each card opens the full clickable prototype. Trade-offs, nav structure, and journey example are shown below.

1
Low disruption
Evolved live site
Start from the current joblogic.com. Keep the existing nav structure but add a problem-based entry layer on the homepage. The least risky path — proven SEO structure preserved, conversion improved.
What changes
"Solutions" added as the first and highlighted nav item — problem-led entry without restructuring everything else
Homepage cards reframed around challenges, not categories
Existing Products, Features, and Industries nav kept intact for SEO and returning visitors
Example journey — Strategic (MD / FD)
Lands on
Homepage — "Increase margin"
Gathers information
Job costing feature page
Key decision point
Premium vs Enterprise tier
End page
Pricing page
Conversion action
Book a demo
Trade-offs
Lowest SEO risk — existing page equity preserved
Familiar to returning visitors, minimal retraining
Seven top-level nav items still competes for attention
No tonal differentiation between strategic and operational visitors
View Option 1 prototype
2
Balanced evolution
Problem-first nav
Build on the Huble v2 prototype. Replaces the existing nav logic with a Challenges-led structure mapped directly to the pain points in Joblogic's content strategy. The strongest alignment with the workshop outcome.
What changes
"Challenges" replaces Features as the primary nav item — each challenge maps to a pain point from the content strategy
Homepage cards: "I need to solve a challenge / Evaluate the platform / Find my industry"
Destination pages carry tonal differentiation for strategic vs operational visitors
Example journey — Operational (Service Mgr)
Lands on
Homepage — "Dispatch faster"
Gathers information
Challenge page — scheduling and dispatch
Key decision point
Standard vs Premium features
End page
Pricing page
Conversion action
Free trial
Trade-offs
Directly reflects the workshop outcome — problem first throughout
Single shared entry, differentiated destination — minimal journey forking
"Challenges" as a nav label needs client buy-in
New challenge pages need to be written from scratch
View Option 2 prototype
3
Max CRO focus
Single conversion journey
No homepage fork. One bold problem statement, one primary CTA. Visitors self-segment through scroll behaviour and content resonance — not through an explicit choice widget. The most conversion-focused option.
What changes
Homepage hero leads with a single bold problem statement and one primary CTA — no cards, no fork
"How it works" replaces Products + Features: Run the job / Manage the business / Scale the operation
Case studies surface in the nav — social proof at the point of evaluation, not buried in Resources
Example journey — all visitors
Lands on
Homepage — hero statement
Gathers information
Scrolls — "How it works" sections
Key decision point
Case study — relevant industry
End page
Pricing page
Conversion action
Book a demo
Trade-offs
Fewest decision points — aligns with Hick's Law, fewer options = faster decisions
Matches client preference for not wanting many wildly different journeys
Requires one agreed hero problem statement — needs client alignment first
Biggest departure from current site — highest content rewrite effort
View Option 3 prototype