Tools adapt to you.

A custom CRM starts at €5,000, one-time payment, source code yours, no subscription. The price depends on your scope: how many modules, how many users, which integrations (invoicing, calendar, payments), and whether you need a mobile app on top of the web interface. A CRM handling clients, quotes and follow-ups isn't the same budget as a multi-team tool with business-specific modules. Rather than quote a package that wouldn't fit your case, I price after the free diagnosis, once we've mapped what you actually use. You leave with a firm price, not a vague range.

Between 6 and 18 weeks depending on complexity: • Basic CRM (6-8 weeks): clients, quotes, invoices, dashboard • Advanced CRM (8-12 weeks): + sales pipeline, email automations, Stripe/Calendar integrations • Complete CRM (12-18 weeks): + business-specific modules, advanced dashboards, mobile app Delivered in batches for fast feedback. Timeframes include a safety margin to absorb adjustments along the way.

Yes, that's exactly the point of custom. The code is modular: adding a module, a field, an integration takes a few days. A monthly maintenance package lets your CRM evolve with your business without re-quoting every time.

YOU do. 100%. Upon full payment of the service, source code and all deliverables belong to you under a non-exclusive license. You receive a complete archive + technical documentation. Any Next.js/Firebase developer can take over.

You're not tied to me. The code is documented, the stack is standard (Next.js, Firebase, TypeScript, technologies used by tens of thousands of developers), and you have all access. You can: take over internally, hire another freelance dev, or hand it to an agency. Zero lock-in.

Main stack: Next.js (frontend), Firebase (auth, Firestore, Storage), TypeScript throughout. For dashboards: Looker Studio or custom visualizations (Recharts). For automation: N8N or Node.js scripts. For payments: Stripe. These are industry-standard technologies ensuring any senior developer can take over.

The real difference isn't price, it's ownership and fit. With an Odoo (or a HubSpot, a Salesforce), you rent a tool built for everyone. You adapt your team to the software, you pay a per-user subscription that grows as you hire, and you depend on a certified partner for the smallest change. The day the vendor changes prices or rules, you take the hit. With a custom CRM, the tool fits your actual processes: your team only sees what it uses, the code is yours, and any developer can take it over. You don't start from scratch at every evolution. Odoo remains a good choice if your processes are very standard and you want to start in a few days. Custom makes sense as soon as your business falls outside the boxes, or adoption keeps failing with generic tools.

Yes, but migration is treated as a topic in itself, **in shared scope**, never as a standard promise. **My scope**: I define the target data model, provide the import script, and validate on a staging environment. **Your scope**: your IT or data lead provides the export from the legacy system and guarantees the consistency of incoming data (deduplication, formats, mandatory values). Without a client-side data interlocutor, we don't start the migration. **Timeline**: defined after a joint audit of existing data (~1 day of upfront audit). Typically 2 to 6 weeks depending on volume **and** initial quality. The audit decides, not an upfront promise. **Liability boundary**: the quality of the import depends on the quality of the export. Test on a subset jointly validated before full go-live. Migration is quoted separately from the CRM development itself.

Yes. By default, the CRM is responsive (usable on any mobile browser). For intensive use (field teams, frequent mobile input), we can plan a native React Native app as an optional add-on, priced by need at the diagnosis.

It's planned. Once per sprint (every 2 weeks), we have an adjustment meeting. Minor changes are integrated without extra cost. Major changes (new unplanned feature) are subject to a clear amendment to the quote. No surprises.