About
Kevin Hokoana
Technologist and strategist. Architect of the Asher suite — production platforms spanning market data, charting, artificial intelligence, commerce, and speech. Principal of Hokoana Global.
Background
Most people in this field are one of two things: a strategist who cannot build, or a builder who has never had to defend a business case. Kevin Hokoana works in the overlap, and the overlap is where the useful answers live.
The work is unusually vertical. Rather than assembling products out of licensed components, he tends to build the layer underneath — the market-data pipeline instead of the data subscription, the chart renderer instead of the charting widget, the strategy language instead of the scripting plugin. That is a more expensive first year and a far better fifth one, and having made the trade in both directions is what makes the advice worth paying for.
On the artificial-intelligence side the emphasis is production economics as much as capability. An agent that answers correctly but costs more per conversation than the customer pays is not a product. The Asher agent runs a real tool-use loop against first-party data, with caching, retrieval, and inference-free fast paths engineered specifically to hold that cost down — the part of AI work that rarely makes it into a conference talk and always decides whether the thing ships.
The portfolio is deliberately broad. Alongside the financial platforms there are healthcare portals built for a family member, a bilingual consumer food app, news properties with their own publishing backends, a multi-tenant help-desk product sold as software, and brand work for a luxury label. Breadth is not dilettantism here — it is the evidence that the method is a method, and not a single lucky domain.
The rules the work runs under.
Own the data
Systems that depend on someone else's feed inherit someone else's outages, licence terms, and pricing power. Where it matters, the data layer gets built and owned.
Verify, never assume
No claim ships without a reproduction behind it. Behaviour is proven against real data in the real environment, not argued from first principles.
Done means deployed
Working on a laptop is not finished. An engagement closes when the thing is running in production and has been checked there.
Build the whole stack
Data, engine, interface, billing, and go-to-market. Owning every layer is what makes the strategy advice worth anything.
Make the numbers worse
The standing rule in the engineering notes: every improvement should make the numbers worse and more trustworthy. Most of what a validation pass produces is deletion.
Report the status, not the story
Built is not live. Dormant is not shipped. Systems get described as what they actually are, including on this website.
Work together.
A small number of engagements run at a time, so the fit matters more than the fee.
Start a conversation