Multi-stepClients
Give every new project a clear start.
Collect contacts, goals, files, and launch details through a client intake form, then manage the next steps in a shared project database.
A complete worked example
Get a new client from signed brief to ready for kickoff.
Acorn has agreed to a campaign. The team needs a contact, brand files, and one place to track missing pieces.
Fictional project and sample data. This preview does not submit, publish, or change access.
Client intake; private tracker · illustrative result
Ready for kickoff?
A private team view built from the client's intake.
- Client contact
- Jamie
- Kickoff
- October 2
| Item | State | Next step |
|---|---|---|
| Project goals | Received | Read before kickoff |
| Logo files | Received | Check original SVG |
| Photography | Missing | Ask Jamie for delivery date |
What the client gets
One welcome page links to the brief and asset request. Submitted files stay connected to the intake record, so the designer can find both the material and its context.
What the recipient can access
Welcome page, intake form, and requested upload surface.
Kept out of this handoff
The team's readiness view, ownership, and working notes.
How it runs
- Gather the briefAsk for project goals, contacts, timing, and supporting uploads in one welcoming form. Choose where the assets belong.
- Organize the handoffKeep contacts and onboarding requests in the client project folder. Add internal owner and status fields for your team.
- See the next stepSave a pending-requests view, filter by target date, and chart the number of requests in each status.
- You getAn intake page for the client, contacts and requests tables for the team, and saved views that make follow-up work visible.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Create an onboarding database in Clients/[client name] with contacts and onboarding requests. Build a welcoming intake form for the client with company, contact email, project goals, target date, and supporting uploads saved to the client asset folder. Keep internal owner and status fields out of the form. Use our implementation team's existing folder permissions for the database. Create a pending-requests view and a chart of requests by status. Ask me for the client name and access settings before sharing the link.
What this workflow needs
Your team updates internal status and ownership in the database. Automated assignment can be added through a scoped webhook and an authorized external workflow.
Can internal notes stay out of the client form?
Yes. Choose exactly which database fields the form collects. Your team can maintain additional fields in the table without exposing them to respondents.