Use the CRM to make work visible. Do not confuse a populated property or an automated task with an authorized decision.
Start with relationships, not forms
HubSpot describes contact management, deal tracking, and reporting dashboards. That gives a foundation for relationship and pursuit records, but this guide is an implementation pattern, not a claim that every suggested feature is included in any particular subscription.
Model companies for distinct organizations and contacts for people. Keep the end customer, buying office, distributor, OEM, and prime relationship distinguishable. Create a deal for a specific pursuit rather than treating the company itself as an opportunity.
Keep the first pipeline small
Our suggested sequence is intake, qualification, bid review, quote or proposal preparation, submitted, and won or lost. Split pipelines only when the operating process genuinely differs, such as commercial sourcing versus a prime-led federal pursuit. Start with the smallest set of stages that creates clear decisions.
Each open pursuit should have an owner, a next action, a deadline, an authoritative source, and an explicit customer or partner relationship. Avoid filling the record with speculative fields that will never be maintained.
Treat approvals as controlled decisions
Make bid/no-bid, pricing exceptions, credit terms, representations, and submission authorization owner decisions. Automations can remind a person to review an issue; they should not invent the outcome. Keep source evidence and reviewer identity beside important attestations.
Before relying on any stage rule, test every write path you intend to use: user interface, imports, forms, and integrations. Document behavior instead of assuming all paths enforce the same control. Leave failed or uncertain checks visible for review.
Test intake without losing history
Submit a synthetic RFQ with a unique test identifier. Check that contact details, buyer type, source, and request text arrive intact. If repeated submissions update one contact, preserve each request as its own activity or intake record before creating a pursuit. A contact’s latest fields are not a reliable archive of every quote request.
Use idempotency keys for any deal-creation routine so a retry does not create duplicate opportunities. Verify form and automation entitlements in the actual portal, keep marketing consent separate from responding to an inquiry, and remove test records after validation.
Your evaluation checklist
Use this as a working prompt. Checkmarks stay on this page only and are not saved or sent anywhere.
0 of 4 completed
Method & disclosure. This is AI-assisted desk research using linked primary sources, not a hands-on product test. Recommendations are evaluation advice. Vendor links are direct, non-affiliate links in this edition. Verify current plan terms and applicable contract requirements before acting. Read our standards.