Replace PDF Intake with a Branded Client Onboarding Lumo

New clients still receive PDF intake packets—print, scan, email back, lose half the fields. Meanwhile your team retypes answers into Notion or a project tool. A branded onboarding Lumo collects everything once, in order, with validation and a searchable record in LumoPages Inbox.

Why this workflow works today

Professional services live on clarity before kickoff: goals, stakeholders, brand assets, access credentials, legal acknowledgments. Multi-stage Lumos let you explain why each section matters (reducing incomplete submissions) and branch by service line—retainer vs one-off project vs audit—using conditional logic.

Clients complete on desktop or phone; you avoid "see attached incomplete PDF v3 FINAL."

What you'll need

• Your standard intake questions (grouped by theme: company, project, brand, billing)
• Logo and brand colors for the Lumo
• List of file types clients must upload (logo pack, brand guidelines) if supported in your plan
• Internal owner who monitors Inbox and marks onboarding complete

Step-by-step: build the intake Lumo

Stage 1 — Welcome: Set expectations: time to complete (~10 min), who to contact with questions, confidentiality note.

Stage 2 — Company & contacts: Company name, website, primary contact, role, billing contact if different.

Stage 3 — Project scope: Dropdown for service package, launch date target, budget band, goals (long text), competitors (short text).

Stage 4 — Brand & assets: Links to Google Drive/Dropbox, or file upload fields for logos; checklist block for "Brand guidelines," "Photo library," "Access to ad accounts."

Stage 5 — Legal & preferences: Communication channel preference, signing authority checkbox, terms acknowledgment.

Use the AI Assistant to draft question copy, then tighten legally sensitive lines manually. Preview the full journey before sending the link in your welcome email template.

Connect it to your stack

Send the Lumo link in your contract-signed email ("Complete onboarding before our kickoff call"). Embed a slim version on your client portal page if you use Notion or a members area. Do not publish the link publicly—treat it as a process URL shared per client.

Optionally duplicate the Lumo per vertical (e.g., "Intake — E-commerce" vs "Intake — SaaS") with pre-tuned dropdown options.

Manage responses without a backend

Each submission is one row in Inbox with status workflow: New → In Progress (someone reviewing) → Resolved (ready for kickoff). Export to CSV for importing summaries into your PM tool, or PDF for client files. Team members without LumoPages seats can still receive exports.

Search by company name when a client calls mid-review. No more digging through email threads for "that one attachment."

---

Start building

Upgrade the first impression after the contract sign. Replace the PDF packet with one onboarding Lumo and start every project with clean, structured data.