Sixty people. You still know who is building it.
Omnivance is a technology firm of sixty-plus engineers, consultants and analysts. We build custom CRM, software and the integrations between them — with one named team on each engagement, staying on afterwards, because the people who designed a system are the only ones who can keep it honest.
Headquartered in the United States · working worldwide
It started inside an operation, not in front of one.
Omnivance was started by Oliver Whitfield, who spent six years working inside a lending operation before ever building software for one. Everything the firm does now follows from what those six years made obvious: the constraint is almost never the thing the brief names, and it cannot be found from the outside.
So the first week of an engagement is still spent on a client's floor rather than in a workshop. Four days reading and drawing, one day agreeing a boundary, and no commits until there is a picture everyone has signed. It is the least impressive week of any project we run and the one that decides the rest of it.
The first platform we built replaced a Salesforce org that could not model the process it had been bought for — positions, stipulations, parallel lender submissions and commission splits each needed a place the object model did not have, so the workarounds had become the system. That is still the most common shape of the work, and every system we have built since, we still run.
Sixty-plus people, one named team
Engineers, consultants and analysts across delivery, data and AI. Enough to staff several engagements properly, arranged so the four to eight people on yours do not change and you meet them before anything is signed.
Paid by no platform
No commission, referral fee or partner margin on any software we recommend, across the thirty-plus platforms we have shipped against. It is the only reason a recommendation from us is worth reading — including the common one to stay where you are.
Yours from commit one
The repository is created in your organisation at the start rather than transferred at the end, and your data exports in a usable form whenever you ask. Those are terms we write down, not gestures.
Four positions we hold, whether or not they win the work.
Draw it before building it
What connects to what, who owns which step, where each number comes from — signed off before a line is written.
Buying usually wins
Most problems are configuration, not construction. We will tell you when building is the wrong call.
The floor knows
We watch the work happen before proposing anything. The constraint is rarely where the brief says it is.
Stay after launch
Shipping is the middle of the job. The engineers who built it are the ones who run it.
Who you will actually work with.
Seven people lead the work, and one of them is on every engagement from the first call to the runbook. Their names, what each of them owns, and how sixty people still means one team on your account are set out on one page rather than repeated here.
A named team of four to eight
Sized to the scope and led by one of the seven. You meet them before anything is signed, and they are the same people three months in.
Discovery is never delegated
An engagement lead runs the first week personally. It is the week that decides everything else, which is why it is not handed to anybody else.
The core team does not change
Specialists join for a phase and leave when it ends, introduced by name when they arrive. Nobody appears on your project unannounced.
Systems currently running.
A lending platform, replacing a Salesforce org
Routing, eligibility, dialer, documents, commissions, executive reporting.
→A partner lead-ingest API
Synchronous accept or reject, so a partner knows inside the same request.
→Server-side attribution to five ad platforms
Funnel milestones classified from CRM history, deduped by watermark, pushed daily.
→An autonomous content agent
Production LLM work with scheduling, guardrails and version control.
→Come and tell us what's happening.
You do not need to diagnose it first, and you do not need to know which service to ask for.