Tiffany runs Illumea Advisory, a boutique consulting firm that advises fintech and payments companies on strategy, pricing, and growth. Earlier this year, she was deep into an engagement with a payments technology client who needed a clear competitive picture fast — their pricing was out of step with the market, their positioning was blurring, and the board meeting was on the calendar.
She had the relationships, the judgment, and the trust of the executive team. What she didn't have were the eighty-plus quiet hours the synthesis work was going to take.
I spent three weeks reading, cataloguing, and cross-referencing the eighty-to-ninety documents that had accumulated across her engagement and turned them into a 55-page competitive analysis, an executive summary, and a slide deck she presented to the client's team. The presentation landed. The client's compliance officer committed to reading the full report. And Tiffany's time went where her time was supposed to go — the last thirty percent of the work, where her strategic superpower actually lives.
The Problem
Boutique advisors win business on judgment, relationships, and the ability to see a client's situation from the outside. That's the work. It's also the work that gets crowded out the moment an engagement needs deep document synthesis.
By the time Tiffany brought me in, her working folder held every artifact of a serious, months-long advisory engagement: intake documents, interview transcripts, competitor profiles, billing and operations data, market reports, executive notes, slide fragments, and analyses she had started drafting at different points along the way. Somewhere between eighty and ninety files, all relevant, most partial.
The client had hit a decision point that required all of it to come together. They needed to see how their pricing compared across the competitive set, where their positioning was working and where it was collapsing, and what specific moves would change their trajectory. The board was expecting an answer. Tiffany had the raw material to build one. She didn't have the hours.
"I think the hardest part for me was just managing all the data. It was a lot of data."
— Tiffany, Principal, Illumea Advisory
This is a shape of problem I see constantly with boutique advisors. The synthesis work is unavoidable — a competitive analysis without it is opinion, not analysis. But synthesis is almost never the highest and best use of an advisor's time. The moment it becomes the bottleneck, the engagement bleeds: the advisor either stays up for three weekends in a row or pushes the client's timeline. Neither outcome is what the client paid for.
Why Illumea Hired Me
Tiffany had other options. She could push through the synthesis herself. She could hire a research associate or a VA for the reading and note-taking. She could engage a traditional consulting firm and put a junior team on the work.
None of those fit her situation.
Doing it herself meant pulling hours away from the client-facing work that justified her rate — and the calendar wasn't going to bend. A VA or research associate would need weeks of ramp-up on the competitive landscape, the vocabulary, and the client's specific context before producing anything usable. A traditional consulting firm meant a proposal, a contract, a team onboarding, and a price tag scaled for a firm — none of which fit a three-week window under her existing engagement.
I fit because the operating model was built for this exact shape of work: one operator already calibrated on how advisors think and what client-ready output looks like, working under Illumea's existing client contract, scoped specifically for synthesis — not strategy, not client relationships, not delivery. That division of labor was the whole point.
What I Did in Three Weeks
The scope broke into four deliverables over three weeks in March and April 2026.
Synthesized 80–90 Source Documents
The foundation of the engagement. I worked through the full document corpus Tiffany had accumulated — research, interview notes, billing and operations extracts, competitor profiles, and her own working drafts — and built a single structured knowledge base across the whole set. Not individual summaries. A synthesis that tracked which findings reinforced each other, which contradicted each other, where the data was thin, and where the patterns actually were.
This is the part of the work that looks unglamorous from the outside and matters enormously in the output. A 55-page report built from a shallow read of the same documents would have read like a book report. A synthesis built across them reads like analysis.
Delivered a 55-Page Competitive Analysis Report
The core written deliverable. The report covered the client's competitive position, pricing dynamics, and a prioritized set of strategic options. I structured the sections so different readers could find what they needed: a strategic thread for the CEO, a pricing analysis for the finance lead, a regulatory view for the compliance function, and workstream-level recommendations for the operations and product teams.
The goal was a document that a serious reader — not a skimmer — could sit with for an hour and come out understanding the client's situation in a way they hadn't before. That's the bar. That's what the engagement was for.
Wrote an Executive Summary One-Pager
Partway through the engagement, I produced a one-pager of interim findings so Tiffany could pressure-test the direction with the client before the full report finalized. The executive summary is the form factor that boards and executives actually read. Getting it right early was part of the scope — not an afterthought tacked on at the end.
Built a Slide Deck for the Client Presentation
The deck went through two passes. A first draft landed by the start of April. A refined version went out ahead of the on-site client meeting later that month. The slides carried the narrative of the written report into a presentation-ready form — the same argument, compressed and sequenced for a live room.
The 70/30 Split
The explicit design of the engagement was that I would deliver the seventy percent — the read-through, the synthesis, the first draft of the argument, and the supporting evidence — while Tiffany would overlay the final thirty percent. That last thirty percent is where the advisor's judgment, voice, and client-specific knowledge live. It is also the part that cannot be outsourced, because the advisor is the one the client hired.
"You did not want me to just dump ninety documents on you. You wanted that final few-state synthesis... You gave me the output and I could look at it and say, okay, I feel like this is still missing... It was like 70% of the way there. But not what I would present to the client, which I didn't have that expectation that you would deliver 100."
— Tiffany, Principal, Illumea Advisory
Seventy to thirty is the split where both sides do their highest and best work. An advisor who has to rewrite the whole deliverable has not been helped. An advisor who receives raw notes has not been helped either. The design of the engagement has to produce a draft that is usable as a starting point for the advisor's final pass — not a proxy for the advisor's own thinking.
Results
The engagement delivered on three fronts.
The client presentation landed. The team engaged substantively with the analysis — asking questions, pushing on specific claims, and leaving the room with a shared view of where they stood competitively. That's a different bar than "the deck was well-received."
The client's compliance officer committed to reading the full 55-page report. That's the kind of signal that matters. Compliance leads do not commit to reading long documents casually; they commit when the material is worth their time.
The client team learned competitive dynamics they hadn't had full visibility into. Competitive analysis from inside a company is almost always limited by what the team already believes. An outside synthesis of the full document set surfaced market forces and positioning gaps the in-house team had not seen clearly — not because they weren't paying attention, but because no one in-house had eighty uninterrupted hours to read the whole corpus.
Initial internal skepticism dissolved. The first reaction from some of the team was a version of "we do this every day — we already know this." Fair reaction from people closest to the work. It changed once they saw that the synthesis wasn't a restatement of their operational knowledge; it was a different view of the same reality, made visible by the act of holding the whole corpus at once.
"It's not that you don't know the process, it's that the process sucks."
— Tiffany, Principal, Illumea Advisory (reframing the team's reaction)
The advisor got her time back. This is the outcome that matters most. Tiffany's hours in the last week went into the strategic layer — the thirty percent only she could provide, the client relationships only she held, and the framing decisions that defined how the report landed in the room. None of those hours were spent on document reading or first-draft synthesis. That is the division of labor the engagement was designed to produce.
[Tiffany's formal testimonial quote will appear here once provided. The quote is approved; delivery pending.]
Why This Worked
Three things made this engagement effective.
The document corpus was already there. Tiffany had done the hard upstream work — gathering the research, conducting the interviews, pulling the operational data, and building enough relationship with the client that she had access to the inputs. The bottleneck was synthesis, not acquisition. Fixing the bottleneck was the highest-leverage move.
The scope was bounded and specific. Three weeks, four deliverables, a defined split of responsibilities, and a contract that sat under Illumea's existing engagement. No scope creep. No parallel client relationship. No proposal theater. The work had a shape before it started, and both sides stayed inside that shape.
The division of labor respected where the advisor's value actually lives. Tiffany's superpower is the last thirty percent — the strategic framing, the client-specific judgment, the room-reading that turns analysis into advice. The engagement was designed so her hours went there, and mine went into the seventy percent that feeds it. That's the only arrangement that works. Any other split either overruns the advisor's time or produces a report that isn't quite what the advisor would have delivered themselves.
Frequently Asked Questions
Can I engage you without naming my client publicly?
Yes. That's the default. I sign under your existing client contract, deliver to you, and your end client is never named publicly without their explicit consent. This case study itself is an example — the fintech client is referenced only by industry. Most boutique advisor engagements run this way.
What does "synthesis" actually mean?
Reading, cataloguing, cross-referencing, and structuring a document corpus until the patterns, contradictions, and strategic implications become visible. For this engagement, that meant eighty to ninety mixed-provenance documents distilled into a 55-page written report, an executive summary, and a slide deck. Not summaries of each document — synthesis across the whole set.
How long does an engagement like this take?
Three weeks for this one. Timeline scales with document volume, competitor count, and how fresh the analysis needs to be. Most engagements of this shape complete in two to four weeks.
Do you work in regulated industries?
Yes. Financial services, healthcare, and other regulated verticals are where this kind of synthesis matters most. I work under your existing NDA and compliance structure, so the regulated-industry constraints flow through agreements you already have in place.
How much does something like this cost?
Pricing is scoped to the engagement — volume of documents, number of deliverables, and timeline. For this engagement, the scope was three weeks of focused synthesis work with four deliverables. The pre-engagement conversation is where we figure out whether the shape of the work fits your situation, and what the right scope and price look like.
How is this different from hiring a research associate or a VA?
A research associate or a VA can do reading and note-taking, but they need weeks of ramp-up on the landscape, the vocabulary, and the client's specific context before producing anything usable — and even then, they generally can't produce a structured, argument-driven synthesis. This engagement is priced and structured differently because the output is different: a client-ready draft that you tune, not a pile of notes you assemble.
Related Case Studies
- FirstStepsHQ: Website & CRM Pipeline in One Week — A small business engagement where the problem was structural, not cosmetic
- Career as a Platform: Rescuing a Stalled Team at Stride — Another engagement where the fix was about changing the shape of the work, not adding more people to it