CSV upload
Import a file, map the columns to lead fields, and review what matched before anything is written.
Get leads in, work them down, hand the good ones to an account. BottleCRM does that part properly and does not pretend to do the rest.
Unlimited leads, unlimited users. MIT licensed, self-host it anywhere.
Status, rating, source and the date you said you would call back. Filter it, sort it, and the next hour of your day is decided.
No connector marketplace and no scraping. Your own site posts to your own endpoint, or you bring a file.
Import a file, map the columns to lead fields, and review what matched before anything is written.
Build it in Settings, paste the snippet on your site, and what people fill in arrives here as a lead with its owner, source and tags already set. No account for the visitor and no key in your page. A repeat address updates the lead it already has rather than making a second one.
Every field the form collects is a field the REST API accepts, so anything that can make an HTTP request can file a lead.
The full form on web and on the phone, with your custom fields rendered alongside the built-in ones.
Incoming leads are checked against what you already hold, so an import does not quietly double your list.
Marketing automation is a different product. This page used to claim most of it. It does not any more, because none of it was ever in the code.
The source is public. Every claim above can be checked against it.
The lead model, the import and the conversion path are all in the open repository.
No. There is no scoring engine, no behavioural model and no qualification framework. What you get instead is a rating field you set yourself, hot, warm or cold, alongside status, source, industry and any custom fields you add. If a scoring system matters to your process, the API gives you every field you would need to compute one outside the CRM and write it back to a custom field.
Four ways. A CSV upload with column mapping, a public endpoint your own website can post to using your org API key, the create form on web and mobile, and the REST API directly. Whichever route a lead arrives by, duplicate detection runs against your existing records first.
It becomes an account, with an opportunity if you want one, and the lead status is set to converted. That transition is deliberately one-way: the backend refuses to move a converted lead back, because the account it produced is now the record of truth and two live copies of one customer is how data goes wrong.
Yes. Custom fields are defined per organisation, in text, number, date, dropdown and checkbox types. They are filterable in the list, they render in both the web and mobile forms, and they come back through the API, so a field you add is available everywhere rather than only on the screen you added it from.
No per-seat fee, no lead cap, no trial clock. Host it yourself, or let MicroPyramid run it.