A pitch deck can be easy to skim and difficult to question precisely. OGAD (Off Grid AI Desktop) can help you find statements in a deck, compare them with supporting notes, and prepare a source-backed question list. Select a local model to work on your computer without uploading the material to a cloud AI service. The result is research preparation, not an investment recommendation.
| Download OGAD | Desktop releases |
What would you like to do with Off Grid AI?
Want help with this workflow, or a feature you would like us to add? Email support@offgridmobileai.co with your devices and the task you want to improve.
Start with the decision you need to prepare for
You may be deciding what to ask in a first meeting, what evidence to request, or which claims need a closer review. Those are useful tasks for a local document assistant. Asking whether a company is “a good investment” is much harder to ground in a deck alone.
Suppose a small investment team receives a deck that describes customer growth, a new product, and a planned expansion. You want to know which figures are historical, which are forecasts, and which statements have supporting detail.
The first useful output is a claim table. It should preserve what the company says without treating the deck as independent verification.
Prepare the source material carefully
Use the current deck and any supporting documents you are authorised to review. Record the version and date. If the founder supplied an updated financial note, keep that separate from the deck and label it clearly.
A deck often contains charts, screenshots, and text embedded in images. For the document-search workflow, use a text-based PDF or an approved text export. Inspect the slides yourself to identify information that the text extract may omit.
The desktop extractor reads PDF text. It does not guarantee that a chart’s axes, legend, or visual relationships are represented correctly. Keep the original deck open for those checks.
Create a company-specific local project
Install OGAD and download a local text model that fits your computer. Complete local search setup and a test import while connected. Projects and document chat are core features; this task does not require background capture.
- Choose a downloaded local model in Models > Text.
- Open Projects > New project and name it for the company and review date.
- In Knowledge & settings > Knowledge base, select Add files.
- Import the deck’s readable text and supporting documents, then wait for indexing.
- Enable the sources relevant to this review.
- If Include captured memory is available, turn it off for the source-only task and save.
- Start Chats > New chat inside the project.
Separate projects help keep company context distinct. They are not a substitute for access controls or the handling terms under which the documents were shared.
Ask what the deck actually claims
Use a focused first request:
List the deck’s explicit claims about the product, customer traction, revenue, and planned expansion. For each, give the source filename and supporting passage. Separate historical figures, current statements, forecasts, and goals. Mark information that is not established by the retrieved text. Do not assess investment attractiveness.
Check the answer against the original slides. If the model describes a forecast as current revenue, correct it before continuing.
A useful working table is:
| Claim | Status in the source | What to verify |
|---|---|---|
| Customer count | Current or historical | Definition and measurement date |
| Revenue figure | Actual or forecast | Period, currency, and basis |
| Product capability | Released or planned | What is available now |
| Expansion plan | Intention or committed activity | Dependencies and assumptions |
These categories help structure review. They do not establish that any claim is accurate.
Examine definitions before comparing numbers
Two figures may use different definitions. A deck may distinguish registered users from paying customers, bookings from revenue, or a monthly figure from an annualised one.
Ask:
Identify the definitions attached to these figures. Show the period, unit, currency, and any qualification in the source. If a definition is absent, list a question rather than assuming one.
Check arithmetic with a spreadsheet or calculator. Do not rely on a language model to validate financial statements or recreate missing calculations.
If a chart and a text statement appear inconsistent, inspect both in the original and ask the company to clarify. The model should not choose the more favourable interpretation.
Turn uncertainties into meeting questions
Once you have reviewed the claim table, ask:
Draft questions for a founder meeting from these unresolved items. Keep each question tied to a specific claim. Separate a request for a definition, a request for supporting evidence, and a question about future assumptions. Do not add accusations or imply that an unsupported claim is false.
For the fictional expansion example, you might ask which resources the plan assumes and what must happen before the new market launch. That is more useful than a generic request to “explain the growth strategy.”
Keep the list short enough for the meeting. Prioritise the questions that affect your next research step, using your own judgment.
Compare supporting documents without merging their authority
If you add a financial note or meeting summary, ask the model to name the source of each statement. A founder’s answer can clarify a deck claim, but it is still a statement that may require evidence.
Use a table with the deck claim, supporting note, agreement or difference, and remaining question. Preserve dates. An updated figure may reflect a later reporting period rather than a contradiction.
For long documents, review one topic at a time. Project retrieval selects passages within a context limit; it is not a complete due-diligence process.
Prepare a neutral internal research note
Paste the checked findings and ask for a short note:
Summarise what the supplied material establishes, what it claims without supporting detail, and what we still need to ask. Keep facts, company statements, and our questions separate. Do not recommend a valuation, transaction, or investment decision.
Review names, figures, and quotations before sharing the note internally. Keep confidential material within your permitted process. Remote models, external tools, and device sync have separate data flows from local inference.
Try a narrow first review
Download OGAD and start with one deck and one topic, such as how the company defines its customer count. Find the relevant statements, check the slides, and prepare two useful questions. That gives your next conversation a clearer basis without treating generated prose as investment analysis.