Company

Make every call answerable.

Our mission is narrow and stubborn: a phone call should never go unanswered, never mislead the person on the other end, and never leave a business unable to explain what it said. Everything we build is a consequence of those three sentences.

▪ Founded August 2024, Leeds, West Yorkshire ▪ 84 people across four offices ▪ 61 production workspaces
The short version

Two people started Nivākya after watching a regional property developer lose 340 inbound calls in a single weekend. Nobody was being careless — the phone system simply had no way to answer, qualify and record a call without three humans and a spreadsheet.

We built the version we would have wanted to buy: an agent that picks up in under a second, a rehearsal stage that runs before it ever dials a customer, and an audit trail that a compliance team can read without translating it.

Our story

Twenty-six months, written down as it happened.

August 2024 — Founded

Two people, one rented number and twelve test calls. The first version answered in 2.4 seconds and misheard “Marina Road” as “Marina Grocery”. We kept the recording and still play it at onboarding.

November 2024 — First customer, first certificate

A regional property developer took the pilot after their risk team asked for documentation. We had a runbook and a blank ISO 27001 manual. We shipped the certificate in eleven weeks and the customer stayed.

February 2025 — Studio and Rehearsal 1.0

Agents stopped being prompt files and became versioned artefacts. The first million simulated calls ran that month, and 31 of them found genuine policy breaches before a customer ever heard the agent.

July 2025 — Bengaluru engineering centre

The Hindi, Tamil and Telugu models were not going to be built from a Leeds office. Twenty-two engineers joined in the first quarter, and the ASR team has been in the same time zone as its hardest evaluation set ever since.

November 2025 — SOC 2 and Rehearsal 2.0

Type I in October, Type II in November with a twelve-month observation window behind it. Rehearsal gained the adversarial persona library that most of our customers now treat as the actual approval gate.

April 2026 — Series B

£48M led by Ridgeline Capital, earmarked for regional infrastructure and a second India engineering centre in Pune. No change to pricing, no change to the roadmap we had already published.

June 2026 — Benchmark Q3 published

We ran six vendors through one test set, including ourselves, and published the fabrication-rate table where we finish third. It is the most-read document we have ever released.

September 2026 — Present

84 people, four offices, four data regions, 61 workspaces and 4.2 million calls in the last ninety days. The number we watch hardest is still the post-call escalation rate.

Where we are today
Headquarters
Leeds, West Yorkshire
Offices
Leeds · London · Bengaluru · Dubai
Team
84 full-time, 11 contractors
Data regions
US, EU, UK, India, UAE, Australia
Investors
Ridgeline Capital, Cinder Peak, Arun Bhatt
Certifications
SOC 2 Type II, ISO 27001, HIPAA, DPDP

Operating principles

Six rules we argue about less than you would expect.

PRINCIPLE 01

Publish the numbers we lose on

Fabrication rate, escalation rate, per-region p99. If a figure is embarrassing, it goes in the report with a note on what we are doing about it. Buyers can smell a curated benchmark.

PRINCIPLE 02

Fail closed, never improvise

When a rule cannot be evaluated, the agent hands the call to a person. An agent that guesses is more expensive than an agent that stops, because guessing is invisible until it is a legal problem.

PRINCIPLE 03

Rehearsal before revenue

No agent sees a live customer before a signed rehearsal pass, including internal demos. The rule has cost us two deals and saved us four incidents that we know of.

PRINCIPLE 04

One agent, one signature

Every published version carries the hash of the rehearsal run that approved it. If the signature and the running version disagree, the runtime refuses to answer the call.

PRINCIPLE 05

Data stays where you put it

Residency is enforced at the storage layer. We have no cross-region replica of conversation data, which occasionally makes our analytics slower and our customers calmer.

PRINCIPLE 06

Handover is a feature

Escalation is designed, measured and reported as a success metric, not treated as a failure of the model. The best agents we run hand over more often than the worst ones.

Leadership

Six people, and what they were doing before this.

Every voiceprint below is generated from the person's name — the same deterministic process that gives each agent and integration its own glyph. We do not publish headshots.

Ira Nadkarni

Co-founder & Chief Executive

Ran a 900-seat contact centre for a telecom before joining the platform side. Decides what we refuse to build, which turns out to be most of the job.

Daniel Okafor

Co-founder & Chief Technology Officer

Built realtime media infrastructure at carrier scale, including the part that keeps audio alive when a region fails over. Owns the latency budget personally.

Mei-Ling Tan

Chief Scientist

Fifteen years on speech recognition and prosody, most of it on the unglamorous problem of accented speech on a bad line. Wrote our evaluation set.

Raghav Iyer

Chief Product Officer

Spent a decade turning BPO workflows into software and has strong opinions about which spreadsheets deserve to survive. Owns Studio and Rehearsal.

Sofia Marchetti

Chief Trust Officer

Privacy counsel by training, regulator-adjacent by history. Wrote our DPA, our responsible-AI policy and the objection process customers actually use.

Owen Fitzgerald

VP Revenue & Partnerships

Built partner channels across EMEA and Australia, twice from zero. Insists that every partner gets certified on delivery quality, not on quota.


By the numbers

The company, counted.

0
People
Across four offices, 11 contractors
0
Production workspaces
Zero pilots still in simulation
0M
Calls handled / 90 days
Including outbound attempts
0
Languages shipped
Nine accents on English alone
0
Named sub-processors
Every one region-pinned
Why we count workspaces and not logos. A workspace is a customer running real traffic in production for at least thirty days. Free-tier pilots are excluded, because a pilot that never rings a customer should not be a number on a website.
Careers

Eight roles open right now.

We publish salary bands with every listing, work remote-first, and keep a written decision log that any employee can read. If a role is listed here, it is funded and someone is waiting to interview.

RoleLocationTeamType
Staff Engineer, Realtime MediaBengaluru · hybridRuntimeFull-time
Senior Research Engineer, ASRBengaluru · hybridResearchFull-time
Product Designer, ConsoleRemote · EUDesignFull-time
Solutions Architect, GulfDubaiField EngineeringFull-time
Enterprise Account Executive, DACHLondonRevenueFull-time
Trust & Compliance AnalystRemote · USTrustFull-time
Technical Writer, Developer DocsRemote · anyDeveloper ExperienceContract, 9 months
Customer Support Engineer, APAC shiftBengaluruSupportFull-time
The hiring process, in four stages. A 30-minute intro with the hiring manager, a paid work sample drawn from real (anonymised) problems, two technical or craft interviews with the people you would work with, and a 45-minute conversation about how you like to be managed. Three weeks end to end, and you get a written decision either way within five business days of the last stage.
What we will not do. No unpaid take-homes longer than four hours, no whiteboard algorithm puzzles, no panel that includes someone you will never meet again, and no verbal offer without the band written down. If a recruiter asks you for a current salary, that is not a Nivākya recruiter.

Newsroom

Boilerplate and company facts.

Journalists and analysts may quote the text below verbatim. You do not need to ask first — we would rather you got the name right than asked permission.

Long boilerplate (quote freely).
Nivākya builds voice agents that answer, qualify and prove it. Founded in Leeds, West Yorkshire in August 2024, the company runs inbound and outbound conversations at a median turn latency of 0.61 seconds across 42 languages, and requires every agent to pass a simulated rehearsal against up to ten thousand synthetic callers before it reaches a customer. Nivākya stores conversation data in the region a customer chooses, publishes a signed audit trail for every call, and holds SOC 2 Type II, ISO 27001, HIPAA and India DPDP attestations. The company employs 84 people across Leeds, Bengaluru, Dubai and London, and handled 4.2 million calls in the ninety days to September 2026.
Short boilerplate.
Nivākya builds voice agents that answer, qualify and prove it — rehearsed against ten thousand simulated calls before go-live and auditable call by call. Founded 2024, headquartered in Leeds, West Yorkshire.
Company facts. Legal name: Nivākya Technologies Ltd. Registered in England and Wales, company number 15834207. Registered office: 12 Wellington Street, Leeds LS1 4DL, England. VAT registration GB 374 2918 55. ICO registration ZB739214. Incorporated: 12 August 2024. Investors: Ridgeline Capital, Cinder Peak. Press contact and logo files: all approved assets are published on the brand assets page; for anything else, use the contact form and mark the note as “press”.
Writing about us
  • ▪ Describing the product is welcome; implying a partnership or endorsement is not.
  • ▪ Any screenshot must come from a demo workspace, never a customer's.
  • ▪ Quote either boilerplate freely, in whole or in part.
  • ▪ Interviews, data or anything else: use the contact form and mark the note as “press”.
Logo, palette and brand marks

Every logo file, the full colour palette, clear-space and minimum-size rules, and guidance on what not to do live on the brand assets page — as true vector SVG alongside high-resolution PNG exports.

Open brand assets
Offices

Four places, twenty hours of coverage.

HEADQUARTERS

Leeds, West Yorkshire

12 Wellington Street
Leeds LS1 4DL
England

24 people · UK time (GMT/BST) · covers the UK, EU and Middle East

ENGINEERING

Bengaluru

Prestige Tech Park, Kadubeesanahalli
Bengaluru 560103, India

38 people · India Standard Time (UTC+5:30) · covers APAC and Gulf mornings

REGIONAL

Dubai

Dubai Internet City, Building 8, Office 214
Dubai, United Arab Emirates

9 people · Gulf Standard Time (UTC+4) · Arabic dialects and in-country residency

REGIONAL

London

24 Finsbury Circus, Third Floor
London EC2M 7EB, United Kingdom

13 people · GMT (UTC+0, BST in summer) · EU and UK customer teams

Coverage, honestly stated. Between Leeds and Bengaluru we have an engineer on shift for roughly twenty hours of every day. The remaining four hours are covered by a paging rotation with a fifteen-minute acknowledgement target, and every incident in the last twelve months was acknowledged inside ten. Support in a language other than English is available in Hindi, Kannada, Arabic and Italian during regional hours.
Start

Come see whether we mean it.

A thirty-minute call, three real recordings, and a straight answer about whether we are the right fit. If we are not, we will say so and point you somewhere better.

Careers enquiries go to the same form — mark the note as “careers” and it goes straight to the hiring manager.