Filio
Practice management system for client records, compliance work, and billing.
- Type
- SaaS
- Client
- Practice management product concept
- Role
- Product architecture · Full-stack engineering
- Year
- 2025
Evidence / status
Prototype. Reported outcomes await verification.
Challenge
A fragmented compliance workflow
Client deadlines, service records, and billing information were distributed across shared spreadsheets and communication tools without a dependable source of truth.
Constraints
- Recurring statutory deadlines needed structured ownership.
- Client data required explicit consent and deletion handling.
- Billing needed to connect to completed service work.
- The data model had to support several compliance types.
Approach
Key decisions
Schema before interface
Clients, services, tasks, deadlines, and billing relationships were modelled before interface work began.
Consent included in the data model
Consent purpose and deletion workflows are treated as product records rather than a later policy addition.
Recurring deadline generation
A client service profile determines which compliance tasks should be generated and when.
Billing connected to delivery
Invoice events are tied to service milestones to reduce separate reconciliation work.
Evidence
What can be stated
Current status: Prototype. Unverified outcomes are labelled instead of presented as proof.
Architecture and compliance claims require owner or client verification.
Needs verification
Technology stack
- Next.js
- Supabase
- Drizzle ORM
- Razorpay
Next project
Continue through the work archive.
Start a project
Let's build something great
Drop your details below. We'll have it open in Gmail, ready to send — no copy-pasting.