User Flow Mickael Rutembya · Flow Atlas

Engagement formats

/engagement/

Visitor compares collaboration formats (embedded, fractional, permanent), pricing policy, and decision profiles.

User intent

What the visitor is trying to do

« I want to choose the right collaboration format, understand the pricing policy, and see if my role and constraints match a recommended profile. »

Entry points

ElementDestination
Nav "Engagement"/engagement/
Home "Qualifier une mission"/engagement/#call-qualifier
Offer detail "Qualifier une mission"/engagement/#call-qualifier
Calculator "Discuter d'une mission"/contact/
CV "Qualifier une mission"/engagement/#call-qualifier

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor arrives"]) --> Eng["/engagement/ (Engagement)"] Eng --> Calc["/outils/calculator/"] Eng --> Audiences["/engagement/audiences/"] Eng --> Caps["/expertises/"] Eng --> Contact["/contact/"] Contact --> Qualifier["/contact/#call-qualifier"] Qualifier --> End(["Engagement started"]) click Eng "https://mickael-umt.com/engagement/" "Open Engagement" click Calc "https://mickael-umt.com/outils/calculator/" "Open Calculator" click Audiences "https://mickael-umt.com/engagement/audiences/" "Open Audiences" click Caps "https://mickael-umt.com/expertises/" "Open Capabilities" click Contact "https://mickael-umt.com/contact/" "Open Contact" click Qualifier "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification" click End "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification"

Screen inventory

IDScreenUser task
P0Engagement formatsCompare embedded, fractional, permanent formats
P1Pricing policyUnderstand day-rate reference and calculator
P2AudiencesMatch role and priority tension to an avatar
P3CalculatorEstimate engagement budget
P4CapabilitiesBrowse ten capability offers
P5QualificationSubmit structured call-qualification form

Flow scenario

Scenario G1

VP Engineering chooses engagement format

Trigger

  • Visitor opens /engagement/ from the main navigation
  • Reads the three format cards (embedded, fractional, permanent)
  • Scrolls to the pricing policy block

Experience

  1. The engagement page presents three formats: embedded engineer (2-5 days/week), fractional technical lead (architecture without full-time), and permanent/fixed-term role.
  2. The pricing policy explains that the public day rate is a reference, not the internal formula; coefficients remain server-side.
  3. The visitor clicks "Ouvrir le calculateur" to estimate the engagement budget.
  4. From the calculator, the visitor opens the audiences page to match their role and priority tension to a transformation avatar.
  5. The visitor browses capabilities to see which offer fits their context.
  6. Finally, the visitor clicks "Qualifier une mission" to submit the structured form and receive a recommended meeting format.

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.
  • Pricing policy is explicit: the public day rate is a reference, not the internal formula; coefficients are server-side only.

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
BrowsingEngagement formats with pricing policyVisitor compares formats and opens calculator
MatchedAudience avatar with recommended formatVisitor opens capability or qualification
QualifiedConfirmation with quote contextOwner reviews lead
ConvertedStripe return page with entitlementsBuyer downloads or books