Invara

Tell us what you want built. See the price, the screens and the result before it goes live.

Vara is Invara’s AI delivery platform. It reads your system, scopes and prices each request, builds it, and puts the result in front of you in your own application. Our team runs it and answers for every release.

A price you approve firstEvery request is estimated before work starts. Once you approve it, the price is fixed. If it takes longer, that’s on us.
Nothing built unseenYou see a mockup of new screens before the build, and the finished work in a private preview before release.
People in chargeAn Invara developer reviews every high-risk change. Vara never releases on its own.

How it works

  1. You send a request

    You

    An email in plain words is enough. You don’t write a specification.

  2. Vara scopes it

    VaraInvara

    Vara reads your actual system: the code, the data and the decisions already made. It splits the work into pieces and asks about what it can’t work out. Our team answers what we can. Anything only you can decide comes to you, with why it matters and a suggested answer.

  3. You approve the price

    You

    The estimate is in Delivery Credits, broken into parts so you can see where it goes. Nothing is built until you approve it.

  4. You see the screens first

    VaraYou

    For anything with a new screen, Vara draws a mockup of your own application. The approved mockup is what the build has to match.

  5. Vara builds it

    VaraInvara

    Each piece is built in its own isolated copy of your system, tested, then checked by a separate reviewer that did not write the code. Our developers review every high-risk change and step in where judgement is needed.

  6. You try it in your own application

    You

    You get a private preview with the new work running. A review panel beside it shows what Vara tested and what is left for a person to check. You mark each check pass or fail, leave feedback on the screen you are looking at, and ask our team or Vara a question.

  7. We release it together

    YouInvara

    We agree which feedback to act on and when it goes live. You get screenshots of every finished screen and a report of what was delivered against what was estimated.

What you see

An Invara estimate report: total credits, then each part of the work with its credits and the reasoning.
The estimate. Each part of the work, its credits, and the reasoning.
A mockup of an existing application screen with a new client rating panel drawn in.
The mockup. Your own screen, with the new feature drawn in.
An application in a preview, with a review panel on the right listing checks and one marked as passed.
The preview. Your application on the left, the review panel on the right.

These are from a request we ran on Invara’s own support platform.

The Delivery Credit

What a credit is

A Delivery Credit is roughly one hour of a developer’s work: analysis, building, testing, review and release preparation. You buy credits, and each approved estimate draws on them.

Where the number comes from

We sized 829 finished tickets from six months of our own delivery the same way. A full-time developer delivers about 130 credits a month, so you can weigh an estimate against the team you have today.

Where it fits

Best for

Changes to an application you already run: new features, new screens, redesigns and fixes. It adds delivery capacity without hiring, and without changing how your own team works.

Still with our engineers

Architecture, large new systems and production operations stay with people. So does every release.

NextWatch the demo

Watch a real request go from an email to a preview

We gave Vara a request on our own support platform and filmed every step. Four minutes, with sound.

NextThe Insurely case study
Case study

Insurely’s client portal, redesigned and rebuilt in under four days

Insurely asked for a full redesign of Pocket, the portal its clients use to manage their insurance. Vara, Invara’s AI delivery platform, built all 24 features and had them running in a private preview 3 days and 15 hours after work began.

24features built, covering every screen of the portal
223Delivery Credits, about seven weeks of one developer’s work
51pull requests merged, after 50 rounds of code review
3d 15hfrom the start of the build to the last merge

The business gain

Faster: seven weeks of work, running in under four days

The redesign came to 223 Delivery Credits. At Invara’s measured pace of about 130 credits per developer per month, that is about seven weeks of work for one developer. Vara had all of it built and running in a preview in 3 days and 15 hours.

One developerAbout seven weeks to build the same 223 credits of work.
Vara3 days 15 hours from the start of the build to the last merge.

Both figures are build time. Insurely’s own review and the release come after, either way.

Cheaper: a fifth to a half less per unit of work

A Delivery Credit is roughly one hour of a developer’s work, and it costs less than that hour usually does. For Invara’s clients so far, that has meant between a fifth and a half less, depending on what they were paying before.

The price is also known before the work starts. Each request is estimated in credits and approved up front, and if the build takes longer than estimated, that is on Invara.

Credit pricing depends on volume and commitment. Send us one request and you get its scope and its price before you commit to anything.

The request

A new look for every screen a client touches

Insurely sells home, condo and tenant insurance. Pocket is where its clients sign in to see their policies, make payments, file claims and download documents.

Insurely had an approved design for a new Pocket and wanted the whole portal moved to it: the frame and navigation, every existing screen, and a set of new features the old portal never had. It also wanted Pocket’s actions made available to its AI agent.

What was built

Vara read Insurely’s code and the approved design, then split the redesign into 24 features and worked out which ones depended on which.

The foundation

  • New Pocket frame and menu
  • Restyled sign-in pages
  • Sign-in by emailed link
  • Pocket actions for Insurely’s AI agent

Every screen, rebuilt

  • My Overview
  • My Policies
  • My Payments
  • My Claims
  • My Account
  • Make a Change
  • Cancel policy
  • Documents and proof of insurance

New for clients

  • Coverage and address changes priced as you type
  • Pay now, receipts and one list of payment methods
  • A shareable proof of insurance link
  • Renewal preview and attention cards
  • Options before cancelling, a live refund figure, and a way to withdraw a cancellation
  • Moving a policy to another province
The new Pocket overview, showing a payment that needs attention and the client's policy.
My Overview: what needs attention, then the policies.
A policy page in the new Pocket, with coverage details and actions.
A policy page, with coverage and the actions a client can take.
The Change your coverage screen, with the new price shown beside the form.
Change your coverage: the price updates as the client edits.
The Documents screen, with proof of insurance and policy documents.
Documents and proof of insurance.

Screens are from the preview and show test data.

How the build went

The features were built in five waves, in dependency order: the frame first, then the screens that sit inside it, then the features that build on those screens.

2 hoursThe first pull request is merged.
21 hours19 of the 24 features are built: 155 credits of work.
3 days 15 hoursAll 24 features are built and running in the preview: 223 credits.

A Delivery Credit is roughly one hour of a developer’s work. Invara’s baseline, taken from 829 of its own finished tickets, is about 130 credits per developer per month. On that measure, 223 credits is about seven weeks of one developer’s output.

Who did what

Insurely

Supplied the approved design, and reviews the finished portal in the preview, in its own application.

Invara

Ran the project: answered Vara’s questions, steered the plan, stepped in where judgement was needed, and controls the release.

Vara

Read the code, split the work, estimated each feature in credits, wrote and tested the code, put it through 50 rounds of review by a separate reviewer, and took more than 270 screenshots of the finished screens.

Where it stands

The new Pocket is running in a private preview, where Insurely can use every screen before anything reaches its clients. Vara never releases on its own.

Before release, Invara reviewed the whole build and is working through a final round of follow-up items it found. Release timing is decided together with Insurely.

Back toHow it works