Cases with parties, updates and documents
Case number, court, practice area, parties, client and responsible lawyer, with updates logged in order and filings and documents attached to the case.
What gets built
Four things you could have working this week
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
Deadlines and hearings that remind you
Each deadline and hearing has a date, a case and a responsible lawyer, goes on that person's calendar and sends a reminder as far ahead as you choose. What is due today opens the home screen.
Fees and billing
A fee agreement per case, as a flat fee, instalments or contingency, with card payment and a record of what has been paid. The dashboard shows what is outstanding per client.
Client portal
The client signs in with their own account and sees only their cases, the updates you marked as visible and the documents you shared. Internal notes stay hidden.
Included
The parts nobody wants to build twice
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
A real database, not a form dump
Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.
Login for your own users
Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.
Payments that land in your account
Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.
Web, installable, and in the stores
One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.
Found in search, and by the models
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
React code you can take with you
Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.
How it works
From a paragraph to a published app
Three steps, and the second one is the one people do not believe until they watch it.
Start here
A prompt you can paste right now
This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.
Build a system for a law firm with three lawyers and a legal secretary. Individual and business clients with contact details and documents; cases with case number, court, practice area, parties, client and responsible lawyer; updates on each case in date order, each marked as internal or visible to the client; deadlines and hearings with date, time, case and responsible lawyer, on a calendar per lawyer, with an email and push reminder two days before and on the day; team tasks linked to a case, with an owner and a status; fee agreements per case as a flat fee, instalments or a contingency percentage, with card payment and a record of payments received; a client portal where clients see only their own cases, the visible updates and the shared documents; three roles: lawyer, who sees the firm's cases, secretary, who schedules and logs updates without seeing fees, and client; and a dashboard only I can see, with the week's deadlines per lawyer, active cases by practice area, fees receivable and the month's hearings.
Ready to start from
Templates in this category
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.