An insurance product can be ready for customers long before its software is ready for the product. The price is agreed, the cover is written, the distribution partner is waiting. Somewhere, somebody still has to change a system. INSTANDA has built its business around that awkward interval - and around giving the people who understand the product more power to end it.
The company sells a no-code platform for insurers, managing general agents and brokers. They use it to design products, calculate prices, distribute cover and administer policies. Its proposition sounds almost impolite in enterprise technology: a trained business team should be able to change its own insurance offering without commissioning another development project.
That matters because an insurance product keeps moving after launch. Rates change. Questions change. A new broker needs access. A policyholder wants an amendment. The launch party is brief; the maintenance diary is forever. INSTANDA’s more interesting promise concerns who owns that diary.
The mortgage behind the software
Co-founders Tim Hardcastle and Derek Hill came to the problem through insurance technology. Hardcastle began as a chartered accountant, moved into technology leadership and worked at Hiscox. After leaving, consulting work gave him a chance to test whether the difficulties he had seen were widespread.
They were, in his telling. Insurers had ideas for specialized products and more personal service, but their systems made execution difficult. The company’s origins date to 2012; its first customer went live in 2015. Between those dates lay the less photogenic part of founding a software business.
“We had all of that including mortgaging our homes and selling assets to fund a monthly payroll run!”Tim Hardcastle, recalling the early years in 2022
The recollection describes a long wait for traction and pressure on personal finances. It also gives the origin story some useful weight. The founders were asking insurers to trust unfamiliar infrastructure while having to finance the time it took to earn that trust.

Hiscox gets a second set of keys
By November 2019, Hiscox had a concrete reason to expand its use of INSTANDA. Its first German car product had been built in 10 weeks; the second product, with additional channels, took six, according to the insurer’s European leadership. The expanded relationship covered direct and broker business across four countries.
The consequential detail was the team taking shape around the platform. Hiscox used employees and partners trained as configurators to build products and add books of business. INSTANDA described an internal product factory: a capability the insurer could keep using, rather than a single delivery handed over at the end of a project.
Those two build times are different projects, not a controlled experiment. Still, the account helps explain why Hiscox extended the relationship. The attraction included the ability to adjust pricing and improve the customer journey while trading. Software had become something the product team could operate.
Different product builds. A delivery example, not a universal benchmark.
The plumbing behind “no-code”
For a configurator, the raw materials include questions, rating calculations, documents, emails and rules. These determine what a customer is asked, how an application is assessed and what happens next. The product design layer connects to quoting, binding and policy administration, so the attractive screen at the front has somewhere useful to send its answers.
Distribution is part of that machinery. An insurer can serve customers directly, work through brokers or support partner-led journeys. Customer and broker self-service can sit alongside assisted service. INSTANDA spans property and casualty as well as life and health, making insurance expertise more relevant to its identity than any single line of cover.
The platform runs on Microsoft Azure and can act as a core policy administration system or work with an existing technology estate. That gives a buyer a choice of scope: use it for a new digital offering, or make it central to a broader operation. Connections to other systems remain part of the design.
- 01 / ConfigureQuestions, prices and rules
- 02 / DistributeCustomer, broker and partner journeys
- 03 / AdministerIssue, amend, service and renew
No-code describes the configuration model. INSTANDA still maintains the underlying code, and its documentation allows front-end customization through familiar web technologies. The useful buying question is specific: which changes can your trained staff make, test and release themselves?
A flood marketplace with fewer hurdles
Flow Flood offers a useful view from the agent’s chair. It built a digital marketplace where agents could compare quotes from up to six insurers, bind applications and service policies. INSTANDA’s case study says the marketplace took five months to develop and reached 42 states in the year after its initial launch.
The reported timings are wonderfully unglamorous: quotes in under two minutes, binding in 90 seconds from quote, and agent onboarding reduced from three to 10 business days to less than an hour. Each removes waiting from a different point in the transaction.
This is the customer problem in miniature. A product can be competitively priced and still be troublesome to sell if an agent has to negotiate a maze of portals and administrative delays. Flow Flood’s example makes the case for improving the whole journey. These are customer results reported in a vendor case study; they should be read as a specific implementation.
The bill, and the people who run it
INSTANDA earns its money through enterprise software licensing. Its platform FAQ describes a monthly fee and tailored pricing, with deployment, Azure hosting, maintenance and ongoing support included in the license. A buyer therefore needs a scoped proposal, not a shopping-cart comparison.
Our reading of the operating model is that subscription price alone makes an incomplete business case. A useful evaluation also counts the people configuring products, testing changes and connecting systems. Speed has value when those people can use it repeatedly, after the implementation team moves on.
INSTANDA requires at least two client team members to train as superusers. Its March 2026 training roadmap added specialist learning around operational data, APIs, migration and interface design, following customer feedback and platform-usage analysis. That is a revealing response: giving clients more independence also means teaching them more.
The practical lesson for another business is straightforward. Pick a bounded product, name its owners and measure an ordinary change from request to release. Include an awkward exception in the trial. If every exception still needs an external specialist, the expected benefit of local control will be smaller. The software does not decide who inside the insurer has authority to act.

Inside INSTANDA, the published employment offer includes a monthly Dynamic Day off, a wellness allowance and a paid sabbatical after six years. An employee equity plan is open to everyone. These are tangible expressions of its stated emphasis on collaboration and inclusion, rather than evidence that every employee has the same experience.
AI arrives with an assigned task
The newer products show where INSTANDA wants to extend its reach. Launched in March 2026, MAX is designed for commercial policies containing tens of thousands of assets. It supports analysis at both portfolio and individual-item level, with AI assistance and human oversight.
That addresses a recognizable tension: a large schedule can be easier to process in aggregate, while individual assets still have different characteristics. MAX is designed to let underwriters update those items during the policy’s life. Its launch announcement describes intended capabilities, not a measured improvement in an insurer’s loss experience.
CLEAR, launched in June, tackles complex operational cases: the referrals, follow-ups and exceptions that spill into email and spreadsheets. It brings ownership, deadlines, tasks and completion records into a configurable workflow. It can connect to INSTANDA or other policy systems, widening its potential role beyond the company’s core platform.
Partnerships cover adjacent jobs. February’s ServiceNow offering connects policy administration with service and claims workflows. July’s Diesta partnership addresses premium collection, reconciliation and reporting. The expanding network acknowledges how much must happen after a customer says yes to a quote.
The queue is getting competitive
INSTANDA competes in a market where established suppliers are moving too. Guidewire’s PolicyCenter also promotes configurable product design, no-code tooling and AI assistance. Buyers should be suspicious of any comparison that grants one vendor modernity and assigns every alternative to a museum.
INSTANDA’s case rests on the combination: insurance-specific configuration, distribution, policy servicing and the option to work beside existing systems. Its published roster spans large insurers and specialist businesses. Fit depends on the actual product, operating model and integrations a buyer needs, not the age of a vendor’s logo.
Capital has given it room to pursue that case. A $19.5 million Series A in 2020 was followed by $45 million led by Toscafund in 2022. In October 2025, CommerzVentures led another $20 million round; INSTANDA said it had reached profitability and exceeded 40 percent compound annual growth since its previous raise.
Palatine Growth Credit followed with a facility announced in August 2026, supporting expansion, hiring and investment in AI and data science. The financing backs a larger ambition. The original buying test remains refreshingly small: when an insurer needs to change a product tomorrow, who can actually do it?