Stop starting projects with "TBD" in six fields.

Your project intake form asks for scope, timeline, the people involved, success metrics, and dependencies. You get back "TBD", "ASAP", "the usual people", "we'll figure it out", and "none." Three weeks later, everyone's surprised the project has no plan.

Real response comparison

Without AI

Problem: "we need this thing." Timeline: "ASAP." Dependencies: "none." (Actual dependencies discovered in week 3.)

~5 min

With Pluck + AI

A specific problem statement, a realistic timeline, named stakeholders, and dependencies identified upfront — because the form wouldn't let vague answers slide.

~10 sec

How AI changes this

Pluck's follow-up probes won't accept "ASAP" — they push the requester to estimate a timeline, name dependencies, and define success. If the requester's AI has access to org docs and past project data, it can suggest realistic timelines and flag known dependencies. Either way, the intake arrives complete.

How it works

1You create the form — add fields and follow-up probesyou

2Share the URL — drop it in Slack, email, or a docyou

3Respondent opens it in browser OR hands it to their AIthem

4Probes nudge shallow answers deeper — "can you be specific?"them

5Or their AI pre-fills from context (tickets, docs, conversations)AI

6You get specific, actionable responses in your dashboardyou

Example fields

Project name
Problem statement
Desired outcome
Stakeholders
Priority (P0-P3)
Target date
Dependencies
Success metrics

Follow-up probes

When an answer is too short, Pluck nudges the respondent to go deeper.

Problem statement

▸Who is affected?

▸How do you know this is a problem — any data?

Target date

▸What drives this date?

▸What happens if it slips two weeks?

Dependencies

▸Which teams need to be involved?

▸Have you confirmed their capacity?

Who this is for

PMOs, engineering managers, anyone who triages project requests and is tired of incomplete intakes.

Try Pluck for project intake

Free to start. Create your first form in 2 minutes.