Financial Analysis: Lessons Learned
A good workman never blames his tools but a better workman will be on the lookout for optimisations
“Check out my quant” is something nobody has ever said about me, and for good reason.
I am not a financial analyst, nor am I a financier by training; I am firmly in ops management and qualitative research - much more accustomed to researching by interpreting and cross-referencing texts, tracing arguments and identifying conceptual (meta)structures than by interrogating balance sheets or corporate filings. When FRx’s CEO, Ben, suggested that I would make a suitable guinea pig for purposes that were still yet to be explained, I was game.
The brief I received was deceptively simple. He provided me a name, which we will change to Markus Poole, and said: “I’m your manager at a firm. You have three hours to come back with something I haven’t already found.”
No template, no predefined output and no checklist of questions. The instruction was open ended and intentionally so. Should be straightforward enough. Right?
The manual process
I began where I figured one is supposed to begin: with a search on Companies House.
A trawl through filings, directorships, dates and changes in shareholdings. A few entities that appeared dormant. One that looked active. How can I even be sure that this person exists? “He” could be some kind of shell holdings entity… I wondered.
LinkedIn next.
Employment history, board positions, mutual connections, universities and events. Markus’ professional trajectory appeared coherent enough - not very information rich, however.
On to Google.
News mentions, archived interviews, conference panels. A local newspaper article from a decade ago. A blog post here, a podcast appearance there. Each source opened another tab. Each tab introduced another thread and within forty minutes I found myself with over thirty tabs open.
I was taking “notes” (read: scrappy little fragments, copy-and-pasted excerpts and half-baked hypotheses) in a text editor. Externalising is a favourite coping mechanism of mine and I was sure that when I looked back at the notes I would remember what they signified. Or referred to. Or labelled?
Is there a pattern in the types of companies he joins?
Are there overlapping directors across these entities?
What do the accounts suggest about performance?
The process felt unstructured, lossy and honestly a bit anxiety inducing. I was conscious that I was losing context with every new tab. A date copied into my notes lost its meaning while a quote from an article was detached from its publication source and author. The difficulty was the absence of structure, rather than the absence of information. Provenance was like sand slipping between clenched fists. The more information I gathered, the less confident I felt about my grip on it.
This is an information architecture problem.
The hidden friction
Professionals in financial research are deeply habituated to this workflow. They toggle between tools. They copy and paste. They reconstruct context manually. They hold mental maps of relationships between people and entities. They are highly skilled at it. But the process itself is fragile.
Small errors creep in easily. A misattributed quote. A company with a similar name but a different registration number. I found myself constantly backtracking and triple-checking.
Where did that claim originate?
Was that figure from the 2021 accounts or 2022?
Was that directorship current or resigned?
Each question required reopening a tab, rescanning a page, and reorienting myself.
Three hours, in this context, is not long. It is barely sufficient to construct a coherent map of a moderately active professional life. I began to understand how much of the analyst’s role involves simply maintaining orientation across a sea of fragmented data.
Judgement requires synthesis. Synthesis requires clarity. Clarity requires structure and data quality. Without structure, effort dissipates into some kind of corporate ether.
Introducing Amuse-Bouche into the workflow
At the halfway mark, Ben suggested that I run the same materials through Amuse Bouche.
And while AB’s UI is elegant, it isn’t theatrical. It’s purpose built and restrained, but what changed dramatically was the feeling of cognitive load.
Documents were not treated as flat text, corporate filings retained their internal structure. Names, dates and roles were extracted in relation to one another. Entities were recognised as entities rather than as strings of characters.
Instead of maintaining my own fragile web of notes, I could explore a structured representation of the information.
Markus Poole was linked to Company A as a director from 2018 to 2021.
Company A shared a co-director with Company B.
Company B had filed late accounts twice.
A news article referencing Company B was tied back to the specific entity rather than floating as an isolated citation.
Crucially, finally, each extracted element retained provenance. I could trace a claim back to its source document instantly and the genuine anxiety of context loss subsided.
AB did not replace judgement. It did not generate an opinion for me. It altered the substrate on which judgement could operate and I was no longer expending energy on bookkeeping.
The bottleneck in financial analysis is rarely access to information. It is the management of it.
Amuse-Bouche is a small demonstration of a larger thesis.
If the early stages of research are dominated by manual extraction, context reconstruction and error minimisation, then a significant portion of analytical capacity is diverted away from higher order thinking. Over time, this shapes the profession itself. Analysts become adept navigators of fragmented systems rather than beneficiaries of coherent ones.
For someone like me, entering from a qualitative background, the contrast was stark. The manual workflow felt like playing darts in a pitch-black room. The structured workflow turned the research and discovery process into something intentional and fruitful.
Financial research demands rigour, scepticism and traceability. None of these qualities are enhanced by forcing professionals to act as human glue between incompatible tools.
Amuse Bouche does not claim to solve every dimension of this problem. It does demonstrate that document interaction can feel different.