Description:

We are rebuilding our login and session logic using Webflow (frontend), Memberstack (auth), Wized (frontend logic), and Xano (backend). Our goal is a clean, secure, persistent authentication system that can scale and support future analytics, CRM, and backend processes.

This project will be executed in two phases:

Phase 0: Map the UX and Data Flow of the Auth Journey

Before any implementation begins, we want a clear visual and functional map of how authentication will work from both a user experience and technical standpoint.

Deliverables:

A UX flow diagram showing signup, login, logout, redirect, and session behavior

Session behavior mapping (e.g. what happens on browser refresh, tab close, etc.)

A simple data flow showing how Memberstack → Wized → Xano will interact

Notes on edge case handling (e.g., gated page access while logged out)

Annotations explaining redirects, expected fields, session persistence, etc.

This phase must be reviewed and approved before Phase 1 begins.

Phase 1: Build the Auth & Session Integration

Based on the approved Phase 0 flow, you'll implement the full system across the stack.

Deliverables:

Memberstack login/signup/logout with persistent sessions

Page-level gating in Webflow for private content

Wized integration to access session data and drive redirects

Xano integration to sync user records on login/signup

QA of the full flow, including session behavior and user record creation

Documentation of how the system is structured (short Loom or README)

Stack Overview:

Webflow (frontend)

Memberstack (authentication and user management)

Wized (logic layer)

Xano (backend)

Segment, ActiveCampaign, GA4 (future phases, not in scope yet)

Timeline:

Phase 0 delivery: within 3 days of project start

Phase 1 delivery: within 5–7 business days after Phase 0 approval

Communication:

Use Loom or screenshots to explain visual decisions

Regular check-ins or async updates every 1–2 days

Final handoff must include a Loom walkthrough and simple documentation

To Apply:

Share examples of projects using Memberstack and/or Wized with Webflow

Briefly describe how you would approach mapping the flow before building

Let us know your availability and hourly rate or preferred fixed pricing

• Memberstack (authentication and user management)
• Final handoff must include a Loom walkthrough and simple documentation
• Share examples of projects using Memberstack and/or Wized with Webflow

• Our goal is a clean, secure, persistent authentication system that can scale and support future analytics, CRM, and backend processes
• Phase 0: Map the UX and Data Flow of the Auth Journey
• Before any implementation begins, we want a clear visual and functional map of how authentication will work from both a user experience and technical standpoint
• A UX flow diagram showing signup, login, logout, redirect, and session behavior
• Session behavior mapping (e.g. what happens on browser refresh, tab close, etc.)
• A simple data flow showing how Memberstack → Wized → Xano will interact
• Notes on edge case handling (e.g., gated page access while logged out)
• Annotations explaining redirects, expected fields, session persistence, etc
• This phase must be reviewed and approved before Phase 1 begins
• Phase 1: Build the Auth & Session Integration
• Based on the approved Phase 0 flow, you'll implement the full system across the stack
• Memberstack login/signup/logout with persistent sessions
• Page-level gating in Webflow for private content
• Wized integration to access session data and drive redirects
• Xano integration to sync user records on login/signup
• QA of the full flow, including session behavior and user record creation
• Documentation of how the system is structured (short Loom or README)
• Phase 0 delivery: within 3 days of project start
• Phase 1 delivery: within 5–7 business days after Phase 0 approval
• Use Loom or screenshots to explain visual decisions
• Regular check-ins or async updates every 1–2 days
• Briefly describe how you would approach mapping the flow before building