Skip to content
Conviction Studio
Services-Led Enablement

Start with the deliverable, not the technology.

We choose one recurring document or review process, map how your team produces it, build the first working version, train the users, and support adoption.

No large transformation programme.No generic chatbot handoff.One workflow at a time.
10-Day Core Build Sprint

The 10-Day Core Build Sprint

A typical engagement lasts approximately 4–6 weeks and includes a focused 10-working-day build sprint. Discovery, data access, review cycles, training, and handover make the complete engagement approximately 4–6 weeks.

Days 1–2Step 01

1. Discover

We learn the last real occurrence of the workflow: preparer, reviewer, sources, bottlenecks, and timing.

Days 3–4Step 02

2. Map

We document the current process, templates, approved sources, data boundaries, and acceptance criteria.

Days 5–7Step 03

3. Build

We create the first working version around the firm's actual deliverable.

Days 8–9Step 04

4. Verify

The team reviews the source trail, output quality, exceptions, and unresolved judgment areas.

Day 10Step 05

5. Train

We train users and workflow owners to run, review, challenge, and update the process.

HandoverStep 06

6. Handover

We provide the agreed workflow documentation, operating guidance, and next-step recommendations.

Discover → Map → Build → Verify → Train → Handover

Investment research & monitoring workflows

4 Sprint Templates

Earnings update sprint

Review Pack (.html)
01
Deliverable
A post-results research review covering reported figures, KPI movements, management commentary, thesis changes, and PM questions.
Typical context and sources
  • Prior thesis
  • Model
  • Earnings release
  • Filing
  • Transcript
  • Consensus export
  • Peer commentary
Human review point
Reported facts versus interpretation, estimate changes, and thesis implications.
Enablement outcome
The team can repeat the process each quarter and adapt the workflow as coverage needs change.

Transcript review sprint

Word (.docx)
02
Deliverable
A structured account of what management emphasized, changed, avoided, or left unresolved.
Typical context and sources
  • Prior transcripts
  • Topic watchlist
  • Thesis debates
  • Current transcript
  • Peer commentary
Human review point
Language change, materiality, and interpretation.
Enablement outcome
The team learns to maintain the topics, comparison logic, and follow-up questions.

Company or sector primer sprint

Word (.docx)
03
Deliverable
A comprehensive, sourced primer covering business model, industry dynamics, financials, and key debates.
Typical context and sources
  • Filings & 10-K
  • Industry research
  • Financial model
  • Management transcripts
  • Web research
Human review point
Factual backing, competitive dynamics, and assumption rigor.
Enablement outcome
The team learns to generate and update coverage primers as new filings appear.

Thesis tracking sprint

Word (.docx)
04
Deliverable
A living record of the investment case, evidence, risks, open questions, and changes over time.
Typical context and sources
  • Prior memos
  • Model notes
  • PM comments
  • Filings
  • Transcripts
  • Public sources
Human review point
What strengthened, weakened, or remains unresolved.
Enablement outcome
The team can maintain the thesis record as part of its normal research process.

Transactions & diligence workflows

4 Sprint Templates

Investment committee memo sprint

Word (.docx)
05
Deliverable
A first-pass investment memo in the firm's format, supported by a source and review trail.
Typical context and sources
  • IC template
  • Investment checklist
  • CIM / Teaser
  • Operating model
  • Diligence notes
  • Licensed data
Human review point
Evidence quality, risk framing, unresolved diligence, and judgment areas.
Enablement outcome
The team learns how to run the workflow, inspect sources, update the memo, and maintain its review rules.

Diligence tracker sprint

Excel (.xlsx)
06
Deliverable
A structured record of documents, findings, unresolved questions, ownership, and escalation points.
Typical context and sources
  • Data room
  • Diligence request list
  • Q&A log
  • Financial files
  • Reviewer notes
Human review point
Missing evidence, inconsistent findings, unresolved risks, and ownership.
Enablement outcome
The team learns to maintain the tracker and adjust its review rules for future deals.

Market map sprint

PowerPoint (.pptx)
07
Deliverable
A sourced map of companies, competitors, buyers, segments, or investment themes.
Typical context and sources
  • Search criteria
  • Licensed datasets
  • Company websites
  • Filings
  • Industry reports
Human review point
Coverage quality, classification, source reliability, and missing entities.
Enablement outcome
The team can refresh the market map as new companies and sources appear.

Pitchbook or transaction-material sprint

PowerPoint (.pptx)
08
Deliverable
A first-pass pitchbook or transaction materials in the firm's format, with sourced figures and a review trail.
Typical context and sources
  • Firm template
  • Transaction materials
  • Model
  • Valuation comps
  • Public sources
Human review point
Figure accuracy, narrative consistency, source backing, and judgment areas.
Enablement outcome
The team learns to produce, inspect, and update the materials for future transactions.

Portfolio & client communication workflows

4 Sprint Templates

Portfolio review pack sprint

Excel (.xlsx)
09
Deliverable
A consistent monthly or quarterly review pack covering holdings, KPIs, risks, thesis changes, and action items.
Typical context and sources
  • Portfolio template
  • Prior review
  • Company updates
  • Benchmark feeds
  • Risk model
Human review point
Risk flags, thesis breaks, and required action.
Enablement outcome
The team can rerun and maintain the review process each period.

Investment proposal sprint

Word (.docx)
10
Deliverable
A tailored investment proposal pack matching client IPS constraints, target asset allocation, and house strategy.
Typical context and sources
  • Client IPS
  • Model portfolio
  • Asset allocation model
  • Manager research notes
Human review point
IPS compliance, risk tolerance alignment, and fee disclosures.
Enablement outcome
The team learns to generate customized proposals while maintaining compliance controls.

Manager research note sprint

Word (.docx)
11
Deliverable
A structured diligence note evaluating fund performance, strategy drift, key person risk, and portfolio fit.
Typical context and sources
  • Manager deck & DDQ
  • Performance history
  • Holdings analysis
  • IC interview notes
Human review point
Performance attribution, fee structure, and strategy consistency.
Enablement outcome
The team learns to maintain a standardized manager research library.

Client commentary sprint

Word (.docx)
12
Deliverable
A quarterly market and portfolio commentary connecting macro developments to portfolio performance.
Typical context and sources
  • Macro data & research
  • Portfolio returns
  • Asset class commentary
  • CIO house view
Human review point
Narrative clarity, accuracy of return figures, and alignment with house view.
Enablement outcome
The team can efficiently produce client communications across strategies.
Visual Transformation

Traditional Copy-Paste vs. Conviction Studio Sprint

✕

Traditional Manual Workflow

  • 12+ Open Windows: Analysts manually copy figures across models, SEC filings, transcripts, and Word documents.
  • Invisible Lineage: Numbers in the final memo lack cell addresses—reviewers must open Excel to check formulas.
  • Papered-Over Gaps: Unsupported, stale, or incorrectly transferred figures pass into senior review unnoticed.
✓

Conviction Studio Enablement

  • Native Office Outputs: Drafts arrive directly in your firm’s Word (.docx) and Excel (.xlsx) templates.
  • Inspectable Evidence: Excel-sourced figures ($48.2m) are verified against model cells (`RevenueBuild!C8`); other references cite document sections and pages.
  • Reviewer Sign-Off: Unsourced figures are flagged in a review checklist before senior sign-off.

Which deliverable consumes more time than it should?

Tell us which one. We'll map the process, build the first working version, and train your team to run it.

Discuss a workflow