Affiliate disclosure: This article contains affiliate links. I may earn a commission if you buy through them, at no additional cost to you.
Research checked October 5, 2026. This is a documentary guide based on the official sources linked below. It does not claim personal product testing.
A small agency sales pipeline should show the next action needed to win or close a real opportunity. It should not be a collection of optimistic deal names with no owner, deadline, or evidence.
If this fits your requirements, check HubSpot’s current offer while you work through this guide.
HubSpot can hold the records and stages, but the agency needs to define the process. Start with a simple pipeline that your team can keep accurate, then add automation after the manual workflow is clear.
Separate contacts from opportunities
A person who downloads a resource is not automatically a sales deal. Define what must happen before an opportunity enters the pipeline. For example, a prospect might express a specific service need and agree to discuss scope.
Keep the distinction explicit so deal totals do not become a disguised contact count. A large pipeline with weak entry rules can mislead the team about upcoming work.
For each accepted opportunity, record a responsible owner and the next agreed action. If you cannot name either, decide whether the record belongs in the pipeline or in a different follow-up process.
Use stages with observable entry and exit criteria
The official pipeline guide explains the available setup and notes that capabilities depend on subscription and permissions. Check your account before designing multiple pipelines or advanced rules.
A hypothetical agency could use: qualified inquiry, discovery scheduled, discovery completed, proposal sent, decision pending, closed won, and closed lost. These are sample stages, not a required HubSpot configuration.
Define the evidence for each stage. “Proposal sent” should mean a dated proposal was actually delivered. “Decision pending” should have a known decision process or agreed next contact. A stage called “hot lead” says little about what has happened.
Keep required data small and useful
Start with service need, decision-maker, expected start date, scope, deal amount, next action, next-action date, and owner. Add a field only when it supports a decision or repeated task.
If the agency sells both one-time projects and retainers, define the amount consistently. Do not put one month’s fee in some deals and a full year’s contract value in others without labeling the difference.
Write a short field guide with examples. A new team member should know what each field means without guessing. Consistent data is more valuable than a large collection of half-filled custom properties.
Discovery should resolve scope questions
Before sending a proposal, clarify the problem, desired outcome, existing resources, constraints, decision process, and timeline. Record what is known and what remains uncertain.
Do not move an opportunity forward merely because a meeting occurred. A discovery call that reveals poor fit may belong in closed lost or a deferred process. Progress means the buying decision has advanced.
For an agency, document who provides access and content, who approves deliverables, and what is outside scope. Those questions affect the proposal and later handover.
Every open deal needs a next action
Use a next action that someone can perform: send the revised scope, confirm the decision date, or obtain access requirements. “Follow up” is less useful unless it includes the purpose and timing.
Assign a date and owner. If the customer has agreed to a date, record that rather than inventing a daily reminder pattern. Keep communication appropriate to the relationship and applicable consent rules.
Review overdue actions during a short pipeline meeting. Decide whether to act, reschedule with a reason, or close the opportunity. A task should not remain overdue indefinitely because nobody wants to admit the deal is stalled.
Use amount and probability carefully
Deal value is an estimate until scope and price are confirmed. Label the basis and update it when the proposal changes. For retainers, specify the period represented.
If using stage probability, treat it as a planning assumption rather than a forecast guaranteed by the software. A hypothetical $10,000 deal at 40% probability contributes $4,000 to a weighted calculation, but the customer still either buys or does not.
Review assumptions against actual outcomes when there is enough history. Do not copy a generic conversion percentage and present it as the agency’s measured performance.
Separate sales closure from delivery readiness
Define closed won with the business’s actual commitment criteria, such as an accepted agreement and required initial payment. Then create a delivery handover with scope, contacts, due dates, promised work, and unresolved issues.
A sales deal is not the project-management system by itself. The delivery team needs a clear record of what was sold and who approves it. Include relevant proposal and agreement links with appropriate permissions.
Closed lost should have a concise reason. Distinguish no decision, budget, poor fit, competitor, timing, and unavailable service where those are useful categories. Avoid turning the field into an unstructured complaint about the prospect.
Check email and data practices
Before connecting email, understand what will be logged and who can see it. The agency should have a policy for sensitive client information and personal correspondence.
Seat type and permissions can affect capabilities. Read the seat-management guide and assign access according to the task. Do not buy or share a seat without identifying the work it must support.
For imports, clean a small sample and test the mapping first. Verify that contacts and companies are associated as intended and that an import does not trigger unwanted marketing or billing behavior.
Automate only after the process works
Start with manual stage changes and clear tasks. When the pattern is stable, identify repeated actions suitable for the automation available in your edition.
For each automation, define trigger, action, owner, exceptions, and test case. A workflow that creates duplicate tasks or changes the wrong deal can make the pipeline less trustworthy.
Keep the buying decision separate from the process design. A paid feature should solve a documented repetitive task or reporting requirement, not compensate for unclear stages.
Keep a useful weekly review
- Review overdue next actions.
- Check new opportunities against entry criteria.
- Update proposal amounts and decision dates.
- Identify stalled deals and close or defer them.
- Confirm won deals have a complete delivery handover.
- Record a small number of process improvements.
Use the official export guidance when checking data outside the CRM. Verify the export contains the fields needed for analysis and preserve sensitive information appropriately.
Next step
Evaluate HubSpot’s current tools against this simple process. Build one pipeline with real opportunities, test the handover, and expand only when the team can maintain the basics.
Official sources and next steps
- knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines
- knowledge.hubspot.com/account-management/manage-seats
- knowledge.hubspot.com/import-and-export/export-records
- legal.hubspot.com/hubspot-product-and-services-catalog
Compare the requirements above with your business before buying. You can find the tools covered on this site on the Resources page.
Build the business behind the tools
The tools in this guide are part of a bigger picture. At Ecommerce Paradise, I teach how to build and run a high-ticket ecommerce business. Start with a clear business model, then choose the tools that help you execute it.
If you are still figuring out the model, read my high-ticket dropshipping guide. You will understand the relationship between your store, suppliers, customers, and profit before spending money on software.
For product research, use my high-ticket niches list to explore categories and narrow down your ideas. Go deep before you go wide.
Next, work through my supplier sourcing guide so you know how to research manufacturers and approach them about becoming an authorized dealer.
My business formation checklist helps you organize the legal and financial setup. Use it to prepare your questions and confirm the requirements that apply to your business.
Get help putting the pieces together
If you want me to help you work through your next decisions, check out my private coaching. Bring your actual questions so we can focus on what is holding you up.
If you want a complete business build, take a look at the done-for-you store service. Review the scope and choose the support that fits your situation.

Trevor Fenner is the founder of Ecommerce Paradise. His main projects are Ecommerce Paradise, Supplier Paradise, and Review Paradise, which is currently in development. TrevorFenner.com publishes research-based reviews and practical guides to online business tools and remote-work services, with clear affiliate disclosures.
