Discussion draftPartnership proposal
A proposed strategic partnership between Shore, Betcher Consulting Group and HubSpot
Shore provides the sales methodology. Betcher Consulting Group translates approved methodology into practical CRM processes and tools. HubSpot provides the supporting platform. Together, the proposed partnership connects training, daily execution and manager coaching.



By connecting complementary expertise and builder relationships, Shore, Betcher Consulting Group and HubSpot could create opportunities that each organization would be less likely to generate independently. The proposed partnership combines referrals, licensed methodology, implementation services and event participation into a coordinated commercial approach.
Builder value explains why customers would buy. This proposal also explains how each partner could earn additional business. For the builder, the result is a clearer line between what the team learns, what salespeople do each day and what managers reinforce.
Introduce builders to the right expertise at the right time.
Turn approved training into tools salespeople use daily.
Educate the market on putting training into practice.
This is not a software implementation alone, and not a sponsorship arrangement alone. Each path is expected to produce both a builder outcome and a separate commercial outcome for the partner delivering it.

Sales methodology, coaching expertise, content guidance, approval of methodology applications, builder relationships and education or event opportunities.
A practical way to reinforce approved training between coaching sessions, extend its application and identify appropriate training opportunities.

Builder CRM strategy, implementation, translation of approved methodology into usable CRM tools, automation, reporting, sales enablement and user training.
A repeatable implementation and enablement offering that connects CRM execution with an established sales methodology.

Platform expertise, product-fit evaluation, sales collaboration and assessment of available partner or marketing support, subject to approval and program requirements.
A clearer homebuilder use case, appropriate platform adoption and stronger alignment between software and the builder's sales process.
Platform purchases, consulting engagements and Shore training services each keep their own scopes and agreements.
This proposal does not describe a joint legal entity, an approved bundled product or a shared contract.
Each partner would need a clear commercial reason to participate. The opportunities below are potential, not assumed. They describe where new business could originate if the partnership proceeds.



Paid engagements one partner could invoice: training and coaching, content licensing, implementation and configuration services, ongoing support, platform subscriptions and expansions, event sponsorship, and referral compensation where agreed and permitted.
Conditions that make revenue more likely rather than revenue itself: market visibility, stronger platform adoption, access to builder relationships, a repeatable offering and practical use cases that support evaluation. These are not counted as earnings.
A builder attending a Shore event wants to improve sales follow-through. A coordinated discovery conversation identifies a need for training reinforcement and CRM improvements. Shore could provide approved training or licensed content, Betcher Consulting Group could deliver implementation and enablement, and HubSpot could provide the appropriate subscription. Each component would be scoped and purchased according to the builder's needs.
Opportunities can begin with any partner. A Betcher Consulting Group client may need Shore coaching, while a Shore client may need CRM implementation. No partner is expected to purchase all three services to take part.
No revenue projections, pricing, percentages or budgets are included in this draft. Figures would be developed only after program eligibility, delivery effort and commercial terms are validated.
Opportunities would be attributed once. Existing client revenue would not be reclassified as partnership revenue.
We propose recognizing both direct introductions and meaningful influence in a buying decision, with eligibility and attribution agreed together.
In addition to revenue from each organization's own services, the partnership could explore sharing eligible HubSpot partner-program revenue associated with qualifying builder referrals. This could provide an additional financial incentive for generating and supporting new platform opportunities, subject to HubSpot's applicable program rules and a separately agreed commercial arrangement.
Referral eligibility, attribution, revenue participation and payment terms will be developed together.
HubSpot partner-program revenue, implementation-service referrals and Shore training referrals are treated as distinct streams. No revenue stream is assumed to be shareable.
This draft includes no percentage, guaranteed payment period or projected earnings. It does not assume Shore becomes a HubSpot partner or receives payments directly from HubSpot.
The proposed partnership term is separate from the duration of any eligible partner-program compensation.
Betcher Consulting Group's role is to connect approved methodology to practical system design, then help the team adopt it. Potential deliverables to scope and approve together:
Guided playbooks and structured questions.
Aligned with the 4:2 framework, subject to Shore validating the methodology.
Personalized prompts and templates.
Support for agreed next steps.
Support for coaching and adoption.
Focused on real sales conversations.
Motivation, questions and next steps the buyer explicitly tells the salesperson. This is the foundation of the record.
Website and email activity can inform follow-up. It is context, not proof of motivation or readiness.
This proposal does not reproduce Shore content or describe the details of the 4:2 framework.
Content rights, approval, permitted distribution, maintenance, updates and licensing fees remain to be agreed.
A recommended starting point for discussion, not an agreed scope. The pilot should answer one question: can we deliver meaningful builder value through an offering that is commercially worthwhile for each participating partner?
The pilot is not assumed to be free. Scope, fees and responsibilities would be confirmed in advance.
Pilot builder, users, scope, effort, fees and responsibilities remain to be agreed.
Specific automation, scoring, AI and integration capabilities depend on subscriptions, configuration, permissions and technical validation. Any AI-generated outreach, if explored, would be reviewed by the salesperson before sending.
Before implementation, the pilot should establish baselines and agree how progress will be reviewed.
Conversion changes have many causes. We would not attribute them solely to the pilot.
How sourced and influenced opportunities are recorded needs to be agreed. The same opportunity would not be counted twice, and existing revenue would not be counted as new.
Approved content, configuration patterns, training materials and reporting.
Communities, sales processes, routing, integrations and subscription needs.
The partners would decide what to standardize, what requires customization and who maintains each component.
The offering is not yet available or approved. Packaging, licensing, delivery and pricing remain open.
A coordinated education plan can create interest, help builders evaluate their needs and lead to appropriate conversations about training, consulting or the platform.
Summit sponsorship is one component of the wider relationship, not the relationship itself.
Sponsorship level, benefits, availability, budget, funding source and HubSpot participation remain open. No confirmed sponsorship, speaking slot, funding, attendee-data access, title sponsorship or exclusivity is assumed.
Joint branding, public case studies and use of builder results require approval.
Confirm shared objectives, roles, referral principles, content rights and the proposed pilot.
Select a mutually agreed builder use case, define deliverables, establish baseline measures and confirm scope.
Review adoption, follow-through, builder feedback, qualified business opportunities and delivery cost.
Refine the offering and decide whether to extend it to additional builders, content and events.
| Area | To agree |
|---|---|
| Revenue priority | Which opportunities to pursue first, and what makes each worthwhile for the partner delivering it. |
| Referrals | Qualification, existing relationships, attribution and revenue participation. |
| Partner-program revenue | Program eligibility, whether sharing is permitted, basis of compensation, timing and treatment of changes. |
| Delivery | Implementation scope, training responsibilities, support and fees. |
| Content | Licensing, approvals, permitted use and updates. |
| Ownership | Pre-existing intellectual property, reusable configurations, builder-specific work and maintenance. |
| Marketing | Activities, sponsorship, branding approvals and funding. |
| Operations | Relationship management, reporting and review cadence. |
| Duration | Agreement term, renewal, termination and treatment of active engagements. |
Shore expressed a preference for a multi-year partnership of at least three years. This is noted as a discussion preference, not an accepted term.
Partnership duration is separate from any HubSpot partner-payment period.
Let's agree on the commercial framework, then build a practical first step together.
David Betcher, Betcher Consulting Group