Agreed access boundaries
Define who can access which information and how it may be handled before implementation.
Purpose-built software for financial and advisory firms
Software built around the way your firm works.
We build and manage private software for boutique banks, private equity firms, and advisory teams whose work runs through complex files. It fits the folders, rules, and review process your team already knows.
From the first working version through the changes that follow.
Company A / Deal materials
Company_A_CIM.pdfFY2025 · Selected source01
Company_A_CIM_v2.pdfSame period, unconfirmed version?
Company_A_QoE.pdfFY2025 · Adjusted earnings03
Operating_model.xlsxFinancials worksheet04
CIM · p. 24 → Financials!F12
Deal review workbookFY2025 · USD m
Financials!F12FY2025 · USD millions · Source attached
One discrepancy held for reviewAdjusted earnings need the team’s judgment.
Built around
specialist work
- Boutique & middle-market investment banks
- Independent private equity
- Valuation & transaction advisory
- Specialist professional services
Inside the workflow
There is a lot of context
inside a client folder.
A figure becomes useful once you know which entity, period, and version it refers to. We build those checks into the workflow, alongside the output and review process your team needs.
Find documents across years of engagement folders, with the original location and uncertain versions in view.
Explore this workflowDocument registerCompany A · FY2025
Find in approved folders
Engagements / Company A
02_Financials
Company_A_CIM.pdf↗
FY2025_statements.pdf
Received / Sept
Company_A_CIM_v2.pdf↗
Operating_model.xlsx
Archive / FY2024
Company_A_CIM_2024.pdf
2 relevant sources
Company_A_CIM.pdf
Source selectedVersion unconfirmed
CIM_v2 identifies the same year. Its name alone does not establish which version to use.
Inspect original-file references
Illustrative paths. Authoritative files stay in place.
/Engagements/Company_A/02_Financials/Company_A_CIM.pdf
/Engagements/Company_A/Received/Sept/Company_A_CIM_v2.pdf
/Engagements/Company_A/02_Financials/FY2025_statements.pdf
Original files stay in placeAccess boundaries agreed with your team
Bring the figures into your deal template and keep the supporting pages close enough to check.
Explore this workflowCompany ADeal workbook
Your deal review template
CIM, page 24Revenue · 84.2
Your templateFinancials!F12
| Requested field | FY2025 | Source |
|---|---|---|
| Revenue | 84.2 | CIM · p. 24 |
| Reported EBITDA | 12.6 | CIM · p. 25 |
| Adjusted EBITDA | Review | QoE · p. 18 |
Adjusted EBITDA is held for reviewConflicting adjustment totals. No value accepted.
Each mapped field keeps its reporting period, units, and source reference in the workbook.
Selected sources, with locations
- Revenue · 84.2
- Company_A_CIM.pdf · p. 24
- Reported EBITDA · 12.6
- Company_A_CIM.pdf · p. 25
- Adjusted EBITDA · 14.1 / 13.8
- Company_A_QoE.pdf · p. 18
Operating_model.xlsx · Financials!F18
CIM_v2 remains unconfirmed in the document register. It does not silently replace the selected source.
Confirm the adjustment bridge
Reported EBITDAAdjustments to confirm
QoE14.1
Model13.8
12.6 reported + 1.5 / 1.2 in adjustments. The bridge needs confirmation.
QoE · p. 1814.1
Model · Financials!F1813.8
QoE reports adjusted EBITDA of 14.1; the operating model shows 13.8. Confirm the adjustment bridge before using either figure.
Awaiting professional review. Neither figure is accepted into the workbook.
Compare company submissions in a consistent format while missing reports and unit differences stay visible.
Explore this workflowQuarterly portfolio reportingRevenue · USD millions
What changed this quarter?
Q1 2026Q2 2026
Company A / Q2 2026
Revenue increased from 20.4 to 21.8 USD million. Both periods are attached for the reviewer to check.
Company_A_Q1_2026.pdf · p. 3 / Company_A_Q2_2026.pdf · p. 3Inspect source references
- Company_A_Q1_2026.pdf · p. 3 / Company_A_Q2_2026.pdf · p. 3. Revenue increased from 20.4 to 21.8 USD million. Both periods are attached for the reviewer to check.
- Company_B_Q1_2026.xlsx · Summary!B8 / Company_B_Q2_2026.xlsx · Summary!B8. The Q2 submission reports 10,200 in USD thousands. The workbook uses USD millions, so conversion is held for confirmation.
- Company_C_Q1_2026.pdf · p. 2 / Q2 source not received. The Q2 submission has not been received. The previous period remains visible; no new revenue figure is filled in.
Draft reporting outputProfessional sign-off required
Connect the request list to the files received, so the team can see what is still outstanding.
Explore this workflowDiligence request trackerCompany A · Proposed updates
Request 01 / Received
The file matches the requested year. A proposed “received” status records delivery; the team still reviews the substance.
Prepared for reviewNo external messages sent
Illustrative examples of systems we could scope with your team. Each engagement is purpose-built.
Purpose-built software. Managed end to end.
We stay with the software
as your work changes.
A useful system needs attention after launch. When a reporting template changes or a new document format arrives, we maintain and improve the agreed software with your team. The scope stays clear, and professional judgment stays with you.
01 / UnderstandMap the actual process
Files, review points, and the output your team needs.
02 / BuildValidate a working pilot
Representative documents, unusual cases, and agreed criteria.
03 / MaintainKeep the system useful
Integration, support, and improvements within the agreed scope.
An example after launch
The quarterly template is mapped to the company reports.
TemplateRevenue + EBITDA
Software mappingAgreed fields mapped
ReviewCheck sourced output
Built into the engagement
You should be able to see
where an answer came from.
We define access, data handling, and review requirements with your team before implementation.
That means deciding which information the software may use, how results reach the team, and where a person needs to check them.
Results with sources
Design outputs so reviewers can trace a figure to its file, period, and source location.
Exceptions in view
Make missing information and conflicting figures visible at the point of review.
A useful handoff
Fit the output to the team’s templates and tools, with professional sign-off built into the process.
Let’s look at the work
What does your team
keep doing by hand?
Tell us where the files come from and what you need at the other end. We can work through what a useful first version would look like.