Experts: Building the Gateway to Niche Financial Services Expertise
Client: Bymark Holdings
Sector: Financial services technology and investment management
Services: Knowledge assistants, Workflow automation, Custom application development
The brief
Expert networks aren't a new idea. Investors, researchers, and business leaders have always paid for time with specialists who know something they don't, and there's an established industry built around connecting them. What most of those networks weren't built for is asset management specifically: the niche strategies, the specific roles, the confidentiality that institutional investors and fund service providers need before they'll get on a call with someone outside their own firm.
Bymark brought that gap to Zuko Group, and the two teams worked together on the specification: Bymark's institutional network and its understanding of what asset managers, fund service providers, and portfolio companies actually need from expert access, paired with Zuko's technical delivery, design, and build. That collaboration became Bymark Experts, now live as an invite-only web portal and native iOS app connecting requesters with vetted specialists across asset management.
Starting from the problem, not the feature list
Before any interface got built, Bymark and Zuko mapped what actually goes wrong when someone tries to source specialist knowledge the ad hoc way, through a personal network, a cold introduction, or a generic search. Finding someone with genuinely niche expertise takes longer than it should.
There's rarely a consistent way to verify who's actually qualified before you're already on the call with them. Requests and follow-ups get lost in email threads with no institutional record. And a firm with several people sourcing experts independently has no visibility across the organisation of who's spoken to whom, or why. Bymark Experts was developed as four connected functions, each answering one of those problems directly.
Function one: search built for niche expertise, not broad categories
Generic search treats "asset management" as one category. Bymark Experts doesn't. The search runs across specific financial sectors and niche operating models, so a request for someone who has actually run a particular strategy, or held a particular role at a particular type of firm, returns someone who fits that description rather than a broad list of people with "asset management" somewhere on their profile.
Getting this right meant resisting the temptation to build a directory. A directory is browsable; this had to be searchable against the specific, sometimes narrow, brief a requester actually has, which is a different design problem entirely.
Function two: validation before anyone gets on a call
The biggest risk in ad hoc expert sourcing isn't cost, it's finding out halfway through a call that the person on the other end doesn't actually have the expertise they claimed. Bymark Experts addresses that upfront with a validation step: every specialist's credentials and background are checked before they appear in a search result, not after a requester has already committed time to the conversation.
This function exists to do one thing well, protect the requester's confidence before the call happens, and it was treated as a gate rather than a formality: nobody appears in search results without clearing it.
Function three: the mandate workflow, from request to resolution
A request for expert time isn't a single event, it's a small process: requirements get submitted, a specialist gets matched and booked, the consultation happens, and someone needs to know it was actually completed.
Bymark Experts turns that into a structured mandate workflow rather than an email thread, with automated processes handling status tracking and progress updates so a request doesn't need someone chasing it manually, or custom logic rebuilt every time a new type of mandate comes through.
For firms with research teams, deal teams, or investment teams sourcing experts regularly, and often working across different offices or remotely, this is the difference between a process anyone can pick up mid-flow and one that only makes sense to whoever started it.
Function four: a record that outlives the conversation
Every consultation is transcribed. That's not a convenience feature, it's the function that turns a one-off conversation into institutional memory: a searchable record of what was actually discussed, available to the requester's team long after the call itself is forgotten.
The AI layer's job here is content, not classification, turning a spoken conversation into a usable, readable record, while the workflow logic underneath keeps that record correctly tied to the mandate it belongs to.
Paired with this is the enterprise view: a firm can oversee multiple experts and consultations under a single administrator account, so a COO or research head has visibility across who's been consulted and why, without reconstructing it from individual calendars and inboxes.
Built for the web portal and the phone, not one or the other
Most expert networks run as a web platform, with the actual coordination happening by phone and email once a match is made. Bymark Experts has the web portal, but Bymark and Zuko also built a native iOS app alongside it, and that was part of the specification from the start, not a secondary decision made after the core platform was live.
A business leader with an urgent question doesn't always want to track down a laptop and log into a browser tab; they want to open the app, search, submit the request, and watch the mandate move, from wherever they happen to be, with the same functionality waiting for them on the web portal when they're back at a desk.
For an audience that isn't always at a desk when the question they need answering comes up, that's the difference between a service people actually reach for in the moment and one they mean to get around to later. It's also a genuine point of difference from the desk-bound, email-driven expert networks most requesters have used before, and it's why the search, validation, mandate, and transcription functions above were all designed to work consistently across both, rather than being built for one and adapted for the other afterwards.
Why these four, in this order
Search without validation just returns a list of unverified names. Validation without a mandate workflow leaves trust in the system but no record of how it was used. And a workflow without transcription tracks that a conversation happened without capturing what was actually said. Each function depends on the one before it holding up, which is why building all four properly, rather than shipping the search and bolting the rest on later, was the point from the start.
The result
Bymark Experts now gives investors, researchers, and business leaders confidential, invite-only access to vetted asset management specialists, from their phone or their desktop, with every consultation tracked, recorded, and visible to the firm that commissioned it, not just the individual who made the call.
For Zuko Group, it's another example of the kind of partnership we're built for: a client with institutional depth in a market we don't have on our own, and a technical team that can turn that understanding into a working product across both web and native, not just a set of features.
Find out more about Experts from Bymark.