A catalogue with filters people actually use
Type, area, bedrooms, parking, price range, sale or rent, with a photo gallery and a map. A sold property leaves the site by changing one field.
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.
A lead attached to the property
Whoever fills the form enters the pipeline already carrying the property they were viewing, which is the difference between a contact and an opportunity.
Viewings booked, not arranged
The interested party picks a slot in the responsible agent's calendar, and both sides get a confirmation and a reminder.
A pipeline per agent
Your own stages, tasks with dates, and each agent seeing only their own opportunities. The manager sees everything, with conversion per stage and per person.
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 an app for an estate agency. Properties with type, sale or rent, area, address, size, bedrooms, bathrooms, parking spaces, price, service charge, photo gallery, description and a status of available, reserved or sold; a public search with filters by type, area, price range and bedrooms, and each property with its own page written to be found by search engines; an enquiry form on every property that creates a lead already linked to it; agents with their own sign-up, each seeing only their own leads and properties; viewing appointments in the responsible agent's calendar, with confirmation and reminder for both sides; a pipeline with the stages contact, viewing booked, viewing done, offer and closed, with tasks and follow-up dates; and a manager's dashboard with leads by source, conversion per stage and per agent, and the most viewed properties.
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.