NextoraComment le travail
vraiment connecte.
Practical guides to running sales, delivery and operations in one workspace — the record model behind a CRM, what an AI employee does on its own, and which automation to reach for. Written from the product, not from a keyword list.
Tous les guides
25 articlesCRM vs ERP: what each one is for, where they overlap, and when one database beats two
A CRM answers who might buy and what was promised. An ERP answers what was delivered, what is owed and what is left on the shelf. The trouble starts in the gap between them, and that gap is a design choice.
Reorder point and safety stock: the formulas, a worked example and when to recalculate
Running out of a product you sell every day is expensive; so is a shelf of stock that sits for a year. The reorder point is the number between the two, and it takes about ten minutes to work out.
Email deliverability for small teams: SPF, DKIM, DMARC and the Gmail and Yahoo sender rules
Email that never reaches the inbox looks exactly like email nobody wanted. Three DNS records, an unsubscribe header and a spam rate under control decide which one yours is.
The purchase order process for a small business: from request to paid supplier invoice
Buying looks simple until the invoice arrives for goods nobody remembers ordering, at a price nobody agreed. A purchase order process fixes that with four documents and one comparison.
Lead scoring for a small sales team: a model you can build in an afternoon and trust
Most lead scoring fails in one of two ways: nobody trusts the number, or the number never changes what anyone does. A small model with two halves, checked against real wins, avoids both.
Before a support bot talks to customers: knowledge, boundaries and an exam it has to pass
A chatbot that answers confidently and wrongly is worse than no chatbot, and a tribunal has already held one company to what its bot said. Testing is how you find the wrong answers before a customer does.
Are electronic signatures legally binding? ESIGN, UETA and eIDAS for sales teams
In the US and the EU, a contract cannot be refused legal effect just because it was signed electronically. The harder questions are which documents are excluded, and whether you can prove who signed what.
Connecting Claude or ChatGPT to your CRM with MCP: what it can do, and the guardrails it needs
MCP turns an AI assistant from something you paste data into, into something that reads and changes your records directly. That is useful in proportion to how carefully its access is designed.
Per-seat or flat: what a CRM really costs once the whole company needs a login
Per-seat pricing charges for every person who logs in, so companies quietly stop giving people logins. That hidden cost never shows up on the invoice, and it is often bigger than the invoice.
CRM roles and permissions: designing access before the team grows
Access in a CRM usually starts as "everyone is an admin" and ends as a tangle of exceptions. A role model designed in an afternoon, before the tenth hire, saves months of untangling later.
On hand, reserved, available: the three stock numbers a small business has to keep apart
Most overselling is not a counting error. It is one number doing the work of three, and the fix is a reservation that the warehouse actually respects.
Quote to cash for a small business: one chain from deal to payment, with nothing retyped
Revenue leaks in the gaps between documents: the deal nobody turned into an order, the order nobody invoiced, the invoice nobody chased. Close the gaps by making each document the parent of the next.
Sales pipeline stages that tell the truth: exit criteria, outcomes and the stuck-deal test
A pipeline board is only as honest as the rule for moving a card. Most boards have stage names and no rules, so every salesperson runs a slightly different process on the same screen.
The handoff from sales to delivery: where client projects lose their first week
The deal closes on Friday. On Monday the delivery team asks the client the same questions sales asked a month ago. A good handoff is the cheapest way to make a new client feel looked after.
Single-tenant vs multi-tenant SaaS: what a dedicated server per customer actually changes
Most business software keeps every customer in one shared database and separates them with code. Single-tenant software gives each customer their own. The difference rarely shows in a demo and often shows in year two.
Speed to lead: why the first hour decides the deal, and how a small team answers inside it
A new enquiry is at its warmest in the first minutes after it arrives. Most companies answer hours or days later, and the gap is rarely laziness. It is ownership, routing and a queue sorted the wrong way.
Moving from spreadsheets to a CRM: an import plan that does not breed duplicates
A CRM migration fails quietly: the import succeeds, the numbers look right, and three months later every second customer exists twice. The plan below prevents that before the first row is created.
Weighted pipeline forecasting: a sales forecast a small team can actually trust
A weighted forecast multiplies each deal by its chance of closing and adds the results. The arithmetic takes a second. The probabilities behind it are where most forecasts go wrong.
WhatsApp, Instagram and Telegram in your CRM: setup, platform rules and the 24-hour window
Each messaging platform has its own rules about who can write first and for how long. A CRM that ignores them sends replies that fail; one that respects them turns DMs into a working queue.
Lead, contact, company, deal, project: the five records a CRM actually needs
Most CRM problems are not feature problems. They are modelling problems: the same customer typed in four times, in four shapes. Here is the record model that makes filtering, counting and automation possible.
AI employees, not chatbots: what changes when the AI has a role, a manager and a trial period
A chatbot waits to be asked. An AI employee is on duty by events, works inside your permission model, proposes what it may not do alone — and can be paused like anyone else. Here is how that works in practice.
Pipeline, workflow, form or template: choosing the right automation for the job
Four tools that look interchangeable and are not. A rule for picking between them in one question, the full list of events a workflow can start from, and why a generated automation should always be saved switched off.
Showing the client the project without giving away the CRM
Status update emails are a tax on delivery. A scoped client portal — a link, an access code, and only the sections you switched on — removes it without exposing budget, risks or anything else internal.
The web form that looks like it works: why enquiries arrive and the CRM stays empty
Notifications land, submissions pile up, and nothing reaches a record. Wiring answers to fields is a step with a name of its own — and the reason a form is a CRM feature, not a website feature.
One queue for every channel: what omnichannel actually has to do
Omnichannel is not a list of logos on a pricing page. It is one queue, one thread per customer across sources, an owner on every conversation, and a start-here tab. Here is the anatomy that makes it work.