Team
Two partners. Every engagement.
Fortis is deliberately small. Every engagement is run by a partner from scoping through handoff. There is no staffing model underneath us, which is the point.
Ken Welter
Managing Partner · Finance & Operations
Ken brings 30 years in financial due diligence and operations, including building and running sales, operations, and analytics teams. His background covers accounting, finance, profitability drivers, and operational execution, formerly at EY.
His M&A work is where the Fortis approach originated. Quality of earnings reports are built to answer diligence questions, and they answer them well. Ken's focus is the next question — translating deal data into what actually changes after close.
Bo Osypenko
Partner · Data & Analytics
Bo builds the infrastructure. His work covers data structure and SQL, warehouse architecture across Snowflake, Databricks, and MS Fabric, semantic model design, Power BI, scenario modeling, and revenue analytics.
His role on every engagement is translating finance requirements into systems that hold up in production — models the client's own analysts can extend after we are done.
How we work together
Neither of us hands off to the other.
Ken scopes what the finance question actually is. Bo builds the model that answers it. There is no one to hand off to, so nothing gets lost in the translation between the accounting and the engineering.
When an engagement needs more capacity, we bring in contractors we have worked with before — and a partner stays accountable for the work.
Start with a diagnostic, not a commitment.
Phase 1 is scoped to answer one question: is the opportunity real, and how big is it? If the numbers do not support a Phase 2, we will say so.