A CRM that only accepts its own fields sends you back to the spreadsheet

Short text, long text, rich text, number, date, date and time, yes/no, single choice, multiple choice, email, phone, web address, and a reference to a user. The type is not decoration: it decides how it is entered, sorted, filtered, and what automation can do with it. A date stored as text will never trigger anything.

• Thirteen field types, each with its own input
• Choice lists the server is the source of truth for
• Stable internal key, editable display label
• Optional description, for whoever fills it in

An attribute is not reserved for contacts and companies: it can belong to an object you created — a property, a contract, a case, a piece of equipment. Records of those objects then link to anything else through a universal relation engine, with a named meaning and attributes carried by the link itself.

• Attributes of their own on each custom object
• Relations between any two objects
• A named role on the relation: signatory, owner, director
• Handled by segments and automation like everything else

You write the question in plain language — “is this company multi-site?”, “how mature is this prospect?” — and the source of facts to use: the record's own data, its activity, its sales history (deals, quotes, invoices) or your knowledge bases. The answer is typed like the field: a yes/no stays a yes/no, a category stays inside the list.

• Instruction written in plain language, no syntax
• Four sources of facts to choose from
• Answer typed according to the field
• Model and generation date kept

This is the point we would not give up. When the facts do not allow an answer, the property stays empty with an “abstained” status rather than carrying an invented value. And the value is cached on a fingerprint of the prompt and the facts: as long as nothing has changed, no call to the model, so no credits burnt to reproduce the same answer.

• Four states: generated, running, abstained, error
• Cached on a fingerprint of prompt and facts
• Filling is triggered on request, not in the background
• Errors shown with their reason