# Build brief — a focused alternative to Senja / Testimonial.to

> **Verdict:** Yes, for personal use · **Buildability:** 90/100 · **Category:** Testimonials
> **Source:** https://www.canitbevibecoded.com/testimonial-to
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Senja / Testimonial.to. Verify current pricing and capabilities before acting.

## Context

**Senja / Testimonial.to** — A form, an embed widget, and a wall page. It currently costs $25/mo.

A form, an embed widget, and a wall page. $300/yr for what is essentially a guestbook.

This brief describes a focused, single-operator replacement for the part of Senja / Testimonial.to that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

A focused, single-user version of Senja / Testimonial.to's main workflow.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a testimonial collection and display tool like Senja. Requirements:

- A public /submit page: name, role/company, avatar upload (or auto-fetch from a
  provided URL), star rating, and the testimonial text. Store submissions in SQLite
  with an approved flag defaulting to false.
- An /admin page (basic-auth from .env) listing submissions with approve/delete
  buttons · nothing shows publicly until approved.
- A public /wall page: masonry grid of approved testimonials, clean cards with
  avatar, name, stars, and text. Mobile-friendly, dark mode support.
- An embeddable widget: /embed.js renders the wall into any page via one script
  tag + a div, iframe-free, styled to inherit the host page's font.
- Image uploads resized server-side to 128px avatars, stored on disk.
- Node or Python, single small server, deploy instructions for a VPS.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Video testimonial recording in-browser.
- Imported reviews from other platforms.
- Their widget templates gallery.
- A hosted collection URL that isn't yours.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/testimonial-to