Checklist

Use this checklist to prepare for building your AI application with Empromptu. Thinking through these details beforehand will help you provide better prompts to the Builder and create more successful applications.

Why This Checklist Matters ⏱️ 2 minutes

Better preparation leads to better results:

  • Clearer Builder prompts: More specific requirements produce better applications

  • AI use case: Empromptu AI works best when you are building an app that utilize LLMs such as apps that:

    • Analyze

    • Recommend

    • Classify

    • Summarize

    • and more...

  • Faster development: Less back-and-forth during the clarification process

  • More targeted optimization: Know what success looks like from the start

  • Reduced credit usage: Efficient building with fewer iterations

How to use this checklist:

  1. Complete relevant sections before opening the Builder

  2. Use your answers to craft detailed Builder prompts

  3. Reference during clarification when the Builder asks follow-up questions

  4. Update as requirements evolve during development


🔧 Application Overview

Application Type

What is the high-level purpose or type of application? Select one or more:

  • ☐ Web app

  • ☐ Mobile app

  • ☐ AI agent

  • ☐ Enterprise platform

  • ☐ Internal knowledge base

  • ☐ Task automation system

  • ☐ Customer support chatbot

  • ☐ Compliance monitoring tool

  • ☐ Meeting summarizer

  • ☐ Personalized coaching app

  • ☐ Sales enablement tool

  • ☐ Internal chatbot assistant

  • ☐ A game

Target Users

Who will use this application? Select one or more:

  • ☐ Enterprise teams

  • ☐ B2B companies

  • ☐ Customer Success teams

  • ☐ Marketing teams

  • ☐ Product & Engineering teams

  • ☐ HR & Operations

  • ☐ Sales teams

  • ☐ Finance teams

  • ☐ IT support staff

  • ☐ Executives and leadership

  • ☐ Legal teams

  • ☐ Customer onboarding teams

  • ☐ Support agents

  • ☐ IT security analysts

Additional user details:

  • Primary user role: __________________________________

  • Technical skill level: __________________________________

  • Usage frequency: __________________________________


📥 Input Details

Input Types

What types of inputs will the application accept? Select all that apply:

  • ☐ PDFs / Documents

  • ☐ Emails

  • ☐ Calendar events

  • ☐ Slack messages

  • ☐ APIs

  • ☐ Spreadsheets / CSVs

  • ☐ Internal documentation

  • ☐ Knowledge base articles

  • ☐ CRM data (Salesforce, HubSpot)

  • ☐ Customer engagement data (Planhat, Gainsight)

  • ☐ Text fields / user questions

  • ☐ Meeting transcripts (Zoom, Teams)

  • ☐ Audio files

  • ☐ Video transcripts

  • ☐ Chat logs

  • ☐ Support tickets

  • ☐ Forms and surveys

Input Characteristics

  • Typical input length: ☐ Short (< 100 words) ☐ Medium (100-1000 words) ☐ Long (1000+ words)

  • Input frequency: ☐ Real-time ☐ Hourly ☐ Daily ☐ Weekly ☐ On-demand

  • Input volume: ☐ Low (< 10/day) ☐ Medium (10-100/day) ☐ High (100+/day)

  • Input quality: ☐ Structured ☐ Semi-structured ☐ Unstructured ☐ Mixed

Sample inputs to test with:

  • Example 1: _____________________________________________________

  • Example 2: _____________________________________________________

  • Example 3: _____________________________________________________


🔄 Processing Details

Processing Actions

What should the app do with the inputs? Select all that apply:

  • ☐ Scan and synthesize content

  • ☐ Summarize input

  • ☐ Generate recommendations

  • ☐ Optimize tasks

  • ☐ Manage and automate tasks

  • ☐ Retrieve & augment from knowledge base

  • ☐ Answer natural language questions

  • ☐ Detect insights or trends

  • ☐ Match against internal policies or rules

  • ☐ Trigger actions in third-party tools

  • ☐ Tag or label inputs for classification

  • ☐ Translate or rephrase content

  • ☐ Convert to structured data

  • ☐ Detect sentiment or tone

  • ☐ Extract key information or metrics

  • ☐ Run validations or checks

  • ☐ Rank or prioritize items

Processing Requirements

  • Response time: ☐ Real-time (< 5 seconds) ☐ Fast (< 30 seconds) ☐ Standard (< 2 minutes)

  • Accuracy needs: ☐ High (90%+) ☐ Medium (70-90%) ☐ Acceptable (60-70%)

  • Consistency: ☐ Critical ☐ Important ☐ Nice to have

  • Complex reasoning: ☐ Required ☐ Helpful ☐ Not needed

Special processing rules or constraints: __________________________________________________________________


📤 Output Details

Output Formats

What is the desired output format or result? Select all that apply:

  • ☐ AI-generated recommendations

  • ☐ Actionable tasks

  • ☐ Summarized insights

  • ☐ Reports or dashboards

  • ☐ Slack messages

  • ☐ Pre-filled forms or emails

  • ☐ Knowledge base articles

  • ☐ Internal alerts or notifications

  • ☐ Prioritized task list

  • ☐ Decision-making support notes

  • ☐ Formatted API calls or scripts

  • ☐ Formatted email drafts

  • ☐ Knowledge graph entries

  • ☐ Training datasets

Output Specifications

  • Output length: ☐ Brief (< 100 words) ☐ Medium (100-500 words) ☐ Detailed (500+ words)

  • Tone/style: ☐ Professional ☐ Casual ☐ Technical ☐ Friendly ☐ Formal

  • Structure: ☐ Bullet points ☐ Paragraphs ☐ Tables ☐ JSON ☐ Custom format

  • Language: ☐ English ☐ Multiple languages ☐ Technical jargon ☐ Plain language

Example desired output: __________________________________________________________________


🎯 Success Criteria

Evaluation Planning

Think about how you'll measure success:

  • Accuracy measures: ☐ Factual correctness ☐ Completeness ☐ Relevance ☐ Format compliance

  • Quality measures: ☐ Tone appropriateness ☐ Clarity ☐ Actionability ☐ Usefulness

  • Performance measures: ☐ Speed ☐ Consistency ☐ Reliability ☐ Scalability

Specific success criteria:

  1. __________________________________________________________________

  2. __________________________________________________________________

  3. __________________________________________________________________

Edge Cases to Consider

  • Problematic inputs: _________________________________________________

  • Error scenarios: ___________________________________________________

  • Boundary conditions: _________________________________________________


🔗 Integration & Technical Requirements

System Integrations

  • ☐ CRM systems (Salesforce, HubSpot)

  • ☐ Communication tools (Slack, Teams, Email)

  • ☐ Document storage (Google Drive, SharePoint)

  • ☐ Analytics platforms (Google Analytics, Mixpanel)

  • ☐ Customer support (Zendesk, Intercom)

  • ☐ Project management (Asana, Jira)

  • ☐ Custom APIs or databases

  • ☐ Other: _______________________________________________

Security & Compliance

  • ☐ Data privacy requirements (GDPR, CCPA)

  • ☐ Industry compliance (HIPAA, SOC 2, ISO)

  • ☐ Access controls and authentication

  • ☐ Data retention policies

  • ☐ Audit trail requirements

Scale & Performance

  • Expected users: ☐ < 10 ☐ 10-100 ☐ 100-1000 ☐ 1000+

  • Usage patterns: ☐ Steady ☐ Burst ☐ Seasonal ☐ Growth expected

  • Geographic reach: ☐ Local ☐ National ☐ International


🎨 User Experience & Design

UI/Visual Preferences

  • Design style: ☐ Minimal ☐ Modern ☐ Corporate ☐ Friendly ☐ Technical

  • Color preferences: _________________________________________________

  • Layout preferences: ☐ Single page ☐ Multi-step ☐ Dashboard ☐ Chat interface

User Flow Requirements

  • Authentication needed: ☐ Yes ☐ No

  • User onboarding: ☐ Tutorial ☐ Examples ☐ Self-explanatory

  • Error handling: ☐ Graceful degradation ☐ Clear error messages ☐ Fallback options

Example templates or designs to reference: __________________________________________________________________


📅 Timeline & Priorities

Development Timeline

  • MVP deadline: _____________________________________________________

  • Full launch target: ___________________________________________________

  • Key milestones: ____________________________________________________

Feature Priorities

  • Must-have features: _________________________________________________

  • Nice-to-have features: _______________________________________________

  • Future enhancements: ________________________________________________


👥 Stakeholder Alignment

Decision Makers & Reviewers

  • Primary stakeholder: _________________________________________________

  • Technical reviewer: __________________________________________________

  • End user representative: ______________________________________________

Sign-off Requirements

  • ☐ Functionality approval

  • ☐ Security review

  • ☐ Compliance check

  • ☐ User acceptance testing

  • ☐ Performance validation


✅ Pre-Building Checklist

Before opening the Builder, ensure you have:

  • Clear application purpose and target users identified

  • Sample inputs ready for testing

  • Desired outputs clearly defined

  • Success criteria established

  • Integration requirements understood

  • Stakeholder alignment on core requirements

  • Timeline and priorities defined

Additional preparation:

  • Account setup: Empromptu account active with sufficient credits

  • External accounts: Netlify/GitHub accounts ready if planning to deploy

  • Test data: Realistic inputs prepared for optimization testing

  • Team coordination: Key stakeholders informed and available for review


🚀 Ready to Build?

Once you've completed relevant sections of this checklist:

  1. Open the Builder: Use your preparation to craft detailed prompts

  2. Create your application: Follow the complete workflow

  3. Set up optimization: Use your success criteria for evaluations

  4. Deploy when ready: Choose your deployment method

Pro tip: Keep this checklist handy during Builder conversations - use your answers to provide detailed responses to clarifying questions!

Last updated