We Write Cards

Generates personalized greeting card text by classifying the occasion type (birthday, condolence, apology, milestone, etc.) and applying occasion-specific prompt templates to an LLM. The system likely uses a taxonomy of card occasions mapped to tone/style guidelines, then injects recipient context (name, relationship, specific details) into the prompt before calling an LLM API. This ensures thematically appropriate messaging rather than generic output.

Accepts recipient metadata (name, relationship to sender, age, interests, shared memories) and injects this data into the message generation prompt to create contextually relevant, personalized output. The system likely maintains a simple recipient profile schema and uses variable substitution or prompt engineering to weave details into the generated message, making each card feel individually crafted rather than mass-produced.

Accepts a CSV or list of multiple recipients and generates personalized messages for all of them in a single operation, likely using batch API calls or queued processing to handle 10-1000+ cards efficiently. The system probably implements rate-limiting awareness, cost optimization (batching requests to reduce API calls), and progress tracking to manage large-scale generation without overwhelming the LLM backend or incurring excessive costs.

Allows users to specify or select the emotional tone (formal, casual, humorous, heartfelt, etc.) and writing style (poetic, straightforward, sentimental, etc.) for generated messages. The system likely maintains a tone/style taxonomy and applies these as additional constraints in the LLM prompt, ensuring that a birthday card for a boss differs stylistically from one for a close friend, even if the occasion is the same.

Automatically detects or suggests the appropriate occasion category (birthday, condolence, apology, congratulations, thank-you, etc.) based on user input or context. The system likely uses keyword matching, NLP classification, or a guided workflow to help users identify the right occasion, ensuring that the subsequent message generation uses the correct tone and template. This prevents users from accidentally selecting 'birthday' when they meant 'condolence'.

Displays generated card messages to users for review and allows inline editing, refinement, or regeneration before the message is finalized. The system likely implements a preview UI with edit capabilities, allowing users to tweak AI-generated text, request alternative versions, or manually adjust tone/personalization. This quality gate prevents users from sending messages they're unhappy with and provides a human-in-the-loop safeguard.

Connects generated card messages to physical printing and shipping services, allowing users to move directly from message generation to printed card production without manual export or external tool switching. The system likely implements API integrations with print-on-demand providers (e.g., Vistaprint, Shutterfly, or custom fulfillment partners) and handles order placement, address validation, and tracking. This closes the gap between digital message creation and physical delivery.

Provides a library of pre-designed card templates (visual layouts, colors, fonts, imagery) that users can select and customize to match the occasion and recipient. The system likely maintains a template database organized by occasion type, allows users to customize colors/fonts/images, and combines the selected design with the generated message for final output. This ensures that the visual presentation matches the emotional tone of the message.

Maintains a model of recipient relationships (friend, family, colleague, mentor, acquaintance, etc.) and uses this context to inform message tone, personalization depth, and occasion appropriateness. The system likely stores or infers relationship type from user input and applies relationship-specific rules to message generation (e.g., formal tone for colleagues, casual for close friends). This ensures that messages feel appropriate to the relationship dynamic.

Maintains a curated library of LLM prompts optimized for each occasion type (birthday, condolence, apology, congratulations, etc.), ensuring that generated messages have appropriate tone, structure, and emotional resonance. The system likely stores templates with placeholders for recipient context, tone modifiers, and relationship type, then injects user data at generation time. This is more sophisticated than generic prompting and ensures consistency across all cards of the same occasion type.