By Kurt Diederich, President & CEO

For most P&C carriers, the phrase “partner-first” has lost its meaning. Nearly every core system vendor claims it, but few can show what it looks like in practice.

For executive teams making a core system decision, slogans are not enough. The system you choose has a lasting impact on your financial performance and shapes your operating model, expense ratio, and growth options for years to come. However, the risk is not just the technology but also choosing a partner who may not be a good fit for your goals.

“Partner-first” should be reflected in a vendor’s actions throughout every phase: from assessing fit and implementing, to enabling self-sufficiency and remaining engaged after go-live. As our Chief Customer Success Officer, Emeka Iheme says, “When you find a partner, it’s someone who you share the same core values with, someone you share the same vision with, and who is ultimately headed in the same direction.” Carriers should look for clear evidence before making such a critical decision.

This article will show you what a real partner-first approach looks like throughout the core system journey. You’ll get practical tips for evaluating vendors and distinguishing between marketing and a true insurance technology partnership.

Before Implementation: Taking the Time to Make Sure There’s a Good Fit

How True Partners Approach Discovery

A partner-first vendor starts by understanding your business—not with a generic demo or canned presentation.

In early conversations, the focus should be on understanding:

• Current and planned lines of business
• Growth plans, target regions, and distribution strategies
• Regulatory and rating bureau dependencies (ISO, AAIS, URB, MSO)
• Internal constraints on budget, staffing, and change management

Discovery must confirm mutual fit by clarifying where the platform aligns—and where it does not—with your needs, especially if unique requirements create additional complexity.

Aligning on Scope, Outcomes, and Self-Sufficiency

Alignment upfront shapes the relationship. A partner-first vendor uses this phase to clarify scope, outcomes, and self-sufficiency.

• Scope of supported lines and products: A P&C core platform should support the carrier’s full portfolio—whether personal, commercial, or specialty, or a mix. Both the vendor and the carrier should align early on what’s truly in-scope at go-live (and what isn’t), including any line-specific nuances, regulatory requirements, and dependencies.
• Integration strategy: The vendor should offer a broad range of prebuilt integrations to help carriers avoid the added risk and time required to build one-off connections.
• Target level of autonomy after go-live: Some carriers want to manage products and states independently, and others prefer greater vendor involvement. Alignment on autonomy defines how training, configuration, and staffing should look.
• Delivery predictability: True partnership also means being transparent about what the platform does, what is being purchased, and the resources needed to implement and support it, and setting realistic timelines—whether it’s a single-stage or multi-stage rollout. This clarity is critical, especially when customers are making significant investments.

When the scope is clear, confusion does not cause overruns later and reduces downstream risk.

After deep discovery and alignment, a true partner is candid about fit, even if it means saying, “We may not be the right fit.” Honesty at this stage helps carriers avoid costly missteps and establishes trust and respect.

Core System Implementation: Collaboration and User Empowerment

Working Side by Side During Implementation

A partner-first implementation is truly collaborative. Carrier and vendor teams work side by side, openly sharing knowledge and building the future operating model together rather than handing things off behind the scenes.

A blended team usually includes:

• Tenured vendor staff with product knowledge and implementation experience
• Customer subject-matter experts—including business and technical staff—who understand underwriting, billing, claims, and regulatory requirements

From the start, knowledge transfer should be a core goal. Implementation should leave your teams with an understanding of how and why the system works and how to safely make changes.

Designing for Autonomy with Configuration Tools

Partner-first vendors empower carriers to be as self-sufficient as they want. Everyday changes can be managed through configuration tools like Finys’ Design Studio, while the vendor team can step in for configuration or custom development when carriers prefer more support.

Design Studio is our low-code configuration environment that enables business and IT users to design, configure, and manage products, states, and lines of business. Instead of opening a ticket for every rate, rule, or form change, your team can handle many changes directly.

Configuration tools enable carrier self-sufficiency. Examples of what configuration should handle include:

• Adding a new program to an existing state
• Adjusting underwriting rules or rating factors
• Modifying workflows or correspondence templates

When more changes can be handled with configuration, carriers update products faster and avoid vendor dependency for routine adjustments.

Transparency on Timeline, Cost, and Tradeoffs

During implementation, “partner-first” shows up in how vendors talk about scope, time, and budget. Carrier stakeholders should expect straightforward updates throughout the project: Where do we stand? What has changed? What are the implications?

You should expect:

• Clear project plans with milestones and responsibilities.
• Fixed or defined terms for the agreed scope
• No surprise change orders for capabilities that are already part of the platform

When new ideas or scope changes arise, partner-first vendors explain the trade-offs: what accelerating one workstream does to another, where additional cost is justified, and where it is not. Transparent tradeoffs protect both budget and trust.

Training That Builds Confidence

Training should never be a one-time event or an afterthought. To truly build confidence, training must be continuous, role-based, and embedded in real-life tasks and workflows. Successful adoption has two distinct sides: early orientation for the implementers configuring the system, and ongoing training for the end users who will operate it in production. These may be the same people or entirely different teams, so a thoughtful approach must serve both audiences and provide practical enablement at each stage.

A partner-first training approach goes beyond the basics to drive real autonomy:

• Role-based training for underwriters, billing teams, and claims handlers, each aligned to the specific policy, billing, and claims components they use.
• Hands-on configuration labs and practical exercises, so power users can confidently manage rates, rules, products, and workflows after go-live without ongoing vendor intervention.

When training is done well, it builds lasting confidence and measurable results. Confident users rely less on workarounds, take full advantage of the system, and adapt more quickly as needs evolve. Effective training is measurable: as it improves, support questions and tickets decline, new features are adopted, and users make the most of their investment.

Beyond Go-Live: Building an Insurance Partnership That Lasts

Tenured Staff and Relationship Continuity

Three, five, or ten years after go-live, a true partner-first relationship feels stable. A long-term relationship with a core vendor preserves institutional knowledge.

Carriers benefit when they work with people who know their history, products launched, states added, prior rate filings, integration decisions, and lessons learned. High turnover on the vendor side forces you to re-explain your business, increasing risk with each change. A tenured vendor team preserves continuity across releases and projects.

Ongoing Enhancements Driven by Customer Needs

Partner-first extends past go-live and informs the roadmap. A vendor’s roadmap should link R&D investment to carrier outcomes.

You should see your vendor:

• Investing meaningfully in research and development
• Sharing roadmap visibility and how customer input influences priorities
• Focusing enhancements on outcomes like reduced operating cost, faster time to market, and better support for profitable growth

R&D should focus on carrier outcomes, not just features. Features matter only if they help carriers run efficiently and scalably.

Support That Respects Your Time

In a steady state, support demonstrates “partner-first” daily. A strong model protects carrier operations and reputation.

When support is needed, a partner-first approach ensures customers always know how to get help and what to expect. Key elements include:

• Clear SLAs and predictable communication channels
• Access to people who understand both the technology and P&C operations
• Structured processes that distinguish between general inquiries, incident (bug) resolution, and product enhancement requests, making it easy for customers to get answers, report issues, and request new features.

Helping Carriers Take the Next Step

The real test of a partner-first relationship is how easily you can move to the next stage of your strategy. A mature partnership should make new initiatives easier, not harder.

Common next steps include:

• Adding new states or programs using existing configuration patterns, not starting from scratch
• Expanding distribution or digital self-service through agent and insured portals that are comprehensive and easy to use
• Leveraging business intelligence to make more data-informed decisions using your operational data

When the relationship works, the platform and vendor help carriers advance growth initiatives with less friction and risk.

How to Tell if an Insurance Software Vendor Is Truly “Partner-First”

To separate marketing hype from real partnership, carrier teams should ask direct questions in evaluation: How do you decide if you’re not the right fit? How do you enable customers to be self-sufficient? What’s the average tenure of your team? Can we talk to customers who’ve been with you for years? Good vendors provide clear examples and references; vague answers are a red flag.

Be alert for signs a vendor isn’t truly partner-first, such as:

• Vague promises about configuration or customer autonomy
• Heavy reliance on custom development instead of robust configuration tools
• Few or no long-term customers in your segment

Be alert for signs a vendor isn’t truly partner-first, such as:

• Vague promises about configuration flexibility or customer autonomy
• A heavy reliance on custom development instead of robust, configurable tools
• An inability to provide references that match your organizational profile, implementation timeline, and functional or technical needs
• A lack of references from challenging implementations that show how the vendor responds under pressure

Look for vendors who are willing to walk away from deals that are not a good fit, can demonstrate successful implementations, and maintain long-term, growing relationships with their customers. When customers stay and expand their relationship over time, it is one of the strongest signals of a lasting partnership. At the same time, a vendor may not always have a long-term customer who looks exactly like your organization. Rather than treating this as a disqualifier, focus on how clearly they can connect their existing experience, tools, and delivery approach to your specific scale, complexity, and goals.

Turning “Partner-First” Into Practice

“Partner-first” should not be a tagline. It should describe how a vendor behaves across the entire lifecycle—before selection, during implementation, and through years of growth and change. A partner-first approach is something you can observe and test, not just read about on a website.

Finys takes a partnership-first approach with every customer. We collaborate to confirm the Finys Suite is the right fit for their needs and that we’re the right team to support them. 

If you are evaluating core systems, it is reasonable to expect a future-ready core software for property and casualty insurers, and a relationship model that prioritizes honest fit, predictable delivery, and long-term autonomy. 

If you’re interested in what a true insurance partnership can look like, let’s talk about how we approach partnership at Finys—and how it can make a difference for your business.