Find sales-ready accounts in self-service signups
Combine company fit and product-use signals to identify existing users whose organization may benefit from a broader business conversation.
How this works
Combine company fit and product-use signals to identify existing users whose organization may benefit from a broader business conversation.
Find existing accounts worth a human sales review by combining permitted company fit with meaningful product activity. High usage alone can reflect testing, misuse or one enthusiastic user, so readiness must remain a documented hypothesis.
Before you start
Defined operating scope
Self-service signups provide company and usage signals relevant to a sales conversation.
Required source material
Obtain Signup and account domains; Permitted usage signals; Company attributes; Ideal-customer criteria. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
A signup uses a personal email domain. Keep company identity unresolved unless permitted evidence establishes it.
Prepare the inputs
- account_id
- Required
Workspace and verified domain
Distinguish personal email and shared agency domains.
- usage_window
- Required
Event counts and period
Use defined product events and exclude known test activity.
- company_attributes
- Required
Firmographic facts with dates
Keep uncertain company matches visible.
- readiness_rules
- Required
Fit and activity thresholds
Record rule version and reason for each criterion.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check account_id, usage_window, company_attributes, readiness_rules before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected account_id and any missing required fields.
Join account records with company attributes and relevant usage signals
- Join workspace records to company evidence and the selected product-use window, checking one-to-many domain relationships.
- Verify joins do not multiply event counts or combine unrelated workspaces.
Checkpoint: A saved intermediate result for: Join account records with company attributes and relevant usage signals.
Apply explicit fit and readiness criteria
- Apply explicit fit and readiness rules independently so strong usage does not conceal poor company fit.
- Check each readiness reason against the stated rule and time window.
Checkpoint: A saved intermediate result for: Apply explicit fit and readiness criteria.
Produce a reasoned queue of accounts for sales review
- Build an account queue with qualifying facts, missing information and the reason a conversation may be useful.
- Verify joins do not multiply event counts or combine unrelated workspaces.
Checkpoint: A saved intermediate result for: Produce a reasoned queue of accounts for sales review.
Check relevance before contacting the account
- Have the account owner review relevance, existing customer relationships and contact preferences before outreach.
- Check each readiness reason against the stated rule and time window.
Checkpoint: A saved intermediate result for: Check relevance before contacting the account.
Package the result and unresolved work
- Avoid sensitive personal inference and unsupported company matches. Confirm permission to use each data source and keep outreach decisions reviewable.
- Do not infer sensitive personal traits or purchase intent from incidental activity.
Checkpoint: A prioritized account queue with supporting business signals. Unresolved items remain visible in the review record.
Decisions along the way
A signup uses a personal email domain.
Keep company identity unresolved unless permitted evidence establishes it.
Usage is from a known sandbox or test account.
Exclude it from readiness calculations while retaining the exclusion reason.
Company matching is ambiguous.
Hold the account for review rather than merging unrelated organizations.
What you will produce
product-usage-to-sales-ready-accounts-result.json
JSONA prioritized account queue with supporting business signals. Label proposed and completed states separately.
Include: account_id · company_match · fit_result · usage_signals · readiness_reasons · missing_context · review_priority · status · evidence_reference · review_note
product-usage-to-sales-ready-accounts-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving readiness_rules.
Include: source_reference · question · owner · next_action
Check the result
- Verify joins do not multiply event counts or combine unrelated workspaces.
- Check each readiness reason against the stated rule and time window.
- Inspect account_id and usage_window in both the original and output; confirm that record identity and interpretation survived the transformation.
- Avoid sensitive personal inference and unsupported company matches. Confirm permission to use each data source and keep outreach decisions reviewable.
When something goes wrong
A signup uses a personal email domain.
Keep company identity unresolved unless permitted evidence establishes it. Retain the affected evidence and recovery status.
Usage is from a known sandbox or test account.
Exclude it from readiness calculations while retaining the exclusion reason. Retain the affected evidence and recovery status.
Company matching is ambiguous.
Hold the account for review rather than merging unrelated organizations. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Find sales-ready accounts in self-service signups for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Workspace W-3 has 12 active seats and repeated approved workflow runs; its verified domain maps to a company matching the target segment. W-4 has high test traffic only.
Expected result
Synthetic expected result: Queue W-3 with the specific fit and usage evidence. Exclude W-4’s test activity; neither account receives an automatic sales message.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure human-confirmed account fit; relevant conversations per reviewed shortlist.
Stop or revise
Company matching is ambiguous. Pause affected records and apply this recovery: Hold the account for review rather than merging unrelated organizations.
Keep the scope clear
- Do not infer sensitive personal traits or purchase intent from incidental activity.
- Use permitted account-level signals; outreach remains a reviewed decision.
Check before using
Avoid sensitive personal inference and unsupported company matches. Confirm permission to use each data source and keep outreach decisions reviewable.
Business activities
- Handle inbound enquiries
- Run sales conversations and proposals
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Signup and account domains · Permitted usage signals · Company attributes · Ideal-customer criteria
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow