Brieflet
Client Questionnaire & Brief Platform
The platform I use before every freelance project: I create a project, define its questions, and send the client a public link with a 6-character access code. Answers land in Postgres and read back as a clean brief, exported on demand as .txt or .xlsx, with a Telegram ping on every submission. Whole question sets import from a spreadsheet in a single Postgres transaction, access codes are bcrypt-hashed, failed attempts are rate-limited per IP in the database, and every table runs forced RLS with no client grants — nothing reaches the data without an admin session or a verified code.
- Client
- My own product · used on every freelance project
- Role
- Solo: design, build and operations
The problem
Freelance projects go wrong when requirements live in scattered WhatsApp messages. I needed one place where clients answer structured questions before any work starts.
What I built
- Projects, sections and six question types, shared with the client as a public link and a 6-character access code
- Answers autosave, then read back as a clean brief, exported as .txt or .xlsx
- Whole question sets import from a spreadsheet in a single Postgres transaction
- bcrypt-hashed access codes, per-IP rate limiting in Postgres, and forced RLS with no client grants
- A Telegram ping on every submission
Results
- 6 question types
- bcrypt hashed access codes
- XLSX import & export
- Live in daily use
Stack
- Next.js 15
- TypeScript
- Supabase
- Server Actions
- SheetJS
- Telegram Bot API