We build the app, then improve it with every release.

You have an app or a feature and a number you want to move: more people finding what they came for, coming back or paying. We build it with your team, on the tools you already use.

Before launch we agree the numbers that show it working. After launch we measure each release against them and keep improving it.

What we build.

  • Mobile apps and online portalsNew apps and portals, or new screens in the one you run, built on the tools you already use.
  • Online scheduling, payments and self-servicePatients, residents and customers book, pay and get answers on their own, and your team handles the exceptions.
  • Recommendations that fit each personWhat each person sees next is based on what they and people like them did.
  • Search that finds the right answer firstSearch understands plain language and puts the right result first, with the reason.
  • Clear reports on what’s workingReports show what each release changed, so you know what to keep and what to fix.

What the work looks like in your product.

  • A patient app that rebooks the visit

    A patient asks in the app. It finds the visit, offers the open times and rebooks, and calls to the front desk are measured with each release.

  • A client portal that explains its numbers

    A client asks about a statement. The answer quotes the agreement it came from, and what it can’t answer goes to an advisor.

  • A field app that knows the equipment

    A technician opens the job and sees the unit’s history, the fault that keeps coming back and the part to bring.

What an app needs before it reaches users.

  • Numbers agreed before launch.We choose the numbers that show it working with you, and track them from the first release.
  • Real cases to test against.Examples from your own product that each release has to pass before anyone uses it.
  • A switch your team controls.Your team can turn a feature off or undo a release.
  • An owner after launch.Someone you name before launch watches the numbers and decides what changes next.

Questions.

How do you know a feature is working?

We agree the numbers that matter before launch and measure them with each release, so each change is judged on what people did.

Can you build inside the app we already have?

Yes. We work with your team on the tools you already use, and ship through your release process.

Which AI do you build on?

The one that does the job at a cost you can run. We test the options on your own cases, and it can be swapped later without rebuilding the feature.

Who owns the work?

You do. Everything we build is yours and lives on your systems.

Tell us what’s slowing you down.

Cookie settings

Choose what this site may store in your browser. You can change it any time from Cookie settings at the bottom of every page.

EssentialAlways on

Remembers the choice you make here. Nothing else is stored until you turn analytics on.

What is stored
NameWherePurposeKept
lucitra-consentLocal storageYour analytics choiceUntil you clear it
Analytics

Shows us which pages people read, what breaks, and which links bring people here, so we know what to fix. Off until you turn it on.

What is stored
NameWherePurposeKept
ph_<key>_posthogCookieA random identifier for your browser, and the current session1 year
ph_<key>_posthogLocal storageThe same identifier, as a backup to the cookieUntil you clear it
lucitra-last-touchSession storageThe link or campaign that started this visit, sent only with a contact form messageUntil you close the tab
lucitra-first-touchLocal storageThe link or campaign of your first visitUntil you clear it
lucitra-last-touchLocal storageThe link or campaign of your latest visitUntil you clear it
Cookie policy