A custom CRM, as a subscription

Not a form with sixty questions but a conversation: typing or speaking through the microphone, you tell about your business, the processes, the roles, the data you keep and the integrations you need. You can pause and pick it up later; what you fill in stays.

The chat makes no promises about features, prices or lead times. That conversation you have with Pascal, and there is a button for it in the intake.

Two things come out of the chat. Pascal receives a structured requirements document to build from. You receive a summary of what you told: the processes, the roles, the data and the integrations, in plain language.

The price indication uses the number of users you mentioned: €200 per month including the first user, €75 per additional user and €1 per portal user. If something is off, you adjust it in the intake.

Rather go through it together? Then you book a conversation from the onboarding.

After the intake you supply your house style, users and existing data and submit it. Pascal reviews it within two working days. Only then do you pay the first month, through iDEAL or on invoice, and that is the starting signal for the build. Before that payment you owe nothing.

From the start a term of 12 months applies; after that it is cancellable monthly with 1 month's notice. Your data is always yours and comes with you in full on termination.

If after the intake you decide it is not for you, you simply leave the account as it is. No invoice follows, and no email to talk you round.

No separate hosting contract, no management retainer alongside it, no hourly rate for small changes.

• Hosting

  Vercel and Supabase in eu-central-1, with a separate project per client. No shared database with other organisations.

• Monitoring and backups

  Monitoring of the environment and daily backups of the database and the files.

• Security updates

  Dependencies are tracked and updated, even when nothing changes functionally.

• Management

  Users, roles, mail templates and manuals. Inviting people and revoking access is something you do yourself from within the CRM.

• Ongoing development

  The request list is prioritised and built. Small improvements are picked up as a matter of course; a new module is planned in consultation.

• Text AI in the application

  1,000 calls per month for reading documents, summaries and chats inside the CRM.

• Mail and storage

  10,000 outgoing emails per month through Resend, on your own domain, and 25 GB of storage.

• Usage above the bundles

  Above the bundles the rate is cost price plus 25 percent, charged monthly in arrears with a specification. Image and video generation are always charged on, including within the bundle.

Not included: your website, image and video generation, and external data services with a contract of their own.

The foundation your custom CRM starts on

Every client starts on the same nine modules, taken from a CRM that is already running. That saves build time, and therefore money.

• Login and roles

  Supabase auth with roles for administrator, employee, partner and client, and row-level restrictions in the database.

• Companies and contacts

  Clients, prospects and suppliers with an owner and an activity log per company.

• Case with a status line

  A track with fixed steps, dates per step and the option to move a step back.

• Mail behind a window

  No mail leaves automatically. Every step opens a window with editable text and a live preview, and everything is logged.

• Documents from templates

  Quotes, agreements and letters from templates, filled with the data of the case and delivered as PDF.

• Client portal

  Clients and partners log in and see only what has been shared with them.

• User management

  Invite people, set roles and revoke access from within the CRM, without going through us.

• Manuals

  PDF manuals per role, inside the CRM, kept in step with changes.

• Feedback module

  A note on every screen, with an overview of what is open and what has been handled.

This foundation is a starting point, not a straitjacket. Everything in it can be rebuilt: other fields, other steps, other names. Whatever your process does not know goes out.

Why this can be this affordable

The framework and the base data model are the same for every client: companies, contacts, case files with a status line, roles, mail, documents, a portal. None of that has to be thought out and built again; it is there on day one, and it is already in use at several clients.

No package licences underneath and no implementation partner in between: hosting on Vercel and Supabase costs tens of euros per month, not hundreds per user. The monthly amount pays for the work, not for the layers in between.

For SMEs with a process of their own it is usually less suitable. Licences per user weigh heavily in a small team, every change needs a specialist, and a portal for clients or partners costs extra licences. A custom CRM starts from the process and charges a fraction of that per user.

When Salesforce is the better choice

What it runs on

Next.js

Supabase

Vercel

Resend

Mollie

Claude

• The data is yours and stays yours. On termination you receive all of it: an export of the database plus the files.
• The source code stays with CRM Force while the subscription runs. If you later want to continue on your own, for example with an in-house developer, you buy out the software at a fixed price set out in the terms. It runs on a mainstream stack, so any Next.js developer can manage it from then on.
• Your environment runs on its own Git repository and its own Supabase project. No shared database with other clients.
• You can stop after 12 months, monthly from then on with 1 month's notice. After termination the environment is switched off; your data you already have.
• Your website sits outside all of this. It stays where it is, or it is a separate product.

The buyout arrangement is set out in the terms for the custom CRM.

Three ways to get a CRM, side by side on the points where they actually differ.

A package is not by definition the more expensive choice. when a standard package is the better fit.

Pascal van de Braak of CRM Force is your point of contact, from the first conversation to every request after that. He sets up the process: what the CRM has to do, in which steps it runs and with which permissions, and he keeps the wish list.

No project manager or helpdesk in between. Whoever sits in the first conversation is also there at delivery and for every change after that. For the build work, CRM Force works with a fixed development partner, so the capacity is there without you dealing with a second party.

Pascal van de Braak

CRM Force, your point of contact