Skip to content

Nextora / Field notes

How the work
actually connects.

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.

Start here7 min read

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.

Read the guide

Everything else

6 articles
9 min read

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.

Read the guide
7 min read

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.

Read the guide
5 min read

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.

Read the guide
5 min read

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.

Read the guide
6 min read

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.

Read the guide