> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/demo-center/salesforce-alternative-crm.md). # Salesforce Alternative CRM

Try @Human Buy @Human Subscription Join @Human Community

### Salesforce Standard Objects This @Human CRM uses Salesforce Standard Objects to underpin its data model. The vast majority of such [Standard Objects](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_list.htm) can be created/replicated in @Human. ### Headless Data Models in @Human are API-First by design. Any Namespace Application, Module or Field can be reached via API. No additional fees, API tariffs or any such commercial usage tax. ### Basic Overview This model shows a high-level view of the components that go into building a Salesforce CRM Alternative. It also highlights ease with which the system can be created. {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.planetcrust.com/demo-center/salesforce-alternative-crm.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.