proofpage

byClaudette Schomburg

Build a production-ready SaaS web application named ProofPage. PRODUCT PURPOSE ProofPage helps independent consultants, freelancers, coaches, and small agencies collect strong client testimonials through a branded link and display approved testimonials on a public proof page and embeddable website widget. The application must be original. Do not copy the visual design, written content, branding, source code, or proprietary assets of Testimonial.to, Senja, Famewall, or any other competitor. TECH STACK Frontend: - Next.js App Router - React - TypeScript - Tailwind CSS - Accessible component library Backend: - Next.js server actions or FastAPI - PostgreSQL - Secure ORM - REST API where appropriate Services: - Stripe for subscriptions - Resend for transactional email - OpenAI API for testimonial polishing - S3-compatible storage for customer headshots USER ROLES 1. Business owner 2. Testimonial submitter, who does not need an account 3. Administrator CORE WORKFLOW 1. A business owner creates an account. 2. The owner creates a branded testimonial collection page. 3. The system produces a public shareable URL. 4. A client opens the URL without signing in. 5. The client enters: - Name - Email - Job title - Company - Headshot, optional - Website or LinkedIn URL, optional - Answer to “What problem were you experiencing?” - Answer to “What changed after working together?” - Answer to “What result did you receive?” 6. The AI combines the answers into a concise testimonial. 7. The client reviews and edits the generated testimonial. 8. The client must explicitly approve publication. 9. The business owner receives an email notification. 10. The owner approves, rejects, edits, tags, or archives the testimonial. 11. Approved testimonials can appear on a public Wall of Proof. 12. The owner can generate an embeddable testimonial widget. AI RULES - Never invent results, numbers, companies, quotations, or facts. - Preserve the submitter’s intended meaning. - Do not exaggerate claims. - Label AI-edited text as a draft until the client approves it. - Ask one follow-up question when the answers are too vague. - Do not generate discriminatory, defamatory, or deceptive content. - Store the original answers and approved version separately. DATABASE TABLES - users - organizations - subscriptions - collection_pages - testimonial_requests - testimonial_submissions - testimonial_answers - testimonial_versions - publication_consents - testimonials - tags - testimonial_tags - widget_settings - ai_usage - audit_logs REQUIRED PAGES Marketing: - Home - Features - Pricing - Privacy - Terms - Login - Signup Application: - Dashboard - Collection page editor - Testimonial library - Testimonial detail - Wall of Proof editor - Widget editor - Billing - Account settings Public: - Testimonial submission form - Testimonial approval screen - Public Wall of Proof - Embeddable widget endpoint SUBSCRIPTION PLANS Free: - Five published testimonials - One collection page - ProofPage branding - No AI Proof Packs Solo: - $19 monthly - Unlimited text testimonials - One collection page - Branding removal Pro: - $39 monthly - Everything in Solo - AI Proof Packs - Custom colors - Embeddable widget Studio: - $79 monthly - Five workspaces - Client management - Everything in Pro ACCESSIBILITY - Meet WCAG 2.2 AA practices - Full keyboard navigation - Semantic HTML - Visible form labels - Clear focus indicators - Screen-reader status announcements - Sufficient color contrast - Error messages connected to form fields - Never communicate status through color alone SECURITY AND PRIVACY - Validate all server-side inputs - Apply rate limiting to public forms - Protect against spam - Require explicit publication consent - Allow testimonial withdrawal requests - Never publicly display the submitter’s email - Sanitize all public content - Protect organization data using tenant-level authorization - Record important actions in audit logs - Do not use submitted testimonials to train models ADMIN FEATURES - View users - View subscriptions - Review reported testimonials - Suspend abusive accounts - Inspect AI usage - View basic application health Generate: 1. Product requirements 2. Database schema 3. Architecture 4. User flows 5. Implementation tasks 6. Automated tests 7. Production application 8. Deployment configuration Build the smallest reliable version first. Do not add features outside this specification.