Built for Advisory Firm BD Leaders

The CRM for advisory BD, where every partner is a seller and every seller is a biller.

A BD leader at a 15 to 150 person advisory firm (management consulting, financial advisory, operations advisory, transaction advisory) runs a motion where the sellers are partners carrying 65 to 80 percent utilization targets, every engagement is a scoping conversation that reshapes value three times, and the pipeline rolls up across four or five practice groups with different cycle lengths. Strkr collapses that into one workspace with practice-level forecast rollup, partner-aware pipeline hygiene, and engagement margin visible beside the booking number.

Start free trial See pricing
Why buyers are here

Advisory firms BD Leaders: the daily pains.

Advisory firm BD leaders run a motion that neither a product-sales CRM nor a professional-services PSA tool was built around. The sellers are senior partners and principals who also carry client-service workloads, every pursuit depends on a scoping conversation that reshapes the engagement two or three times before signature, and the pipeline rolls up across practices that each sell different-shaped engagements on different cycle lengths. A standard Salesforce instance maps the motion to a single-stage dropdown graveyard. HubSpot funnels force the firm into a trial-conversion funnel built for software. The pains below are the ones that show up on every advisory BD leader call we run with firms between 15 and 150 people, and each one is a direct consequence of the partner-led, scope-heavy way advisory firms actually sell. The rest of the page shows how Strkr collapses the whole shape into one workspace where the pursuit, the partner, the margin, and the engagement hand-off all live on the same record.

Partners sell between client meetings

Senior partners carry 65 to 80 percent utilization targets.

An advisory firm BD leader manages a pipeline where every seller carries a utilization target that competes with BD time every single week. A standard CRM assumes a dedicated AE spending the full week on pipeline, and the activity dashboards punish partners for behavior that is actually a client hour booked for revenue. Pipeline tools built for SDR teams demand touchpoint volumes a utilization-targeted partner cannot sustain. Strkr ships a partner-aware tier that tracks BD time against utilization, surfaces pipeline moves without demanding activity rituals, and lets the BD leader run a review that respects the dual role instead of forcing partners to pick between the client and the pursuit on Monday morning.

Four practices, one forecast

Strategy, financial, operations, and transaction advisory roll into one number.

Strategy advisory closes in six to twelve weeks at a top-margin shape. Financial advisory engagements move on a slower regulated cycle with external deadlines (audit review, lender diligence) tied to signature. Operations advisory lands on a four-to-six month cycle with a scoping phase that reshapes value twice before signature. Transaction advisory moves on a deal-driven calendar where client urgency can collapse scope decisions into 72 hours. Rolling all four into one firm forecast inside a generic CRM means four spreadsheet tabs and a Friday night reconciliation call. Strkr runs native practice-area forecasts that roll up to a firm number with the four motions treated distinctly in the math and the renewal column captured as a first-class line.

Scope reshapes value three times

A $400K pursuit becomes $220K then $650K before signature.

Every advisory pursuit carries a scoping arc. The partner lands a $400K first proposal, procurement asks for a leaner Phase 1, the pursuit reshapes to $220K with Phase 2 and Phase 3 options, and the client eventually buys $650K because the diligence surfaced two more workstreams. A standard CRM holds one number on the opportunity, and the BD leader forecasts the pursuit at the first number without a trail of what moved. Strkr lets each pursuit carry a scope-version history on the record itself, with the current proposal, prior versions, and reasons for each shift pulled onto one timeline, so the forecast moves with the shape.

Margin tracked offline

Engagement margin lives in the scoping lead spreadsheet.

Every advisory deal carries a scoping phase that estimates hours per role per week, loads a blended bill rate against a cost rate, and lands on a target margin that justifies pursuit. Today that math lives on the scoping lead desktop and never makes it back to the pursuit record. Pipeline reports show revenue only, and margin becomes a quarterly reconciliation surprise. The BD leader cannot sort pursuits by margin band or flag the pursuit priced too thin before the proposal lands. Strkr lets the pursuit record carry a margin estimate alongside the booking number, so the BD leader sorts pipeline by margin as readily as by close date and approves the margin before the deal moves to proposal.

Cross-practice drift

A strategy engagement that pulls in operations never gets attributed.

The strategy partner closes an advisory engagement at a regional bank. Three weeks in, the client asks whether the firm can also run an operations review on the integration track. The hand-off happens in a hallway, no record attaches the second engagement to the first, and the referral chain evaporates before QBR. Strkr runs a native cross-practice referral primitive on the account record so the BD leader sees every multi-practice path, credits the originating partner on every downstream engagement, and reports referral revenue as a first-class line at QBR time.

Pursuit scored by stage math

A relationship-driven pursuit does not fit stage percentage math.

An advisory engagement advances because the senior partner had three conversations with the CFO and the CFO introduced the audit chair, who then looped in the operating committee. Stage percentage math built for software pipeline says the deal is at 20 percent because it has not left Qualified. The BD leader knows the pursuit is a 70 percent close inside sixty days and cannot defend that read in a CRM report, which forces every forecast conversation into a side channel. Strkr runs a relationship-weighted hygiene score that reads signal from meeting cadence, stakeholder count, partner engagement, and referral chain depth, so the BD leader forecasts the way the firm actually sells.

How Strkr fits an advisory BD week

The primitives an advisory firm BD leader actually uses.

Strkr for advisory firm BD leaders is the same CRM every partner, principal, and operations lead at the firm uses, with a BD-tier overlay for forecast rollup, pipeline hygiene, scope history, margin tracking, and cross-practice referral attribution. Everything below ships on every paid tier with no premium professional-services module gate. The primitives below map to the five jobs an advisory BD leader repeats every week: run partner pipeline reviews, roll a practice-area forecast, coach specific pursuits, track margin on open engagements, and manage the scope-version history on open proposals. When those five jobs happen inside one workspace with partner-aware context, the BD leader stops reconciling spreadsheets and starts coaching deals.

Practice-area forecast

Four motions, one rollup.

Strategy, financial, operations, and transaction advisory each roll up through their own forecast with motion-appropriate category math. Strategy uses commit, best case, and pipeline on a six-to-twelve week cycle. Financial moves on a regulated cycle with external deadline anchors. Operations lands on four-to-six month cycles with scoping checkpoints. Transaction advisory carries the deal calendar as the driving anchor. The four streams combine into a firm number without a Google Sheet, and the BD leader sees per-practice contribution at a glance.

Partner pipeline view

Every partner pipeline on one scrollable screen.

The BD leader opens the partner rollup and sees every partner pipeline grouped by partner, sorted by stage and close date. Filter by practice, deal size, margin band, or hygiene score to find the fifteen pursuits that matter this week. Collapse per partner when running firm-wide reviews and expand per partner when running a 1:1 on a specific pursuit, so the review flows from zoomed-out to zoomed-in without opening a second tool.

Scope-version history

Every proposal version on the pursuit timeline.

Each pursuit carries a scope-version history with the current proposal, prior versions, and a one-line reason for each shift pulled onto one timeline. The BD leader sees that a $400K pursuit reshaped to $220K at procurement review and then to $650K after diligence surfaced two more workstreams. The forecast moves with the shape, and the margin block updates with the version so the BD leader sees margin at the current scope, not the opening number.

Relationship hygiene score

A score that reflects how advisory actually closes.

Every open pursuit carries a hygiene score built from inputs that match the motion: meeting cadence with the economic buyer, stakeholder count across the account, partner engagement in the last two weeks, referral chain density, next-step date, and scoping completeness. Sort the partner pipeline by hygiene and the five pursuits that need a partner nudge this week surface above the fold.

Engagement margin on the pursuit

Margin estimate lives beside the booking number.

Each pursuit carries a scoping block with hours per role per week per partner, a blended bill rate, a cost rate, and a target margin. The number lands on the pursuit record, surfaces in every pipeline report, and lets the BD leader sort pursuits by margin band. The scoping lead edits the block inline, and the BD leader approves the margin before the deal moves to proposal.

Strkr AI pursuit risk

The pursuit the partner is overcommitted on, flagged early.

Strkr AI reads pursuit activity, email thread tone, meeting cadence, stakeholder movement, and scoping completeness, then flags pursuits where the partner commit looks optimistic versus the signal. The flag opens into a specific reason (no economic buyer meeting in 30 days, scoping phase slipping twice, procurement never engaged) so the coaching conversation is grounded in a case, not a hunch.

Cross-practice referral chain

Every multi-practice path attributed to the originating partner.

An account carrying a strategy engagement that spawns an operations review and a transaction-advisory diligence is one account with three engagements and one referring partner. Strkr renders the full chain on the account record with originating partner attributed, so firm-level reporting captures referral revenue as a first-class line at QBR time without a manual roll-up ritual every quarter.

Dashboards by practice

Partner, practice, and firm, one page.

The BD leader dashboard renders pursuit velocity by stage per practice, average deal size per practice, win rate per partner, cycle time per lead source, booked margin per practice, and referral revenue by originating partner. Each tile filters by practice, partner, segment, and timeframe. The weekly firm pipeline review runs off the dashboard in 20 minutes.

What Strkr automates for an advisory BD leader

The repeatable work the CRM should do before Monday.

The best advisory BD leaders are the ones who automate the repeatable moves and spend the week on partner coaching and account strategy. Strkr Flows handle the dozen automations every advisory BD leader should run, and each one ships as a native trigger with no webhook plumbing. The pattern below is what shows up in week two of every mid-sized advisory firm deployment, and each flow respects that the sellers are partners carrying utilization targets.

Forecast submit cadence

Monday open, Thursday nudge, Friday lock.

A weekly flow opens the forecast on Monday, nudges partners on Thursday if submission is still open, locks submissions Friday 5 PM firm-local, and rolls each practice number to the BD leader queue. Partners who miss the lock surface on a BD leader list without a chase email going out, and the practice number that rolls up is the number the practice agreed on.

Scope-shift notification

A new proposal version pings the BD leader with the delta.

When a scoping lead posts a new proposal version on a pursuit, the flow logs the version, calculates the delta against the prior proposal, and notifies the BD leader with a one-line summary (opened at $400K, reshaped to $220K, reason: procurement asked for leaner Phase 1). The BD leader walks into the next partner review already aware of every pursuit that moved, and the forecast update is a two-click confirmation instead of an interrogation.

Stale pursuit nudge

Pursuits past the per-stage threshold surface weekly.

Monday 7 AM, Strkr identifies every open pursuit past the per-stage age threshold with no partner activity in the window. Drops a nudge on the owning partner dashboard and attaches the batch to the BD leader partner review. The weekly review opens with the stale list already surfaced instead of the BD leader building the list live during the meeting.

Scoping handoff flow

Pursuit moves to proposal, scoping lead gets the brief.

A stage transition from Discovery to Proposal triggers a scoping handoff flow: the brief lands with the designated scoping lead, the margin block opens for edit, the BD leader is notified of the handoff, and the pursuit is tagged with the scoping lead for accountability. Nobody drops a handoff in the hallway, and the margin estimate reaches the pursuit record before proposal land day.

Cross-practice trigger

A new engagement on an existing account flags.

When a second engagement opens on an account that already carries one, the flow tags it as a cross-practice referral, credits the originating partner, and surfaces it on the referral dashboard. The firm captures referral revenue as a first-class number without a quarterly reconciliation call.

Risk-flag digest

Monday email, five pursuits, two paragraphs each.

Monday 7 AM email to the BD leader: the top five Strkr AI risk-flagged pursuits across the firm with the specific reason per pursuit and a suggested partner conversation. The BD leader walks into the Monday partner review with the risk list in hand. The digest frames the week coaching around five specific pursuits.

Partner utilization check

Partners drifting past the utilization split get a weekly flag.

Monday 7 AM, each partner sees utilization hours, BD hours, and the gap versus the target split for last week. Partners drifting past the band in either direction surface on a BD leader list for a soft conversation. The weekly rebalance arrives before the quarterly practice-lead confrontation.

Engagement renewal flow

Advisory retainers surface renewal 60 days out.

Advisory engagements with a retainer shape open a renewal pursuit automatically 60 days before contract end, assigned to the practice lead with current engagement data pre-attached. The renewal flows through the same forecast primitives as a new engagement, so the firm number captures renewal risk the same way it captures net-new pipeline.

What a BD leader sees that partners do not

The BD tier that respects the partner workspace.

A BD tier that creates a parallel UI is a tier partners resent, and at an advisory firm resentment at the top of the sellers list kills adoption firm-wide. Strkr keeps the partner workspace identical for partner and BD leader, then adds a BD-only overlay for practice rollups, private partner notes, risk flags, scope-shift history, and margin visibility that partners do not see on each other.

Firm rollup

Every practice pipeline on one scrollable view.

The BD leader firm rollup shows every practice pipeline on a single screen, grouped by practice and then by partner, sorted by stage and close date. Filter by segment, lead source, deal size, margin band, or hygiene score. Collapse per practice for firm-wide reviews, expand for a practice-specific session.

Private partner notes

BD leader notes partners do not see.

Notes captured during a partner 1:1 can be marked private to the BD leader or shared with the partner. Private notes feed the annual review view and the partner development dashboard. Shared notes become visible to the partner with the related action items queued, both living on the same partner timeline.

Submit-lock override

The BD leader read beats the partner read when it has to.

Partners submit their weekly category calls through the Friday workflow. The BD leader overrides the partner call per pursuit where the BD read differs, and the override carries a one-line reason the partner sees on Monday. The practice number that rolls up is the BD-adjusted number, with the partner submission preserved as an audit trail.

Risk-flag inbox

The pursuits Strkr AI flagged, in one list.

Every Strkr AI pursuit risk flag across the firm lands in a BD-leader-only risk inbox. The BD leader triages each flag in two clicks: dismiss (false positive, carries a reason), schedule coaching (creates a task tied to the pursuit), or escalate (routes to the practice lead with the flag history attached). The inbox clears to zero on a disciplined week.

Scope-shift timeline

The full shape of every pursuit on one record.

Each pursuit timeline shows every scope version with the delta from the prior proposal and a one-line reason. The BD leader walking into a difficult pursuit review scrolls the timeline in two minutes and arrives knowing exactly how the pursuit got where it is, which keeps the review grounded in events, not opinions.

Margin visibility

Every pursuit margin visible to the BD leader.

Partners see the margin estimate for their own pursuits, the practice lead sees margin across the practice, and the BD leader sees margin across the firm. The BD leader runs a margin review to spot pursuits priced too thin for the hours scoped, approves the margin before proposal, and defends firm pricing discipline with grounded numbers.

Partner benchmarks

Partner against practice, practice against firm.

Every partner metric (BD hours, pursuits opened, win rate, deal size, cycle time, referral revenue) renders against the practice average and the firm average on the same tile. The BD leader spots the partner a quarter outside the practice on cycle time and runs a specific coaching session instead of a generic conversation grounded in no numbers.

Head-to-head

Strkr vs Salesforce plus LinkedIn plus scoping spreadsheets.

Most 15 to 150 person advisory firms run Salesforce for records (often an inherited instance from a prior CIO), LinkedIn Sales Navigator for relationship surfacing, a Google Sheet for the practice forecast rollup, a scoping spreadsheet on the scoping lead desktop for margin, a shared drive folder for proposals, and email threads for cross-practice coordination. The stack is five surfaces, five logins, and five places the firm number drifts. Strkr collapses that into one workspace with one bill, with the BD leader tier shipped by default on every paid plan.

What matters Strkr Salesforce + LinkedIn + spreadsheets
Number of surfaces the BD leader opens for a weekly review 1 (Strkr) 5 (Salesforce, LinkedIn, Sheet, scoping, email)
Practice-area forecast rollup Native rollup across strategy, financial, operations, transaction Google Sheet with four tabs reconciled Friday night
Partner pipeline view Native partner-grouped rollup with utilization context Salesforce pipeline report filtered by owner
Scope-version history Native scope-version timeline on the pursuit Three Google Docs the scoping lead keeps on desktop
Relationship-weighted hygiene score Native score built for advisory motion Stage percentage math built for product sales
Pursuit risk flags Native Strkr AI flags with specific reasons BD leader eyeballs the pipeline Monday morning
Engagement margin on the pursuit Margin block beside the booking number Scoping spreadsheet on the scoping lead desktop
Cross-practice referral attribution Native referral chain on the account record Quarterly reconciliation call across practices
Retainer renewal pursuit Auto-opens 60 days before contract end Calendar reminder in the practice lead inbox
Monthly cost per partner (BD stack) One per-seat line, see pricing page Four to five per-seat lines stacked

See the CRM built for the BD leader at an advisory firm.

Start a trial with the full BD leader stack enabled: practice-area forecast rollup, partner pipeline view, scope-version history, relationship-weighted hygiene score, Strkr AI pursuit risk, engagement margin on the pursuit, cross-practice referral attribution, retainer renewal flow. One bill, one workspace, one source of truth for the firm. Migrate from the Salesforce plus LinkedIn plus Sheet stack in an afternoon and keep every account, pursuit, forecast submission, and open scoping block intact. The pricing page lays out the per-seat line in full.

See pricing Explore sales forecast
Common questions

Advisory firms BD Leaders buyer FAQ.

Can Strkr handle a forecast that rolls up four advisory practices on different cycles?

Yes, and it is the primary reason advisory BD leaders adopt the product. Strkr runs native practice-area forecasts that treat each motion with its own category math: strategy uses commit, best case, and pipeline on a six-to-twelve week cycle; financial moves on a regulated cycle with external deadline anchors; operations lands on four-to-six month cycles with scoping checkpoints; transaction advisory carries the deal calendar as the driving anchor. The four streams combine into one firm number without a Google Sheet, and the BD leader sees per-practice contribution against target at a glance.

How does Strkr handle a pursuit that reshapes value three times before signature?

Each pursuit carries a scope-version history on the record itself. The current proposal, prior versions, and a one-line reason for each shift pull onto one timeline. When a scoping lead posts a new proposal version, Strkr Flows log the version, calculate the delta against the prior proposal, and notify the BD leader with a one-line summary. The forecast moves with the shape, the margin block updates with the version, and the BD leader walks into the next partner review knowing exactly which pursuits moved and why. The scope-version history also feeds the pursuit timeline so the full shape of every deal is auditable at any stage.

How does the relationship-weighted hygiene score actually work?

Every open pursuit carries a hygiene score built from six advisory-motion inputs: meeting cadence with the economic buyer, stakeholder count across the account, partner engagement in the last two weeks, referral chain density, next-step date present and in the future, and scoping completeness. Each input carries a tunable weight so a strategy pursuit with a six-week cycle and an operations pursuit with a four-month cycle both run the same column with motion-appropriate math. Sort the partner pipeline by hygiene and the five pursuits that need a partner nudge this week surface above the fold. The BD leader coaches on specifics instead of a vague prompt across the firm.

Can we track engagement margin on the pursuit record alongside the gross fee?

Yes. Each pursuit carries a scoping block with hours per role per week per partner, a blended bill rate, a cost rate, and a target margin. The number lands on the pursuit record, surfaces in every pipeline report, and lets the BD leader sort pursuits by margin band. The scoping lead edits the block inline, and the BD leader approves the margin before the deal moves to proposal. Firms running tiered pricing can configure target margin bands per practice and per segment so the sort flags pursuits priced too thin before the proposal lands.

How does Strkr handle cross-practice referrals between strategy, financial, operations, and transaction advisory?

Strkr ships a native cross-practice referral primitive on the account record. When a second engagement opens on an account that already carries one, the flow tags it as a cross-practice referral, credits the originating partner, and surfaces it on the referral dashboard. The firm captures referral revenue as a first-class number without a quarterly reconciliation call, originating partners see their referred-revenue line next to their direct-closed line, and the BD leader reports cross-practice contribution at QBR with grounded numbers. For firms running a formal referral comp plan, the attribution math exports to the comp spreadsheet without a manual pull.

What does Strkr cost for a 40-person advisory firm?

Starter is $29 per seat per month, Pro is $59, and Scale is $119. Most 40-person advisory firms land on Pro for the pursuit-centric features and the forecast primitives. For 40 seats that is $2,360 per month on Pro. The Strkr AI module is an opt-in $49 per month that includes 5,000 Strkr AI calls, which covers risk-flag digests, scope-shift summaries, and email drafting for a firm this size with headroom. There is no premium professional-services module gate, and the BD leader tier ships on every paid plan. The 14-day trial includes every surface above so the BD leader can run a live Friday forecast through Strkr before the first invoice lands.

Also considering

Related combinations.

For Consulting Firm Sales Managers For Consulting Managing Partners For Consulting Account Executives For Professional Services Sales Managers For Accounting Firm Sales Managers For Agency Business Development

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing