What happened, and why?
Bring technical uncertainty, alternatives and documented work into one project account.
Engineering evidence. R&D review.
Turn engineering work into evidence you can use.
Understand the work behind your engineering investment. Bring technical records, project context and costs into a review you can inspect and act on.
Start with uploads. No card or sales call required.
Bringing a client? Explore the adviser path Your existing records Sources you can inspect
Initial R&D evidence reviewIllustrative example · fictional records
Software reliability · January–June
Retrieval reliability
Version 1
What the records supportAn approach is documented.
An approach is documented.
The outcome needs more support.
The project notes describe comparing keyword and embedding retrieval for ambiguous queries. Final benchmark results have not been supplied.
- Technical question
- Can the retrieval service return useful evidence when the request is ambiguous?
- Source support
- Repository change reference and experiment-note revision.
- What remains open
- The recorded outcome, evaluation method and connection between supplied AI costs and this project.
Selected repository history+ experiment note
This sample explains the format; it is not a customer result or an available allocation feature. Your review uses supplied records and identifies its preparer. An initial review is not a tax eligibility determination or an approved annual report.
A useful first deliverable
See the work.
Understand its support.
An initial R&D evidence review connects what was attempted, the records behind it and the questions that still need an answer.
What can the records support?
Follow findings back to saved source versions. Keep an unverified outcome visible.
Which costs need explanation?
Review supplied payroll, AI and cloud costs with an explicit method. Missing records stay missing.
Connect the context
The work and the spend
belong in the same conversation.
Use the records you already have. No installation on every employee’s computer.
Engineering work
Selected repository history, issues, project briefs and experiment notes explain what the team worked on.
GitHub · Linear · Jira · GitLabAI and cloud costs
Upload invoices and usage exports alongside project evidence. Establish what a bill covers before assigning it to a project.
Invoices · usage exports · expense recordsPeople and project context
Bring payroll, participation records, decisions and supporting documents for the agreed reporting period.
Uploads · Notion · Google DriveConnections depend on configuration and permitted scope. Uploads can be used on their own.
Explore the inputsFrom records to review
Start small.
Make the evidence useful.
One company, one reporting period, one initial review. Preparation can be manual, with an identified preparer.
- 01
Set the scope
Create your account and agree the company, reporting period and jurisdiction.
- 02
Bring the records
Upload what you have or authorize selected sources. Save exact evidence versions.
- 03
Prepare the review
A preparer examines the records, explains supported findings and identifies gaps.
- 04
Choose the next step
Open the saved review, inspect its references and resolve the next questions with your adviser.
AI assistance in the Proforma Workspace
Put AI to work on
the questions that matter.
Use configured AI to investigate your data and build on the evidence. Keep the questions, source records and methods in view.
Investigate the work
Ask the agent to inspect records, compare supplied experiment outcomes and identify open questions.
Prepare a narrative
Use the Workspace to draft a source-linked account, then review its reasoning and references.
Make the method repeatable
Build SQL Models, Apps and Actions for calculations and investigations you want to run again.
AI and cloud spending
Your AI bill is
only half the story.
Pair invoices and usage exports with the work they supported. A defensible cost account needs project context and a stated allocation method.
“What does this bill cover—and which records connect it to the project?”Bring AI cost records
Your initial review is prepared explicitly. Connecting an account or uploading a bill does not automatically calculate ROI or produce a tax determination.
Two ways to begin
For the team doing the work.
And the people advising them.
Companies
Make your engineering investment easier to explain.
Supply technical and financial records. Get an initial review of the available evidence, gaps and next steps.
Advisers
Bring your method.
Keep your judgment.
Start with one permitted client engagement. Collect its evidence and prepare a review your team can inspect.
Explore the adviser pathKeep the basis of the review visible
Selected access. Exact sources. Explicit preparation.
You choose the records in scope. Saved evidence and published reviews keep their exact versions. An initial review is not a tax eligibility determination or an approved annual report.
Read about access and controlsThe wider Proforma platform
From what if
to what works.
R&D review is a focused place to start. The platform underneath connects data, preserves methods and supports software and analysis you can build on.
Keep the evidence
Versioned Files retain the record and its source history.
Make the method inspectable
Query Data and preserve calculations in SQL Models.
Build on the investigation
Use Apps and configured AI or Actions for useful, repeatable work.
Research & field notes
Make a better case for the work.
Practical research on changing tax rules, engineering evidence and the economics of AI.
U.S. tax changes
Explore the research library What Section 174A changes—and what your records still need to explain.
Read the guide ↗AI & ROIMeasure the work that survives review.
Read the guide ↗Australian R&DTICurrent rules, proposed reforms and the records to prepare.
Read the guide ↗Start with the records you have
Make the work
easier to explain.
Set your scope and take the first step toward an initial R&D evidence review.
“Talk to an advisor” opens an email draft. Follow-up, fees and formal delivery are agreed separately.