An order taken on the visit
Customer, products, quantities and payment terms, at that customer's price list. The order reaches the office ready, with no retyping.
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.
Price lists and a discount cap
A price list per region or customer type, and a maximum discount per rep. Go over the limit and the order goes to the manager for approval.
A portfolio and the day's route
Each rep sees their own customers, with the last purchase and days without an order, and the day's visits in order. Each visit is logged with a time and an outcome.
Targets and commission per rep
The month's target, sales so far and commission calculated on invoiced orders. The rep sees their own number, the manager sees the team.
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 field sales app for a food distributor with six sales reps. Customers with company name, company registration number, address, contact, region, price list and assigned rep; products with code, name, packaging, photo and a price on each price list; a rep sees only their own portfolio, with the last purchase and days without an order for each customer; they take the order on the visit by choosing products and quantities, at the customer's price list, with payment terms and a note, and can give a discount up to their own limit, above which the order waits for the manager's approval; a visit route per day with the order of customers, and each visit logged with the time, outcome and a reason when there was no order; the office receives orders in a queue with the statuses received, approved, invoiced and delivered, and the rep is notified at every change; a monthly target per rep with actual sales and commission calculated on invoiced orders; and a manager dashboard with sales per rep, per region and per product, customers with no purchase in over thirty days and orders awaiting approval.
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.