Check whether he suits your project
assess_fitRead-only
Compares a description of a project, business or problem against a fixed published rule and returns a verdict: good_fit, mixed, poor_fit or insufficient_information. Wording alone never produces poor_fit. Where the text touches one of the things Ashley turns down, the result lists questions in ask_these_then_call_again, and the three named fields take the person's own answers on a later call. poor_fit needs an explicit yes in one of those fields; good_fit needs an explicit no in all three. Having a development team is not the same as wanting Ashley to supply one.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| situation | Yes | What the person is trying to build or solve, their stage, team and constraints. Free text. | |
| wants_a_delivery_team | No | Does the person want Ashley to SUPPLY a team? Leading a team they already have is 'no'. | |
| must_start_within_a_week | No | Does the work have to start within a week? Starting within two weeks is the normal target, so that alone is 'no'. | |
| wants_spec_built_without_challenge | No | Do they want a finished spec built exactly as written, with no room to challenge it? A complete brief to quote from is 'no'. |