B2B SaaS-adjacent consultanciesNew

What gets pre-loaded

• preferenceimportance 9/10

  SOW discipline — every engagement carries an explicit named-outcome statement + named-platform-version scope + change-order protocol

  Implementation consultancies live and die by the statement of work. The most common failure mode is starting work on 'a Salesforce implementation' without naming (a) the explicit business outcome the client is buying ('cut sales-cycle time from 60d to 30d', 'enable revenue-recognition automation for ASC 606 compliance'), (b) the named platform version scope ('Salesforce Sales Cloud Enterprise edition, Spring '26 release'), AND (c) a written change-order protocol that defines what triggers a new SOW vs an in-scope adjustment. Engagements without these three carry pricing risk, scope-creep risk, AND vendor-version-mismatch risk all simultaneously. Surface a watch item on any active engagement whose SOW doesn't have all three elements on file.

• preferenceimportance 8/10

  Vendor relationship hygiene — every active platform-vendor partnership carries a named partnership tier + named partner manager + last-touched date

  B2B SaaS-adjacent consultancies depend on platform-vendor partnerships for (a) referral leads, (b) implementation discount authority, (c) early access to product roadmap, AND (d) named partner-manager support during escalations. Consultancies that don't actively manage the partner-manager relationship lose all four advantages within 12-18 months as partner managers churn or rotate territories. The right practice rule is: every active platform partnership carries (a) the named partnership tier (Bronze/Silver/Gold/Platinum equivalent for the specific platform), (b) the named partner manager with direct contact, (c) the last-touched date, AND (d) the named next-touch commitment. Surface a watch item on any partnership that hasn't been touched in 60+ days.

• lessonimportance 9/10

  Platform-version red flag — any client implementation locked to a platform version more than two release cycles behind the vendor's current GA poses an immediate upgrade-debt risk

  B2B SaaS platforms ship 2-4 releases per year and routinely deprecate features 4-6 release cycles after the deprecation announcement. Consultancies who let client implementations lock to old versions (because the client doesn't want to pay for upgrades, or the consultancy isn't proactively flagging deprecations) expose the client to compliance risk, security risk, AND a forced-upgrade cost spike that the client perceives as the consultancy's fault even when it's the platform vendor's deprecation. The right practice rule is: every active client implementation carries a tracked platform-version tag, AND any implementation more than two release cycles behind the vendor's current GA triggers an upgrade-debt watch item. The watch item names the deprecated features in use, the vendor's deprecation deadline, and the proposed upgrade engagement scope. Surface a watch item the moment the version drift crosses two release cycles.

• lessonimportance 8/10

  Recurring-revenue red flag — implementation consultancies whose top-three clients account for more than 60% of annual revenue have no negotiating leverage in renewal conversations

  Implementation consultancies routinely accumulate client concentration because a successful implementation tends to extend into a long-tail managed-services engagement. Consultancies whose top-three clients account for more than 60% of annual revenue lose the ability to walk away from bad-faith renewal negotiations, lose the ability to push back on scope-creep without an SOW, AND lose the ability to maintain pricing discipline against the client's procurement team. The right practice rule is: track client concentration as a quarterly metric, AND surface a watch item when the top-three concentration crosses 50% (warning) or 60% (red flag). The watch item names the action (run a focused new-business motion to dilute the concentration) with a 90-day window before the next quarterly review.