User Flow Mickael Rutembya · Flow Atlas

Home

/

Landing page entry points: hero matrix, specialty bento, positioning columns, and primary CTAs to engagement, capabilities, and projects.

User intent

What the visitor is trying to do

« I want to understand what this consultant does, see proof of capability, and decide whether to engage. »

Entry points

ElementDestination
Hero matrix capability tiles/expertises/<slug>/
Specialty bento cards/expertises/<slug>/
Primary CTA "Qualifier une mission"/engagement/#call-qualifier
Secondary CTA "Examiner les preuves publiques"/realisations/
Consultant band "Voir le parcours détaillé"/parcours/

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor arrives"]) --> Home["/ (Landing)"] Home --> CapDetail["/expertises/<slug>/"] Home --> EngQual["/contact/#call-qualifier"] Home --> Projects["/realisations/"] Home --> CV["/parcours/"] CapDetail --> EngQual Projects --> CV CV --> EngQual EngQual --> End(["Engagement started"]) click Home "https://mickael-umt.com/" "Open Home" click CapDetail "https://mickael-umt.com/expertises/agentic-ai/" "Open Offer" click EngQual "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification" click Projects "https://mickael-umt.com/realisations/" "Open Evidence" click CV "https://mickael-umt.com/parcours/" "Open CV" click End "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification"

Screen inventory

IDScreenUser task
P0LandingChoose an entry point
P1Capability detailReview offer, mechanism, evidence
P2Evidence listingBrowse projects by domain
P3Career pathRead profile, competencies, certificates
P4QualificationSubmit structured call-qualification form

Flow scenario

Scenario H1

CTO evaluates AI security offer

Trigger

  • Visitor lands on home page
  • Clicks "AI Security, Assurance & DevSecOps" in the bento grid
  • Reads the before/after positioning block

Experience

  1. The home page hero matrix shows the capability tile with code "AS".
  2. The bento card opens /expertises/ai-security/ with mechanism, deliverables, and public evidence.
  3. The visitor clicks "Qualifier une mission" → opens the contact page with the qualification form pre-focused.
  4. The form captures outcome, urgency, budget, and collaboration format.
  5. On submit, a CallQualification row is created and the visitor sees a confirmation with a quote context.

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
BrowsingHome page with hero matrix, bento, and CTAsVisitor chooses a path
QualifiedConfirmation with quote contextOwner reviews lead
ConvertedStripe return page with entitlementsBuyer downloads or books