TRFlow
Multi-tenant SaaS
An accounting routine that repeats itself, on purpose.
An accounting firm's work is the same set of deadlines every month, multiplied by every client. TRFlow models that work as workflows with their own statuses, generates recurring tasks, collects what it needs from clients through a portal instead of an inbox, and keeps the entire trail auditable.
Stack
front-end
Next.js 02 framework Next.js Two apps in one: the firm's workspace and the client portal. nextjs.org React 03 interface React The board, the task drawer and the collaborative editor. react.dev Tailwind CSS 04 styling Tailwind CSS The interface for both sides, firm and client. tailwindcss.com shadcn/ui 05 design system shadcn/ui The shared component base across both apps. ui.shadcn.com
back-end
integrations
Resend 10 email Resend Scheduled reminders, with every link tracked down to the click. resend.com Pluggy 11 open finance Pluggy Open finance: bank accounts and transactions the firm would otherwise retype. pluggy.ai Stripe 12 payments Stripe Subscriptions and the paid modules attached to them. stripe.com
01 workflow
The routine
Each service becomes a workflow with its own statuses, and recurrence turns the calendar into work already assigned.
- Statuses per workflow
- Recurrence generates the runs
02 collection
The client's side
Documents and answers come in through a portal with forms and requests. Reminders go out automatically, and every response is tracked.
- Scheduled emails, tracked links
- Bank data through open finance
03 record the month closes
Trail
Every change to a task becomes part of its history, and documents record who opened them and when.
- Task history and audit log
- Roles per team and customer