Prompts
Send 5 to 10 real prompt examples or prompt-like requests that reflect the actual workflow.
Sample validation
Test the bounded claim on your real material before you buy a pilot.
This path is for buyers who want a concrete answer to one question: does PalmerAI fit the prompts and business documents already in scope? The right validation pack is small, representative, and honest.
What to send
Keep the validation pack bounded and representative.
Documents
Send 5 to 15 representative business documents, ideally across readable docs, scanned PDFs, or mixed PDFs if those are in scope.
Context
Include one short note about the workflow, the intended output, and the main governance concern.
What we check
Workflow fit
Whether the workflow belongs in a posture review first or is already narrow enough for a pilot.
Document fit
Whether the sample documents stay inside PalmerAI's current bounded support path for readable files, scanned PDFs, mixed PDFs, and governed images.
Governance fit
Whether the main need is approvals, inspectability, evidence, or a more basic workflow boundary decision.
What you get back
Validation outcome
- Fit / partial fit / out-of-scope recommendation
- Readable docs versus scanned/mixed path assessment
- Likely approval and evidence pattern
- Main bounded-support notes
Next-step recommendation
- Posture review first
- Narrow workflow pilot
- Partner conversation
- Pricing lane if already clear
How to keep it useful
Do send
- Representative prompts and files
- Real document shapes
- Scanned samples if scanned work is in scope
- One short workflow description
Do not send
- Huge random document dumps
- Every file type the company owns
- Material outside the intended workflow
- Content you are not allowed to share
Start with a bounded pack.
The fastest path is one small representative sample pack, not a broad promise about every possible document case.