Financial Services
›
Capital Markets & Investment Management
›
Private Equity
Platform Investments
High-stakes financial decisions requiring trust, structured diligence, and coordinated stakeholders.
Example organizations in this space:
KKR
Blackstone
Thoma Bravo
Vista Equity
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Pre-Sales
Qualify and align executive priorities and constraints before investing in a full discovery.
-
Initial Qualification
Confirm intent, timeline, decision-makers, and high-level fit before investing in a full discovery conversation.
Qualification Questions
Quick context: company fit and sector
- Roughly what was your last 12 months' revenue?
- Which industry best describes the business today?
- Does the business process or store regulated data or contracts we should know about (for example PHI, sensitive financial data, or government/public-sector contracts)?
Founder priorities and deal economics
- How do you feel about retaining meaningful rollover equity as part of a transaction?
- What role would you expect to play after closing?
- What are the top one or two non-negotiables for you in a partner relationship (for example culture preservation, employee outcomes, brand integrity)?
Operational and integration fit
- How open are you to centralizing back-office functions such as finance, HR, and IT as part of scaling the business?
- How would you describe the current management bench for supporting rapid growth and bolt-on acquisitions?
Decision makers, budget, and timing
- Who will be involved in deciding whether to pursue a platform partnership (select all that apply)?
- What timing are you considering for a transaction or partnership conversation?
- Do you have a minimum price expectation or other financial constraint that would be a deal stopper?
-
Executive Discovery
Map stakeholders, current performance, strategic priorities, cultural concerns, and measurable success criteria across the ownership team.
Discovery Questions
A Brief Snapshot of Today
- Tell me briefly why you are considering a partnership now
- How many locations or service sites does your business operate today
- Who currently holds legal ownership and what approximate equity split exists
- When did your revenue trend change materially most recently and what drove that change
- Give your trailing twelve month revenue and adjusted EBITDA, and note whether each is trending up, flat, or down
- Which customer segments or payer types account for the largest share of revenue today
- Describe a recent decision that exposed limitations in your ability to scale operations
Where Growth Is Stuck
- If you could remove one structural limit that prevents faster growth, what would it be
- Identify the top three bottlenecks that regularly force you to turn down new business
- How often do talent or capacity gaps cause you to lose revenue opportunities
- Walk me through the last time you had to decline a contract because you could not support it, including the estimated lost revenue
- Estimate the share of proposals that require a custom operational setup versus repeatable delivery
- What single financial or operational metric, if unchanged over 12 months, would make you decline a partnership
Who Holds the Keys
- Which internal person or external advisor would object strongly enough to veto a sale, and why
- List the decision-makers required for final approval and each person's primary concern about a transaction
- Name who will serve as the day to day post-signing contact and their current responsibilities
- Share how involved your spouse or financial advisor is in evaluating deal economics and governance
- If a single stakeholder refuses a rollover equity plan, what fallback path would you pursue
What Success Will Look Like
- Pinpoint the one measurable outcome that would make you call this transaction a success in five years
- Rank these outcomes by importance, one being most critical: retained headcount, revenue growth multiple, founder role duration, culture preservation, rollover value
- Provide target ranges for revenue growth, EBITDA margin, and headcount retention at 24 months that would satisfy you
- Describe how you and your advisors would measure cultural preservation objectively
- Would a shortfall of 20 percent in post-close EBITDA be a deal breaker for you
Culture, People, and the Founder Role
- What elements of your company culture are nonnegotiable under new ownership
- Explain the benefits, equity arrangements, or leadership practices you believe must remain to keep your team intact
- Who on your leadership team do you expect to stay and who might be open to a change to scale
- Estimate retention risk among your top 20 employees in the first 12 months post-close
- Would the departure of key frontline managers within six months prevent you from meeting your growth targets
What's Most Likely to Break
- Where in your delivery or operations does a failure convert quickest into lost customers
- List the top three operational risks that have produced repeated problems in the last 18 months
- Summarize any regulatory, licensing, or payer constraints that could delay integration or require carve outs
- Identify any vendor or third party dependency with contract terms that would impede transfer or scaling
- Name the single contractual clause, license gap, or site specific issue that would force you to pause or cancel a sale
The Competitive Landscape
- Tell me who else you are actively considering to achieve the same goals and why they are attractive
- Select which options you have evaluated or are evaluating: incumbent partner, internal build, strategic buyer, private equity platform, family office, other
- Explain what would have to be true about your current approach for you to stay with it rather than change
- Have any internal teams proposed solving this without an outside partner, and who proposed it
- Pinpoint the single advantage an incumbent would need to show today to keep you from switching partners
Operational Readiness and Constraints
- Confirm whether your core finance, payroll, and scheduling systems allow an external partner to access data and run parallel reporting within 60 days
- Provide the primary systems that host your customer, scheduling, payroll, and financial data, and name who holds admin access for each
- Do APIs or automated export processes exist for those systems, or will manual extraction be required
- Project how many dedicated internal hours per week your team can commit to integration work during the 90 day pre close window
- Does the absence of a single owner for data and approvals mean you will pause a close until one is appointed
- Select the regulatory or licensing approvals required before transfer: company license, local permits, payer contracts, background checks, none, other
Commercial Terms That Change Everything
- Flag the headline term that would make you walk away from an otherwise acceptable partner: valuation, rollover equity, founder role, governance, post close control
- Choose your preferred acquisition structure: full cash sale, majority buyout with rollover, minority recap, or earn out heavy
- State the minimum rollover equity percentage you would consider and why
- Specify who must sign off on any founder employment agreement and how long you would commit to an active role
- Could a buyer requirement of two years of active service, when you prefer one year, stop the deal
Integration Expectations and Services
- Assuming a partnership, what central services do you refuse to hand over to a platform and why
- Choose which shared services you expect to transfer to the platform: finance, HR, IT, marketing, operations support, sourcing
- Share the three integration outcomes you would insist be contractually guaranteed in the first 12 months
- When do you expect IT and HR access to be granted after signing to enable parallel workstreams
- Does the platform refusing to fund integration headcount for six months change your willingness to proceed
Timing and Next Moves
- Project your ideal close date and explain why that timeline matters
- State the earliest practical date your advisors could deliver final financials and legal cleanups
- Outline the internal milestones that must be completed before you sign, for example board approval, vendor consents, or customer notifications
- Choose whether you would accelerate to close in 30 days for a higher price, or wait 90 days for better terms and transition support
- Rate your team's readiness to engage in weekly integration planning now
-
-
Strategic Partnership Experience
Walk through how a platform-building partnership delivers the founder's priorities — brand and culture preservation, employee outcomes, rollover equity, and growth execution — using the buyer's operating playbook applied to the seller's context.
Solution Experience
- Strategic Partnership Experience Workshop
- Confirm the current state and its cost
- You confirm the articulated current state and agree on its quantified cost to your business.
- Provide a tailored integration outline showing shared services scope, expected timeline, and named integration leads based on today's scenarios.
- Share current org chart, most recent P&L, revenue by location, and any employee engagement or retention data needed to validate retention assumptions.
- Map your founder priorities to measurable success criteria
- You validate that the applied operating playbook materially removes the constraints you described while preserving brand and improving employee outcomes.
- Apply the operating playbook to your context
- You and the seller agree on the remaining evidence and decision milestones required to advance toward mutual commit.
- Agree on a shortlist of 2–3 operational KPIs and the timeline to measure them during diligence and in the first 12 months post-close.
- Demonstrate transaction and rollover mechanics
- Validate the future state
- Agree remaining evidence and next milestones
- Strategic Partnership Experience Workshop
- Strategic Partnership Experience Deck
- Strategic Partnership Solution Brief
- meeting
- slides
- document
-
Transaction & Integration Scope
Define acquisition structure, rollover equity mechanics, integration services, central shared services scope, and measurable post-close deliverables.
Scope Configuration
- Centralize Finance Shared Services
- Migrate General Ledger to Central ERP
- Consolidate Payroll and Benefits Administration
- Implement Standardized Month‑End Close Process
- Deploy Centralized HRIS and Employee Records
- Recruit and Onboard C‑Suite and Functional Leaders
- Migrate CRM and Standardize Sales Pipeline
- Professionalize Marketing and Digital Brand Assets
- Deploy Unified IT Infrastructure and Security Controls
- Integrate Bolt‑On Acquisition into Platform Operations
- Execute Add‑On Acquisition Sourcing and Closing
- Establish Shared Procurement and Vendor Management
Scope Questions
Centralize Finance Shared Services
- Which finance processes should move to the central shared services (select all that apply): accounts payable, accounts receivable, billing/invoicing, cash application, financial planning and analysis, treasury, fixed assets, other
- How many monthly vendor payments does your accounts payable team process?
- What is the size of your accounts receivable ledger (total AR balance and number of open invoices)?
- Who is the current owner of month-end close in your finance organization and what access will they continue to provide?
- Are there state registrations, payer enrollments, or industry-specific reimbursement rules we must preserve when centralizing finance?
- What acceptance criteria will confirm the central finance service is operational (for example centralized AP processing for a percentage of vendors and consolidated close within a target number of business days)?
Migrate General Ledger to Central ERP
- Which chart of accounts dimensions does your current general ledger use (for example department, location, service line)?
- How many years of historic general ledger transactions must be migrated to the central ERP?
- What is the size of your master chart of accounts (number of unique account codes)?
- Who will provide trial balance and subledger exports for accounts payable, accounts receivable, payroll, and fixed assets during the migration?
- What defines done for the GL migration (for example reconciliation variance threshold between legacy ledgers and central ERP, percentage of open items cleared)?
- Are there custom tax rules, contract accounting schedules, or revenue recognition workflows that must be preserved in the ERP configuration?
Consolidate Payroll and Benefits Administration
- List the payroll provider file types and formats your current payroll run generates (for example ACH files, timecard exports, benefits deduction CSVs).
- Provide your current employee headcount for payroll (active employees).
- List any state payroll registrations, multi-state withholding rules, or collective bargaining agreements that affect payroll processing.
- Identify the owner responsible for benefits reconciliation and employer contributions post-consolidation.
- When do you typically process recurring payroll changes (for example new hires or terminations) relative to pay date: same day, 2-3 business days prior, or more than 3 business days prior?
- What evidence will validate payroll and benefits consolidation (for example payroll register totals match legacy runs within a defined variance for the first two payroll cycles)?
Implement Standardized Month‑End Close Process
- List the close checklist items you currently use (for example bank reconciliations, accruals, intercompany eliminations).
- State the target number of business days after period end for delivery of a consolidated trial balance.
- Identify the current owner of intercompany reconciliations and indicate whether centralization is required.
- Specify any tax provision or revenue recognition schedules tied to customer contracts that must be preserved in the standardized close.
- Do you require a reconciliation dashboard with drill-down to general ledger detail during the close process?
- Select the automation tools or templates you prefer for enforcing the standardized close (for example spreadsheet templates, ERP close module, dedicated close checklist tool).
Deploy Centralized HRIS and Employee Records
- Provide a list of employee record types that must be migrated to the central HRIS (for example employee census, employment contracts, benefits elections, certifications/licenses).
- State counts for active, terminated, and contingent workers to include in the HRIS migration.
- Identify any regulated workforce credentials (for example medical licenses, security clearances, professional certifications) that require verification and expiry tracking.
- Name the authorized signer or contact who can approve employee data sharing and provide signed data processing agreements.
- When do you run benefits eligibility snapshots for mid-month hires or leaves (for example at payroll cut, end of month)?
- Do you require employee self-service access for pay stubs, PTO requests, and certification uploads in the centralized HRIS?
Recruit and Onboard C‑Suite and Functional Leaders
- Outline executive roles required in the new platform within 90 days of close (for example CEO, CFO, Head of Operations, Head of Sales).
- Estimate acceptable vacancy-to-hire weeks for each executive role (for example 8-12 weeks).
- Name the approver who will finalize candidate offers and equity rollover decisions.
- Select whether interim leadership or fractional executives are required during recruitment ramp.
- Describe interview steps and assessment artifacts required for C-suite candidates (for example cultural interview, technical panel, reference checks).
- Specify timing expectations for onboarding milestones for incoming executives (first 30/60/90 day goals).
Migrate CRM and Standardize Sales Pipeline
- Specify the CRM objects that must be migrated (for example accounts, contacts, opportunities, service contracts).
- Estimate counts and total value for active opportunities and open quotes to be migrated.
- Confirm whether historical activity (emails, meetings, call logs) must be migrated and linked to contact and opportunity records.
- Assign the role that will own sales stage definitions and conversion criteria after standardization.
- Describe commission plans or quota rules that must be preserved in the standardized pipeline.
- Indicate desired CRM cutover timing relative to close (for example prior to payroll, on close date, 30 days after close).
Professionalize Marketing and Digital Brand Assets
- Detail brand assets that must be consolidated (for example logo master files, style guide, customer-facing templates, domain names).
- Approximate the number of customer-facing templates that need rebranding (for example invoices, proposals, service agreements).
- Confirm whether a published brand voice or messaging framework exists to be adopted across markets.
- Designate the contact role responsible for domain and email infrastructure and confirm DNS access availability for migration.
- Outline content pieces that must be live at launch (for example primary website pages, pricing page, service descriptions).
- Document any industry-specific compliance requirements for marketing claims or privacy disclosures we must follow (for example HIPAA patient notices, financial services disclaimers).
Deploy Unified IT Infrastructure and Security Controls
- Detail locations, data centers, or cloud accounts that must be onboarded into the unified IT estate.
- Approximate counts for end-user devices and servers that will require imaging and management.
- Confirm if multi-factor authentication and single sign-on are required for employees accessing customer data.
- Designate the administrator with access to your primary network firewall and who can approve new rules during integration.
- Indicate acceptable system cutover windows for shared services relative to close (for example payroll, finance reporting, CRM).
- Declare minimum security compliance standards the unified infrastructure must meet (for example HIPAA, SOC 2, PCI DSS).
Integrate Bolt‑On Acquisition into Platform Operations
- Detail operational areas that must be aligned for the bolt-on (for example service delivery, billing, scheduling, fleet management).
- Report counts of locations or service centers the bolt-on adds and list their core operating hours.
- Document any legacy local service level agreements or vendor contracts that must be honored after integration.
- Assign the role responsible for customer-facing communications during transition of service delivery to the platform.
- Enumerate cutover activities required to move scheduling and dispatch to platform tools (for example migrating work orders, technician profiles, customer equipment lists).
- Declare the required integration completion date to meet customer continuity service level agreements.
-
Mutual Commit
Finalize commercial and legal terms, confirm governance, founder role commitments, and dependencies required to close and transition.
Agreement Modules
- Acquisition Agreement
- Equity Rollover Agreement
- Founder Role & Retention Agreement
- Governance & Shareholders Agreement
- Escrow & Indemnity Agreement
- Transition Services Agreement (TSA)
- Closing Conditions & Deliverables Checklist
- Disclosure Schedules & Seller Disclosures
- Non-Compete, Non-Solicit & Confidentiality Agreement
- Employee Transition & Benefits Addendum
- Tax Allocation & Treatment Letter
- Regulatory & Compliance Addendum (conditional)
- Integration Dependencies & Pre-Close Readiness Statement
- Closing Protocol & Authorized Signatories
-
Integration
Lock operational readiness, integration responsibilities, and the launch plan before executing post-close integration.
-
Pre-Close Integration Readiness
Capture concrete readiness facts the integration team needs before closing — named owners, approvals, data access, and critical dates.
Pre-Deployment Questions
Environment and site access
- Which production systems must the integration team be able to access before close? (select all that apply — we use this to scope connectors and auth)
- For each system selected above, who is the named approver for access requests (name, role, email) — this is the person we will request credentials/authorizations from
- Who will perform access provisioning and initial connectivity testing?
Data and configuration
- Which datasets require pre‑close transfer, provisioning, or test data copies for go‑live tests? (select all that apply — drives migration scope)
- Has a field‑mapping owner been assigned for the critical datasets above? Select the current state (we need an owner to schedule mapping sessions).
- Are backups, retention, and restore procedures approved for the migration cutover window (this informs the rollback plan)? If 'Pending', indicate the target approval date.
People and ownership
- Provide the named primary and backup owners for these integration workstreams (format: workstream — primary name, role, email; backup name, role, email): IT/Systems, Finance (AR/AP), HR/Payroll, Operations/site leads.
- Have the seller's executive sponsors confirmed pre‑close governance and approval authority for integration actions?
- Are any employee notifications, retention agreements, or change‑of‑control approvals required pre‑close (e.g., retention offers, union notices)? If yes, list required notices, timing, and the owner responsible.
Timing and constraints
- What is the target legal close date or best estimate (mm/dd/yyyy or month) — we will anchor cutover milestones to this date.
- Are there blackout windows or business‑critical dates within ±60 days of close that block integration activities (e.g., fiscal close, peak season, audits)?
- Are contractual or data‑access approvals required before connectivity (examples: MSSA, DPA, SSO enablement)? Select current status.
-
Integration Playbook
Lock configuration and handover details — shared services scope, reporting cadence, IT/HR access, and bolt-on M&A cadence the teams will execute.
Configuration Details
Shared Services Scope & Ownership
- Select primary shared services the platform will own post-close (select all that apply). These values drive service-level configuration and owner assignment.
- Platform integration lead (full name and role) — default owner if no service-specific owner is provided (format: 'Full Name, Role'). This value is consumed by the handover owner mapping.
- Primary seller contact for shared-services handover (full name and role) — the person who approves final configurations (format: 'Full Name, Role').
Reporting & Meeting Cadence
- Operational reporting cadence for shared services (Default: Weekly) — cadence the integration team will schedule for operational dashboards and reconciliations.
- Executive steering meeting cadence (Default: Monthly) — cadence platform and seller executives will use for governance reviews.
- Primary reporting delivery format the platform will consume (Default: Shared dashboard link) — used to configure delivery method during handover.
Identity, Access & Data Connections
- Your identity provider (IdP) type for granting user access (Default: SAML-based IdP) — used by the integration team to plan SSO setup.
- Seller HRIS system name (enter exact system name as used by your HR team; leave blank if none) — consumed to map people data feeds.
- Integration account identifier for IT/HR system (non-secret) — enter the username or service-account name. The credential itself will be exchanged via your secrets manager at handover.
Bolt-on M&A Cadence
- Target bolt-on acquisition cadence (number of add-ons per 12 months). Default: 3 — used to size the M&A enablement and integration backlog.
-
Post-Close Integration & Launch
Execute the integration plan and bolt-on acquisition cadence with sequenced milestones, named owners, and escalation paths to realize scale.
-
-
Value Realization & Retention
Track financial and people outcomes, confirm culture and retention metrics, and maintain a shared channel for issues, enhancements, and bolt-on pipeline updates.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Acceptance Gate — 90-Day Value Acceptance
- Quarterly Value Realization and Retention Review
Issues & Enhancements
- Update the shared issue channel with the new priorities and confirm the escalation path for any item not completed on the next quarterly review.
- Document root-cause analysis for each underperforming metric and list the remediation tasks with target completion dates.
- Schedule a checkpoint two weeks before the acceptance gate to confirm remediation progress and evidence availability.
- Restate acceptance criteria and numeric targets
- Produce a documented acceptance decision with pass/fail recorded for each criterion and capture the required signatory for managed engagements.
- Where acceptance criteria failed, finalize a remediation schedule with completion dates that will be monitored in ongoing reviews.
- Confirm the incumbent systems wind-down is scheduled and will not remain an active fallback after the remediation window.
- Publish the acceptance record that lists pass/fail status for each criterion and includes the captured signatory or buyer owner decision documentation.
- Create a remediation tracker for failed criteria with tasks, milestones, and target completion dates for monitoring in quarterly reviews.
- Finalize and publish the legacy system decommission plan, including contract termination or read-only retention terms and data archival confirmation.
- Financial outcomes review
- Validate whether the business remains on the expected value trajectory against EBITDA margin, employee retention, and bolt-on pipeline metrics recorded in Transaction & Integration Scope.
- Ensure persistent blockers and enhancement requests have owners, deadlines, and a clear escalation path if not resolved within the agreed window.
- Maintain a shared, documented channel for ongoing issues and bolt-on pipeline updates to prevent information loss between quarterly reviews.
- Publish the quarterly value dashboard with validated metrics for EBITDA margin change, employee retention rate, and bolt-on pipeline count, including data sources.
- List the top three persistent blockers and assign remediation milestones with target dates for the next quarter.
- Re-confirm agreed success criteria and owners
- Confirm the deployment status for each integration workstream and that no critical go-live defects remain unowned.
- Agree a prioritized remediation plan with clear resolution dates for all high-severity blockers.
- Ensure the data sources and dashboards required for the first measurement meeting are available and validated.
- Publish a remediation tracker that lists each blocker, the remediation action, and target resolution date.
- Confirm and document the data sources and ownership for the metrics to be reported at the first measurement review.
- Circulate a short tally of early adoption signals and any failed end-to-end runs for async review within 48 hours.
- Present first measurement data against targets
- Determine whether the deal is on track to meet the acceptance criteria recorded in Transaction & Integration Scope or identify the required remediation to get on track.
- Agree a concrete list of corrective actions with clear completion dates that will be re-reviewed at the acceptance gate.
- Ensure evidence sources for each reported metric are validated and available for the 90-day acceptance decision.
- Produce an updated metric dashboard that includes organic revenue growth rate, EBITDA margin delta vs baseline, and founder and key-leader retention rate, with data provenance notes.
- Present outcome data against each criterion
- People outcomes and culture metrics
- Deployment and data migration validation
- Root-cause diagnosis for any gaps
- Document pass/fail per criterion and capture acceptance decision
- Early adoption signals
- Bolt-on pipeline and M&A cadence update
- Culture and retention signals
- Persistent issues and enhancement backlog
- Agree remediation plan for any failed items
- Open issues and blockers
- Open integration blockers impacting metrics
- Agree corrective actions and timeline to acceptance
- Legacy system decommission status and final wind-down
- Agree next quarter monitoring and escalation paths
- Immediate remediation plan