Off-the-shelf CRMs make assumptions about your process. A custom CRM is built around the records, stages and follow-ups your team really uses, and nothing it doesn’t.
We start by mapping how an enquiry becomes a customer today: where information arrives, who touches it, what gets lost. The system is built around those records and stages, with automations that remove repeated typing, and connected to the tools you keep, such as email, calendars, invoicing or your website forms.
What we deliver
- Customer, company and contact records
- Lead and opportunity pipeline
- Quotes and proposals with PDF output
- Tasks, reminders and activity history
- Roles, permissions and an audit log
- Website form and email integration
- Reporting views
- Data import from spreadsheets or a previous CRM
Technology & implementation
A CRM is an application, not a website. It holds customer data the business depends on, so it needs a proper data model, user accounts with roles and permissions, a record of who changed what, and backups that can be restored.
The architecture depends on the users, the data and the systems the CRM has to connect to. One setup we have built is Next.js and TypeScript with a PostgreSQL database through Supabase, which provides authentication and row-level security, so permissions are enforced in the database itself and not only hidden in the interface. In that setup, quotes are generated as PDFs, website enquiries arrive through a signed webhook, and a background worker handles reminders and scheduled messages.
Important workflows are covered by automated tests, including tests that check one role cannot read another’s data. Personal data is handled with the GDPR and Switzerland’s Federal Act on Data Protection (FADP) in mind: what is stored, for how long, and how a customer’s data is exported or deleted on request.
How the work runs
Process mapping
How enquiries, quotes and customers move through the business today, with the people who do the work.
Data model and prototype
Records, stages and permissions defined, then a clickable prototype of the main screens.
Build in phases
The core pipeline first, then quotes, automations and integrations, each in use before the next.
Migration and rollout
Existing data imported and checked, the team trained, the old tools retired.
Example use
An illustrative scenario, not a description of a completed project.
A specialist service business needs to manage incoming enquiries, customer records, quotations and follow-up tasks in a single workspace.