You do not need to learn prompt engineering to use Finlay. A strong request simply explains the outcome, the scope, and the format you want.
A practical request pattern
Outcome + scope + important rules + useful format
For example:
Show active investments for the Vienna portfolio, sort by invested amount, and highlight records without a next payment date.
Useful examples
Explore data
Create a report
Import files
Draft a dashboard
- Show all projects with a completion date this quarter.
- Compare planned and actual investment amounts by company.
- Find records with missing owner relationships.
- Create a quarterly report in English for the selected project and include the attached board notes.
- Generate a sustainability report from this agent’s configured source.
- Import the attached supplier list into the selected Data Collection.
- Create a new Data Collection from these onboarding documents.
- Create a private dashboard showing active projects, total investment, and upcoming payments.
- Add a table of overdue receivables to my dashboard draft.
Attachments
Attach Layest files or folders when the request depends on their contents. Finlay includes listed attachments automatically for compatible imports and reports.
Work in steps when the decision matters
Start with a broad view, then refine:
- ask for the relevant records or summary
- check the result and terminology
- narrow the time period or business unit
- request the final report, table, or draft only when the scope is clear
Be explicit about irreversible decisions
Finlay can help prepare work, start supported workflows, and save dashboard drafts. Publishing, approval, payment authorization, and other consequential decisions remain deliberate user actions.
If Finlay cannot identify the correct project, collection, or target, name it exactly as it appears in Layest.
