How does Strkr handle the long sales cycle common in consultative B2B?
Strkr ships the consultative pipeline pre-wired with the stages (Discovery, Assessment, Pilot, Proposal, Negotiation, Signed) with per-stage activities and exit criteria that gate stage progression. The long-cycle Flow automation runs stage-specific cadence: weekly in Discovery, bi-weekly in Assessment, monthly during Pilot, weekly in Negotiation. The quiet-stretch nurture Flow fires when a deal goes quiet for 30 days with Strkr AI drafting a value-added touch (relevant industry article, benchmark data, event invitation). The multi-stakeholder cadence runs different touches for different buying committee roles. The mutual action plan surface creates a shared document per deal with commitments and next steps tracked. The pattern reflects the real consultative motion instead of forcing the rep into a transactional template, which is where most independent sales representative CRM deployments break.
How does the referral network tracking actually work?
Every contact on Strkr carries a referral source field (previous client, industry contact, professional association, strategic partner, inbound, outbound) with the referrer named. The attribution runs through to opportunity and closed revenue, so the rep sees which referral sources drive the most value. The partner-level LTV surface shows which referral partners have driven the most pipeline and closed revenue over the career. The referral partner nurture Flow fires quarterly outreach to the top-decile referral partners with Strkr AI drafting personalised touches based on recent activity and shared professional context. The reciprocal referral tracking captures referrals the rep sends to partners, which balances the referral ledger. The professional association tracking connects membership, event attendance, and speaking engagements to the referral flow. The pattern treats referrals as a first-class growth engine instead of a free-text attribution field.
How does trailing commission tracking work for multi-year contracts?
The trailing commission tracking surface captures each contract with the term (annual contract value, contract length, renewal cadence) and the trailing commission structure (percentage of ACV per year, bonus on renewal, override on expansion, commission vesting schedule). The commission dashboard shows the commission flow forward across the contract term: year one, year two, year three, with the renewal risk flagged on contracts approaching the renewal date. The commission forecast rolls up expected trailing commission by month, quarter, and year, so the rep has cash-flow visibility across the full book. When a contract renews, the trailing commission continues; when a contract churns, the trailing commission ends and the chargeback flow fires if the contract terms require it. The pattern replaces the parallel-spreadsheet tracking that most independent sales representatives run with a native workflow that keeps the long-term revenue visibility intact.
What happens if I change corporate principals or add a new principal?
Adding a new corporate principal is a configuration change in the admin UI: define the principal with the commission structure, the client ownership rules, the sales methodology nuances (consultative stages, pilot engagement pattern, mutual action plan template), and the reporting cadence. The new principal starts flowing deals the day the principal is activated without a data migration or a configuration project. Dropping a principal preserves the historical deals, commissions, and client activity on the Strkr tenant with the principal reference preserved for audit and historical reporting. The client ownership tagging per principal (configured in the admin UI based on the actual principal contract terms) surfaces which clients are portable (the rep can take them to a new principal) and which are non-portable (the principal retains ownership). The referral network stays with the rep regardless of principal changes, so the rep rebuilds the pipeline on the new principal with the referral engine intact.
Can Strkr handle multiple principal relationships simultaneously?
Yes. The multi-principal model on Strkr supports multiple corporate principals on one tenant with clean separation on commission structure, client ownership rules, and reporting while sharing the referral network, the client activity surface, and the professional network. A rep representing three principals (an IT value-added reseller carrying security, backup, and networking vendors; a business development consultant representing legal, consulting, and accounting firms; a SaaS reseller carrying five software vendors) runs three or more separate commission flows on one tenant with the cross-principal view available on the dashboard. The admin configures each principal in the admin UI with the per-principal rules, and the cross-principal reporting shows the aggregate book value, the aggregate commission forecast, and the aggregate pipeline across all principals. The pattern is particularly common for seasoned independent sales representatives who have built multi-principal portfolios over years.
Does Strkr work for a solo representative or does it require a team?
Strkr works for both solo representatives and small representative groups. For solo reps, the single-seat subscription covers the full workflow with Strkr AI running as the admin surface for configuration, Flow design, reporting composition, and data hygiene. The solo rep sets up the tenant in a day: tenant creation, principal configuration, pipeline setup, commission structure definition, client import, referral network import, and user onboarding. The in-product onboarding tours walk the rep through the first week of use, and the Strkr support channel runs with sub-hour response during business hours for configuration questions. For small rep groups (2 to 10 reps with a managing partner), the multi-seat subscription supports per-rep principal assignment, override commission for the managing partner, shared referral network tracking, and group-level reporting. The pattern avoids the common failure mode where a solo rep buys a CRM designed for a corporate team, fails to configure it to the independent motion, and uses the system at ten percent of its functionality.