Skip to content
One page per company

Master Customer Account Management

Every deal, person, ticket and invoice attached to a company, on one page. Flat, searchable, and honest about what it does not model.

Unlimited accounts and unlimited users. MIT licensed, self-host it anywhere.

The account is the hub

Not because it sits above anything, but because everything else points at it. Open a company and the four things you were going to go looking for are already there.

  • Tabs Deals, people, tickets, invoices Four tabs on the account, each listing the records attached to it. This is what "single view of the customer" actually means here: no hierarchy diagram, just everything that points at this company.
  • Firmographics Industry, headcount, annual revenue Real fields on the record, with a currency on the revenue figure, so filtering by company size or sector works on data rather than on a tag somebody remembered to apply.
  • People Many contacts, and they can be shared Contacts attach to an account through a many-to-many, so a consultant who works with two of your customers appears correctly on both.
How contacts attach to accounts
[ APP.BOTTLECRM.IO/ACCOUNTS/:ID ]
On every account

Fields that are actually fields

Each of these is a real column you can filter and sort on, not a note somebody has to remember to write.

Industry and sector

A classification field on every account, filterable in the list.

Headcount

Employee count as a number, so "under 50 staff" is a filter rather than a guess.

Annual revenue

Stored with its own currency code, not assumed to be dollars.

Website and address

Site URL plus the full postal address: street, city, state, postcode, country.

Owners and teams

Assign an account to several people, or to a whole team.

Custom fields

Text, number, date, dropdown and checkbox, defined per organisation.

Accounts are flat

If you need to model a group structure, this is not the tool for it today. Tags will get you grouping and filtering, and that is the whole of it.

An earlier version of this page claimed hierarchies. It was wrong, and it has been removed rather than relabelled.

  • Parent and subsidiary account hierarchies
  • Account health scoring
  • Churn prediction
  • Engagement or growth indicators
  • Saved views and dynamic segments
  • CSV import or export for accounts
Questions

Account management FAQs

Check the model

Every field named on this page is in accounts/models.py, in the open repository.

How many accounts can I store?

No limit in the software and no per-account price. The bound is the Postgres database you run it on. Because you self-host, capacity is a question about your server rather than about your invoice.

Can I model parent companies and subsidiaries?

No, and an earlier version of this page said otherwise, which was wrong. Accounts are flat: there is no parent field on the record and no way to nest one company under another. If you need to group them, tags work and are filterable. Nesting would be a schema change, and we would rather tell you it is missing than describe a feature you would go looking for.

What does an account actually gather?

Open one and you get four tabs: its deals, its people, its tickets and its invoices. Everything in the CRM that points at that company is reachable from one page, along with notes, comments and file attachments on the account itself.

How do leads become accounts?

Converting a lead creates the account, and an opportunity alongside it if you want one. The conversion is deliberately one-way: the backend will not move a converted lead back, because the account is now the record of truth and two live copies of one customer is how data goes wrong.

Ready to Master Account Management?

No per-account fee, no seat count, no trial clock. Host it yourself, or let MicroPyramid run it.

MIT licensed Unlimited accounts 100% data ownership