How we work
From the first workflow to its daily operation.
Strategy, design, engineering and running the system belong in one conversation. This is how that conversation goes.
- Strategy
- Design
- Build
- Integrate
- Operate
- Improve
Six stages, one system.
- Strategy: Decide what needs to changeUnderstand the current workflow, the people involved and the result to work towards. Define a useful scope.
- Design: Make the system understandableMap the experience, the information it needs, the decisions it may make and the points where people approve or take over.
- Build: Implement the agreed systemDevelop the application, workflow or product against the written scope.
- Integrate: Connect it to the businessConnect the agreed systems, and check what happens when information is missing, access fails or a request needs a person.
- Operate: Keep the agreed parts runningCarry out the checks, backups and operational work the engagement includes.
- Improve: Change it with evidenceReview what the system is doing, agree improvements and record every change with a way back.
After the first conversation
Services are quoted in writing for their scope. Nothing starts until the scope and the price are agreed.
- Understand the workWhat happens today, and what you want to change.
- Confirm the fitAn existing product, a custom build, or a combination.
- Write the scopeDeliverables, integrations, responsibilities, stages and commercial terms, in writing.
- Agree how it is checkedThe scenarios and evidence that show the work is done.
- Agree how it runsWhat Omvora will operate, what you will own, and what happens at handover.
Ways to work with us
- A projectA fixed price for a written scope, paid stage by stage. Stop after any completed stage. Repository, keys and runbook are handed over where the project agreement provides for it.
- A subscriptionBilled monthly in advance, cancel from the end of any month. The written scope defines what is included.
- Operation after a buildOptional, as a subscription. We agree the systems covered and the work Omvora will do.
- Our own productsSoftware we build once and run for many businesses, such as Clinic Intelligence, as a subscription.
GST is added and shown on the invoice. Prices are given in writing; see Pricing.
The work continues after launch.
This is how we run our own systems, and the systems we operate for customers. Your operating agreement sets which parts of your system Omvora is responsible for, and the hours and response times that apply.
- Nightly checksEvery night the systems are checked, and an alert reaches a person.
- Backups you can restoreEncrypted backups every night, kept in several places, and restore drills that count every record.
- Secrets in a vaultKeys and passwords live in a vault, never in code.
- Changes with a way backEvery change is recorded with how to reverse it.
- People approve what goes publicPosts and bulk messages wait for a person’s approval.
- A security gateBefore a launch, a security review that must pass.
Decide where information goes.
We run open models on our own GPU server, so some workloads and data can stay with us rather than go to a provider. Paid model APIs are used too, under a budget for each project.
The systems we run ask for consent and record it; Preeco’s assistant handles access, correction and erasure requests, and Clinic Intelligence keeps each clinic’s data apart and an audit record of every action.
For each engagement, the scope names the data, where it is processed, which providers are involved, who has access, and how long it is kept.
Our privacy notice covers this website.
Tell us how the work happens today.
Describe the process, the people involved and the part you want to improve.