12:00Use cases
A simple CRM from a description
Contacts, a stage for each one, and a note about the last conversation. Build3 builds that as a private web app. It is the tracker you described, not a clone of a product a large sales team has used for years.
A prompt to start from
A simple CRM for a small agency. Contacts with name, company, phone, and email. Stages: new, talking, proposal, won, lost. A note on each contact.
- No subscription
- Credits do not expire
- A link when you publish
12:00What you get
The pipeline you actually use
Name the fields and the stages. Leave out anything you would not open on a Tuesday.
Your stages, not a template
New, talking, sent, paid. Or lead, viewing, offer, closed. If you can say the stages, they can be the board.
The fields you need
Name, phone, email, what they asked for, the next date to call. Extra fields are easy to add later by asking.
Notes on the person
A box for what was said last. That is the part a spreadsheet makes annoying. Ask for it in the first prompt.
A login, because this is private
A CRM should not be a public page. Accounts and saved contacts use the database unlock, 100 credits once on the project. Say who should be able to sign in.
One board, then another
Start with contacts. Add tasks or a simple invoice list after the board is something you would use. Each of those is another prompt.
A link for the people on the team
Publish it, then share the link with the people who have accounts. Your own domain is optional.
12:00How it works
From a sentence to a link
You describe it, look at the preview, and publish when it is the one you want people to see.
01
Write the stages and the fields
Five stages is plenty. List the columns you would put on a sheet of paper.
02
Add five real contacts
Use the preview. If a field is missing, ask for it before you invent more screens.
03
Turn on accounts and publish
Unlock the database so the contacts are saved behind a login, then publish. The unlock is 100 credits on that project.
12:00Prompts
Start from one of these
Copy the one that is close, change the names, and send it. The button opens a new account. It does not send the prompt for you.
Agency
“A CRM for a design studio. Contacts, the project they want, a budget, and stages from first call to paid. Login required.”
Start buildingProperty
“A tracker for apartment listings. Address, rent, bedrooms, and stages: available, viewing, holding deposit, let.”
Start buildingSchool
“A simple admissions tracker. Student name, parent phone, class applied for, and stages: enquiry, form sent, accepted, enrolled.”
Start buildingFreelance
“A client list for a freelance writer. Name, what they hired me for, the fee, and a note. Stages: lead, in progress, invoiced, paid.”
Start building
12:00Included
What the project comes with
- Contacts with the fields you name
- Stages you define
- A note on each contact
- A preview you can try with sample people
- Logins and saved data after the database unlock
- A private build3.site link when you publish
- More lists later, by asking
- Your own domain after you unlock it
12:00Questions
Before you start
Is this Salesforce?
No. It is a small app shaped like the way you keep track of people. If you need a product’s existing integrations, reports, and marketplace, this is the wrong tool. If you need a board your team will actually open, describe that board.
Will other people on the internet see my contacts?
Ask for a login, and unlock the database before you put real contacts in. Do not publish a CRM that has no sign-in.
How do I pay?
You buy credits and spend them as you build. Nothing renews each month, and unused credits stay on the account. A website prompt needs at least 10 credits on the account before it can start. A game prompt needs at least 15. After that, the charge follows the work, so a small change costs less than starting over.
Can I export the contacts?
Ask for a way to download them. If that control is missing from the first version, ask for it in the same project.
Describe the board.
Stages, fields, and who is allowed to sign in.
Start building