Add Prospect Tool
add-prospect-toolInternal Coderbuds staff only. Add a company or adviser to the outbound pipeline.
The buyer to look for: a CTO, head of engineering or hands-on engineering manager at a product company with 10–30 engineers on GitHub or Bitbucket. Coderbuds does not support GitLab — a GitLab-only team is not a prospect, however good the fit otherwise looks.
Give the signal that made them worth writing down and the source_url it came from,
and put what you could not verify in qualification_needed rather than guessing. A row
whose signal is "looked like a fit" is a row nobody can act on later.
Everything starts at Sourced regardless of what you pass. Duplicates are worth checking
for first with get-prospect-worklist.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | company or partner. An adviser — fractional CTO, consultancy — is a partner. | company |
| name | Yes | Company or adviser name. | |
| signal | No | What makes them worth approaching now. | |
| website | No | Their website. | |
| location | No | Where they are based. | |
| priority | No | A, B or C. | |
| source_url | No | Where the signal came from, so it can be rechecked. | |
| contact_url | No | Profile URL for that person. | |
| next_action | No | The first thing to do about them. | |
| contact_name | No | Who to approach. | |
| contact_role | No | Their role as published, not as inferred. | |
| qualification_needed | No | What you could not verify. |