Nerida
Nerida is a modular platform for solo health professionals in Brazil. Psychology is in production, nutrition in beta. Agenda, structured records, native Pix, a financial module that handles Carnê Leão, and meal plans with a public patient link. All of it designed, built, and operated by one person.
- 100+
- Active clients
- 12 days
- Zero to live
- 51+
- Database migrations
Challenge
Brazilian psychologists running solo practices have a few software options, and they all stop at the same place: CRUD over patients and payments. Tools like PsicoManager and Psicoplanner manage the appointment book, but they don't help with the things that actually keep solo psychologists awake: irregular income, the social weight of asking patients to pay, and the tax mess of Receita Saúde and Carnê Leão.
The pattern came up over and over in conversations with psychologists in my circle: people pay late and asking for it feels uncomfortable; income swings make planning impossible; tax season is a frantic Excel reconstruction. Existing tools were built for the appointment side. The financial side was a gap.
Approach
I forked an internal multi-tenant clinical tool I'd been building and rebranded it for the solo market: single persona, no team views, no multi-clinic switcher. From fork to live product took twelve days.
The working rhythm: sprints of one to three days with Claude Code as build partner. I owned product direction, design, copy, and security calls; Claude handled scaffolding, schema migrations, and integration code (Asaas webhooks, Pix, email templates, cron jobs). I wrote a brief, reviewed every diff, shipped, repeated.
A month after launch the product became a platform: a per-clinic module system with row-level security, so the same core serves psychologists in production and nutritionists in beta with different navigation, records, and tools.
Outcome
Nerida runs in production with real paying users: over a hundred active clients. Two plans (R$49 and R$89 monthly, less on annual), 7-day trial, Pix through Asaas.
Live today for psychologists: agenda with reminders, structured records (anamnese, session evolutions, contracts), patient management with CSV import, and the financial module running five tabs: overview, payments, humanized two-step collections, subscriptions, and a fiscal tab that exports Carnê Leão CSV in the exact Receita Federal format. For nutritionists, in beta: anthropometry, meal plan builder with a public real-time patient link, and a 24-hour recall.
The public landing at nerida.com.br ships separately as a static LP with custom motion and a full SEO/AEO setup, and now tells the multi-profession story: psychology and nutrition available, more areas prioritized by demand. Fifty-one migrations in, the schema has survived a launch, a pivot to multi-profession, and a second vertical.
Who I designed for
One persona. Brazilian psychologist running a solo practice: usually 20-50 patients, often working from home, frequently on the CPF tax regime. Not a tech buyer. They want software that disappears and lets them focus on the session.
That single-persona constraint changed every design decision. No team views. No multi-clinic switcher. No role permissions. The product is built around one person, not a workflow team.
The lilac brand and the glass-sphere login both fight the same enemy: clinical software that feels cold and bureaucratic. Nerida is meant to feel calm.
The key decision: the financial module
Competitors stop at "mark this payment as paid." Nerida starts there.
The financial module has five tabs. Overview shows projected end-of-month income, separating confirmed from outstanding. Payments is the listing. Collections runs a humanized two-step charge (cordial first, firm later, opt-in by patient). Subscriptions handles monthly recurring plans. Fiscal exports Carnê Leão CSVs in the exact Receita Federal format, tracks deductible expenses, and estimates IRPF.
Other tools show you what you charged. Nerida shows you what's left, helps you ask for it without discomfort, and handles tax season without an Excel rebuild. That's the gap I kept hearing about in conversations, and it's where the product lives.
What didn't go well
The pivot to a multi-profession platform came early, three weeks after launch, before I had usage data to justify it. The module system is good engineering and it made the nutrition beta possible, but the decision was driven by ambition, not by users asking for it. If nutrition doesn't convert, that month belonged to psychologist-facing features.
The marketing also lagged the product: for about a month the landing page kept telling the single-vertical story while the platform had already moved on. It caught up in late May, but the gap is the honest cost of a one-person company where product, ops, and marketing take turns getting attention.
Selected screens
" Twelve days from fork to live, another month to become a platform. The pace with Claude Code teaches you that the constraint isn't typing speed; it's decision quality. The AI never owned a decision; it owned the keystrokes that came after. "
Norius
→Redesign of an industrial IoT monitoring platform, from discovery to Storybook. 33 component families, 179 stories, a navigable prototype.