A simple CRM you can build around

A custom CRM is one where the core can change - what an object is, how a stage behaves, what happens between two steps. That is different from a configurable product, where custom fields only decorate the edges of a shape the vendor designed. It is also different from a build from scratch, where you pay to recreate contacts, deals, pipeline and reporting that every CRM on the market already has.

Configuration answers a different question from customisation. Configuration asks: can I store this, and can I automate between the things that already exist? Customisation asks: can the model itself be different? That is the line. Below it, configuration is fine and cheaper. Above it, no amount of configuration reaches, because no custom field represents a rule about when something happens.

The signal is a spreadsheet, not a seat count. Teams do not outgrow a CRM at fifteen users or at fifty - they outgrow it the first time somebody opens a spreadsheet to hold something the CRM cannot hold, and then keeps it open. That spreadsheet is the shape of the gap between your process and your tool, and once it exists the CRM has stopped being the system of record.

No, and confusing the two is why people assume custom means expensive and slow. Building from scratch means paying to recreate contact management, deal tracking, pipeline views, permissions, email sync, search and reporting - the identical 80 per cent every CRM already ships. A custom CRM starts with that foundation working and changes only the parts your business does differently.

Codnity starts you on a free trial and quotes a fixed price once we have seen your process, publishing no number before that. What moves the figure is how many things your process does that no product represents, how messy the data you are leaving behind is, whether your integrations have a public API, and how many people need training. The standard 80 per cent is not where the cost sits, because it is not where your business is different.

Customising is usually cheaper when the gap is a workflow rather than scale, because migration costs more than its licence. A move to a heavier CRM is treated by the industry as a two to three month project, and it buys you a different fixed shape rather than a changeable one. If the thing you need is one or two workflows, changing the CRM you have is the smaller job.

Only within what their APIs and app frameworks allow, which covers integrations and automations but not the core data model. HubSpot, Pipedrive and Zoho are the same shape for every customer. That is not a criticism - it is how software products work, and it is why they can be good and affordable. It does mean the fit you get is the fit they designed.

When your process is standard, which most are. A fixed product is the same shape for every customer, and if nothing about how you sell is unusual, that shape already fits and you should not pay anyone to reshape it. Codnity says so on the call rather than after it. The same applies when you actually need a different category of tool: field service, a support desk, or a full ERP.

Days to weeks per change, because the foundation already exists and only the specific part gets built. That is the practical difference from a build from scratch, which runs to months before anyone uses anything. Your team can be working in the standard CRM while the custom part is still being built, so nobody waits on a months-long implementation before getting value.

You scope the next change, which is the point of a changeable core. The failure mode this design avoids is the one where growing means migrating again: on a fixed product the answer to a new requirement is a feature request or a higher tier, and both are versions of no. Here the answer is a scope and a date.

Contacts, companies and deals export cleanly from every major CRM and import from a CSV or directly. What does not travel is workflow automation, custom properties tied to their objects, sequences, and reporting built on their schema. Codnity does the migration as part of setup rather than handing you a template, and the part that takes real time is attaching historical email to the right contacts.

Data is stored on EU infrastructure and the system is GDPR-compliant. Codnity is an EU software and data engineering company and the data never leaves the EU. You can export contacts, companies, deals and full activity history in a standard format at any time, and anything remaining is deleted on request.