A productive discovery call depends on having the right context shared in advance. The checklist below covers the materials we typically ask for, by engagement type. If your situation does not fit cleanly into one of these, share whatever you have — we will work with what is available.
Originals stay with you. We never need direct access to your accounts, codebases, or production systems before the engagement is signed — only descriptions, screenshots, or anonymized samples.
AI Consulting
The workflow you are evaluating AI for, in 5–10 sentences
Current cost / time spent on that workflow per month
Volume estimates (requests / day, documents / month, users)
Any AI tools you have already tried, and what worked or did not
The decision criteria you would use to call the project a success
AI Integration
The system the AI integrates into (CRM, ERP, internal tool)
Sample data the AI would read or write (anonymized OK)
Existing API documentation if the system has one
Latency, accuracy, and cost ceilings you are comfortable with
Who would maintain the integration after launch
Custom Software
The business problem the software solves, end to end
Who uses the software (internal staff, customers, vendors)
Any existing system the new software replaces or augments
Approximate user count and growth expectations
Hard constraints (specific cloud, specific stack, regulatory)
Web Applications
The user journey the app supports, step by step
Authentication needs (none, email/password, SSO, government ID)
Payment integration needs (PayMongo, Stripe, etc.)
Performance targets (page-load time, supported devices)
Brand or design assets if any exist
AI Deployment & Operations
Existing prototype repo or working demo URL
Current infrastructure (cloud, hosting, third-party services)
Expected production load (peak requests / second, daily volume)
Budget ceiling for inference + infrastructure per month
On-call / incident-response expectations
Technical Consulting
Repository access for the audit window (read-only is fine)
The specific question or risk we should focus on
Names and roles of the engineers we would talk to
Any prior architecture documents, ADRs, or postmortems
The decision the audit informs (a rewrite? a hire? a migration?)
Ongoing Support
The system to maintain (URL, repo, infrastructure)
Existing monitoring and alerting (or “we have none”)
Recent incidents that would have been prevented by maintenance
Decision-making authority (who can approve fixes, who reviews)
Expected hours of work per month and response-time tolerance
For any engagement, share:
A short written description of the problem — even a half-page is helpfulThe decision-makers — names and roles of who approves scope, budget, and changes (so we are talking to the right people)Hard constraints — regulatory, contractual, geographic, or cost-relatedThe deadline that matters — and why it matters
If documentation is missing, that is fine. The discovery call exists in part to ask the questions and produce the missing context. Bring what you have, and we will work out the rest.
After reviewing this checklist, contact us to schedule your discovery call.