FormsCAN I VIBECODE
Alchemer?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Alchemer (formerly SurveyGizmo) is a no-code survey and feedback platform aimed at business teams. It supports 43 question types, branching logic, piping/merge codes, custom themes, dynamic content, and multi-language surveys. Distribution channels include email, SMS, QR codes, shared links, quick polls, and video responses. The broader Business Platform adds in-app feedback, bi-directional integrations with 400+ systems, automated workflows, and Pulse, an AI tool that analyzes open-text feedback. Alchemer emphasizes security and compliance: SOC 2 Type II, GDPR, HIPAA and FERPA compliance, end-to-end encryption, data residency/isolation, and identity access management. It positions itself as easy to adopt without IT support, scaling from one-off surveys to enterprise feedback programs.
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused replacement for Alchemer (formerly SurveyGizmo), a no-code survey platform. The core workflow: an admin creates a survey in a drag-and-drop builder, configures per-question logic and piping, chooses one or more delivery channels, publishes, monitors real-time responses in a dashboard, and exports or pushes results via integrations. Do not copy Alchemer's brand, logo, color scheme, or UI layout; create an original, clean interface.
User-facing requirements: (1) Survey builder with at least 20 question types (text, multiple choice, rating, dropdown, ranking, matrix, image choice, date, etc.), drag-and-drop reordering, and live preview. (2) Branching/skip logic with simple condition builder; piping (inject earlier answers into later question text/labels); merge codes for respondent/URL parameters. (3) Custom theme: brand colors, logo, fonts, CSS override. (4) Delivery: generated shareable link + QR code, email invite with tokenized link, SMS link, and embeddable iframe. (5) Respondent experience: mobile-responsive, progress bar (optional), back/next navigation, validation, and thank-you/screen-out messages. (6) Results dashboard: per-survey response list, aggregate charts, filters, export to CSV/JSON, and webhook delivery on new response. (7) Basic auth for admin accounts; respondents do not need accounts.
Technical requirements: choose a stack suitable for a solo or small team — e.g., React/Next.js frontend, Node.js or Python backend, PostgreSQL with JSONB for survey definitions and responses. Implement a branching evaluator that walks the question tree, a template renderer for merge codes, and pluggable delivery adapters (web link, email, SMS) so new channels can be added. Store responses opaquely but include timestamps, submission IDs, and channel/source metadata. Include an API for creating surveys and pulling responses. Implement encryption at rest (DB) and in transit (TLS), plus row-level tenant isolation if multi-user.
Out of scope: in-app/mobile SDKs, AI text analytics (Pulse-like features), enterprise compliance certifications (SOC 2/HIPAA/FERPA), multi-language survey authoring, A/B testing, and a full report builder — a basic chart view suffices.
Deliver a runnable project with migrations, seed demo survey, and a README covering setup, architecture, and known limitations (e.g., no offline mode, no real-time collaboration, limited webhook retries).