Strong fit
Book discovery or send a bounded recommendation after qualification evidence is collected.
Discovery Booked or Recommendation Sent
Contact / Intake
Tell us where the work is breaking.
This intake starts an OS review. From there, we route your request into a Deploy review, Build discussion, clarification step, parked follow-up, or a clean no-fit.
Best-fit signal
The right lead has operating pain, not just AI curiosity.
The first screen checks whether there is live delivery work, founder-router pain, owner availability, and willingness to put real work into a system.
Founder-led AI, automation, AI-enabled consultancy, or B2B services team.
Recurring client delivery work is active now.
The founder or senior operator is still the router for work, decisions, QA, reporting, or escalation.
Three priority workflows can be named before scope expands.
An internal OS Owner can be assigned for the install.
The team is willing to move real work into a system of record.
Intake fields
Capture the fields that decide the next path.
The form captures enough context to choose the next move: Deploy review, Build discussion, clarification, parked follow-up, or no-fit. External CRM sync remains a separate approval gate.
Identity
NameWork emailCompanyWebsiteRole
Company fit
Company typeTeam sizeActive clients or projects
Operating pain
Where delivery is breakingFounder-router momentsMessiest handoff
Workflow fit
Repeating weekly workflowsCurrent system of recordWhere work actually starts
Ownership and timing
OS Owner candidateBudget fitAuthority pathStart timing
Routing paths
Every intake path has a next status.
Possible fit
Clarify missing budget, owner, authority, workflow, or timing fields before proposal work starts.
Qualifying
Build-first request
Route to Build only when the operating problem, user path, inputs, outputs, risk tier, and acceptance criteria are concrete.
Qualifying or Build discussion
Not ready
Park the lead with a real revisit trigger or disqualify when a hard blocker is present.
Parked or Disqualified
Public proof required
Do not move the lead forward on public outcome proof until the claim-review gate clears.
Parked or Disqualified
Hard filters
Some leads should not move into active sales.
The page makes the no-fit path explicit so Valdris does not sell around missing budget, owner, workflow, authority, or proof-gate boundaries.
No recurring team workflow
No active client delivery work
No buyer authority path
No budget for a 90-day implementation
No internal OS Owner candidate
Unwilling to move work into a system of record
Wants full automation without human accountability
Requires full tool migration before workflow design
Requires public proof claims before claim approval clears
Lead status flow
No lead gets an active status without a next action.
Public proof claims require written approval before publication. Intake can collect fit evidence; it cannot bypass claim review.
New
Qualifying
Discovery Booked
Recommendation Sent
Stakeholder Review
SOW Sent
Won
Parked
Disqualified
Lost
Private intake boundary
The public receipt excludes submitted personal fields and internal source-control IDs.