User Flow Mickael Rutembya · Flow Atlas

Offer Detail

/expertises/<slug>

Visitor inspects a specific offer: mechanism, deliverables, evidence, pricing, and CTAs to qualify or estimate.

Flow intent

What the user is trying to do

« Understand what this engagement delivers, how it works, and what it costs — then decide if I want to request a quote. »

Entry points

ElementDestination
Capabilities catalogue offer card/expertises/<slug>
Expertise category offer card/expertises/<slug>
Programmes related offer/expertises/<slug>

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR A["Visitor clicks offer"] --> B["Land on /expertises/<slug>"] B --> C["Read hero and promise"] C --> D["Review mechanism section"] D --> E["Check deliverables"] E --> F["View evidence and references"] F --> G["See pricing / day-rate"] G --> H["Click Request quote"] H --> I["Land on contact form"] G --> J["Click Contact"] J --> I F --> K["Click related capability"] K --> L["Land on capability detail"] C --> M["Return to capabilities"] M --> N["Browse other offers"] click B "https://mickael-umt.com/expertises/agentic-ai/" "Open Offer" click I "https://mickael-umt.com/contact/" "Open Contact" click L "https://mickael-umt.com/expertises/agentic-ai/" "Open Capability" click M "https://mickael-umt.com/expertises/" "Open Capabilities"

Screens

ScreenKey contentCTA
Offer detailHero, mechanism, deliverables, evidence, pricing, related offersRequest quote, Contact, Compare
Contact formFree-form message or structured qualificationSubmit message, Book call
Capability detailScore, evidence breakdown, skillsCompare, See related

Scenario

Scenario

CTO evaluates AI Production Assurance offer

Trigger

  • CTO searches "AI production assurance" on Google
  • Organic result links to /expertises/agentic-ai/
  • CTO clicks through to evaluate the service

Experience

  1. Page loads with hero, promise, and mechanism explanation.
  2. CTO reads deliverables list and sees 4 concrete outputs.
  3. Evidence section shows public repositories and audit proofs.
  4. Day-rate reference gives budget context.
  5. CTO clicks "Request quote" and fills the contact form.

Trust and safety rules

  • Structured data (Service schema) is present for rich SERP results.
  • No inflated claims — mechanism and deliverables are specific and verifiable.
  • Evidence links point to public repositories and on-chain certificates.
  • Pricing is transparent — day-rate references help budget planning.

Interaction notes

  • Page uses Open Graph and Twitter Card meta tags for social sharing.
  • Bilingual content via data-fr/data-en attributes.
  • Related offers are filtered by capability family.
  • Offer URL is stable and never changes (SEO-friendly).

Result states

StateWhat the visitor seesWhat happens next
BrowsingVisitor reads offer details, no clickMay return or explore other offers
ComparingVisitor clicks related capabilityReads capability score, may return
QualifyingVisitor clicks Request quote or ContactMoves to contact/qualification flow
ConvertingVisitor submits formLead created → owner notified → follow-up