User Flow Mickael Rutembya · Flow Atlas

Offer detail

/expertises/agentic-ai/

Visitor reviews a specific capability offer, its mechanism, deliverables, evidence, and day-rate references.

User intent

What the visitor is trying to do

« I want to understand exactly what this offer delivers, see the proof behind it, and decide if it fits my context. »

Entry points

ElementDestination
Capabilities listing offer card/expertises/<slug>/
Hero matrix tile/expertises/<slug>/
Bento card/expertises/<slug>/

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor arrives"]) --> Offer["/expertises/<slug>/ (Offer detail)"] Offer --> Eng["/contact/#call-qualifier"] Offer --> Calc["/outils/calculator/"] Offer --> Projects["/realisations/"] Eng --> End(["Engagement started"]) Calc --> End click Offer "https://mickael-umt.com/expertises/agentic-ai/" "Open Offer" click Eng "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification" click Calc "https://mickael-umt.com/outils/calculator/" "Open Calculator" click Projects "https://mickael-umt.com/realisations/" "Open Evidence" click End "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification"

Screen inventory

IDScreenUser task
P0Offer detailReview mechanism, deliverables, evidence
P1QualificationSubmit structured call-qualification form
P2CalculatorEstimate engagement budget
P3Evidence listingBrowse related projects

Flow scenario

Scenario O1

CTO assesses AI Security offer

Trigger

  • Visitor clicks "AI Security" in the capabilities listing
  • Reads the before/after positioning block
  • Inspects the mechanism and deliverables list

Experience

  1. The offer detail page shows the capability title, promise, and evidence links.
  2. The visitor scrolls to the mechanism section and the deliverables grid.
  3. The day-rate reference table shows quartiles for this specialty.
  4. The visitor clicks "Qualifier une mission" → contact page with qualification form.
  5. On submit, the lead is created and the owner receives an audit event.

Trust and safety rules

  • All pricing is public and deterministic; no coefficient reaches the browser.
  • The calculator access gate blocks disposable and non-routable domains.
  • Payment pages are blocked by robots.txt and carry no editorial SEO value.
  • No card data touches the server; Stripe hosts the checkout page.

Interaction rules

  • Mobile fields use 16 px text to avoid browser zoom.
  • Reduced-motion preferences disable nonessential transitions.
  • Language toggle switches FR/EN across all strings.

Result states

StateWhat the visitor seesWhat happens next
ReviewingOffer detail with mechanism, deliverables, evidenceVisitor decides to engage or not
QualifiedConfirmation with quote contextOwner reviews lead
ConvertedStripe return page with entitlementsBuyer downloads or books