With Solartis, new lines of business and programs typically launch in weeks, because Solartis Base Products already include the full policy lifecycle and bureau content. Timing depends on how much carrier-specific configuration, integration, and data migration the product needs. Work is delivered in 2 to 4 week Agile sprints, each ending with a demo.
A Solartis implementation follows the same proven path every time: project kickoff, requirements gathering, Agile delivery in sprints, product configuration in Solartis Builder, governance through daily scrums and steering committee reviews, and testing built into every sprint. Every change is promoted through DEV, TEST, UAT, and LIVE before it reaches production.
Solartis business analysts work side by side with the carrier's or MGA's team to document everything each line of business and program needs. That covers bureau content, carrier-specific rates and coverages, forms, underwriting and referral rules, subjectivities, and integrations. AI turns state filings and Excel rating requirement documents into Builder-ready first drafts that the team reviews, and every requirement is signed off before configuration begins.
ISO content is extensive, so Solartis uses a structured requirements methodology to identify exactly what each program needs. During requirements gathering, Solartis business analysts work with the customer's team to select the ISO versions, sublines, classes of business, and coverages for each program and state. The product then carries only the ISO content it uses, within the customer's ISO license.
Solartis tests every product at both the microservice and full-product level, in every sprint. Testing uses Solartis Builder's built-in tools, automated UI regression, load and performance testing, and API validation, and AI helps generate test scenarios and check coverage. Each change moves through DEV, TEST, UAT, and LIVE before reaching production.
Solartis converts legacy data into complete submissions, quotes, and policies with Solartis Explorer, so migrated business can be endorsed, renewed, and serviced like any other policy. Solartis has refined its migration approach over more than 10 years, works with each customer on data quality and mapping, and scopes the effort to what needs to move.
Solartis provides two kinds of training. Train-the-trainer end-user training, offered as a professional service, prepares the customer's team to lead the rollout. Solartis Builder training is hands-on, including shadowing the Solartis configuration team, so the customer's business and technical users can manage products on their own.
Solartis provides documentation generated through the configuration process, so it always reflects the current setup. It includes process flows for the full policy lifecycle, product-specific data models that can be exported to Excel, and configuration documentation for rating algorithms, business rules, forms, and screens.
With Solartis, customers choose. They can maintain their products themselves in the no-code Solartis Builder, or have Solartis maintain them as they change over time, as an optional professional service. Customers can also change that choice later as their team takes on more.
Solartis customers get a dedicated account manager, ongoing software maintenance through patch, minor, and major releases, and post-production support for usage guidance, troubleshooting, and issue resolution. Solartis Monitoring Specialists, Solartis Monitor, and Jarvis AI also watch the platform 24×7.
Solartis consumes each ISO ERC release electronically and validates it before it's available for adoption. Carrier deviations stay in their own layer, so they carry forward with each new ISO version without rebuilding the product.
Yes. Customers can start with the lines, states, and programs they need first, then add more later without rebuilding what's already live, because each new product builds on the same base configuration. For package or multi-line products, Solartis can configure the lines at the same time.
