Federal Buyer Expansion Plan
# Federal Buyer Expansion Plan
## User Input
- **Target vendor:** [Vendor name, UEI, CAGE, GovTribe link, or company description]
- **Target buyer office:** [Federal agency, component, office, VISN, IC, command, acronym, or GovTribe link]
## Goal
Use GovTribe MCP tools to build a grounded **one-office federal buyer expansion plan** for a specific target vendor and a specific target buyer office.
A complete answer should produce an office-specific plan with representative buys, evidence-backed contacts, ordering-path analysis, and a light micro-offer menu.
## Required Input
The user must provide both of the following before analysis begins:
1. A **target vendor**
2. A **target buyer office**
Accept any of the following for the target vendor:
- Company name
- UEI
- CAGE
- GovTribe link
- Plain-language description only if it resolves to a single vendor without ambiguity
Accept any of the following for the target buyer office:
- Federal agency, component, office, VISN, IC, or command name
- Acronym
- GovTribe link
- Plain-language description only if it resolves to a single federal agency record without ambiguity
Optional constraints the user may provide:
- Additional context that may help resolve the vendor or the buyer office cleanly
Input rules:
- If either the target vendor or target buyer office does not resolve cleanly to one entity, ask for the minimum missing detail required to proceed.
- Do not guess the vendor, the office, or the office hierarchy.
- Do not start substantive analysis until both sides are resolved well enough to search.
## Workflow
### Steps
1. Call `Documentation` once with `article_names=["Search_Query_Guide", "Search_Mode_Guide", "Aggregation_and_Leaderboard_Guide", "Date_Filtering_Guide"]` before any other GovTribe tool.
- Use the documentation results to confirm valid tool names, filter names, `fields_to_return`, `query`, `search_mode`, and aggregation options before searching.
2. Resolve the target vendor with `Search_Vendors`.
- Use a double quoted `"query"` for exact names, UEIs, CAGEs, or GovTribe links.
- Request `fields_to_return` explicitly. At minimum request `govtribe_id`, `govtribe_url`, `name`, `uei`, `dba`, `business_types`, `sba_certifications`, `parent_or_child`, `parent`, `naics_category`, and `govtribe_ai_summary`.
3. Resolve the target buyer office with `Search_Federal_Agencies`.
- Use a double quoted `"query"` for exact names or acronyms.
- Request `fields_to_return` explicitly. At minimum request `govtribe_id`, `govtribe_url`, `name`, `alternate_name`, `acronym`, and `defense_or_civilian`.
- If the office label does not resolve to one federal agency record, stop and ask for the minimum clarification needed.
4. Set the fixed planning window and derive the vendor's lane focus.
- Use the last 24 months for office buying analysis. Do not ask the user to choose a different time window in this workflow.
- Run `Search_Federal_Contract_Awards` for the resolved `vendor_ids` as an aggregation-first vendor-history pass.
- Use `per_page: 0`.
- Request aggregations that characterize the vendor's recent federal lane. At minimum use `dollars_obligated_stats`, `top_naics_codes_by_dollars_obligated`, `top_psc_codes_by_dollars_obligated`, `top_set_aside_types_by_dollars_obligated`, `top_federal_contract_vehicles_by_dollars_obligated`, and `top_idvs_by_dollars_obligated`.
- Use this pass to derive the vendor's dominant recent NAICS, PSC, set-aside pattern, vehicle or IDV usage, and likely entry lanes.
- If this pass is too thin or too noisy to support a defensible lane focus, stop and ask the user for the minimum NAICS, PSC, or work-category guidance needed.
- Analyze the buyer office as both a `contracting_federal_agency` and a `funding_federal_agency` in later steps. Keep those roles separate.
5. Run aggregation-first office buying passes with `Search_Federal_Contract_Awards` for both office roles.
- Use `per_page: 0`.
- Run one pass with the resolved office in `contracting_federal_agency_ids`.
- Run a separate pass with the resolved office in `funding_federal_agency_ids`.
- Keep the 24-month window stable in both passes.
- Use the vendor-derived lane focus from Step 4 to interpret which office buying lanes are most relevant. Only add resolved `naics_category_ids` or `psc_category_ids` when the vendor-history aggregation pass fails and the user then provides explicit lane guidance.
- Request aggregations that support buyer planning. At minimum use `dollars_obligated_stats`, `top_awardees_by_dollars_obligated`, `top_naics_codes_by_dollars_obligated`, `top_psc_codes_by_dollars_obligated`, `top_federal_contract_vehicles_by_dollars_obligated`, `top_idvs_by_dollars_obligated`, and `top_transaction_points_of_contact_by_dollars_obligated`.
- Use these passes to identify how the office buys as a contracting node versus as a funding node, where those roles overlap, and whether the office appears to buy mainly through stand-alone awards, IDVs, or master vehicles.
6. Run row-level office award retrieval pass(es) with `Search_Federal_Contract_Awards` before any optional branch.
- Reuse the same stable 24-month window and office-role filters from Step 5.
- Paginate as needed rather than assuming the first page is enough.
- Retrieve representative rows for both the contracting role and the funding role. If one role is sparse or mostly duplicates the same core awards, say that clearly instead of forcing a redundant second row set.
- If the first page is dominated by very large outlier awards, off-lane buys, or records that are not representative of the vendor's plausible entry lane, run at least one additional row pass using the vendor-derived lane focus from Step 4 or a more representative sort before selecting the office's representative buys.
- Request `fields_to_return` explicitly. At minimum request `govtribe_id`, `govtribe_url`, `name`, `contract_number`, `award_date`, `completion_date`, `ultimate_completion_date`, `contract_type`, `descriptions`, `govtribe_ai_summary`, `dollars_obligated`, `ceiling_value`, `set_aside_type`, `awardee`, `parent_of_awardee`, `contracting_federal_agency`, `funding_federal_agency`, `naics_category`, `psc_category`, `federal_contract_vehicle`, `federal_contract_idv`, `transaction_contacts`, and `originating_federal_contract_opportunity`.
- Use these rows to select representative recent buys and confirm how the office behaves in each role, its ordering-path pattern, and repeat-awardee behavior.
7. Run a vendor-fit and access pass with `Search_Federal_Contract_Awards`.
- Use the resolved `vendor_ids` for the target vendor.
- First check for direct office overlap in the same 24-month window against both the contracting-role cohort and the funding-role cohort from Step 5.
- If direct office evidence is sparse or absent, run one careful adjacent-evidence pass that compares the vendor against the office's dominant NAICS, PSC, value band, and recurring vehicle or IDV patterns.
- Keep direct evidence separate from adjacent evidence. Label adjacent evidence as adjacent or inferred rather than presenting it as direct office familiarity.
- Use this pass to decide whether the vendor appears to have direct office access, partial ordering-path access, only adjacent lane evidence, or no meaningful evidence yet in each office role.
8. Run the ordering-path branch only when the office award evidence shows meaningful IDV or vehicle concentration.
- First use `federal_contract_vehicle` and `federal_contract_idv` already returned on award rows.
- Only call `Search_Federal_Contract_IDVs` or `Search_Federal_Contract_Vehicles` when a dedicated follow-on lookup materially improves correctness.
- For IDV follow-on calls, seed the search from IDs already returned on award rows whenever possible and request fields such as `govtribe_id`, `govtribe_url`, `name`, `contract_number`, `award_date`, `last_date_to_order`, `contract_type`, `description`, `govtribe_ai_summary`, `ceiling_value`, `multiple_or_single_award`, `set_aside`, `awardee`, `parent_of_awardee`, `federal_contract_vehicle`, `contracting_federal_agency`, `funding_federal_agency`, `naics_category`, `psc_category`, `task_orders`, `transaction_contacts`, and `originating_federal_contract_opportunity`.
- For vehicle follow-on calls, seed the search from IDs already returned on award rows whenever possible and request fields such as `govtribe_id`, `govtribe_url`, `name`, `award_date`, `last_date_to_order`, `contract_type`, `descriptions`, `govtribe_ai_summary`, `set_aside_type`, `shared_ceiling`, `federal_agency`, `federal_contract_awards`, and `originating_federal_contract_opportunity`.
- Use this branch to explain how the office routes work, whether the lane is stand-alone or vehicle-mediated, and whether the vendor already holds a plausible access path.
9. Run the evidence-backed contact branch with `Search_Contacts`.
- Use the resolved office through `federal_agency_ids`.
- Prefer `reference_types` of `pointOfContact` and `transactionContact`.
- When representative awards from Step 6 materially sharpen the contact set, add `referenced_govtribe_ids` from those awards.
- If the office-wide contact cohort is broad, noisy, or dominated by contacts outside the vendor-relevant lane, narrowing with `referenced_govtribe_ids` from the most representative awards is required.
- Request `fields_to_return` explicitly. At minimum request `govtribe_id`, `govtribe_url`, `name`, `email`, `phone`, `title`, `role`, `organization`, and `parent_organization_details`.
- If this branch returns no usable contacts, say so clearly. Do not invent broader outreach targets.
10. Run the current-opportunity branch as a required live-demand check.
- Use `Search_Federal_Contract_Opportunities` with the resolved office and the strongest office-lane filters derived from earlier steps.
- Run an active-solicitation pass with `opportunity_types=["Solicitation"]`.
- Use a future-facing `due_date_range` so the solicitation results are currently open for bid.
- Run a recent pre-solicitation pass with `opportunity_types=["Pre-Solicitation"]`.
- Use `posted_date` with `from="now-180d/d"` on the pre-solicitation pass so only recent near-term demand remains.
- Request `fields_to_return` explicitly. At minimum request `govtribe_id`, `govtribe_url`, `name`, `solicitation_number`, `opportunity_type`, `set_aside_type`, `posted_date`, `due_date`, `descriptions`, `govtribe_ai_summary`, `federal_meta_opportunity_id`, `federal_contract_vehicle`, `federal_agency`, `naics_category`, `psc_category`, and `points_of_contact`.
- Keep active solicitations separate from pre-solicitations in the final answer.
- If one bucket returns no usable results, say that clearly rather than implying current demand exists.
- Use this step to validate whether current demand resembles the historical buying pattern and to sharpen pursuit angles and next actions.
- Do not let sparse or off-pattern live opportunities override the office's core buying profile.
11. Perform a verification pass before finalizing the office plan.
- Remove obvious outlier awards or weak adjacent-evidence claims and confirm the main office-buying pattern still holds.
- Lower confidence if the plan depends on sparse office history, one-off vehicle signals, or one-record contact evidence.
- This pass does not require an extra tool call unless the current evidence still leaves the office pattern in doubt.
- If evidence is too thin to support a credible office plan, say so clearly and stop.
## Output Format
Return the answer in this order:
1. **Vendor and Office Resolution**
- Briefly explain how the target vendor and target buyer office were resolved.
- State that this workflow uses the last 24 months of office buying behavior.
- State that the office was analyzed as both a contracting office and a funding office.
2. **Search Approach**
- Briefly explain which GovTribe tools were used.
- Briefly explain how the vendor-history lane-derivation aggregation pass, the office-role aggregation passes, the office row pass or passes, the vendor-fit pass, the contact pass, the mandatory active-solicitation pass, and the recent pre-solicitation pass were used.
3. **Office Buying Profile**
- Use a required markdown table.
- Recommended columns: `Dimension`, `Finding`, `Evidence`.
- Cover dominant work categories, leading awardees, value-band pattern, concentration, recurring ordering paths, the vendor-derived lane focus, and any contracting-versus-funding differences that matter.
4. **Representative Recent Buys**
- Use a compact markdown table.
- Recommended columns: `Role`, `Award`, `Awardee`, `Date`, `Value`, `Structure`, `Why It Matters`.
5. **Evidence-Backed Contacts**
- Use a compact markdown table.
- Recommended columns: `Contact`, `Organization`, `Role / Signal`, `Why Relevant`.
- If no evidence-backed contacts are available, say so clearly instead of fabricating a contact list.
6. **Ordering Path and Access Assessment**
- Explain whether the office appears stand-alone, IDV-led, vehicle-led, or mixed.
- Explain whether the vendor shows `Direct`, `Adjacent`, `Inferred`, or `Weak` access evidence and why.
- Label inferences clearly.
7. **Office-Specific Pursuit Angles / Light Micro-Offer Menu**
- Provide 3 to 5 concise pursuit angles or micro-offer themes.
- Tie each one directly to observed buying evidence, work category, value band, or ordering path.
- Do not turn this section into a full offer packet, CLIN build, or long outreach draft.
8. **Current Open and Near-Term Opportunities**
- Use a compact markdown table.
- Recommended columns: `Stage`, `Opportunity`, `Agency`, `Due Date / Posted`, `Lane Fit`, `Why It Matters`.
- Use the `Stage` column to distinguish `Open Solicitation` from `Pre-Solicitation`.
- If no open solicitations are found, say so clearly instead of implying current demand exists.
- If no recent pre-solicitations are found, say so clearly instead of implying near-term demand exists.
9. **Recommended Next Actions**
- Provide concise next steps for the vendor's federal buyer expansion plan.
- Reflect the current opportunity scan, including monitoring guidance when no open solicitations are found.
10. **Overall Confidence**
- State overall confidence and briefly explain the main supporting evidence and limitations, including live-demand signal quality.
## Citation Rules
- Only cite sources retrieved in the current workflow.
- Never fabricate citations, URLs, IDs, or quote spans.
- Use exactly the citation format required by the host application.
- Attach citations to the specific claims they support, not only at the end.
## Grounding Rules
- Base claims only on provided context or GovTribe MCP tool outputs.
- If sources conflict, state the conflict explicitly and attribute each side.
- If the context is insufficient or irrelevant, narrow the answer or state that the goal cannot be fully completed from the available evidence.
- If a statement is an inference rather than a directly supported fact, label it as an inference.Last updated
Was this helpful?