Skip to content
Late Payment ReminderDesign concept

Late Payment Reminder

Business and customer names, invoice number, issue/due dates, amount already paid, total, payment URL and tone. Generate an editable reminder with exact remaining balance. Copy text, download or open the user’s mail client; never send automatically or invent late fees.

A visual concept with a complete implementation prompt. Use the prompt to build the working app.

Published by build.host
Download source + assets

421 words · Complete build specification

BUILD SPECIFICATIONDownload .md

ONE-PAGE TOOL: Late Payment Reminder Build one complete, working single-page utility for a US small business. No signup, dashboard, admin console, account setup or multi-page app. The page follows input → live preview/result → copy, print or download. Optional browser-only draft storage must be clearly labeled with Clear all.

INPUTS, CALCULATIONS AND OUTPUT Business and customer names, invoice number, issue/due dates, amount already paid, total, payment URL and tone. Generate an editable reminder with exact remaining balance. Copy text, download or open the user’s mail client; never send automatically or invent late fees.

ACCEPTANCE EXAMPLE Invoice total 1000 and payments 150 produces $850 outstanding. A future due date uses upcoming-payment wording. A fully paid invoice prevents a late-payment message. Sanitize payment URLs and do not imply successful sending.

US LOCALE Use USD, en-US thousands separators, two-decimal currency outputs, American English and US names (Emily Carter, Jessica Miller, Maple Goods, Oak Supply Co.). Use US addresses, ZIP strings, US Letter printing, inches and pounds when relevant. Dates must be unambiguous; numeric dates use MM/DD/YYYY. All samples are fictional and available through Load example, never mixed into user data. Any tax rates are user-configured examples, not a national rate.

IMPLEMENTATION Use decimal-safe money arithmetic and explicit rounding at the displayed/exported precision. Validate inputs inline, show useful empty/error states, and preserve edits during recalculation. Never fabricate OCR, payment, email, postage, cloud save or export success. Process files locally where possible. No network upload of user files without an explicit user action and destination. Actual downloads must open and contain the displayed totals. If PDF export is implemented through browser print, label it Print / Save as PDF. Do not add unnecessary backend dependencies.

DESIGN Follow the supplied preview composition and palette; translate tiny gallery text to accessible 16px body and labeled controls. Responsive one-page layout, 44px touch targets, keyboard focus, readable contrast, no horizontal overflow. Keep input and output together on desktop; stack them in workflow order on mobile. Use actual product uploads when requested; no stock photos of unrelated people or regional factory imagery.

VERIFY Test the numeric example above, zero/blank/negative inputs, reset, repeated export, keyboard operation and a 390px mobile viewport. Ensure printed pages have no navigation, clipped rows or missing totals. Deliver the working tool and explain only real required integrations.

VISUAL REFERENCE Brand: GENTLE NUDGE. Headline: A reminder, not a hassle.. Composition: letter. Palette: pink. Primary action: Copy reminder. Preview inputs: Customer: Olivia Bennett; Invoice: INV-1042; Outstanding balance: $850. Preview result: READY TO COPY — POLITE · FIRM · FINAL.