Investors
What we are building.
Four products, built out of twenty years of engagement work. None is deployed, none generates revenue, and this page says what each one actually is.
XONIK is building four products out of work that kept recurring across engagements — AI search visibility, business operations, a universal dashboard, and an agent platform. None is deployed or generating revenue. This page states what each is, what stage it is at, what capital would fund, and what would show the thesis wrong.
What is being built
Four products, all in build.
AI search visibility
A continuous version of the visibility measurement we run by hand for clients — a fixed prompt set, tracked weekly, rather than a one-off screenshot. In build, not deployed.
Business operations
The reconciliation and evidence-record layer we have built bespoke for four separate integration engagements, generalised into a system a team could run without us. In build, not deployed.
Universal dashboard
An early attempt at turning a one-time governance review into something that runs continuously instead. In build, not deployed.
Agent platform
Departments of specialist agents working a workflow together, with attribution designed in from the start rather than added afterwards. In build, not deployed.
Others, earlier
Two further ideas exist at the stage of a written specification and nothing else. We are not naming them until there is a codebase to describe.
All four are in build
None has a paying user, none is deployed outside XONIK, and none is further along than the others in any way that would matter to you. What differs is what each one does, not how close it is.
Why not a normal raise
This is not a normal software raise.
Most software companies start with a product hypothesis and go looking for customers to test it on. These four started the other way round. A visibility baseline rebuilt from scratch because the last one measured the wrong thing. An evidence layer bolted onto a system that should have had one from the start. A governance review redone because nobody could say who had decided what. And a chain of agents unpicked by hand, because when one step was wrong there was no way to establish which.
The question a normal raise asks is whether the product will find a market. The question here is narrower: whether a fix we already know works, and have already been paid to build by hand more than once, is worth building once, properly, instead of every time. That is a smaller bet, and a different one — capital funds the second version of something proven, not the first version of something guessed at.
None of that changes what stage each product is actually at, which the previous section states plainly.
What capital would fund
Engineering and pilots, specifically.
The AI search visibility product to a deployable state
Engineering time to take it from a working codebase to something a team outside XONIK can run unsupervised.
A first pilot cohort for business operations
Run at a price that covers support rather than at a margin.
The compliance and security review
The review a product needs before it can sit inside an enterprise client's own infrastructure.
Not: marketing spend or headcount growth
Capital raised here funds engineering and pilots, not a sales team or a hiring plan. If that changes, this page will say so before it happens rather than after.
The thesis
The thesis, and how to falsify it.
The thesis
Twenty years of engagement work keeps producing the same handful of gaps, on unrelated engagements, for unrelated clients. A fix built once and generalised should cost less than a fix rebuilt by hand every time, and should be worth more to a client who can run it themselves. That is the entire bet.
What would show us wrong
- If engagements stop turning up the same handful of gaps
- If a product takes longer to reach a first pilot than the consulting equivalent takes to deliver by hand
- If a pilot client will not let the deployment be referenced, even anonymously
- If the consulting margin alone makes productising not worth the engineering time
What you can check today
Available before a call is booked.
The Field Report
The same evidence and the same limits sections this page uses, published on a rolling basis since before any of this was written down as a pitch.
The codebase
The AI search visibility product specifically, under a data room NDA.
References
From the engagements each product was generalised out of, contactable directly, not through us.
The people
Backgrounds available on request; we do not publish headcount or org structure.
We would rather you found the thesis boring than found it later.
A raise that depends on a story holding up is a worse bet than one that depends on arithmetic anyone can check.
Nothing on this page is written to be persuasive. It is written to be checked.
Read the Field ReportQuestions
Before you write.
Why build products instead of scaling the consultancy?
Consultancy revenue is bounded by the hours we can bill. A product built once and used by many clients is not. That is the entire commercial argument, and it is the only one on this page.
What is the revenue model for these products?
That belongs in a data room conversation, not a public page — this page carries no figures, no projections and no forecast of returns, on principle.
Who owns the intellectual property?
XONIK does. Nothing here was built on client-owned code or client-owned data; the pattern was learned across engagements, not extracted from any one of them.
Is XONIK raising right now?
This page exists so that when the answer is yes, an investor is not starting from zero. Whether a round is currently open is answered directly, by email, not published here.
What stage is this at?
Pre-product-revenue on all four. The stage statements in the sections above are exact and are not softened for this page or any other.
How do I get data room access?
Write to investors@xonik.com. Access is granted individually, not by a form.
Start a conversation.
One person reads everything that arrives, and an investor enquiry reaches the same inbox as everything else.