How no-code works (objects, fields and metadata)
Why you can adapt the CRM on your own, without programming, and how to think about that flexibility.
In many systems, changing a record type requires a programmer and a new release. Not here. Objects, fields and values are treated as configuration. When you create or change a field, the system starts displaying it, validating it and including it in forms, lists, the board and exports automatically.
What this means in practice
- Need to store companies' tax IDs? Create a "Tax ID" field and it shows up instantly.
- Does your funnel have different stages? Edit the Stage field's values to match your own phases.
- Want a new object, like "Contracts" or "Properties"? Model it as a custom object.
- Team changed? Create a new access role and define what it sees, object by object.
Example: A real estate agency creates the "Property" object with the fields Address, Area, Price and Status, and starts managing properties in the same CRM, alongside Contacts and Opportunities.
Example: A consulting firm changes the opportunity's "Type" field to contain "Project", "Retainer" and "Training", and the board and reports immediately reflect that reality.
How to approach modeling
- List the "cards" your business uses (objects).
- For each card, list the data you need to store (fields).
- Identify the choice fields (lists) and their values (e.g. Stage, Status, Industry).
- Define who accesses what (roles).
💡 Think first about "what cards do I need?" and "what data does each one have?". The system builds the rest for you: the screens, the validation and the exports.