GuidesProduct

The 90-Second Client Intake Pattern for Small Teams

Intake should feel immediate for clients and structured for operators. This pattern keeps both without sacrificing data quality.

Folio Team • May 6, 2026 • 2 min read

On this page

Build two tracks in one flow
Use a constrained first screen
Implement the 90-second intake sequence
Add progressive enrichment after first submit
Measure friction at handoffs
Prevent common intake failure modes
2-week rollout plan

Intake has one job: convert initial client intent into structured operational context fast. If intake takes too long, clients abandon. If it is too loose, teams rebuild context manually later. See how portal setup can happen in 10 minutes when intake is designed correctly.

Intake objective

Speed without structure creates downstream chaos. Structure without speed kills completion.

Build two tracks in one flow

Great intake combines:

a client speed track (minimal friction to submit), and
an operator context track (enough metadata to route and execute).

Two-track intake model

Track	Primary goal	Minimum data captured
Client speed track	Submit quickly with confidence	Identity, category, key artifact
Operator context track	Route correctly on first touch	Priority, owner routing key, dependency signals

Use a constrained first screen

Most intake abandonment happens before first meaningful action. The first screen should do only three things:

First-screen requirements

One clear CTA and one obvious next step.
2-4 required fields max for first submit.
Category hints with concrete examples.
Visible trust cue (security/privacy statement).

First-screen design quality

High friction

12 fields, multiple optional paths, no examples.

Low friction

3 required fields, one path, category examples, immediate progress cue.

Implement the 90-second intake sequence

90-second intake flow

0-20s: Start

One CTA with plain-language promise: “Submit request in under 90 seconds.”

20-45s: Identify

Capture client identity + request category only.

45-70s: Submit core artifact

Guide first upload with accepted format and one sample.

70-90s: Confirm and route

Show completion receipt, expected response time, and next action.

intake-minimum-fields.json

{
"clientId": "required",
"requestCategory": "required",
"primaryArtifact": "required",
"priorityHint": "optional",
"notes": "optional"
}

Minimum viable payload for routing

Add progressive enrichment after first submit

Do not request all metadata upfront. Ask for additional context after successful first submit.

Progressive enrichment stages

Stage 1: Capture intent

Get only what is needed to create the request and route to the right queue.

Stage 2: Capture execution detail

Request supporting fields based on selected category and client type.

Stage 3: Capture optimization data

Collect optional process details that help future automation, not immediate routing.

Measure friction at handoffs

Track conversion at each handoff to pinpoint abandonment and ambiguity.

Intake handoff metrics

Start → submit rate

adoption

Share of users who complete initial request.

Submit → valid rate

quality

Requests passing initial validation without correction.

Submit → routed SLA

speed

Time to assign request to owner queue.

handoffs to monitor: start, submit, route

Source: Folio intake benchmark

Prevent common intake failure modes

Rapid intake tradeoffs

Pros

Faster first completion rates.
Lower abandonment on mobile devices.
Cleaner initial dataset for routing automation.

Cons

Requires strong post-submit enrichment design.
Needs category taxonomy discipline to avoid routing errors.

2-week rollout plan

Intake rollout sequence

Days 1-3

Map existing intake

Audit current fields, abandonment points, and manual routing fixes.

Days 4-7

Launch constrained first screen

Deploy minimal first-submit path with explicit examples.

Days 8-10

Add progressive enrichment

Move non-essential fields to post-submit stage.

Days 11-14

Tune by handoff metrics

Adjust copy, validation, and category cues based on drop-off data.

Implementation rule

If intake requires training to complete, it is over-engineered. Good intake should be self-guided and auditable.

Get more intake playbooks

The 90-second intake pattern works because it captures intent first, structure second, and detail third, in that order.

Stay close

Want more practical client-ops playbooks?

Join the waitlist and get the next essays on request automation, document operations, and client delivery systems.

Join waitlist