Everything you need to go from a spreadsheet to working software your team can use. Start at the top if you're new — each section builds on the one before it.
What the platform does, and what you need before you begin.
A spreadsheet. That's it. Excel (.xlsx, .xlsm), a CSV, or a Google Sheet. It does not need to be tidy — merged cells, multiple tabs, blank rows and inconsistent headers are all normal, and the analysis step handles them. You do not need to know how to code, and you do not need to move your data anywhere.
You upload your sheets, pick what kind of tool you want, and describe it in plain English. The AI reads your data's structure, asks a few clarifying questions, then builds a working app. A real engineer checks the result before you rely on it. Most builds finish in a few minutes.
The app reads from and writes back to your sheet. Nothing is migrated into a database you can't see, and you keep working in the spreadsheet if you want to. If someone edits a row in the sheet, the app reflects it.
Upload a sheet, choose a tool, and describe what you need.
Drag a file onto the builder, use the file picker, or connect a Google Sheet through the Google picker. You can attach more than one file to a single build when the tool supports it — useful when your data is split across a leads sheet and a jobs sheet, for example.
Six starting points cover most work: a Website built from your data, a Dashboard with charts and filters, a CRM for contacts and deals, a Project Tracker with a board and timeline, a Form that writes new rows back to Google Sheets, and a Calculator that runs your existing spreadsheet formulas. Forms and Calculators work from a single sheet; the rest accept several.
Write what you actually want, the way you'd explain it to a colleague: "a job tracker my foremen can update from their phones" or "a dashboard of this month's revenue by salesperson". Specifics help — name the columns that matter, say who will use it, and mention anything that should be hidden from them.
Before building, you'll be asked three to five short questions about your data and how you want it to behave — which column is the status, who should see what, whether dates are start or due dates. You can skip them and the build proceeds with sensible defaults, but answering takes a minute and gets you far closer on the first pass.
Getting from a first draft to something your team will actually use.
The first build is a draft. Use Run Again to revise it with extra context rather than starting over — the project keeps its history, so you can see what changed between runs and go back if a revision made something worse.
You can attach a different spreadsheet to an existing project and rebuild against it. This is how you move from a sample export to the real thing, or add a second sheet once you realise the app needs it.
When something is wrong in a way that's hard to describe, message the engineers from inside the builder. They can open the project, look at your sheet's actual structure and fix the mapping. This is the part AI can't do on its own, and it's included rather than an upsell.
Putting the app in front of your team or your customers.
Every finished build gets its own public URL straight away. Share the link, or the QR code, and it works on phones without anyone installing anything.
If the app shouldn't be public, turn on login so only people you authorise can open it. Your customers and crew sign in at a login page of their own — they do not need Love Spreadsheets accounts.
Point a custom domain at a published app by adding a CNAME record with your DNS provider. The setup panel gives you the exact record to create and then waits for it to verify.
Bringing colleagues in, and deciding who can change what.
Invite people by email from Settings → Team. They land in a shared workspace where your projects and files live side by side, instead of everyone building in isolation.
Admins manage the team and billing, editors build and publish, and viewers can look but not change. Roles are enforced everywhere — inviting, publishing and deleting all check them.
Your personal workspace stays separate from any team you join. Use the switcher at the top of the sidebar to move between them; nothing crosses over unless you build it there.