Menus and plan rules change often. We read the vendors' help pages on 1 November 2026 where they were available and mark where we could not confirm a detail.

Two kinds of memory

Saved memories. The assistant keeps short facts, either because you asked ("remember I prefer short answers") or because it decided a fact was useful. You can usually list them and delete them.

Chat history reference. The assistant searches or draws on your earlier conversations when answering. This is broader and less visible than a list of facts.

Both can be helpful. The difference matters for privacy: a list of ten lines is easy to review, while a reference to everything you ever typed is not.

What to look for

Whatever product you use, these controls decide whether memory is safe at work.

1. You can see it. A full list, not a hint.
2. You can edit or delete one line. And delete all.
3. You can pause it. Existing memory stays, nothing new is saved.
4. There is a no memory mode. Incognito or temporary chats for sensitive questions.
5. You know where it came from. Learned in chat, learned from a file, or written by you.
6. Workspace owners can set a policy. Important for teams.
7. Sensitive topics are not saved by default.

The options at a glance

ChatGPT

OpenAI's memory help page describes two controls: saved memories, and reference to chat history. Memories can be managed under Settings, then Personalization, then Manage memories. Turning off saved memories also turns off chat history reference. OpenAI notes that deleting a saved memory does not remove mentions from past chats, so you may need to delete the source chat too. Temporary chats do not use or create memories. Which features your plan includes has varied, so check the live page.

Claude

Anthropic's help page says memory is on by default for Free, Pro, Max and Ultra plans, while on Team and Enterprise plans owners decide whether it is available and it is off for each member until they enable it. Claude saves memory as topics; you can read, edit or delete them under Settings, Your Claude, or ask in chat. Pause memory keeps existing memory but stops Claude using or adding to it, and Reset deletes everything. Each project has its own memory. Chat search covers past conversations on paid plans. Incognito chats are not saved. Sensitive topics such as health are not saved by default unless you opt in.

Gemini

Google describes past chats as personal context, which you can turn off in settings. The sources we found describe a temporary chat option that does not affect personalization, and noted that turning the setting off does not delete your history, which is managed separately in your activity settings. Menu names have changed more than once, such as Keep Activity, so look at the current app rather than older articles.

nerix

nerix keeps short lines about you and your work, such as your role or how you like answers written. Each line says where it came from: learned in a conversation, learned from a document, or written by you. Memory in Settings lists all of it. You can add a line, mark one Keep this so it survives a clear out, forget one, or forget everything except the kept lines (this cannot be undone). Turning off Remember things about me pauses it: nothing new is saved and what is saved stays. If the workspace owner set it for the whole workspace, only an owner or admin can pause it.

What it is not: memory is about you, not a record of the workspace. What nerix knows about your company comes from the documents you add to the library, which follow roles and access rules. And it is early in its life, so expect fewer options than the large assistants.

Memory and company data

Memory raises a business question the consumer help pages skip: whose data is it? Three habits keep you safe.

• Do not use a personal assistant account for client work. Memory then mixes your private and professional life, and a leaver takes it with them.
• Check training and retention terms. Whether your chats train a model depends on the product and plan. Read the privacy page for your plan. Our note on keeping your data in the EU covers location questions.
• Keep facts about people out of memory. Customer health, finances and employee issues belong in controlled documents, not in a memory line.

Also remember that an assistant with memory can be wrong about you. A stale line ("I work in sales") can colour answers for months. Review the list every few months and delete what no longer holds.

A ten minute check

Do this on whichever assistant you use:

1. Open the memory list and read every line aloud.
2. Delete anything confidential, outdated or about another person.
3. Add two or three lines that really help, such as your role and preferred answer length.
4. Find the switch that pauses memory, and find the temporary or incognito mode.
5. Ask the assistant "what do you remember about me" and compare its answer with the list.

The short version

Memory is useful when it is short, visible and under your control. Check that you can see it, delete it, pause it and talk without it. Use temporary or incognito chats for sensitive questions, keep other people's details out, and review the list every few months. Menus change often, so rely on the settings screen in front of you.

When a spreadsheet is enough

A sheet works well when:

• You have one or two openings at a time.
• One or two people read applications and interview.
• You get tens of applications, not hundreds.
• You do not need a public careers page that posts to job boards for you.

Set it up with one row per applicant and these columns: name, opening, source (where they heard of the job), date applied, current step, interviewer, score, decision, reason, and a link to the resume in a folder. Give the sheet to the few people who hire, because it holds personal data.

Signs you have outgrown it

• Two people contact the same applicant, or nobody does.
• You cannot say how many people are at the interview step without counting.
• Interviewers keep their notes in their own notebooks, and you cannot compare them.
• You want one place to post the job, receive applications and send standard emails.
• You need to prove you treated applicants the same way.

What the free plans give you

Free plans are real, but they are built to be outgrown. Checked on each vendor's own pricing page on 1 November 2026:

Look hard at the limits. One active job is fine if you hire one role at a time, and a trap if you open three. Visibility limited to the last 30 days means older candidates are hidden on the free plan. Ask each vendor where your data is stored, whether you can export every applicant as a file, and what happens to the data if you leave.

The hiring process that matters more than the tool

A tool only holds the steps. These are the steps to write down first.

1. Write the job down. A short job description with the real tasks, the hours, the place and the pay range if you can share it. Pay transparency is now required in some countries, so check yours.
2. Decide the steps before you advertise. For example: applied, screening, interview, offer, hired, not taken forward. Use the same steps for everyone.
3. Agree what good looks like. Pick four to six things the job needs and score every person against them with an interview scorecard, not against each other.
4. Ask every applicant the same core questions. It is fairer and makes notes comparable.
5. Write notes the day of the interview, while you remember. Stick to what the person said and did, not guesses about age, family plans or background.
6. Reply to everyone. A short, kind no is far better than silence, and it protects your name.
7. Put the offer in writing, with the start date, pay and conditions, using a job offer letter. Then keep the steps from there in line with our guide to onboarding a new hire in 30 days.

Fairness and the law

Hiring is one of the areas where the law looks closest. In most places you cannot treat applicants differently because of things such as sex, age, religion, disability or ethnic origin, and you should not ask about them in interviews. Some countries add rules on criminal record checks, work permits and what a job advert may say. In the EU, the AI Act treats AI systems used to filter or rank applicants as high risk. That is one reason to keep a person in charge of decisions. Ask an adviser what applies in the country where you hire, since this guide cannot do that for you.

Hiring in nerix

If you want hiring next to your people records, nerix has a Hiring place on Business workspaces. You create an opening with the job title, team, place and status, add applicants with their resume and where they heard of the job, and move them across the board: Applied, Screening, Interview, Offer, Hired or Not taken forward. For an interview you note the kind, time and interviewers, and each interviewer fills a scorecard with a rating from 1 to 5, a recommendation and comments that only the hiring side sees. An offer can be sent, accepted, declined or withdrawn, and when someone accepts, a manager can turn the applicant into an employee record in one step.

Some limits, so that you can decide with open eyes. The AI in nerix never ranks, scores, shortlists or rejects an applicant, and never recommends who to hire. It can show a short summary of a resume that is labelled as a reading aid. Applicant pages are visible only to the people who have hiring access. It is not a job board, so you still post the advert where candidates look. See the People page and Pricing for the plans that include it.

Questions to ask before you pay for any ATS

• How many open jobs and users does my plan allow, and what is the price at twice that?
• Can I export every applicant and every note as a file?
• Where is the data stored, and can I set how long it is kept?
• Does it post to the job boards I use, or only to its own page?
• Can interviewers score on a form, and see only their own scores before they finish?
• What happens to my data if I cancel?

A worked example: hiring one person on a sheet

Say you hire a customer support person. You write the job description on Monday and post it on one job board and your own site. Over two weeks, 40 people apply. You read each application against the same five points from the scorecard, mark each row in the sheet as Screening or Not taken forward, and send a short reply to everyone who is not continuing. Eight get a 20 minute call, three come to a longer interview with two interviewers, and each interviewer fills in their own scorecard before they talk to each other. That last rule matters, because the first person to speak tends to steer the rest. You then compare the written scores, decide, and write the offer. The whole thing ran on one sheet and a folder, and the record shows why each person was chosen or not.

The short version

You do not need an applicant tracking system until several people hire at once or applications outgrow a sheet. Free plans exist, with limits such as one active job, so read them before moving data. Fix the steps, the scorecard and the deletion period first, because they make hiring fair whatever tool you use. Keep a person in charge of every decision.

Check the official pages before you buy, since plans change: Calendly and Cal.com.

What a booking page should do

Before comparing names, list what you actually need. A good scheduling tool:

• shows only times you are really free, taken from your calendar, and never shows what is in it;
• shows times in the guest's own time zone;
• lets you set minimum notice, how far ahead people can book and a limit per day;
• adds buffer time before and after meetings, so back to back calls do not happen;
• asks the questions you need answered before the call;
• sends a confirmation and reminders, with a link to cancel or change;
• creates the video link for you.

Teams add two more: taking turns between members (round robin), and requiring several people to be free at once.

The options at a glance

Calendly

Good at: being familiar. Guests know the interface, and it connects to many calendars and apps. The page lists Free at 0 dollars with 1 event type and 1 calendar connection, Standard at 10 dollars per seat a month on yearly billing with unlimited event types and 6 calendar connections, and Teams at 16 dollars per seat on yearly billing with round robin and team scheduling.

Falls short: the free plan is narrow, and team features need the higher plan. Enterprise starts at 15 thousand dollars a year with at least 50 seats.

Cal.com

Good at: flexibility and openness. The Free plan is listed as free forever for one user, with unlimited event types, calendars, email and SMS notifications, and Stripe and PayPal payments. Teams is 12 dollars per user a month on yearly billing with shared availability, round robin and recurring events, and Organizations is 28 dollars per user a month and adds SAML single sign-on and SCIM. The page links a self-hosted option and a GitHub repository.

Falls short: more options mean more to set up. The page does not describe self-hosting terms, so read the licence on GitHub if you plan to run it yourself.

Booking pages in nerix

Good at: meetings that should land in the same place as everything else. A booking page has a link, a name, a colour, one to four meeting lengths and a place: a video room, a phone call, in person at an address, or a link. Free times come from your working hours minus whatever is in your calendar, and people only see open times. Guests pick a time in their own time zone and answer your questions. Name and email are always asked, and you can approve each booking yourself.

After booking, the guest gets a confirmation and can add it to their calendar. Reminders go a day and an hour before, and the email has a link to cancel or choose another time. The booking is a normal meeting in your calendar with its own video link, so Meetings features such as notes work on it. Team pages take turns between free members or need everyone free. Guests need no account.

Falls short: booking pages are for business workspaces, so they are not a standalone scheduler for people who do not use nerix. It has fewer outside integrations than Calendly. Plans and credits are on the pricing page.

Questions to ask before you choose

1. How many meeting types do you offer? A free plan with one event type suits a consultant with one call type. A team with intro calls, demos and support calls needs more.
2. Do several people share a page? If yes, check that team scheduling is in the plan you can afford, not only in the enterprise tier.
3. Which calendar do you use? Confirm two way sync. Double bookings usually come from calendars that are not connected.
4. Do you collect payment at booking? Some tools support it, some do not, and the free plan may leave it out.
5. Where are the notes and follow ups? A booking is the start of a meeting. If the tool ends at the confirmation email, you will need another tool for the rest.
6. Where is the data held? If your clients are in the EU, read the provider's data location and privacy pages.

Common mistakes

Offering too many times. A page with every half hour open invites fragmented days. Use working hours, daily limits and buffers.

No minimum notice. Without it someone books a call for fifteen minutes from now.

Forgetting the time zone. Guests should see their own zone and be able to change it.

Skipping reminders. A reminder a day and an hour before cuts no shows. Check that your tool sends them.

The short version

For one person with one kind of call, a free plan from Calendly or Cal.com is enough. For a team, compare the plan that includes round robin: 16 dollars per seat at Calendly or 12 dollars per user at Cal.com on yearly billing when we checked. If your team already works in nerix, booking pages keep the booking, the meeting and the notes together. Whatever you pick, test with a colleague in another time zone before you share the link.

What bookkeeping records

Every transaction has four facts: a date, an amount, who it was with, and what it was for. Group them into five kinds:

1. Income. Sales and other money earned.
2. Costs. Rent, software, materials, wages, travel.
3. Assets. What you have: cash in the bank, money customers owe you, equipment, stock.
4. Liabilities. What you owe: supplier bills, loans, taxes due.
5. Owner's share. What the owner put in or took out, and profit left in the business.

Every business, whatever its size, is described by these five. Reports are just different ways of adding them up.

Double entry in plain words

In double entry, every transaction is written twice, in two places, and the two sides must be equal. This is what makes mistakes visible.

Example: you sell a service for 1,000 and the customer pays at once. Money in the bank goes up by 1,000, and income goes up by 1,000. If the customer pays later, you first record that the customer owes you 1,000 (an asset) against income, and when the payment comes you move the 1,000 from "owed to you" to "bank".

A second example: you buy software for 50 on a card. Costs go up by 50 and the bank goes down by 50.

The test is simple: for every entry, what came in must equal what went out. If an entry does not balance, you made a mistake, and it is found in seconds instead of months.

The reports you will use

• Profit and loss. Income minus costs for a period. It tells you if you made money.
• Balance sheet. What you have and what you owe on one date.
• Trial balance. A list of all accounts that proves debits equal credits. If it does not, something is wrong.
• Tax summary. The figures your tax return or sales tax filing needs.
• Cash and what is owed. Not a formal report, but the one owners look at: what is in the bank, what customers owe, what you owe.

A routine that takes an hour a month

1. Collect. Sales invoices, supplier bills, receipts, bank statements, staff expense claims.
2. Record. Enter everything with date, amount, party and purpose.
3. Match the bank. Every line on the bank statement should match an invoice, a bill or an expense. Lines that match nothing are the ones to investigate.
4. Chase. List unpaid customer invoices and send reminders. Our guide to payment reminder emails helps.
5. Check. Run the trial balance and compare profit with last month.
6. Close the month. Lock it so old figures do not change. Fix errors with a new entry in the open month.
7. File what is due. Sales tax, payroll tax, anything with a date.

Choosing a method and a tool

Start with the simplest thing that does not lie to you.

• A spreadsheet works for a sole trader with a few transactions a week. The risk is silent formula errors and no lock on old months.
• Accounting software brings double entry, bank matching and reports. The big names are strong on tax filings in their home countries. Check that the tool handles your country's sales tax and filings before you commit.
• An accountant or bookkeeper can do all of it for a fee. Many owners keep the receipts and invoices and hand the rest to a person each month.

Whichever you use, get an accountant's view on the basics for your country: cash or accrual, sales tax registration, what you must keep and for how long, and which year end to choose. One hour at the start saves many later. A simple budget template helps you plan against the real figures you now have.

Common mistakes

• Mixing personal and business money. Use a separate account from day one.
• Entering things late and from memory. Details are lost within weeks.
• No receipts. A bank line without a document is hard to defend. See expense tracking for small teams.
• Ignoring the bank match. It is the best check you have.
• Editing closed months. The tax return you already filed no longer matches.
• Treating the owner's withdrawals as costs. They are a movement of the owner's share, not a business expense.

Bookkeeping in nerix

nerix has a Money place on Business workspaces, and it follows these basics. It has accounts (what you have, what you owe, owner's share), and entries made of lines that must balance before you post them. A posted entry is never edited, only reversed with a reason. Invoices, expenses and payroll post into it when those places are on, and are marked so that you can trace and reverse them from the source.

For the bank, you add an account and bring in a statement. For each line you accept a suggested match (an invoice, an expense or your own rule, marked very likely, likely or possible), put it in an account, or leave it out. Reports are the trial balance, profit and loss, balance sheet and tax summary for any dates, and you can print them. "Close the month" locks closed months and needs everything matched first.

Two limits. nerix records money, it does not move it. And the assistant explains the figures but does not give tax or legal advice and never posts, reverses, closes or matches anything without a person confirming. Your accountant is still the right person to confirm tax treatment for your country. See the Money page and Pricing.

A worked example month

A one person design studio sends three invoices in March, for 2,000, 1,500 and 800. Two are paid in March and the third in April. The bank shows 3,500 received in March, and the studio's books show 4,300 earned. Both numbers are right, and they answer different questions: the bank shows cash, the invoices show income. The studio also paid 120 for software, 300 for a shared office desk and 90 for a train ticket. In March the profit and loss shows income of 4,300 and costs of 510, a profit of 3,790, while the bank shows 3,500 in and 510 out, a gain of 2,990. The 800 difference is the unpaid invoice, which the books list as owed to the studio until the money arrives. Seeing that gap each month is how an owner stays out of trouble with cash even when the business is profitable.

The short version

Bookkeeping is writing down every transaction with a date, amount, party and purpose, in a form where two sides always balance. Keep business money separate, match the bank every month, close the month and fix errors with new entries. Start on a sheet if you must, move to software when volume grows, and ask an accountant about the rules of your country at the start.

Start with a one page policy

People spend carefully when they know the rules, and are annoyed when rules appear after the fact. Write a page that answers:

1. What can be claimed. Travel, meals with clients, software, supplies, training. Say what cannot, such as fines or personal items.
2. Limits. A daily meal limit, a hotel limit, and the amount above which you want approval before the purchase.
3. Proof. A receipt for everything above a small amount. The tax invoice, not only the card slip, where that is what your tax office wants.
4. Timing. Claims within 30 days, say, so the books can close.
5. Who approves. Normally the person's manager. Nobody approves their own claim.
6. How you pay back. Which day, to which account.

Our expense policy template is a starting point, and the expense report template gives people one format to fill in.

Capture receipts at once

Lost receipts are the biggest practical problem. Paper fades and gets left in jackets. Fix it with one rule: photograph the receipt the same day. A phone photo, in a shared folder or an expense tool, is enough in many countries. Ask your accountant to confirm for yours.

For each expense, record the date, the amount and currency, the supplier, what it was for, and the project or customer if you charge it on. Foreign currency expenses need the rate you used. Write the purpose in plain words, because "lunch" tells an auditor nothing, while "lunch with the customer to discuss the renewal" does.

The claim flow

A good flow has five stops, and a status at each:

1. Not sent. The person is still filling it in.
2. Waiting for approval. Sent to the approver.
3. Approved or sent back with a reason so the person can fix it.
4. Paid back, with the date.
5. Posted to the books, under the right account.

Put a time limit on each stop. A claim that sits waiting for two weeks teaches people not to claim.

Sheet or tool

A sheet is fine for a team of three to five with a few claims a month. Use one tab per month, one row per expense, and a folder of receipts named by date. It stops working when:

• Receipts and rows no longer match.
• Approvals happen in chat messages nobody can find.
• You spend a day each month typing amounts into the books.
• Mileage and per diems are calculated by hand.
• You need to show an auditor who approved what.

At that point a tool pays off. Here is what some cost, checked on the vendors' own pages on 1 November 2026:

Prices change and differ by currency, so look at the page before you decide. Ask any vendor: Can I export all claims and receipts? Can approvers work from a phone? Does it handle mileage rates and foreign currency? Does it connect to my accounting tool? What does a person cost when they only submit one claim a quarter?

Common problems and fixes

• Claims arrive in a bunch at year end. Ask for claims monthly and close the month.
• Personal and business money mixed. Use a company card or account for business costs.
• Duplicates. The same receipt is claimed on a card statement and by a person. Match against the bank statement each month.
• Vague descriptions. Make the purpose a required field.
• No limit on what a manager can approve. Set an amount above which a second person signs.
• Staff paying for the company out of pocket for weeks. Pay back on a fixed day. If a person lends money to the business without being paid back fast, trust drops.

Expenses in nerix

On Business workspaces, nerix has an Expenses place. A person writes a few words on what the claim is for, then takes a photo of the receipt. nerix reads it into a draft, and the person checks the details and fixes them by hand if needed. A claim can also be added by hand or as a trip by car, where distance is multiplied by the rate. A receipt is required above a set amount. The claim can be saved for later or sent for approval.

Approvers see a To approve list, and can approve or send back with what to fix. After that the claim is marked paid back with a date. That is only a note that someone paid, since nothing is paid from nerix. Approved claims post to the Money place if you use it. A person sees only their own claims, and the receipt reading never approves or pays anything: an unclear receipt is flagged "We are not sure about this one". The Money page and People page describe the rest, and Pricing lists the plans.

If staff costs go through payroll, see how it fits in our guide to payroll for a small business, and for the books themselves read bookkeeping basics for small business.

A worked example

A team of six travels to a customer. One person pays for the train tickets and a taxi, another pays for lunch with the customer. On the same day each takes a photo of the receipt and writes the purpose: "train to customer workshop" and "lunch with the customer to plan the renewal". Both send their claims on Friday. The approver, their manager, sees the amount, the photo and the purpose, approves one and sends the other back because the lunch receipt does not show the total. The person fixes it on Monday, it is approved, and on the fixed pay back day on the 15th both are paid. At month end the accountant gets the approved claims with their receipts and posts them. No one searched through jackets, chat messages or bank statements.

The short version

Expense tracking for small teams needs a one page policy, a photo of every receipt on the day, and an approver who answers within days. Use a sheet while claims are few and a tool when receipts or approvals go missing. Pay people back on a fixed day and make sure nobody approves their own claim.

For a wider market view see DocuSign alternatives. This post is only about what you get without paying.

Two jobs, not one

Sign it yourself. You have a PDF and need to add your signature and the date. A browser tool does this. No one else is involved, so there is no audit trail to speak of.

Collect signatures from others. You send the document, other people sign by email link, and you want proof afterwards. This needs a service, because it must keep a record, send reminders and produce a finished file.

Most free plans for the second job limit the number of documents a month. That suits a freelancer sending a few contracts and rarely suits a team sending dozens.

Are free signatures legal?

Mostly yes. The EU's eIDAS regulation says an electronic signature cannot be denied legal effect only because it is electronic, and it separates simple, advanced and qualified signatures. In the United States the ESIGN Act and state UETA laws give a similar basic rule. Everything below produces a simple electronic signature unless a vendor says otherwise. Some documents, such as certain property or family papers, are excluded or need extra formalities, and some contracts name a stronger signature in their own terms. This is general information, not legal advice.

The options at a glance

Adobe Fill and Sign

Good at: signing your own PDF fast. Adobe describes it as free: type, draw or upload your signature and place it on any PDF in the browser, with no download. Adobe also says that requesting signatures from others is free with an Adobe account.

Falls short: account rules differ by country page, and we could not find a clear published cap on free signature requests, so check the page for your region before building a process on it.

SignWell

Good at: a clean free plan for occasional use. The page lists Free at 0 dollars with one sender, one template and 3 documents a month, and an API with 25 free documents a month on all plans. Light costs 10 dollars a month billed yearly (12 monthly) with unlimited documents and 5 templates per sender.

Falls short: three documents a month is a real ceiling. SOC 2 Type II and HIPAA support start at Light, not on Free.

DocuSeal

Good at: an open source product with a hosted free tier and a self-hosted edition. The Basic cloud plan is free, with legally valid e-signatures, unlimited storage, multiple signers and 10 signature request emails a month. Pro costs 20 dollars per user a month and adds unlimited emails, reminders, bulk send and branding. The open source self-hosted edition is free and you bring your own mail server.

Falls short: the free cloud tier is limited by emails, and self-hosting means you run and secure it. Reminders and bulk sending are not in the free or open source tiers.

Documenso

Good at: another open source signing product. The Free plan allows 5 documents a month with up to 10 recipients per document, no card required. Individual is 25 dollars a month (300 yearly) and Teams is 40 dollars a month with five users.

Falls short: five documents a month is the free ceiling. The pricing page does not state the open source licence terms, so read the repository if you plan to self-host.

nerix

Good at: documents you already write in nerix. A document can go out with Ask to sign, and people accept or sign from a private email link with no account. The request is tied to that version, so if the text changes afterwards signing is refused. Every step (created, sent, viewed, signed, declined, reminded, expired, cancelled, completed) is added to a tamper evident record, and the signed PDF prints that trail with the signer's IP address and browser. Reminders go out on days you choose and requests expire after 30 days unless you change it. See E-signatures.

Falls short: it is a simple electronic signature, not a qualified one, and no identity check is made. It has no library of thousands of forms and no outside certificate authority. If your contract needs a qualified signature by law or by its own terms, use a specialist service. Plans and credits are on the pricing page.

When free stops being enough

Free plans work for a handful of documents a month. Look at paying when any of these is true:

• You send more documents a month than the cap, which is 3 to 10 for the plans above.
• You need reminders, bulk sending, branding or integrations that sit behind the paid tier.
• A client or regulator wants a stronger signature than a simple one.
• You need compliance reports such as SOC 2 or HIPAA support.

Before relying on any free plan, send yourself a test document and open the finished PDF. A good record shows who signed, when and what version they saw. If the finished file does not show that, the plan is not giving you the proof you wanted.

The short version

Signing your own PDF is free in a browser. Collecting signatures from others is free within limits of roughly 3 to 10 documents a month on the plans we read. Pick by volume, by whether you need open source, and by whether a simple electronic signature is legally enough for your document. If it is not, pay for a service that offers a stronger one.

1. Know what you hold

• List the personal data you collect: customers, prospects, staff, applicants, suppliers' contacts, website visitors. For each, note where it comes from, why you hold it, where it is kept, who sees it and when it is deleted.
• Keep this list as your record of processing activities (Article 30). Organisations under 250 employees have a limited exemption, but it falls away if processing is not occasional, risks people's rights or includes special category data such as health. A short table is usually easier than arguing about exemptions.
• Find the special category data (Article 9), which includes health, biometric data, religion and trade union membership. It needs an extra condition.

2. Have a lawful basis for each purpose

Article 6 gives six bases: consent, contract, legal obligation, vital interests, public task and legitimate interests. For each purpose in your list, pick one and write it down.

• A customer's address to deliver an order is contract.
• Keeping invoices for the tax period is legal obligation.
• A newsletter to people who ticked a box is consent, which must be freely given, specific, informed and as easy to withdraw as to give (Articles 4(11) and 7).
• A fraud check on your own shop may be legitimate interests, which needs a short written balancing of your interest against the person's.

Do not use consent when another basis fits. It can be withdrawn, and then you must stop.

3. Tell people clearly

Articles 13 and 14 list what a privacy notice must say: who you are and how to reach you, the purposes and bases, who receives the data, transfers outside the EEA and their safeguards, how long you keep it, the rights people have, the right to complain to an authority, and whether giving the data is required.

• Publish a notice in plain words where people give data (website, forms, shop). A website privacy notice is a starting point to adapt to your facts.
• Cookies and similar trackers also fall under the ePrivacy rules in each country, which usually require consent before non-essential ones load.
• Give staff and applicants their own notice.

4. Respect people's rights

People can ask for access (Article 15), correction (16), erasure (17), restriction (18), portability (20) and can object (21). The standard deadline is one month from the request, extendable by two months for complex or numerous requests, and you must tell the person if you extend (Article 12(3)).

• Decide who receives requests, how to check identity and where to look. A personal data access request and a deletion request template help keep the steps the same each time.
• Keep a log with the date received, the date answered and what you decided.
• Erasure is not absolute: you may keep what the law requires, such as invoices.

5. Choose processors carefully

Anyone who handles personal data on your behalf, such as a cloud host, email service, payroll provider or accountant, is a processor (Article 28).

• Have a written contract or data processing agreement with each one, covering instructions, confidentiality, security, sub-processors, help with requests, deletion or return at the end and audits. Use a data processing agreement where the provider has none.
• Keep a list of processors and review it yearly. See supplier audits for small companies.
• Check transfers outside the EEA (Chapter V). Look for an adequacy decision, standard contractual clauses or another valid tool, and see keeping your data in the EU.

6. Keep the data safe

Article 32 requires appropriate technical and organisational measures, considering risk and cost. For a small business that usually means:

• Unique accounts with a second factor on email, cloud storage and accounting.
• Updates applied promptly, and encrypted laptops and phones.
• Access only for people who need it, removed when they leave.
• Backups that you have tested by restoring.
• Staff who know not to send personal data to the wrong person or personal accounts.

Article 25 adds data protection by design and by default: collect only what you need and keep it only as long as you need it. Set a retention period for each item in your list, and delete on schedule.

7. Be ready for a breach

A personal data breach is a security incident that leads to accidental or unlawful destruction, loss, alteration, disclosure of or access to personal data (Article 4(12)). A lost unencrypted laptop or an email to the wrong list qualifies.

• Report to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk (Article 33). A late report must say why.
• If the risk is high, tell the people affected without undue delay, in clear words (Article 34). A notification template saves time under pressure.
• Record every breach, including those you do not report, with the facts, effects and action taken (Article 33(5)).
• Name who decides, and practise once. See incident reports and how to investigate.

8. Assess risky projects, and decide on a DPO

• Do a data protection impact assessment (Article 35) before processing that is likely to be high risk, such as large scale monitoring, large scale special category data or systematic profiling with serious effects. A privacy impact assessment gives the structure.
• Appoint a data protection officer only if Article 37 or national law requires it. Otherwise, name one person responsible and write it down.
• Train staff once a year and when they start, and keep the attendance.

A common small business example

A dental practice with eight staff keeps patient records (special category data), sends appointment reminders by text, and uses a cloud booking system and an outside payroll service. Its list has four lines. Patient care runs on contract plus the health-care condition in Article 9(2)(h). Reminders are covered by the contract if they are about the appointment itself, and need consent if they go further. The booking system and payroll provider each have a processor agreement. Staff have a short notice. The practice keeps a breach log, tests restores quarterly and answers access requests inside one month. None of this takes long once written down, and it is exactly what an inspector asks to see.

Evidence to keep

The processing list, the lawful basis for each purpose, current privacy notices, consent records where you rely on consent, processor contracts, the requests log, the breach log, impact assessments, training records and the date of the last review. When a data protection authority asks, you must be able to show how you comply (accountability, Articles 5(2) and 24).

Penalties are set by Article 83: up to 10 million euros or 2 percent of worldwide annual turnover for some infringements and up to 20 million euros or 4 percent for others, whichever is higher. Authorities consider size and effort, and in practice start with the most serious cases, but a business with nothing written down has little to show.

Using software for the check

Checks in nerix is in early access and has the GDPR in its library of about 90 frameworks. Under "Get ready for a check", nerix reads the notices, policies and records in your library and marks each requirement as Evidence found, Partly found, Not found or Can't tell, and a person confirms each one. The price is shown before you start. It is readiness information, not a legal opinion, and it does not discover what personal data sits in your systems. A table and a calendar reminder also do the job for a small business. Our security page explains how nerix handles your data.

The short version

List the personal data you hold and why. Pick a lawful basis for each purpose, tell people in a plain notice, answer requests within one month and put contracts in place with every processor. Keep the data safe, know the 72 hour breach rule, and record what you decided and when. A short, dated, honest record is what a regulator wants to see.

Sources

• Regulation (EU) 2016/679 (GDPR), Articles 4 to 7, 9, 12 to 21, 24, 25, 28, 30, 32 to 35, 37 and 83, on EUR-Lex.

What HKZ is, and what it is not

The HKZ scheme describes how a care organisation should organise its quality system so that care is safe, effective and centred on the client. Its norms follow the philosophy of ISO 9001: leadership, planning, process control, measurement and continual improvement. Unlike ISO 9001, they are written for care and welfare, with requirements around the client's wishes and involvement, the client file, the competence of professionals, safety and handling complaints.

There is not one HKZ norm but a set, each for a type of provider. The certifying bodies list schemes such as HKZ 104 for physiotherapy practices, HKZ 118 for care of people with disabilities, HKZ 136 for public pharmacies, HKZ 143 for small organisations and HKZ 144 for nursing homes, residential homes and home care. There is also a certificate for self-employed professionals. The numbers and titles change as norms are revised, so confirm which one fits you with hkz.nl before you plan anything.

HKZ is a voluntary mark. It is not the law, and it does not replace legal duties such as the Dutch quality and complaints act for care (Wkkgz) or the inspectorate's supervision. Many purchasers value it, and some contracts refer to it or to an equivalent.

Who certifies you

HKZ certificates are issued by independent certification bodies that are accredited for the scheme. The HKZ website lists them. At the time of writing these include CIIO, DNV, DEKRA, Keurmerkinstituut, Kiwa, LRQA and TÜV NORD. Prices and lead times differ, so ask for quotes from at least two, and ask what the audit days depend on, usually the size of the organisation, the number of locations and the risk of the care you give.

How the certification route runs

The exact steps depend on your scheme and your certification body. The usual shape, described by the certification bodies, is:

1. Request a quote and agree the scope. Which locations, services and client groups the certificate covers.
2. Build and run the system. The system must run for long enough to leave records: complaints handled, an internal audit done, a management review held.
3. Document review and initial visit. The certification body reviews your documents and how ready you are.
4. Certification audit. The auditors check how the system works in practice: interviews with staff and clients, observations and a sample of client files and records.
5. Findings. Nonconformities need a cause analysis and a corrective action within the agreed period.
6. Decision and certificate. Usually valid for three years, with a yearly interim check, and renewal by recertification audit at the end.

The cycle of three years with a yearly review matches what Kiwa and LRQA describe for most schemes. Confirm yours in writing.

HKZ readiness checklist for a care provider

Use your own norm as the master list. These areas appear in nearly every care quality system, so they make a good starting grid. Under each, ask: is it written, is it done, is there a dated record?

Leadership and policy

• A quality policy and measurable objectives that the board or owner approves and reviews.
• Clear roles, including who is responsible for quality and for client safety.
• A scope that says which services and locations are included.

Client centred care

• A way to record each client's needs, wishes and goals, and to review the plan with them.
• Informed consent and the client's rights explained in words they understand.
• Involvement of clients and representatives in how you improve.

Safety and incidents

• A process for reporting incidents and near misses, analysing causes and acting. See incident reports and how to investigate.
• Risk analysis for your care processes, kept in a risk register.
• Hygiene, medication and emergency procedures that match your service.

People

• Job descriptions and the qualifications needed.
• Records of training, competence and refreshers for each person, such as a staff training record.
• An induction for new staff and volunteers. See onboarding a new hire in 30 days.

Complaints and feedback

• A complaints procedure that clients know about, with an independent route where the law requires it. A customer complaints procedure is a base for the written steps, and handling customer complaints shows the habits.
• A yearly look at the numbers and causes of complaints and client satisfaction.

Suppliers and records

• Evaluation of suppliers that affect care: medication, equipment, subcontracted staff. See supplier audits.
• Client files and data protected under the GDPR; see our GDPR checklist.
• Document control: the current version of each procedure is easy to find.

Checking and improving

• An internal audit programme with results. See your first internal audit and the internal audit plan.
• A management review with minutes and decisions, using the management review minutes.
• Corrective actions that remove the cause, tracked to completion on a corrective action report.

Common findings in care audits

These are gaps that any care quality system tends to have, so test yourself against them before an auditor does. Client plans exist, but nobody can show they were reviewed with the client. Incidents are logged, yet the cause analysis is missing, or the same incident returns. The internal audit looked only at paperwork and spoke to nobody. Training records exist for staff but not for volunteers, temporary staff or subcontractors. Complaints are handled well in practice but not recorded, so the yearly analysis has no numbers. The management review repeats last year's minutes. Each is easy to fix and expensive to explain at the audit. Treat the checklist above as a monthly habit, not a project in the month before the audit.

What the audit feels like in practice

Expect the auditors to ask for evidence in the order care is actually given. They may start with a client's file and follow it back: how the need was assessed, who agreed the plan, which professional delivered it, whether the plan was reviewed and what happened when something went wrong. They talk to professionals on the floor, and often to clients or their representatives. A binder that matches the practice earns trust, and a binder that contradicts it loses it. Prepare two or three client journeys in advance, with the permission and privacy safeguards the law requires, and make sure the staff who will be interviewed know the quality policy and where to find procedures. If an auditor raises a finding, answer with the cause and the corrective action, not an excuse.

A realistic timeline for a small provider

A provider of five to fifteen people, starting from a basic system, can often reach the certification audit in six to twelve months, because the records have to exist before the auditors arrive. Plan this order: scope and gap check, policy and objectives, risk analysis and processes, run them for a few months, internal audit, management review, then book the certification audit. Do not book the date first.

Using software for the gap check

Checks in nerix is in early access, and its library of about 90 frameworks includes ISO 9001. It does not include the HKZ norms, which are NEN's own text, so use ISO 9001 as a first gap check of the quality management system, then compare with your HKZ norm. nerix reads the policies and records in your library and marks each requirement Evidence found, Partly found, Not found or Can't tell, and a person confirms each one. It is readiness information, not an audit and not a certificate, and it does not replace the norm or a certification body.

The short version

HKZ is a voluntary Dutch quality mark for care and welfare, built on the ISO 9001 philosophy and written for care. Find the scheme that fits your type of provider on hkz.nl, choose an accredited certification body, run your system until it leaves records, and complete an internal audit and a management review before the certification audit. Certificates usually run three years with a yearly check.

Sources

• HKZ, part of NEN: hkz.nl, with the list of certification bodies.
• Scheme pages and certification process: Kiwa HKZ, LRQA HKZ and DEKRA HKZ, consulted 1 November 2026.

Decide whether you need it

ISO 27001 certifies your information security management system (ISMS). It is worth the effort when customers, tenders or partners ask for it, or when you hold data for others and want a clear way to run security. It is not a legal requirement in itself, and it does not make you secure. It shows that you manage security by risk, with records, and that an independent body checked.

Before you start, ask your three biggest customers what they actually want. Some accept a completed security questionnaire. Some want ISO 27001, others SOC 2, which is a different report from an audit firm, not a certificate against an international standard. If nobody asks, a lighter set of good practices may do for now.

Who does what in a small team

• Top management (the owner or a director) approves the policy, scope and risk acceptance, joins the management review and gives time. Auditors interview them.
• The ISMS owner is one named person who keeps the system running. It need not be a full time job, and in a small company it is often the technical lead or operations manager.
• Risk owners are the people responsible for each asset or process, who accept the remaining risk.
• Everyone knows the policy, completes awareness training and reports incidents.
• An internal auditor who is not auditing their own work. In a tiny team that may be an outside person for one day.

Choose a small, honest scope

The scope says which products, locations, people and systems the ISMS covers (clause 4.3). Smaller is allowed if it is real and matches what customers care about. A software team may scope the one product it hosts and the staff who work on it. You must still say how you depend on what is outside the scope, such as the cloud host and the office network.

A scope that is too wide means more controls to evidence. One too narrow may not satisfy the customer who asked. Write the sentence you would give a customer and check it is true.

A 90 day plan

This assumes one person spending roughly a day or two a week, and a team that already uses sensible tools. If you start from nothing, expect longer. Treat the weeks as a sequence, not a promise.

Weeks 1 to 2: set the frame

• Ask customers what they need, set the scope and write the context: issues and interested parties (clause 4).
• Have top management approve an information security policy (5.2) and name the ISMS owner (5.3).
• Make an asset list: laptops, phones, cloud services, code repositories, key data sets (Annex A 5.9).

Weeks 3 to 5: risk

• Choose a simple method: rate likelihood and impact on a scale of three or five, and fix the level you accept (6.1.2).
• List risks against your assets in a risk register. Twenty real risks beat a hundred generic ones. See how to run a risk register.
• Decide the treatment for each risk, and have risk owners approve the plan and accept what remains (6.1.3).
• Draft the Statement of Applicability: all 93 Annex A controls, with included or excluded, why, and whether in place.

Weeks 6 to 9: put controls and records in place

Focus on the controls your risks point to, which for a small cloud based team are usually these:

• A second factor and single sign-on or a password manager on every account that offers it (Annex A 5.15, 5.17, 8.5).
• Disk encryption, screen locks and updates on laptops and phones (7.9, 8.1, 8.8).
• Backups with a restore test you record (8.13).
• Access rights reviewed when people join, change role and leave (5.18, 6.5).
• A supplier list with the security terms of each cloud provider checked (5.19 to 5.22).
• An IT security policy, an incident response plan and a place to log incidents (5.24 to 5.27).
• Awareness training with a record per person (6.3, 7.3).
• A way to track changes, vulnerabilities and logging proportionate to your systems (8.8, 8.15, 8.32).

Everything you do has to leave a trace: a ticket, a screenshot, a signed list, a dated review.

Weeks 10 to 12: check and review

• Run the internal audit across the whole ISMS, with a written report and findings (9.2). Use the internal audit plan and read your first internal audit.
• Hold the management review with the required inputs and recorded decisions (9.3), using management review minutes and this one afternoon guide.
• Fix findings with corrective actions that address the cause (10.2).

At the end of this you are ready to book the audit. Certification bodies want to see the system running, so a few weeks of records before the audit is the minimum, and several months is common.

The certification route and what it costs

You choose an accredited certification body and agree scope and audit days. Stage 1 reviews your documented information and readiness, and stage 2 audits that the system works through interviews and samples. The certificate usually lasts three years with a surveillance audit each year, and then recertification. Audit time is planned from the number of people and the complexity in scope, following ISO/IEC 27006, so quotes differ. We do not publish audit prices because they are quoted case by case: ask two or three bodies for a written quote, including the surveillance years.

The other costs are your own time, any consultant days, a copy of the standard, and tools. A spreadsheet is enough for the ISMS of a small team. Platforms that connect to cloud accounts, such as Vanta, Drata or Secureframe, can save evidence gathering when most of your work happens in those tools. Check each on its own pricing page, because most show plans without prices.

Keeping it running after the certificate

A certificate is the start of a yearly rhythm. Put four dates in the calendar when you certify: a quarterly review of the risk register and incident log, a yearly access review, a yearly internal audit that covers a different part of the system each time, and the management review before each surveillance audit. Keep the ISMS owner's list of recurring tasks short and visible, and note the dates in the same place you keep your policies. The usual reason a small team loses its certificate is not a failed control but a year in which nobody did the checking.

What small teams can leave out

• Controls that do not apply. Without your own data centre, physical controls shrink, but you still document the exclusion with a reason.
• Long procedures. The standard asks for specific documented information, not a library. Short, used pages beat long, unread ones.
• A tool you do not need. Choose a tool once you know your evidence.

What you cannot skip: scope, policy, risk assessment and treatment, the Statement of Applicability, objectives, competence, internal audit, management review and corrective action.

Where nerix fits

Checks in nerix is in early access. "Get ready for a check" lets you pick ISO 27001 from a library of about 90 frameworks. nerix reads the policies and records in your library and marks each requirement Evidence found, Partly found, Not found or Can't tell, and a person confirms the result. The price is shown before you start. Use it before the internal audit to see which records are missing. It is readiness information only: it does not scan cloud settings, monitor controls or certify anything. Only an accredited certification body issues a certificate.

Mistakes small teams make

• Buying a policy pack and signing it unread. Staff cannot explain it to an auditor.
• Making the ISMS owner a lone hero. If they leave, the system stops. Write down what they do and train a second person.
• Booking the audit before the internal audit and management review are done.
• Saying "certified" in sales material before the certificate arrives.

The short version

Confirm that customers really want ISO 27001, then give the work to one named owner, choose a scope you can defend and follow a sequence of frame, risk, controls, check and review. Keep dated records for every step. Skip what does not apply, with a reason, and keep short documents. Only a certification body can certify you.

Sources

• ISO/IEC 27001:2022 Information security management systems, requirements, at iso.org.
• ISO/IEC 27006 on requirements for bodies certifying information security management systems, at iso.org.

It follows ISO 9001:2015, which was amended in 2024 to add climate change as an issue to consider in clause 4. Always read the standard itself, bought from ISO or your national standards body, because this is a summary in our own words and not its text. It is general guidance, not advice from a certification body.

Clause 4: context of the organisation

Questions to answer, in writing:

• Have we listed the outside and inside issues that affect our ability to deliver what customers expect (4.1)? This includes climate change if it is relevant to you.
• Have we listed the interested parties, such as customers, staff, suppliers and regulators, and what each requires of us (4.2)?
• Is the scope written down: which products, services and sites the system covers, and any requirement that does not apply, with the reason (4.3)?
• Have we identified our main processes, what goes in, what comes out, who owns each one and how they connect (4.4)?

For a ten-person company, four processes on one page (win work, deliver, support, improve) is a fair start. Do not map forty processes you do not run.

Clause 5: leadership

• Is there a quality policy, suitable to the business, that includes a commitment to meet requirements and to improve, available as documented information and communicated to staff (5.2)?
• Are roles and responsibilities assigned and understood, including who reports on how the system performs (5.3)?
• Can the owner or director show involvement, such as asking for the numbers, setting objectives and providing resources (5.1)?

Top management cannot hand this entirely to a consultant. Auditors interview the owner.

Clause 6: planning

• Have we listed risks and opportunities that could stop the system achieving its results, and decided what to do about them (6.1)? A short risk register is enough.
• Are there measurable quality objectives with a number, an owner, a date and a way to measure (6.2)? "Answer every complaint within two working days" is measurable. "Improve service" is not.
• When we change the system, do we plan it and think through the consequences (6.3)?

Clause 7: support

• Do we have the people, premises, equipment and working environment we need (7.1)?
• Where we measure with instruments, are they checked or calibrated against a reference and is there a record (7.1.5)?
• Do we know what knowledge the organisation needs and how we keep it when someone leaves (7.1.6)?
• Is each person competent for their job, with a record of training, experience or qualification (7.2)? A staff training record covers this.
• Does everyone know the policy, their effect on quality and what happens if they do not follow the system (7.3)?
• Do we know who communicates what, to whom and when (7.4)?
• Are documents and records identified, approved, protected, controlled for versions and retained (7.5)?

Clause 8: operation

This is the longest clause and where most of the daily work sits.

• Do we plan and control each process, with criteria for acceptance (8.1)?
• Do we communicate with customers, understand and review requirements before we promise anything, and record changes (8.2)?
• If we design products or services, do we plan the design, review it, verify and validate it, and control changes (8.3)? If you do not design, say so in the scope and the clause does not apply.
• Do we evaluate and choose suppliers on set criteria, monitor them and tell them what we need (8.4)? A supplier evaluation record is the usual proof.
• Do we deliver under controlled conditions, identify and trace outputs where needed, look after customer property and handle changes (8.5)?
• Do we check products and services meet requirements before release, and keep who released them (8.6)?
• Do we identify, separate and decide what to do with outputs that do not conform (8.7)?

Clause 9: performance evaluation

• Do we decide what to monitor, how, how often and who analyses it, including customer satisfaction (9.1)?
• Is there an internal audit programme covering the whole system over time, with independent auditors and reported results (9.2)? See your first internal audit step by step and the internal audit plan.
• Does top management review the system at planned intervals, with the inputs the standard lists and recorded decisions (9.3)? See a management review in one afternoon.

A worked example

A six-person print shop wants a customer to see its order process as a controlled one. It writes one process page with five steps (quote, artwork approval, print, check, deliver), names who owns each, and sets an objective of "reprint rate under 3 percent each quarter". It checks the printer's calibration every month and records it (7.1.5), approves two paper suppliers on delivery quality (8.4), and logs each reprint as a nonconformity with a cause (8.7, 10.2). Nothing here is elaborate. Each line answers a question above and leaves a record.

Clause 10: improvement

• When something goes wrong, do we react, find the cause, decide if it could happen elsewhere, act and check that the fix worked (10.2)? A corrective action report holds that chain, and corrective actions that fix the cause shows how.
• Do we keep improving, using audit results, customer feedback and the management review (10.1, 10.3)?

The documents and records the standard names

ISO 9001 asks you to keep or maintain documented information in particular places. The ones people miss are the scope (4.3), the quality policy (5.2), the quality objectives (6.2), evidence of calibration (7.1.5), evidence of competence (7.2), supplier evaluation results (8.4), who released products (8.6), nonconformities and actions taken (8.7, 10.2), monitoring results (9.1), the internal audit programme and results (9.2) and management review results (9.3). Anything else, such as work instructions, you write only where staff would otherwise do the job inconsistently.

What an auditor samples

A certification audit usually has two stages. Stage 1 looks at your documented information and readiness. Stage 2 looks at the system working: interviews, observation and samples of records, after which the certification body decides. Certificates normally run for three years with yearly surveillance audits. Have these ready and dated:

• Last year of complaints and what you did about each.
• One internal audit report, with its findings and closed actions.
• The last management review minutes with decisions and owners.
• Training and competence records for people in key roles.
• Supplier approvals and one supplier review.
• Two or three customer jobs followed from enquiry to delivery.

How nerix helps with the check before the audit

Checks in nerix is in early access. "Get ready for a check" lets you pick ISO 9001 from a library of about 90 frameworks. nerix reads the policies and records in your library and marks each requirement as Evidence found, Partly found, Not found or Can't tell, and a person confirms each result. The price is shown before you start. It shows ISO clause numbers with short topic labels of its own, not ISO's text. Its output is readiness information, not an audit and not a certificate. Only an accredited certification body can certify you. A spreadsheet with one row per clause also works for a small system.

Mistakes that cost small businesses time

• Copying a template system. Staff cannot explain procedures they did not write, and auditors ask them.
• A scope that is too wide. Cover what customers ask about, and extend later.
• No evidence of improvement. An internal audit with no findings at all looks like a missed audit.
• Objectives nobody tracks. Put the numbers on a monthly agenda.
• Claiming certification early. Say "certified" only with a certificate in hand, within its scope.

The short version

Answer the questions clause by clause, from context and scope to improvement. Keep the records the standard names, write procedures only where they help, and run one internal audit and one management review before the certification audit. Keep dated evidence as you go, because auditors sample it. A spreadsheet is enough for a small system, and only a certification body can certify you.

Sources

• ISO 9001:2015 Quality management systems, requirements, and Amendment 1:2024 on climate change, at iso.org.

Step 1: does NIS2 apply to you?

Work through these questions with your national law open next to the directive.

1. Do you operate in a listed sector? Annex I lists sectors of high criticality, among them energy, transport, banking, health, drinking water, digital infrastructure, ICT service management for business customers, public administration and space. Annex II lists other critical sectors, such as postal services, waste management, chemicals, food production, manufacturing of certain products, digital providers (marketplaces, search engines, social networks) and research.
2. Are you medium-sized or larger? As a rule the directive applies to entities at least the size of a medium enterprise under the EU definition, which means 50 or more staff or more than 10 million euros in annual turnover or balance sheet. A small or micro enterprise is generally outside, with exceptions.
3. Are you one of the entities in scope whatever the size? The directive names some, including providers of public electronic communications networks or services, trust service providers, top-level domain name registries and DNS service providers. Member states may also include small entities that are the only provider of a service in a country or that matter for public safety.
4. Are you an essential or an important entity? Large entities in Annex I are essential, others are mostly important. The security duties are the same. The supervision differs: essential entities can be checked proactively, important ones mostly after an incident or evidence.
5. Do you supply to someone who is? Article 21 requires entities to manage supply chain risk, so a big customer may put NIS2 style clauses into your contract even if you are not in scope.

If the answer to 1 and 2 (or 3) is yes, continue. If not, you may still use the measures below as a baseline, and write down why you concluded it does not apply.

Step 2: management and governance

• Management approves the cybersecurity risk measures and oversees them (Article 20).
• Members of the management body follow training so they can judge risks, and offer similar training to staff.
• Management can be held liable for infringements under national law, so a signed approval record matters.
• Register with the national authority if your country requires it, and keep the contact details current.

Step 3: the ten measures of Article 21(2)

Article 21 requires appropriate and proportionate technical, operational and organisational measures, based on an all-hazards approach. The minimum list has ten items. For each one, write what you do and keep a record.

1. Risk analysis and information system security policies. A risk assessment and an IT security policy, reviewed on a date.
2. Incident handling. An incident response plan with roles, a contact list and a way to decide what counts as significant.
3. Business continuity. Backup management, disaster recovery and crisis management. A data backup policy is a start, but add a restore test with a date.
4. Supply chain security. Security aspects of relations with direct suppliers and service providers, covering their vulnerabilities and their own practices. See supplier audits for small companies.
5. Security in acquisition, development and maintenance of systems, including vulnerability handling and disclosure. Who patches what, and how fast?
6. Assessing the effectiveness of the measures. Internal audits, tests and a review by management. See your first internal audit.
7. Basic cyber hygiene and cybersecurity training. A training record per person and date.
8. Cryptography and, where appropriate, encryption. A rule for when data is encrypted in transit and at rest.
9. Human resources security, access control and asset management. Joiners and leavers, who can reach what, an inventory of devices and systems, and a password policy.
10. Multi-factor or continuous authentication, secured voice, video and text communications, and secured emergency communications where appropriate. Switch on a second factor everywhere that offers one, starting with email and admin accounts.

Step 4: incident reporting under Article 23

A significant incident is one that has caused or can cause severe operational disruption or financial loss, or affected others with considerable damage. If you suffer one, three reports follow, to the national CSIRT or the competent authority.

If the incident is still going after a month, send a progress report and then the final one within a month of handling it. If it affects service recipients, you may also have to tell them. If personal data is involved, the GDPR has its own 72 hour clock to the data protection authority; see our GDPR checklist.

Practise this before it happens. Decide who can call it significant, who sends the early warning, and keep a post-incident review for what you learned.

A quick self-check for the first month

If you are in scope and have nothing written, do these in order. First, a one page scope note and a management sign-off. Second, switch on a second factor for email, admin and remote access, and confirm backups restore. Third, name an incident lead and a deputy, and put the authority's reporting address and phone number in the plan. Fourth, send your five most important suppliers a short security questionnaire. Fifth, book a half-day tabletop exercise ("our laptop is encrypted by ransomware on a Friday evening") and record what you decided. These five steps cover parts of measures 1, 2, 3, 4, 9 and 10, and they are the first things an authority is likely to ask about.

If you are out of scope

Write one dated paragraph saying which sector, size and national rule you checked and why you concluded NIS2 does not apply, and review it yearly or when you grow, merge or enter a listed sector. Then ask whether a customer in scope has pushed obligations down to you in a contract. Typical clauses ask for a named security contact, notice of incidents within a set time, a right to audit or a completed questionnaire, and use of a second factor. These are contract duties, not NIS2 duties, but they are real and they are the way many small suppliers meet the directive.

Step 5: evidence to keep

• The scope decision (why you are in or out), dated.
• Management's approval of the measures, and training records for management.
• The risk assessment, policies, asset list and supplier list, each with a review date.
• Test records for backup restores and incident drills.
• The incident log, including small events, and any report sent.
• The supplier assessments and signed security terms.

Your national authority sets the supervisory powers: audits, on-site inspections, requests for information and fines. The directive sets maximum fines of at least 10 million euros or 2 percent of worldwide turnover for essential entities, and at least 7 million euros or 1.4 percent for important ones, whichever is higher. National laws apply these.

Using software for the preparation

Checks in nerix is in early access and includes NIS2 in its library of about 90 frameworks. Pick it under "Get ready for a check", and nerix reads the policies and records in your library, marking each requirement as Evidence found, Partly found, Not found or Can't tell. A person confirms each result, and the price is shown before you start. It gives you readiness information, not legal advice, and it does not scan your cloud accounts, monitor systems or file reports with an authority. NIS2 is a legal duty, so your national authority and a lawyer decide whether you are in scope.

The short version

Check whether you are in scope by sector, size and national law. If you are, have management approve the measures and cover the ten items of Article 21(2) with a document and a record each. Prepare for the 24 hour, 72 hour and one month incident reports before you need them. If you are out of scope, the same list is still a sound baseline, and your customers may ask for it.

Sources

• Directive (EU) 2022/2555 (NIS2), Articles 2, 3, 20, 21, 23 and 34, Annexes I and II, on EUR-Lex.

The parts

• Objective. A short sentence on what you want, which should inspire and be clear. "Make onboarding painless for new customers."
• Key results. Two to four numbers that show whether you got there, each with a start and a target. "Cut the average time to first value from 9 days to 3."
• Initiatives. The work you do to move the numbers. They are not key results. "Rewrite the welcome emails" is an initiative, because finishing it does not prove anything improved.

Writing a good objective

1. Pick the one thing. Ask: if we achieved only one thing this quarter, what would it be?
2. Use plain words. No jargon. A new hire should understand it in one read.
3. Keep it within reach of the team. If it depends on someone outside the team, it is a wish.
4. Keep it to a period. A quarter is the usual length. A year is too long to steer by.

Writing key results that mean something

A key result has a measure, a start value and a target. Good ones count outcomes, such as customers, time, errors, money or satisfaction. Poor ones count activity, such as meetings held or posts published.

The numbers in the table are examples for illustration, not benchmarks. Use your own starting point, from your own data.

Before you commit, ask for each key result: can we measure it today, who updates it, and how often?

Size and cadence

• How many. One to three objectives per team, two to four key results each. A team of ten with five objectives has no focus.
• How ambitious. Many teams aim so that reaching about 70% is a good result. Others set targets they expect to hit. Choose one style and tell everyone, or people will argue about what 60% means.
• Weekly check in. Fifteen minutes. Each key result gets a fresh value and a one line comment, plus a confidence level: on track, at risk, off track. Spend time on the at risk ones.
• End of quarter review. Score each result, write what you learned, and decide what carries over. Then pick the next set. See also how to run a weekly planning meeting.

An example

A six person online shop.

Objective: Make the first order a great experience.

• Key result 1: Raise the share of first orders delivered on time from 82% to 95%.
• Key result 2: Cut "where is my order" emails from 60 a week to 25.
• Key result 3: Raise first order reviews with four or five stars from 70% to 85%.

Initiatives: agree delivery times with the carrier, send tracking links at dispatch, ask for a review one week after delivery. Each initiative lives as a task with an owner in your task and project tool, and the key results are updated weekly. If the numbers do not move after a month, change the initiative, not the numbers.

Mistakes to avoid

• Too many. Pick fewer and finish them.
• Using OKRs as a to do list. They are about outcomes.
• Tying them to pay. People will sandbag. Keep goals about learning and focus.
• Setting and forgetting. If nobody opens the OKRs after week one, they are decoration.
• Cascading everything from the top. In a small team, let the people who do the work help write the key results.
• Changing the target halfway to look better. If the target was wrong, note it and say why.
• Measuring people instead of the work. A number about a person invites fear. Measure the work and the customer.

Goals and key figures in nerix

nerix covers this in its Goals and figures place on Business workspaces, in the Quality group, next to Work. You add a goal in words, say how far ahead it looks (this year, several years, company or team), set a date, and place it under a bigger goal if there is one. Its status is Working on it, Reached or Dropped. A goal shows the key figures that measure it and "n% of the way there".

A key figure is what you measure, in a number, percent, money, days, hours or score, how often you look, which way is better, the target and who looks after it. Values come from three places: you type them in, they come from your records, or they come from a sheet. Starter sets are provided for customers, quality, people and safety, money and sales, and operations, and you can import a KPI sheet. A figure shows a chart, a plain reading, and whether it is on target, close or off target, and when it keeps missing it can open an action. nerix words these as goals and key figures rather than "objectives and key results", but the structure is the same: a goal in words, and numbers that measure it.

A figure is a number about the work, never a score of a person. The reading is a draft from the numbers, and the assistant does not invent values or targets. If you follow a standard such as ISO 9001, goals and measured results are also what an auditor asks for, as in our internal audit guide. See Work, Checks and Pricing.

Running the first quarter

For the first round, keep it small. In the first week, the team spends one hour choosing one objective and writing three key results with start values taken from real data. Put the page where everyone sees it, and give each key result one owner. In weeks two to twelve, hold the 15 minute check in at the same time each week and change the confidence level honestly. In week six, ask whether the initiatives are moving the numbers, and swap the ones that are not. In the final week, score the results, write down two things that worked and two that did not, and carry over only what still matters. After one quarter you will know whether your key results were measurable, whether the target was too soft or too hard, and what to do differently in the next round.

The short version

Choose one to three objectives for the quarter, each with two to four key results that measure an outcome, with a start and a target. Check in for fifteen minutes every week, with a confidence level, and review at the end of the quarter. Keep OKRs separate from pay and measure the work, not the person. Start with the OKR template and your own numbers.

Before the first pay run

Set these up once, in this order, and the monthly work becomes small.

1. Register as an employer where your country asks for it. This is usually a separate registration with the tax office or social security body.
2. Decide who is an employee. Employees go through payroll. Contractors send invoices. Getting this wrong is expensive in many countries, so use the official test, not a guess.
3. Collect the details for each person. Full name, address, tax number or national ID, bank account, start date, contract, pay rate and any tax code or form your country uses.
4. Choose a pay schedule. Weekly, every two weeks, or monthly. Some countries fix this by law or by contract. Pick one and keep it, because every change creates extra work.
5. Open a clear route for the money. Many owners keep a dedicated account for wages and tax, so the money for payroll is never spent on something else.

How one pay run works

Every pay run follows the same line, from hours to a payment.

1. Collect the inputs. Hours worked, overtime, days off, bonuses, expenses to pay back, and any change since last time such as a raise or a new bank account.
2. Work out gross pay. Salary for the period, or hours times rate, plus extras.
3. Take off the deductions. Income tax, social contributions, pension contributions, and anything the person agreed to, such as a loan repayment. The rules and rates come from your country.
4. Add the employer costs. Contributions and levies the employer pays on top. They do not appear in the person's net pay, but they are part of what the person costs you.
5. Get net pay. This is the amount that reaches the person's bank account.
6. Approve. Someone other than the person who prepared the run looks at it and signs it off.
7. Pay people and pay the authorities. Wages go to staff. Tax and contributions go to the tax office, on their deadline.
8. Give out payslips and file the reports. Each person gets a payslip. Your country may also want a report per period or per year.
9. Keep the records.

The checks that catch mistakes

Most payroll errors are not clever. They are a missing bank detail, a rate typed with an extra zero, or a leaver who was paid again. A short check before approval catches nearly all of them.

• Compare with last time. Any line that moved by a lot needs an explanation: a bonus, extra hours, a raise.
• Look for gaps. A person with no bank details, no pay set up or no hours entered.
• Check new joiners and leavers. Joiners are on the run from their start date, leavers are not on it after their last day, and final pay includes unused leave if your rules say so.
• Match the totals. The total net pay plus the tax and contributions should equal the total cost you expect.
• Two people. The person who prepares the run should not be the one who approves it. In a very small business that may be the owner and the bookkeeper, which is still better than one pair of eyes.

Who does the work: you, an accountant or software

Whatever you choose, you remain responsible as the employer. Using a provider moves the work, not the responsibility.

Payroll in nerix

nerix has a Payroll place for Business workspaces, built on the People records, and it follows the line above. You enter the first day, last day and pay day of the period, then calculate. Lines that need a look are marked, for example no bank details, no pay set up, missing hours or a big change from last time. A different person than the preparer must approve the run, and then it is finalised. A payslip shows pay, deductions and employer costs, and an employee sees only their own.

Two limits are worth knowing before you rely on it. First, nerix makes the numbers, the payslips and a bank file in XML or CSV that you upload to your bank yourself. It never pays anyone, and "Mark as paid" is only a note that a person paid. Second, the rules for deductions come from pay rule packs for a country, which go through the states Draft, Needs review, In use and Retired, so a person on your side reads and accepts the rules before they are used. Treat that review as part of payroll, and ask your accountant to look at the first run. Payroll data is private, with separate permissions to read, run, approve, export and manage. See the People and Money pages for the rest of the family, and Pricing for which plans include them.

Common mistakes to avoid

• Treating an employee as a contractor to save paperwork. The cost of putting it right can be far greater than the saving.
• Paying late to the tax office. Penalties and interest usually come on top. Put every deadline in a calendar the day you register.
• Mixing business and personal money. It makes the books hard to read and the tax return harder.
• No written record of changes. A raise agreed in a corridor and never written down is a dispute waiting to happen. Put every change in writing and date it.
• Forgetting the leave balance. Unused leave can be owed at the end of a job. Keep a clear record next to payroll, as in our guide to time off tracking.
• Sharing pay with people who do not need it. Payslips and pay rates are private. Give access only to the people who run payroll.

Records to keep

For each pay run, keep the inputs, the calculation, the approval, the payslips, the proof of payment and the filings. For each person, keep the contract, the pay history and the tax forms. Many countries ask for several years, and some ask for longer for pension or tax. Ask your tax office what applies to you, then set a reminder to delete what is past its time.

If you are also tracking costs staff paid for themselves, read expense tracking for small teams so claims reach payroll or the books in a clean way.

The short version

Payroll is a loop: collect inputs, work out gross to net, check, approve, pay, file and keep records. Set up the employer registration and staff details once, check each run against the last one, and never let one person prepare and approve alone. Choose a spreadsheet, an accountant or software by how many people you pay and how complex the rules are, and remember that you stay responsible either way.

Two questions, not one

Most confusion comes from mixing them up.

What can this person do? Invite people, change billing, create folders, delete files, export data. This is a role.

What can this person open? The payroll folder, the board minutes, one client's documents. This is access.

A good setup answers both separately. Roles are few and apply to everyone with that job. Access is set on the folders and documents that need protecting, and everything else stays open to the workspace.

Start from the principle of least privilege

Give people the access their work needs, and no more. It sounds strict, but in a small team it mostly means one decision made once: who is an admin. Many teams make everyone an admin because it is easier, then discover that anyone can delete or export everything.

A workable starting point:

Add custom roles only when a real job needs them, such as a billing manager who handles invoices but not hiring, or a support agent who answers customers but sees no finances.

Set access on the few things that need it

Resist locking everything. A workspace where every folder is private becomes a place where people cannot find the thing they need and ask an admin each time. Keep the default open, and lock a short list:

• payroll and pay reviews;
• HR files, warnings and contracts (see how to write an employee warning letter for what such files contain);
• board or partner papers;
• client files covered by confidentiality;
• security notes and passwords documentation.

Use three levels. Can view lets a person open and read. Can edit lets them change and upload. Can manage lets them also decide who else can open it. Give manage to as few people as possible.

What good tools get right

Whatever product you use, check these points, because they separate real access control from a label.

1. Limits follow into search. If someone cannot open a folder, they should not see its name in search results either.
2. Limits follow into AI answers. An assistant that answers from your documents must answer only from what the asking person can open. Otherwise a chat window becomes a way around the permissions.
3. Limits go down the tree. What is inside a limited folder is limited too, and can be narrowed but never widened.
4. Exports respect access. An export should leave out what the exporting person cannot open.
5. Nobody can grant more than they hold. A role builder that lets an admin create a role stronger than their own is a hole.
6. There is a way to see. You should be able to check what a person sees, and who can open a given folder and why.

How nerix handles it

Roles and access in nerix follows those points. Every workspace has Owner, Admin, Member, Viewer and Guest, and you can make your own role from blank, from a built-in role or from a ready-made one such as Billing manager, Library manager, Team lead, Support agent or Auditor. Nobody can build a role that can do more than they can, and a role that someone holds cannot be deleted until they have another. Preview as this role shows the app as that role would see it, read only, and you can compare two roles side by side.

On any folder or document you choose Everyone in the workspace, which is the usual, or Only these people, teams and roles, with the three levels above. A person who cannot open a folder does not see its name or contents in the library, search, the assistant's answers and sources, widgets, exports or share links. nerix answers only from what the person asking can open, and an automation reads only what its maker can open. An Access page shows the library as a tree with every limit, lets you pick a person to see what they see, or pick a folder to see everyone who can open it and why.

Two honest limits. An admin's reach is limited like anyone's: only the owner can open a limited folder as owner, with a written reason, for eight hours, recorded and with the folder's managers told. And a role made earlier does not receive a permission added later until someone adds it, which is safe but means a review after updates. Details on security and how the library is organised are on their own pages.

A review routine for twice a year

Put this in the calendar. It takes about an hour for a team of twenty.

1. List admins and owners. Is each still needed? Two owners is enough for most teams, so one person on leave never blocks you.
2. List people outside the company. Guests, contractors and former staff. Remove any whose work has ended.
3. Open the access view of each locked folder. Is the list of people still right?
4. Check leavers. Everyone who left in the period should be gone. Do this on the last day, not at the review.
5. Look for workarounds. Shared logins, files copied into open folders, screenshots in chat. They show where the rules hurt.
6. Write down what you changed. One paragraph in the same place each time.

Common mistakes

Everyone is an admin. It feels friendly and removes the point of roles.

Permissions per person. Setting rights one person at a time fails the day someone changes job. Use roles and teams.

One shared account. You lose the record of who did what, and you cannot remove one person.

Forgetting leavers. Remove access on the last working day.

Locking too much. If people cannot do their jobs they will copy files into places you do not control.

The short version

Separate what people can do (roles) from what they can open (access). Keep few roles, make members the default, lock a short list of sensitive folders and check that search, assistants and exports follow the same limits. Review twice a year and on every departure.

What a good training record holds

For each training event, per person, record:

1. Who. Name and role.
2. What. The topic or course, and the version of any procedure it was based on.
3. When. The date, and how long it took.
4. By whom. The trainer or provider, and for external courses a copy of the certificate.
5. How you checked it worked. A short quiz, watching the person do the task, or a manager's sign off after a period.
6. The result. Passed, needs more practice, or not yet competent.
7. Expiry or refresh date, if the skill needs renewing.
8. Confirmation. The person's signature, or a recorded confirmation that they took part.

The staff training record template has these columns. Start there if you use a sheet, and edit it to match how you work.

Start from what each role needs

Records are easier when you know what you are tracking against. Make a simple list:

• Required for the role. For example first aid, safe handling, data protection, a machine licence, or your own procedures.
• Required by law or by a customer. Mark these so they never lapse.
• Nice to have. Skills that help but are not required.

A training needs analysis helps you compare what each person can do today with what the role needs, and the gaps become your training plan. After the training, a training evaluation form records whether it helped.

Handling certificates that expire

Expiry dates are where most training records fail. Someone's forklift licence or first aid certificate lapses, and nobody notices until an inspector does.

• Write the expiry date in its own column, not in a note.
• Sort or filter by that date every month and list everything expiring in the next 90 days.
• Book renewals as soon as they show up on that list.
• Keep a copy of the certificate next to the record, in a folder with limited access.
• When someone leaves, keep their records for the period your rules ask for, then delete.

Policies people must read

Not all training is a course. Often you only need proof that every person read and understood a policy: the code of conduct, the safety rules, the data protection policy. The method is simple:

1. Send the document to the people who need it, with a date to read it by.
2. Ask each person to confirm that they have read and understood it.
3. Keep who confirmed and when, and who is late.
4. When the document changes, ask again.

A confirmation is weaker evidence than a test. For policies that carry real risk, add a few questions and a pass mark, and keep the results with the record.

What an auditor looks for

Whether it is an ISO 9001 audit, a customer audit or a regulator, the questions are alike. Be ready to show:

• A list of the skills each role needs.
• A record per person showing they have those skills.
• Evidence of competence, not only attendance.
• Certificates that are in date.
• What you did when someone was not yet competent, and who supervised in the meantime.

If you are preparing for a certificate, our guides to getting ready for an ISO 27001 or 9001 check and the internal audit step by step show where these records appear.

Keeping it light

Records that take an hour per person will be skipped. A few habits keep them alive:

• Add the record in the same sitting as the training, not afterwards.
• Let the trainer fill it in, and the person confirm.
• Use one place for everyone, not a folder per manager.
• Review once a month, 15 minutes, with a list of what expires soon and who has not confirmed.
• Collect only what you will use. Training records are personal data, so keep access to the managers and HR who need them.

Training records in nerix

On Business workspaces nerix has a Training and skills place, priced per person. Everyone sees a "My training" page with what is to do, the policies to read, booked sessions, their skills and certificates. Managers see a skills matrix with people against the skills a position needs, showing In place, Expires soon, Missing or Expired. Courses give skills, and you can book a session with a date, trainer and places, invite people, mark it held and note who came. Certificates take an expiry date, and an "Expiring soon" list helps you renew in time. Required skills are set per position, and each skill level is a manager's assessment.

For policies, the read and confirm feature sends a document to everyone or to chosen teams, with a read-by date and reminders, and can ask again when the document changes. A manager sees who has confirmed, who is waiting and who is late. A quiz can be added: the AI drafts questions from the document and a person checks them and sets the pass mark. The AI does not grade people or rank them. See People, Checks and Pricing for more.

A worked example

A small food business hires a kitchen assistant on 3 March. The role needs food hygiene training, safe use of the slicer and the allergen procedure. The manager adds the three required skills to the person's record. On day two the assistant completes the hygiene course online, and the certificate is saved with an expiry date three years ahead. In week one the manager watches the assistant use the slicer safely three times and signs it off as "can do alone". In week two the assistant reads the allergen procedure and confirms it, then answers five questions with a pass mark of four. When an inspector comes in the autumn, the manager opens one record and shows each skill, the date, who checked it and when the hygiene certificate runs out. Nothing was recreated for the visit, which is the point of keeping records as you go.

Mistakes that weaken a record

• Writing "trained" with no date, trainer or check, which proves nothing.
• Keeping records in each manager's own folder, so nobody can find them when someone leaves.
• Letting a certificate lapse and finding out at the inspection.
• Counting a one off talk as competence for a task that needs practice.
• Keeping the records of people who left long ago, past the period you need.

The short version

Good staff training records show who was trained, on what, when, by whom and how you know it worked. List what each role needs, record training the same day, keep certificate expiry dates in their own column and review them monthly. Add proof of competence, not only attendance, and keep the records only as long as your rules require.

Start with the jobs that repeat

A good first candidate has four traits. It happens at least weekly. It follows the same steps each time. A mistake is easy to undo. And someone currently does it from memory, which means it is sometimes forgotten.

Write down every job you did twice this month that felt like chasing. Then sort that list by two questions: how often does it happen, and what is the cost if the automation gets it wrong? Frequent and cheap to get wrong goes first. Rare or expensive to get wrong goes last, or stays manual with a checklist.

Ten routines most small businesses can automate

1. A weekly list of open and overdue tasks. Every Monday morning, one message with what is late and what is due this week. It replaces a status meeting for many teams.
2. Reminders for overdue tasks. The owner of a late task gets a nudge, and nobody has to play the nag.
3. A follow up after each meeting. When a meeting ends, send the notes and the action items to the people who were there. See meeting minutes with AI for what good notes contain.
4. Payment reminders. A polite note when an invoice passes its due date. Pair it with wording from payment reminder emails that get paid.
5. Contract renewal alerts. A message 30 or 60 days before a contract ends, so you decide on renewal instead of finding out afterwards.
6. A welcome for a new team member. The same checklist, accounts and first week plan every time. The 30 day onboarding guide gives the content.
7. A feedback round every quarter. A short survey goes out on the same day each quarter and the answers come to one place.
8. A morning brief. What is on today: meetings, deadlines, anything waiting for your answer.
9. Unanswered requests. If a customer or colleague has waited a day without an answer, flag it.
10. Month end packs. On the last working day, collect the numbers and tasks you always look at into one document.

None of these needs a custom integration. Most need only a trigger (a schedule or an event), a lookup of your own data, and one message or document.

Keep a person in the loop where it matters

The mistakes people make with automation are rarely technical. They are two kinds. The first is a rule that runs too often, such as emailing the same customer every hour. The second is a rule that sends something to people with no one looking. A few habits prevent both.

• Test run first. Run the rule on a copy or with a preview that shows what each step would do. Do not let a new rule loose on real customers on day one.
• Approval for outward messages. Anything that reaches customers or suppliers should wait for a yes from a person until you trust it. Reminders to your own team can go straight out.
• A cap. Put a limit on how many runs, messages or paid AI calls one rule can make in a month.
• A log. You should be able to see what ran, when and what it did. When something odd happens, the log is how you find out why.
• An owner. Every rule has a person who maintains it. Rules with no owner keep running long after the process changed.

What it looks like in practice

In nerix, Automations work this way. You say when a rule starts (a schedule, a date found in your data, or an event such as a file arriving, a meeting ending or a task going overdue) and what happens next, one step after another. There are ready-made recipes for several of the routines above, such as the weekly list of open and overdue tasks, overdue reminders, a follow up after a meeting, payment reminders from a workbook, contract renewal alerts, a quarterly feedback round and a morning brief.

NXFIG0X An automation runs as the person who made it, with only what that person is allowed to do. An email, signing request, post or meeting invite waits for your yes unless you switch on "Send without asking" for that one automation, and it is off by default. A test run shows what each step would do without sending anything. You can set a credit cap per run and per month, and three failed runs in a row pause the rule. Every change and run is kept in its history.

Be aware of the limits. Automations in nerix are in early access as we write this. They act inside nerix and its connected tools, so if your process lives in many outside apps, a dedicated connector service such as the ones below may reach further.

Choosing a tool

The main options for a small business, with prices read on each vendor's page on 1 November 2026. They change, so confirm before you buy.

How to decide:

• If your work sits in many different apps, pick Zapier or Make and start on the free plan.
• If you have a technical person and care about owning the data, look at n8n self-hosted.
• If the routines are about tasks, documents, meetings and people inside one workspace, a built-in tool avoids another login and another bill.

The two things to read before buying are what counts as a task or a credit (a rule with five steps may use five) and how often a free plan checks for new events. Zapier's free plan, for example, checks every 15 minutes. For deeper comparison see our guide to Zapier alternatives.

The short version

Automate what is frequent, boring and easy to undo. Test every rule, keep a person approving outward messages, cap the cost and keep a log. Start with three routines, watch them for a month, then add more. Pick the tool that already holds the data the rules need.

Prices were read from each vendor's own page on 1 November 2026. Plans change often, so open the page before you decide: Zapier, Make, n8n.

Why people look beyond Zapier

Three reasons come up again and again.

Cost grows with use. Zapier bills by task, and each action step in a Zap counts. A workflow with five steps run 200 times a month uses far more tasks than the number of runs suggests. Free is limited to 100 tasks a month.

Free plan limits. Zapier's free plan allows two-step Zaps only, so a trigger and one action. It checks for new events every 15 minutes, so it is not instant.

Control. Zapier is a hosted service. Teams with strict data rules or technical staff sometimes want to run the tool on their own server.

The options at a glance

Zapier

Good at: being the default. It connects thousands of apps, the editor is plain, and templates exist for common jobs. The page lists a free plan, a Pro plan from about 20 dollars a month (750 tasks, billed yearly), and a Team plan from 69 dollars a month (2,000 tasks, billed yearly).

Falls short: price at volume, and the free plan's two-step limit. Task counting rewards simple workflows and punishes long ones.

Make

Good at: a visual canvas where you can see branches, filters and loops, which suits flows that are not a straight line. The free plan gives 1,000 credits a month.

Falls short: it takes longer to learn than Zapier. We could not read paid plan prices on Make's own page in a form we could quote with confidence, and third party sites disagreed, so check Make's pricing page for the current figure. Also read how it counts credits before you compare costs.

n8n

Good at: control. A standard self-hosted version is available on GitHub, and cloud plans start at 20 euros a month (billed yearly) for 2,500 workflow executions. Counting whole executions rather than each step helps long workflows.

Falls short: it suits people comfortable with servers, updates and backups. The pricing page does not state the licence terms of the self-hosted edition in a way we could quote, so read the licence in the repository if that matters to you. The hosted Business plan is listed with waiting list limits.

Built-in automations

Many work tools now include their own rules, so you do not need a separate connector for jobs that live inside them. In nerix, Automations run on a schedule, around a date found in your data or when something happens such as a meeting ending, a task becoming overdue or everyone having signed.

Good at: work that stays inside one workspace, such as weekly task lists, overdue reminders, follow ups after meetings and contract renewal alerts. Anything that reaches other people waits for your yes, a test run shows what each step would do, and there are credit caps and a history.

Falls short: this is early access. It is not a general connector between thousands of outside apps, and it is not meant to be one. If your process starts in a shop system and ends in an accounting tool nerix does not connect to, use Zapier, Make or n8n for that.

How to choose

Ask four questions.

1. Where does the work live? If it moves between many separate apps, you need a connector service. If it stays in one workspace, use that workspace's own rules first.
2. How many steps and how often? Multiply steps by runs per month and compare to each plan's limit. This is the number that decides the bill.
3. Who maintains it? A visual tool in Make or Zapier needs no developer. n8n self-hosted does.
4. What goes wrong if it misfires? Prefer a tool with a test mode, an approval step for outward messages and a log.

A sensible small business path: begin on a free plan with one routine, watch it for a month, and only pay once you know the volume. Our guide to what to automate first lists ten routines that suit that first month.

The short version

Zapier is the easiest start and the widest in apps. Make is the visual option with a free plan of 1,000 credits. n8n is the choice for teams that want to host it themselves. Built-in automations cover work that stays in one tool. Count steps times runs before you compare prices, and confirm every figure on the vendor's page, since these change.

Prices checked on each vendor's own page on 31 October 2026: Otter, Rev, Happy Scribe, Sonix and Fireflies. Prices change, so confirm before you buy.

The tools side by side

Fireflies' pricing page did not show prices when we read it, so its figures come from Fireflies' own blog and are less certain. We could not read a current Trint pricing page, so we leave it out rather than guess.

Otter

Otter has a free Basic plan with 300 minutes a month, 30 minutes per conversation and a small number of imported files. Pro costs $8.33 a month per user on yearly billing or $16.99 month to month, and raises the limits to 1,200 minutes a month and 90 minutes per conversation. Business is $19.99 yearly or $30 monthly. Otter names English, Spanish, French, German, Japanese and Chinese.

Good for: regular team meetings where you want notes without effort.

Falls short: the free plan limits imports, so call recordings you upload run out quickly.

Fireflies

Fireflies lists a free plan, a Pro plan around $10 a month per seat on yearly billing (about $18 monthly) and a Business plan around $19 yearly. It accepts uploaded audio on all plans, and says it supports more than 100 languages, with some still in beta. Uploads count against your storage.

Good for: teams that want one tool across many meetings and languages.

Falls short: we could not confirm the current prices on its pricing page.

Rev

Rev has a free plan with 45 AI minutes a month, English only. Essentials is $25.49 a month on yearly billing ($29.99 monthly) with 5,000 AI minutes per user, English and Spanish, and up to three users. Pro is $47.99 a month on yearly billing ($575.88 a year) or $59.99 on monthly billing, with 10,000 AI minutes, five users and 37 or more languages. Essentials on yearly billing is $305.90 a year. Both are per seat, checked 31 October 2026. Rev also sells human transcription at $1.99 a minute.

Good for: work where a person must check the text, such as interviews or legal style records.

Falls short: more expensive than the rest per user, and the cheapest paid plan covers two languages.

Happy Scribe

Happy Scribe lists Basic at 8.50 euros a month on yearly billing (17 monthly) with 120 AI minutes a month, Pro at 19 euros yearly (29 monthly) with 600 minutes, and Business at 59 euros yearly (89 monthly) with 6,000 minutes. Extra minutes on Basic cost 0.20 euros each. It covers more than 150 languages for speech to text, and human proofreading starts at 1.75 euros a minute.

Good for: interviews and calls in many languages.

Falls short: the lowest plan has few minutes, so a busy team buys Pro.

Sonix

Sonix charges $10 an hour pay as you go, or $25 a month (billed $275 a year) for Core with 5 hours a month, Advanced at $50 with 20 hours, and Pro at $80 with 40 hours. It has no free plan, only a 30 minute trial, and covers more than 54 languages.

Good for: people whose use is uneven and who think in hours, not seats.

Falls short: an extra seat costs $25 a month on Core.

What to check before you choose

1. Minutes you really need. Add up an average month. Ten one hour calls is 600 minutes, which already passes Otter's free plan and Happy Scribe's Basic.
2. Languages. If your calls are not in English, test a real recording in your language. A long language list does not guarantee good quality in every one.
3. File or live call. Some tools join the call, some only take a file. Confirm which one you get.
4. Where the audio goes. Calls often hold customer details. Read the privacy page and see whether the audio is used to train models.
5. Consent. Tell everyone on the call that it is recorded and transcribed.

Where nerix fits

We make nerix, so weigh this accordingly. nerix can turn a meeting recording into minutes with decisions and tasks, see meetings, and you can ask questions about the text in chat. Voice transcription as a stand alone tool is marked early, so if you need a transcript of a call recording today, a dedicated tool above is the safer pick. Plans are on the pricing page.

Getting a good transcript from any tool

The tool matters less than the recording. Four habits improve every result:

1. Record close to the voice. A phone on a desk picks up the room. A headset or a phone held near the mouth gives far cleaner text.
2. Say names and numbers slowly. Spell unusual names once at the start. Say amounts and dates clearly and repeat them at the end of the call.
3. Avoid talking over each other. Crosstalk is the biggest source of errors and of mixed up speakers.
4. Add a custom word list if the tool offers one, for product names and jargon.

After the call, read the transcript once while the call is fresh. Fix names and numbers, then share the cleaned version. A ten minute check turns a rough transcript into a record you can trust.

What to do with the transcript

A transcript is raw material. The useful outputs are short: a summary of three to five lines, a list of decisions, and a list of follow up tasks with an owner and a date. Put the follow ups where the work happens, for example in a task list, and file the full text with the customer record. If you promised a customer something on the call, copy the exact sentence into the follow up email so both sides see the same words.

Keep recordings only as long as you need them. Audio of a customer is personal data in most countries, and a long archive is a risk you carry for no benefit. Set a retention period, for example 90 days for audio and longer for the cleaned notes, and delete on schedule.

Cost in practice

Take a small sales team with three people who each hold ten one hour calls a month. That is 1,800 minutes in total, or 600 minutes per person. On Otter's Pro plan at $8.33 per user on yearly billing, that is about $25 a month for the team and inside the 1,200 minute limit for each person. On Happy Scribe, 1,800 minutes is the Pro plan (600 minutes) plus extra minutes, so the Business plan at 59 euros a month on yearly billing, with 6,000 minutes shared among five seats, is the better fit. On Sonix, 30 hours a month needs the Pro plan at $80 a month, since Advanced covers 20 hours. The same need can cost three times as much depending on how the plan counts minutes, so do this sum with your own numbers before you sign.

The short version

Start with the free plan of Otter or Fireflies if your calls are regular meetings, pick Rev when a human must check the text, Happy Scribe for many languages, and Sonix when you pay by the hour. Test one real recording in each, count your minutes, and check consent before you record.

Prices checked on each vendor's own page on 31 October 2026: Zoho Invoice, Wave, Invoice Ninja, QuickBooks, Square. Fees depend on your country, so confirm on the page.

The free options side by side

Zoho Invoice

Zoho lists one free forever plan with up to 500 invoices a year, two users and three projects. Invoices carry a "Powered by Zoho Invoice" line, and accounts inactive for 180 days may be deleted. We could not confirm payment fees from its page.

Good for: a freelancer or small shop with a steady, modest volume of invoices.

Falls short: the cap of 500 invoices a year matters once you grow.

Wave

Wave's Starter plan is $0 and covers unlimited estimates, invoices, bills and bookkeeping. Card payments cost 2.9% plus $0.60 (Amex 3.4% plus $0.60). Pro at $19 a month adds automation such as bank import, and the first ten card payments each month are charged 2.9% with no fixed $0.60. Wave's page still showed an old promotion when we read it, so check the current terms.

Good for: unlimited invoicing for free, with bookkeeping in the same place.

Falls short: you must enter bank transactions by hand on the free plan, and payment fees apply.

Invoice Ninja

Invoice Ninja is free for up to five clients, with unlimited invoices and 11 templates. Pro is $14 a month or $140 a year for unlimited clients. You connect your own payment gateway, such as Stripe or PayPal, and their fees apply.

Good for: a small, stable group of clients, and people who like open source tools.

Falls short: the free plan has no reminders, bank sync or API.

QuickBooks

QuickBooks lists a free tier for one user with two invoices a month. The paid plans are full accounting software: Simple Start at $38 a month, Essentials $85, Plus $140 and Advanced $340, each often at half price for the first three months. It has no invoicing only plan on its pricing page.

Good for: businesses that will soon need full accounting and an accountant who uses it.

Falls short: the free tier is tiny and the paid price is high for invoicing alone.

Square Invoices

Square says its free plan starts at $0 and includes invoices, recurring invoices, estimates and contracts, and its invoices page says you can send unlimited invoices. Plus is marked best value, with lower card fees and a $10 cap on ACH bank transfer fees; Premium lists the lowest processing fees and 24/7 phone support. On 31 October 2026 the pages we could read (squareup.com invoices and pricing) did not show the monthly price of Plus or Premium or the per-payment fee rates, so we do not quote them. Read the fee table for your country on Square's own page.

Good for: shops that already take card payments with Square.

Falls short: the details we could confirm are thin, so read the fee table for your country.

Paying for payments

An invoice you send is free. Getting paid by card is not. PayPal lists 2.99% plus $0.49 for cards and 3.49% plus $0.49 for PayPal and Venmo. FreshBooks, a paid tool with a 30 day trial and plans from $23 a month, lists 2.9% plus $0.30 for cards. Stripe Invoicing adds 0.4% or 0.5% per paid invoice on top of its card rates. Bank transfer is usually cheapest, so print your bank details on every invoice.

Or use a template

If you send fewer than ten invoices a month, a template is enough. Our free invoice template downloads as Word or PDF, no account needed. Keep a simple list of invoice numbers, dates, amounts and paid dates, for example in a sheet. Move to a generator when you chase payments by hand every week.

How to choose

1. How many invoices and clients? Under five clients, Invoice Ninja's free plan fits. Up to a few hundred invoices a year, Zoho fits. Higher, Wave.
2. Do you take card payments? Add the fee to your price, or pay by bank transfer.
3. Do you need accounting too? Wave and QuickBooks include it. The others do not.
4. Does your country need special invoices? Tax numbers, e-invoicing and sequential numbering are national rules. Check the tool supports yours.

What a good invoice looks like

Whatever tool you use, the invoice itself decides how fast you are paid. Keep these habits:

1. A clear subject. Put what the invoice is for at the top, with the project or order name the customer knows.
2. One due date, in words and numbers. "Due 30 November 2026" is better than "net 30".
3. Payment details that work. Bank account name, number and a reference. A payment link if you accept cards.
4. Late payment terms. State any interest or fee your contract and local law allow.
5. A person to contact. An email and phone for questions, so a query does not delay payment.
6. Send it promptly. Invoice on the day the work is done or at the milestone, not at the end of the month.

If a payment is late, send a friendly reminder on the due date and a firmer one a week later. Our guide to payment reminder emails that get paid has wording for each stage.

Getting paid on time

The tool matters less than the habits around it. Send the invoice the day the work is done, not at the end of the month. Put the due date and the payment details on the first page, and name the late payment terms you actually agreed, for example "payment within 14 days". Rules on late fees and interest differ by country, so check yours before you add a charge.

Number invoices in one unbroken sequence and never reuse a number; many countries expect this, and it makes your books easier to check. Show the tax rate and amount separately if you charge tax, and keep your tax number on the invoice where the law asks for it.

A short polite reminder a few days before the due date, and another the day after, collects more than a long letter a month late. Free plans often leave out automatic reminders (Wave and Invoice Ninja do, as the table shows), so put a weekly reminder in your calendar to look at what is unpaid. Keep a PDF copy of every invoice you send, whichever tool made it, so you can leave the tool later without losing your history.

Moving later

Free tools are easier to leave if you keep your data portable. Before you pick one, check that you can export customers and invoices as CSV or PDF. Keep your invoice numbers in one unbroken series, even if you change tools, because many tax offices expect numbers without gaps. If you must switch mid year, start the new tool at the next number and write down the change date.

Also think about records. Tax rules in most countries require you to keep invoices for several years. A free account that is deleted after a period of inactivity, as Zoho warns for accounts unused for 180 days, is not a safe archive. Download a PDF copy of every invoice, or export once a quarter, and store it with your other business documents.

The short version

Free invoicing is real, but the limits differ: Zoho caps invoices, Invoice Ninja caps clients, QuickBooks caps both tightly, and Wave caps neither. Pick on your volume, expect to pay card fees, and use a template while you are small.

Prices checked on each vendor's own page on 31 October 2026: BambooHR, Factorial, Humaans and Timetastic. We could not read the current pricing pages of Gusto, Zoho People or Personio, so we do not quote them.

The tools side by side

BambooHR

BambooHR lists three plans: Core at $10 per employee a month, Pro at $17 and Elite at $25. For companies with 25 or fewer employees it quotes flat monthly rates of $250 for Core, $425 for Pro and $650 for Elite, and we could not confirm whether those are billed monthly or yearly. Core includes HR data and reporting, time off, benefits tracking and hiring basics with five job openings. Payroll is a separate add on for US employees only, priced on request.

Good for: a business of 20 to 200 people that wants one familiar HR system.

Falls short: for a very small team, the flat rate is a lot for a few people.

Factorial

Factorial shows "starts at $8 per month, per user" and builds a plan from modules. The core covers the directory, onboarding, payslip distribution, e-signature and documents. Time off, time tracking, recruitment, performance and training are separate modules, and the page shows no price for each. You need a tailored quote. We did not find a free plan.

Good for: teams that want only a few parts at first.

Falls short: you cannot see the full price before you talk to sales.

Humaans

Humaans lists Growth, Enterprise and Athena plans and shows no prices, only "talk to sales". Growth covers the directory, documents, absence, timesheets and onboarding. Hiring works through integrations with Ashby and Greenhouse.

Good for: growing, international teams.

Falls short: no prices to compare, so it is hard to judge for a team of eight.

Timetastic

Timetastic does leave and absence only: approvals, a shared calendar and a mobile app. It lists Business at $1.50 per user a month and Pro at $2.50 (its structured data shows pounds, so the currency you pay may differ), billed monthly with no minimum term. A 30 day trial needs no card. A Rota and Time Clock plan at $5.50 adds rotas and timesheets.

Good for: teams whose only problem is knowing who is off when.

Falls short: no hiring, no documents, no payroll.

What small teams really need first

Most small businesses do not need a full HR system on day one. Start with the jobs that go wrong without a system:

1. Time off. Who is away, how many days are left.
2. Documents. Signed contracts and letters in one place that you can find. See the templates for offer letters, warnings and terminations.
3. Onboarding. A checklist so a new hire gets laptop, accounts and a plan on day one.
4. Reviews and one to ones. A regular, simple routine. See feedback and surveys.
5. Payroll. Often best left to a payroll service or your accountant who knows your country.

How to choose

1. Count your people. Flat rates for 25 or fewer favour BambooHR for the small end; per user prices favour Factorial or Timetastic.
2. Ask for the full price in writing when a page shows only "from".
3. Check your country. Payroll and legal templates differ.
4. Ask where the data lives. People data is sensitive. Look for the storage region and how to export everything.
5. Try before you sign. Run a real month of time off requests.

What it really costs

A price per employee is only part of the bill. Ask about these before you compare:

• Set up or onboarding fees. Some vendors charge once to import your data.
• Modules. The base price may not include time off, hiring or reviews.
• Add ons. Payroll is the usual extra, and may be limited to some countries.
• Contract length. Annual terms are common, so a bad fit costs a year.
• Price changes. Ask how much the price can rise at renewal and with how much notice.

Here is a worked example for a company of 18 people. BambooHR's flat rate for 25 or fewer on the Core plan is $250 a month, which is about $14 per person. Factorial from $8 per user is $144 a month for the core, before the modules you add. Timetastic Business for 18 people at $1.50 is $27 a month, but covers only time off. These are not like for like, which is why the first question is always "what job do we need done?".

Data protection and trust

HR software holds some of the most sensitive data you have: addresses, bank details, health information in absence records, and performance notes. Check these points on the vendor's own pages:

1. Where the data is stored, and whether you can choose the region.
2. Who can see what. Managers should see their own team, not everyone's pay.
3. A data processing agreement, which most vendors publish.
4. Export. You must be able to download every record in a usable format.
5. Deletion. When someone leaves, can you remove their data on schedule?

If you employ people in the EU or UK, also ask how the vendor handles transfers of data outside those areas. Your own duties as the employer stay with you, even when the software is hosted elsewhere.

A simple rollout

Do not move everything on day one. A calm order is: load the people directory and contracts in week one, turn on time off in week two, add onboarding checklists in week three, and leave reviews and hiring for the next quarter. Ask two employees to try each step before you announce it. Keep the old spreadsheet read only for a month, then archive it. Staged rollouts give you time to fix mistakes before everyone sees them.

The short version

Choose BambooHR if you want public prices and a full suite, Factorial if you want to buy modules, Humaans if you are fine with sales calls, and Timetastic if time off is the whole problem. Get the full price in writing and keep an export of your data.

Download the risk register template to follow along, or use the risk assessment template for a single activity.

Step 1: Find the risks

Do not start from a blank page. Ask the team four questions and write down every answer:

1. What would stop us serving customers for a day, a week, a month?
2. What would cost us a lot of money suddenly?
3. What could hurt a person, a customer or our reputation?
4. What do we depend on that only one person or one supplier provides?

Typical small company risks: a key person leaves, a supplier fails, the main customer pays late or leaves, a laptop with customer data is lost, the system you sell from goes offline, a rule changes. Look also at past incidents, complaints and audit findings, which are real evidence of risks that already happened.

Step 2: Describe each risk clearly

A vague line cannot be managed. Write it as cause, event and effect:

• Weak: "Supplier risk."
• Better: "Our only packaging supplier is late or closes (cause and event), so orders ship late for weeks (effect)."

Step 3: Score it

Use a simple three by three scale, which is enough for a small company.

Multiply the two numbers. A score of 6 or 9 is high and needs action now, 3 or 4 needs a plan, 1 or 2 you watch.

Step 4: Decide what to do

For every risk choose one of four answers:

• Reduce it. Add a second supplier, back up the files, train a second person.
• Avoid it. Stop doing the risky thing.
• Transfer it. Insurance, a contract clause, an outside service.
• Accept it. Write down that you accept it and why, for low risks.

Write the action as a task with a date: "Find a second packaging supplier by 15 January." Track it in tasks and projects so it is not forgotten.

Step 5: Give each risk an owner

One name, not "the team". The owner watches the risk, does or assigns the action, and reports changes at the review. An owner without time or authority is not an owner, so check.

Step 6: Review on a rhythm

1. Monthly, 20 minutes. Go through the high risks and the actions due.
2. Every quarter. Re-score everything and add new ones.
3. After any incident. Did it show a missing risk or a wrong score?
4. Yearly. Feed the register into your management review.

A worked example

A six person design studio lists these risks:

Four rows, four owners, four dates. That is a working register.

Common mistakes

• Copying a generic list. The register must describe your business.
• Scoring everything high. Then nothing stands out.
• No review. An out of date register is worse than none, because it gives false comfort.
• Hiding it. The team that sees the risks every day knows them best. Share the register.

Where it connects to quality work

If you work toward ISO 9001 or 27001, the register is the document an auditor asks for first, and corrective actions often start as a risk that happened. See checks for running internal audits, and our guide on corrective actions that fix the cause.

Risk levels and what to do at each

A score only helps if it triggers action. Agree in advance what each level means:

This keeps meetings short, because you only talk about the top of the list. If more than a third of your risks are high, you are probably scoring too harshly, or the business really has a problem that needs a bigger plan than a register.

Types of risk to check

If you are stuck for ideas, walk through these groups and ask whether each applies to you:

• People. Key person leaves, illness, hiring takes too long, a safety hazard on site.
• Customers and money. One customer is most of your income, late payment, price pressure, refunds.
• Suppliers. Single supplier, price rise, delivery delays, quality problems.
• Operations. Equipment fails, stock runs out, a process depends on one spreadsheet.
• Information and technology. Lost devices, phishing, no backups, a service outage.
• Legal and rules. A new regulation, a missing licence, a contract clause you did not read.
• Reputation. A bad review, a public mistake, a complaint that spreads.
• Outside events. Weather, power cuts, transport strikes, a pandemic.

Pick the three or four that could really hurt you, not all of them.

Opportunities too

Some teams add a second column for opportunities, things that could go better than planned, such as a new market or a repeat order. It is optional, but the same scoring works, and it keeps the register from becoming a list of worries.

Records an auditor will ask for

For ISO 9001 or ISO 27001, keep evidence that risks were identified, scored, treated and reviewed. The register itself, the dates of the monthly reviews, the closed actions and the notes of the management review are the proof. You do not need a long procedure, only a register that is used. When you plan an internal audit, choose a few risks from the register and check that the action really happened. This is the simplest way to make audits useful, and it turns the register from a document into a habit.

Keep the register short enough to use

A register with 200 lines is read by nobody. For a company of 10 to 50 people, 15 to 30 live risks is normal. If you have more, group the small ones ("minor IT faults", "routine supplier delays") into one line and keep the separate lines for risks that could really hurt the business. Move closed risks to a second tab instead of deleting them, so you can show later that you looked at them.

Write each action so a stranger could tell whether it was done. "Improve backups" cannot be checked. "Test a restore of the accounts folder from last week's backup, by 15 December, Maria" can. Each action needs one named person and a date, and the next review should start with the overdue ones.

Watch for the same score everywhere. If every risk is a 3 for likelihood and a 3 for impact, the scale is not helping you decide. Ask which two risks you would fix first if you only had a week, and compare those two against each other. The order you end up with is usually more useful than the numbers.

Finally, record what you decided not to do. Accepting a risk is a legitimate choice, but write down who accepted it and why, for example "the cost of a second supplier is higher than a two week delay would cost us". That line is what you want to find when someone asks a year later.

The short version

List real risks as cause, event and effect, score each on a three by three scale, choose reduce, avoid, transfer or accept, give every risk an owner and a dated action, and review monthly. Ten good rows beat a hundred copied ones.

Use the contract termination letter template as the base.

Step 1: Read the contract

Before you write, find these clauses and copy them out:

• Term and renewal. Does it renew automatically? Many contracts roll over if you miss the window.
• Termination. For convenience, for cause, or both?
• Notice period. How many days or months, and counted from when?
• Form of notice. Letter, email, registered post, a named person or address.
• Cure period. For a breach, you may need to give the other side time to fix it first.
• Fees on exit. Early termination charges, minimum terms, return of equipment or data.

Check amendments and any order forms too. The latest version rules.

Step 2: Decide the reason

If the contract allows termination for convenience, you can say you are exercising that right and need not explain. If you end for breach, describe the breach in facts and say you gave the required chance to fix it, with dates. Do not add accusations or complaints you cannot prove.

Step 3: Write the letter

A clear letter has these parts, in this order:

1. Your name and address, the date, and the other party's name and address.
2. A subject line: "Notice of termination of [contract name] dated [date]".
3. The decision: "We give notice that we are terminating this agreement under clause 12.1."
4. The end date: "The agreement will end on 31 January 2027, which is 60 days after this notice."
5. The reason, if one is needed, in two or three factual sentences.
6. What happens next: final invoice, return of equipment, data export or deletion, handover of work.
7. A request to confirm receipt in writing.
8. Signature and role.

Keep it to one page. Be polite and firm. Do not mix in other disputes.

Example wording: "Dear Ms Lopez, under clause 9.2 of the services agreement dated 4 February 2025 between Northwind Ltd and Harbor Studio, we give 60 days' written notice of termination. The agreement will end on 31 January 2027. Please send the final invoice by 15 February 2027 and confirm in writing that you received this letter. Please also delete our files in line with clause 11 and confirm when done."

Step 4: Send it so you can prove it

• Send it the way the contract says, to the address it names.
• Use tracked post or a courier with a signature, and email a copy if allowed.
• Keep proof: the receipt, the tracking page, the sent email and a copy of the letter as sent.
• Count the notice from when the contract says it starts, often receipt, not posting. Send early to leave margin.
• Put the end date in your calendar, with a reminder a month before.

Step 5: Close out

1. Confirm the other side acknowledged the notice.
2. Pay or collect the final invoices.
3. Return equipment and get a receipt.
4. Get your data back and ask for written confirmation of deletion.
5. Cancel linked services: payments, access, subscriptions.
6. File the contract, the notice and the proofs together. Store them with the rest of your library.

Mistakes that cost money

• Missing the renewal window. The contract renews for another year.
• Wrong address or wrong channel. The notice is invalid.
• Ending too early. Some contracts have a minimum term and you owe the rest.
• No cure period for a breach. The other side says you did not follow the process.
• Vague end date. Say the exact date.
• Sending an angry letter. It can hurt you if the matter reaches a court.

Related reading

If you also sign contracts, read contract clauses to read twice before you sign, and if the other side owes you money, the payment reminder guide. To summarise the clauses of a long contract before you write, you can ask questions about the text in chat.

Ending different kinds of contract

The same steps apply, but each kind has its own points.

• Service or supplier agreement. Check minimum terms and monthly fees due to the end date. Ask for a final statement and the return of your data.
• Subscription or software. Cancel before the renewal date, not on it. Export your data first, then cancel, because access may stop at once.
• Lease or rental. Notice often has strict timing, such as to the end of a month, and a required condition for the premises. Photograph the state on the last day.
• Employment. Special rules apply, including notice periods set by law, reasons that are protected and process duties. Do not use a general template without advice. See our guide on the employee warning letter for the steps before this point.
• Consumer contract. Consumers often have cooling off and cancellation rights set by law, which can override the contract. Check what applies in your country.

Mutual termination

If both sides want to end early, you can sign a short agreement instead of a one sided notice. It should name the contract, the agreed end date, what each side pays or returns, and that neither side has further claims, if that is what you agreed. Both sign and date it. This avoids disputes about whether notice was valid, and it is often the quickest way out when the relationship has run its course.

Termination for breach

If the other side broke the contract, ending it is a bigger step than ordinary notice. Before you write:

1. Identify the clause that was broken and the facts.
2. Check if the breach is serious enough to allow ending, or whether the contract requires a warning and a time to fix.
3. Send a breach notice first if the cure period requires it, and keep the proof.
4. Wait for the period to pass. Then send the termination notice.
5. Keep calm and factual. Courts and mediators read these letters.

Because the stakes can be high, this is where a lawyer's review pays for itself.

If the other side disagrees

Sometimes the other side replies that the notice is invalid. Do not argue by email in circles. Re-read the clause, and if you were right, reply once, politely, quoting it. If the answer is still no, suggest a call and, if needed, mediation, which is usually cheaper than a court. Keep paying what you clearly owe and keep delivering what you clearly owe while the matter is open, so you stay in the stronger position.

You can ask questions about a long contract in chat, but always check the answer against the original clause, and let an adviser confirm anything that matters.

The short version

Read the notice clause, decide the reason, write one clear page with the contract, the clause, the end date and next steps, send it the way the contract demands and keep proof. Mark the renewal and notice dates in your calendar so you never have to rush again.

Use the incident report template for the form, the incident log to list every event in one place, and the post incident review for the learning meeting.

In the first hour

1. Make people safe. Treat injuries, stop the danger, call emergency services if needed.
2. Contain the event. Switch off the machine, isolate the account, secure the area.
3. Tell the right person. Your manager or the person responsible for safety or security.
4. Preserve the evidence. Take photos, keep logs, do not clean up or delete before you record.
5. Note who saw it. Names and contact details of witnesses.

What to write down

Facts first, opinions never in the same sentence. Record:

• Date, time and place.
• Who was involved and who saw it.
• What happened, in order, in plain words.
• Injuries, damage or data affected.
• What was done immediately, and by whom.
• Who was told and when.
• Photos, logs or documents attached.

Write "The forklift struck the shelf at about 10:40 and two boxes fell" rather than "The driver was careless". Leave out guesses about blame.

How to find the cause

The cause is rarely the person who happened to be there. Use the five whys:

1. A box fell on a worker. Why? The shelf was hit.
2. Why was the shelf hit? The aisle was too narrow for the turn.
3. Why was the aisle narrow? Pallets were stored in it.
4. Why were they stored there? The racks were full.
5. Why were they full? Stock levels grew and nobody reviewed the layout.

The fix now is a stock and layout review, not a warning to the driver. Stop when you reach something you can change. Talk to everyone involved, look at the place, read the procedure, and ask what would have stopped it.

Decide the actions

Sort actions into three kinds:

• Correction. Fix this event: clear the aisle, restore the data.
• Corrective action. Remove the cause so it does not return: review layout, add a rule, train.
• Preventive action. Check whether the same cause exists elsewhere.

Each action gets an owner and a date, tracked in tasks and projects. Later, check that it worked. See corrective actions that fix the cause.

Sample report in short

Security incidents

For a lost laptop, a wrong email or a suspected breach, add: what data was involved, whose data it is, whether it was encrypted, who has been told, and whether the rules in your country require telling the people or an authority. Time matters: some rules give 72 hours.

Keep a log and look for patterns

Every report goes into one log. Once a quarter, read the log: which place, which task, which time of day shows up again and again? Patterns point to the real fixes, and they are the evidence an auditor wants to see under ISO 9001 or 45001. Keep the log honest: a team that gets blamed stops reporting.

Who writes the report

The person who saw the event or the manager of the area writes the first version, ideally the same day, while memory is fresh. A second person, usually the manager or a safety or quality lead, reviews it and leads the investigation. Do not let the person involved investigate alone, and do not let the investigator be someone who might be blamed. For small companies one trusted person can review all reports, with the owner stepping in for serious events.

Types of incident to include

Define what is reportable so people know when to write one. A short list works:

• Injury or illness at work, however small.
• Near miss, where nobody was hurt but could have been.
• Property damage, including vehicles and equipment.
• Security or data event, such as a lost device, a wrong recipient or unauthorised access.
• Quality failure, where a product or service reached a customer wrong.
• Customer or visitor harm on your premises.
• Environmental event, such as a spill.

Anything that someone would want to know about next month belongs on the list.

Interviews that give you the truth

When you talk to people involved, the way you ask decides what you hear.

1. Choose a private, calm place and start by saying the aim is to learn, not to blame.
2. Ask open questions. "Tell me what happened from when you arrived" gives more than "Did you see the sign?".
3. Let them finish before asking follow ups.
4. Ask about the system. "What would have made this easier to avoid?"
5. Write notes and read the main points back to confirm them.
6. Thank them. People who feel safe tell you more next time.

Talk to witnesses separately so they do not influence each other.

Closing the report

A report is closed only when every action is done and checked. Set a date for the check, usually 30 to 90 days after the event, and ask a simple question: did the cause go away? If the same event happens again, the first fix did not work, so reopen the report and look deeper. Record the final result, the date, and who confirmed it. Share the lesson with the team in a short note, without names, so others can learn from it.

Retention and privacy

Incident reports can contain health and personal information. Keep them with restricted access, share only what each person needs, and keep them for the period your local rules require. Injury records often have a legal retention time, so ask your adviser before you delete anything.

The short version

Make people safe, contain the event, record facts and evidence, ask why until you reach a cause you can change, set owned and dated actions, check they worked and keep one log. Report to an authority first when the law says so.

Prices checked on each vendor's own page on 31 October 2026: Timetastic, BambooHR and Factorial.

What a spreadsheet does well

A sheet is free, familiar and quick to set up. A simple layout works:

• One row per person, with a yearly allowance, days taken and days left.
• A second tab with one line per request: person, start, end, days, approved by.
• A calendar tab, one column per day, so you can see clashes.

Use a leave request form so every request is written down the same way, and keep the sheet in a shared place with edit rights only for the person who manages it. See the sheet for working with tables.

Where a spreadsheet breaks

1. Balances go wrong. A person who joins in June, works four days a week or carries days over needs a formula for each case, and one wrong cell is invisible.
2. No approval trail. An email asking "is this okay?" is not a record.
3. No clash warning. Nothing tells you three people are off in the same week.
4. Public holidays. They change by country and region, and you must update them each year.
5. Privacy. A sheet shared with everyone also shows everyone's sick days. Reasons for absence can be sensitive health information.
6. One owner. When that person is away, nobody knows how it works.

What software costs

Timetastic's page shows dollars while its structured data shows pounds, so the price you pay depends on where you are. For ten people on Timetastic Business, the cost is about $15 a month at the dollar price. BambooHR's flat rate makes sense only if you also want its other HR features.

When to switch

Move from a sheet to software when two or more of these are true:

• You have more than about fifteen people.
• You have staff in more than one country or region.
• You answer "how many days do I have left?" more than once a week.
• A mistake in a balance has already caused an argument.
• You need to show records to an auditor or an inspector.

If none is true, stay on the sheet, and revisit every January when allowances reset.

Setting the rules before you track anything

Software cannot fix unclear rules. Write these down first:

1. How many days each person gets and how part time work changes that.
2. Which year you count: calendar, or from the start date.
3. What carries over, how many days, and until when.
4. How much notice a request needs, and who approves it.
5. Which public holidays count, and what happens in a busy week.
6. Sick leave and other absence types, kept separate from holiday.

Counting days correctly

Most disputes come from counting, not from the tool. Settle these points in your policy:

1. Half days. Allow them or not, and count each as 0.5.
2. Weekends and public holidays. Do they count against the allowance when they fall inside a leave period? Most employers say no.
3. Part time staff. Give the allowance in days or hours, pro rated to the contract. Hours are fairer for irregular patterns.
4. Joiners and leavers. Accrue by month worked, and settle unused days when someone leaves as the law and the contract require.
5. Sick leave. Track it separately from holiday, and limit who can see the reason.
6. Unpaid and special leave. Name the types (parental, study, bereavement) so approvals are consistent.

A short worked example: Maria has a 25 day allowance, works four days a week, which is 80 percent of full time, so her allowance is 20 days. She joins on 1 July, so she earns half for the first year: 10 days. Each of these is easy once, but across twelve people with different start dates a sheet needs a formula per row, and that is where errors creep in.

Making a sheet safer

If you stay on a spreadsheet, a few habits reduce the risk. Lock the formula cells and let only one or two people edit. Keep a separate sheet for the totals, so the numbers a manager sees are separate from the raw requests. Export a copy at the end of each month and name it with the date, so you can show the state of balances at any point. Do not put the reason for sick leave in a sheet that everyone can open, and store the file where only managers and HR can read it.

Questions to ask a tool

When you try software, test with real cases from your team, not the demo. Ask:

• Can it handle part time staff and different allowances?
• Does it show who is away on a shared calendar, and can it sync with the calendar you use?
• Can managers approve on a phone?
• How are public holidays set for each country?
• Can you export every request as a file?
• What happens to the data if you cancel?

Timetastic gives a 30 day trial with no card, which is long enough to run one full cycle of requests. Use it to compare, and decide with your team, because the people who request leave will use it more than you do.

Carry over, part time staff and leavers

Three cases cause most disputes, so decide them in writing before the first request arrives.

Carry over. Say how many unused days move into the next year, and by which date they must be used or are lost. Some countries have rules on this, so check the rules where your staff work. In a sheet, keep carried days in their own column so the balance shows where each day came from.

Part time staff. Count time off in hours, or in days of that person's own working week, not in plain calendar days. Someone who works three days a week and takes a full week away has used three of their days, not five. A sheet that counts everyone in the same days will be wrong for these people from the start.

People who join or leave mid year. Work out their share of the year's allowance from the start or end date, and write the calculation next to the number. When someone leaves with days unused or overused, the final pay may be affected, so the figure must be one you can explain. Here a tool that does the arithmetic and keeps the history saves the most argument, but a careful sheet with a note per person works too.

Whatever you use, keep the approved requests, not only the balances. If a manager says "I never approved that", you want the date and the name.

The short version

A spreadsheet is a fine start for a small team with plain rules. Switch when balances, approvals or privacy start to hurt. A dedicated tool like Timetastic costs a few dollars per user a month, and the full HR suites cost more because they do more. Write the rules first, whatever you choose, and check what your country requires you to keep.

Use the employee warning letter template for the layout.

Before you write anything

A letter should never be the first time the person hears about a problem. First:

1. Talk to them. Describe the issue, ask for their side and listen. There may be a reason you do not know.
2. Check the facts. Dates, examples, numbers, witnesses. If you cannot show it, do not write it.
3. Check the rules. The contract, the staff handbook and local law set the steps.
4. Compare cases. Treat like cases alike. A different outcome for the same issue needs a reason.
5. Think about support. Training, tools, workload or health may be part of the problem. See our guide on how to handle a performance problem fairly.

What the letter should contain

1. Names and date. Employee, writer, date, and a line saying whether this is a first, second or final written warning.
2. The issue, in facts. "On 3, 7 and 12 March you arrived more than 30 minutes late without notice" not "you have an attitude problem".
3. The standard. The rule or expectation, with where it is written.
4. Earlier conversations. The dates of any talks or earlier warnings.
5. What must change. Specific, measurable and realistic: "arrive by 9:00 or tell your manager before 8:30."
6. Support offered. What you will do to help.
7. A review date. When you will check progress.
8. The consequence. What may follow if it does not improve, stated plainly and not as a threat.
9. Their right to respond. A meeting, a written reply, and a right to be accompanied where the rules provide it.
10. How long it stays on file. Many policies set a period, such as six or twelve months.

Wording that works

• Use short sentences and plain words.
• Describe behaviour, not character.
• Stay calm. No sarcasm, capital letters or exclamation marks.
• Do not mention other staff by name.
• Keep to one issue per letter where you can.

Weak: "You are lazy and your work is always late."

Better: "The three reports due on 5, 12 and 19 March were delivered on 8, 17 and 25 March. The standard is delivery by the due date. Please deliver the April report by 5 April. If you think a deadline is not realistic, tell me at least two days before."

The meeting

Deliver the warning face to face, or by video if you must. Allow time, read the key points, let the person respond and write down what they say. Give them the letter in the meeting, ask for a signature to confirm receipt (not agreement) and keep a copy.

After the letter

• Keep your promises. If you offered training, give it.
• Check in at the review date and record the result.
• Recognise improvement. Tell the person when the problem is solved and the warning is closed.
• Store it safely. Warnings are personal data. Keep them in the personnel file with limited access and delete them when your policy says so.
• Next step. If nothing improves, the next step may be a final warning or a meeting about ending employment. Use the termination letter only after you checked the process.

Common mistakes

• Skipping the conversation and going straight to the letter.
• Mixing several unrelated problems in one letter.
• Vague wording like "improve your attitude".
• Setting a standard that nobody else is held to.
• Writing in anger and sending the same day.
• Putting it in an email chain copied to others.

For regular, calmer feedback that prevents warnings, see feedback and surveys and keep a routine of one to ones, as in run one to ones that people value.

First, second and final warnings

Many policies use stages. A rough pattern, which you should adapt to your country and contract, is:

Some conduct, such as theft or violence, can be treated as serious from the start. Even then, investigate and hear the person's side before you decide anything.

Performance or conduct

The two need different handling. A performance problem means the person cannot or does not reach the standard of the work: quality, speed, results. Support matters more here: training, clear targets, time. A conduct problem is about behaviour: lateness, rudeness, breaking rules. Here the rule and the facts matter most. The letter looks similar, but the plan differs. For performance, set a plan with checkpoints. For conduct, state what must stop.

Special cases to handle carefully

• Illness or disability. A problem may be linked to health. Ask what support is needed and get advice before you warn.
• Pregnancy, parental leave or protected reasons. Treating someone badly for these reasons is unlawful in many countries.
• Complaints and whistleblowing. Never warn someone because they raised a concern.
• Cultural and language differences. Check the person understood the rule and the letter. Offer to explain it, or provide a translation.
• Small teams. When everyone knows everyone, privacy is harder. Keep the discussion private and do not talk about it with others.

A sample paragraph set

Issue: "On 3, 7 and 12 March you arrived more than 30 minutes after your 9:00 start without telling me beforehand. Our attendance policy, section 4, requires notice before the start if you will be late."

What must change: "From today, please arrive by 9:00, or message me before 8:30 if you cannot. I will check attendance each week for the next two months."

Support: "If something is making it hard to arrive on time, please tell me, and we can look at options such as a changed start time."

Consequence: "If attendance does not improve, we may need to take further steps under the disciplinary policy, which could include a final written warning."

Response: "You are welcome to reply in writing or ask for a meeting within seven days."

Adapt these to your facts, and have someone else read the letter for tone before you send it.

The short version

Talk first, check the facts and rules, then write a short letter with facts, the standard, what must change and by when, the support you offer, a review date and the consequence. Deliver it in a meeting, keep it private, and follow up. When in doubt, ask an adviser.

This checklist follows ISO/IEC 27001:2022; the transition from the 2013 edition ended on 31 October 2025. Its 2024 amendment adds one question to clause 4: whether climate change is a relevant issue for you. At the end we compare the tools, with prices checked on 25 October 2026. This is general guidance, not legal advice: read the standard itself or work with a qualified adviser.

The checklist, clause by clause

These are not optional. For each line ask: do we do this, is it written where required, and can we show a record?

Context and scope (clause 4)

• List the internal and external issues that affect your information security, climate change included if relevant.
• List interested parties (customers, staff, suppliers, regulators) and what they require, including laws and contracts.
• Write the scope: which services, locations, teams and systems are in, and how you depend on what is outside it.

Leadership (clause 5)

• An information security policy, approved by top management and known to staff (5.2).
• Security roles and who holds them (5.3), even if one person holds several.

Planning (clause 6)

• A risk assessment method: how you rate likelihood and impact, and which level of risk you accept (6.1.2).
• The results of the risk assessment, usually kept in a risk register.
• A risk treatment plan, approved by the risk owners, who also accept the risk that remains (6.1.3).
• The Statement of Applicability (6.1.3 d), explained below.
• Security objectives you can measure, with who does what by when (6.2).

Support (clause 7)

• Proof that people with security roles are competent (7.2): training, qualifications or experience.
• Awareness: everyone knows the policy, their part in it and how to report an incident (7.3).
• Document control: versions, approval and one place for the current copy (7.5).

Operation, evaluation and improvement (clauses 8 to 10)

• Run what you planned, keep records that it ran and control what you outsource (8.1).
• Repeat the risk assessment at planned intervals and after big changes (8.2).
• Decide what you measure, how often and who looks at the results (9.1).
• An internal audit programme and its results (9.2). See your first internal audit.
• A management review with its decisions (9.3). See preparing a management review.
• Nonconformities, what you did about them and whether the fix worked (10.2), as in corrective actions that fix the cause.

Annex A: choose controls by risk

The 93 controls sit in four themes: organisational (5.1 to 5.37), people (6.1 to 6.8), physical (7.1 to 7.14) and technological (8.1 to 8.34). Check your risk treatment against the whole list, then record every control in the Statement of Applicability: included or not, why, and whether it is in place.

For a small company working in cloud services, these weigh most:

• Assets and access: an inventory of information and devices (5.9), access control and access rights (5.15, 5.18), and secure sign-in such as a second factor (8.5).
• Suppliers and cloud services (5.19 to 5.23): who holds your data and what the contract says. See supplier audits.
• Incidents (5.24 to 5.28): reporting, deciding, responding and learning.
• Law and privacy (5.31, 5.34): the data protection rules that apply where you and your customers are.
• People: screening, confidentiality agreements, awareness training and remote working (6.1, 6.6, 6.3, 6.7).
• Devices and systems: laptops and phones (8.1), malware protection (8.7), vulnerabilities (8.8), backup (8.13) and logging (8.15).
• If you build software: secure development, testing and change control (8.25 to 8.32).

Remote teams still need equipment off the premises (7.9) and the disposal of old devices (7.14).

The evidence an auditor will sample

Stage 1 of certification reviews your documents and readiness. Stage 2 checks that the system works, through interviews and samples of records. Surveillance audits follow yearly, and the certificate is renewed after three years. Have these ready and dated:

• The signed policy and the current scope.
• The risk register, the treatment plan and the Statement of Applicability, each with its review date.
• Access reviews, training records, and what happened when people joined and left.
• The supplier list with reviews and data processing agreements.
• The incident log, even with only small events, and backup restore tests.
• Internal audit reports, management review minutes and closed corrective actions.

A record made at the time beats a document written the week before the audit.

Spreadsheet, open source or a platform

A spreadsheet works for many small companies; software helps when evidence is spread across many tools. Prices were checked on each vendor's own pricing page on 25 October 2026 and change often: CISO Assistant, ISMS.online, Vanta, Drata, Secureframe, nerix. The certification audit is always a separate cost, quoted by the certification body and driven mostly by how many people are in scope.

CISO Assistant by intuitem is an open-source risk and compliance tool; Community is self-hosted, with unlimited users under the AGPLv3 licence. ISMS.online says its pricing is bespoke.

Vanta, Drata and Secureframe show plans without prices. All three connect to the tools you already use (Vanta says more than 400), monitor controls continuously and collect much of the evidence automatically. Vanta also lists audit firms you can contact, and Secureframe says it has more than 30 in-house compliance experts and former auditors.

nerix works differently. In Checks, which is in early access, "Get ready for a check" lets you pick ISO 27001 from a library of about 90 frameworks, including ISO 9001, ISO 14001, ISO 45001, GDPR, NIS2, the EU AI Act and sector packs. It adds the laws ISO 27001 needs when they apply, such as the GDPR for personal data in or for the EU, and says why. nerix reads the policies and records in your library and marks each requirement Evidence found, Partly found, Not found or Can't tell, and a person confirms each one. ISO 27001 has 118 requirements there (clauses 4 to 10 and the 93 controls), so checking them all costs 141,600 credits, about 14 euros, plus each document read for the first time. The price is shown before you start. It shows ISO clause numbers with its own short topic labels, not ISO's text, so keep your copy of the standard.

Where it falls short: nerix is not a certification body, and its result is readiness information, not an audit or legal advice. It does not connect to cloud accounts to test settings, does not monitor controls continuously and has no directory of auditors. If most of your evidence lives in cloud systems, a platform built for that saves more time. If it lives in documents and records, nerix shows the gaps before an auditor does.

Mistakes that cost small teams time

• Signing a bought policy pack unread. Auditors ask people how things work, and the answers must match the paper.
• A scope wider than you can run. Start with what customers ask about.
• Booking stage 2 before the first internal audit and management review.
• Claiming too early. "Certified" is only true with a certificate in hand, within its scope; see getting ready for an ISO 9001 or 27001 check.

The short version

Work through clauses 4 to 10 first: scope, policy, roles, risk assessment and treatment, Statement of Applicability, objectives, competence, document control, internal audit, management review and corrective action. Choose Annex A controls from your risks and give every exclusion a reason. Keep dated records as you go, because auditors sample evidence. A spreadsheet is enough for a small scope, platforms help when evidence is spread across many tools, and only a certification body can certify you.

Small teams have an advantage. You know each other, so a review can be short and honest. What you need is a simple shape that you repeat, so it is fair from person to person.

Decide what the review is for

Pick one main purpose, and say it to everyone beforehand. Common purposes are to help the person grow, to agree on goals for the next period, to recognise good work and to decide pay or promotion. These pull in different directions. A review that tries to do everything in one hour usually does none of it well.

A workable split for a small team: a development review once or twice a year, a light monthly check in, and a separate conversation about pay. Tell people which is which.

Write down what good looks like

People cannot be fairly judged against something nobody wrote down. For each role, list four to six things that matter, in plain words, with an example of good work for each. "Handles customer complaints calmly and fixes the cause" is better than "good communication".

Share the list at the start of the period, not at the end. If you have job descriptions, use them; if you do not, write the list together in the first month.

Collect before you talk

Good reviews are mostly prepared. Gather, for each person:

1. Their own view. A short self review: what went well, what was hard, what they want to learn.
2. The manager's view. Examples, not adjectives. "Delivered the new price list two days early and answered every question from sales" is evidence. "Reliable" is a label.
3. Others' views, if useful. Colleagues and people they serve can add things a manager does not see. Keep it to a few questions and a few people.
4. Facts. Goals set last time and what happened to them.

Use the same questions for everyone in the same role. That is what makes the review fair, and it makes it easier to see patterns.

Questions that work

• What did you do this period that you are proud of?
• What was harder than it should have been?
• Where did you help others, and where did you need help?
• What do you want to learn in the next six months?
• What should we start, stop or keep doing as a team?

For feedback about someone, ask for one strength and one thing to improve, each with an example. Rating scales help when they have words attached to each number. "3: does what is expected, sometimes more" is clearer than a bare 3.

Watch for the usual biases

Managers remember the last month best. Look back at the whole period, using your notes. People who are more visible look better than quiet people with the same results. Compare the work, not the personality. And a rating on one thing leaks into others, so score each area on its own.

If you do 360 feedback, remember that comments from peers are opinions to be weighed, not verdicts. Read them for themes that appear more than once.

Hold the conversation

Plan an hour. A shape that works:

1. Open by saying what you want from the hour.
2. Let the person go first on their own view.
3. Share your view, starting with what went well, then with what to change. Give one or two examples for each point.
4. Listen to disagreement. If your evidence is solid, hold your view kindly. If theirs is, change yours.
5. Agree on a few goals for the next period, each with a date and a way to see if it happened.
6. End by asking what you can do differently as their manager.

Avoid a feedback sandwich that hides the point. Be warm, but say the real thing in plain words. No review should contain a major surprise: if the problem is new to the person, the monthly talks failed, and you should say so.

After the talk

Write a short summary the same day: what was said, what was agreed, who does what by when. Send it to the person and ask them to correct anything. Our follow up after a meeting template is a good frame.

Then turn the goals into tasks with owners and dates, and check them at the monthly talk. A review that ends in a drawer is the quickest way to make the next one meaningless.

If the person asks for a raise, handle it as its own conversation, with its own preparation. Our salary review request template shows how an employee can ask clearly, which is useful for a manager to read too.

Keep it private and proportionate

Reviews are personal. Share them only with the person and the people who need to see them, and keep the written record safe. Collect only what you need. In some countries employee data has special rules, so check what applies to you.

Where nerix helps

Feedback (early access) has twelve starting forms, including a performance review, 360 feedback, a self review, a monthly one to one and a team pulse. You pick a form, change any question, choose who answers about whom and send everyone a link by email. Reminders go out before the request closes. When it closes, you see who answered, the averages and each answer, and you can ask nerix for a short written summary of themes, strengths and what to work on. It says that it is AI work, and the answers sit beside it so you can check.

Goals from the conversation can become tasks in Work with an owner and a due date. And in the chat you can ask nerix to help word a hard piece of feedback in plain, kind language. You decide what is said.

The short version

Say what the review is for. Write down what good looks like. Collect the person's view and evidence before you meet. Use the same questions for everyone. Talk, agree on goals, write them down and follow up every month.

This guide covers each of those three, with attention to the problems of small teams, where anonymity is fragile.

Decide what you want to learn

A survey with no purpose becomes a pile of numbers. Choose one topic: how people feel about workload, how well the team communicates, how meetings are going, how new people are welcomed, what gets in the way. Write the decision it will inform. "We will use this to decide whether to change how we plan the week."

Keep it short. Five to ten questions that take five minutes get more answers and more honest ones than forty questions that take half an hour.

Write questions people can answer

A few rules make a big difference.

1. One question, one idea. "Are our meetings useful and well organised?" asks two things. Split it.
2. Concrete over abstract. "In the last month, how often did you leave a meeting unsure what to do next?" beats "How is communication?".
3. Balanced scales with labels. A rating from 1 to 5 where each end is named ("never" to "always") is easier to answer than a bare number.
4. Not leading. "How great was the new schedule?" invites a polite yes. "How has the new schedule changed your week?" invites a truthful one.
5. A few open questions. "What is one thing we should stop doing?" and "What is one thing we should keep?" give you the reasons behind the numbers.
6. A way out. Let people skip any question. Forced answers get false ones.

Ask about things the team can change. A question on pay may be fine, but only if you are willing to talk about it.

Make anonymity real

People can tell when anonymity is a promise and when it is a design. For it to be real:

• Do not collect names, emails or any detail that identifies the person. Be careful with questions on role, team, age or length of service: the answers together can point to one person.
• Do not show results until enough people have answered. A threshold of three answers is a minimum; a larger team can use more.
• Do not split results by group unless every group is big enough. A result for "the two people in design" is not anonymous.
• Read open answers with care. A comment that mentions a specific event can reveal its writer. You can group comments into themes rather than quoting every one.
• Never try to find out who wrote something. Ever. If you do, the next survey will be worthless.

Say all of this at the start, in plain words: who sees what, what is collected, when results are shown. And keep the promise.

For a very small team, consider whether a survey is the right tool. With five people, a conversation in a trusted setting, or a facilitated one, may do more than a form.

Timing and sending

Pick a moment that is not the busiest week. Give people at least a week to answer, and a reminder in the middle. Tell the team why you are asking, how long it takes and when they will see results. Reminders go to everyone who has not answered, without saying who that is.

Do not ask people to complete the survey while a manager stands nearby. Let them do it on their own time, within working hours.

Share the results quickly

Within two weeks, share what you found, including what is unflattering. Do not argue with it in the first meeting. Start by thanking people, show the results simply (the averages, the spread and the themes in comments), and say what surprised you.

Then ask the team what they make of it. Often the explanation is something you could not have guessed.

Choose two or three actions

The point of a survey is change. Do not promise to fix everything. Pick two or three things that matter most and that you can do in the next quarter, say who owns each and when you will report back. Write them down and tell the team. Our follow up after a meeting template is a clean format for this.

Some answers need patience. Say so honestly: "We cannot change pay this year, here is what we can do about workload."

Run the next survey on the same questions, so you can see whether the actions helped. Keep a trend, not just a score.

Avoid the usual mistakes

• Asking and not telling. Silence after a survey is worse than no survey.
• Punishing honesty. Even a small sign of irritation spreads quickly.
• Surveying too often. If every month nothing changes, answers drop.
• Over reading small differences. A move from 3.8 to 3.9 in a team of six means nothing.
• Mixing it with performance data. The moment people think answers feed their review, honesty ends.

Where nerix helps

Feedback (early access) includes a team pulse, a weekly check in, a meeting feedback form and a customer survey among twelve starting forms. You copy one, change any question and send each person their own link by email. In an anonymous request an answer is saved with no link to the person and its time is cut to the day, and nothing is shown until at least three people have answered. When answers are split by group, the split appears only if every group is big enough. Reminders can go to the people who have not answered.

When the round closes, you see how many answered, the average per question and the answers, and you can ask nerix for a short summary of themes, strengths and what to work on. It says that it is AI work and reads only what the results page may show, so an anonymous request stays anonymous.

Turn the actions into tasks with owners in Work. In the chat, you can ask nerix to suggest neutral wording for a question you fear is leading.

The short version

Choose one topic and keep it short. Write concrete, balanced questions. Make anonymity real and say how. Share results fast, pick two or three actions with owners and ask the same questions again later.

Prices checked in October 2026 and they change, so confirm them on the official pages: Asana, Trello, ClickUp, monday.com, Basecamp.

What Asana costs

According to its pricing page, Asana's Personal plan is free for up to two users. Starter is 10.99 dollars per user a month billed annually (13.49 dollars monthly), and Advanced is 24.99 dollars annually (30.49 monthly). Enterprise plans are by quote. Asana's page also lists AI usage per plan, with a small number of AI requests per user each month and extra requests sold separately. That is worth reading if you plan to lean on AI.

The options at a glance

Trello

Good at: boards and cards that anyone understands in a minute. The free plan lists up to 10 collaborators and 10 boards per Workspace, with 250 Workspace command runs a month.

Falls short: it is a board tool first, so timelines, workload and reporting need paid plans or add-ons. Large projects can become a pile of cards.

Price: Standard is 5 dollars per user a month billed annually (6 monthly), Premium is 10 dollars annually (12.50 monthly).

ClickUp

Good at: breadth. ClickUp's Free Forever plan lists unlimited tasks and members, plus several views, with limits on storage, spaces and automations. It also sells AI as credits.

Falls short: the depth can overwhelm a small team, and the pricing page shows two different layouts for paid plans, so confirm the current ones. Its free plan has 60 MB of file storage.

Price: paid plans start from roughly 9 dollars per user a month billed yearly on one layout of the page. Check the page before you rely on it.

monday.com

Good at: colourful boards that make status obvious to people who do not live in a task tool. The free plan covers up to two seats, three boards and three docs.

Falls short: the paid plans for work management start at three users, and the features you may want, such as more views and automations, sit on higher plans.

Price: Basic 9 euros, Standard 12 euros, Pro 19 euros per seat a month, billed annually, on monday.com's euro page.

Basecamp

Good at: a calm, opinionated tool with to-dos, messages, files and schedules per project. Pricing is flat per package rather than per user. The free plan allows one project and up to three users.

Falls short: if you want boards, timelines and custom fields, Basecamp deliberately keeps it simple. Plans cap the number of active projects and users.

Price: Freelancer is 29 dollars a month (up to 5 users, 3 projects), Pro 79 dollars (up to 10 users), Pro Unlimited 199 dollars a month billed annually.

nerix

Good at: work that starts as a conversation. Tasks and projects in nerix come as a list, a board, a table or a calendar, with states, checklists, subtasks, saved views and rules. You can ask the assistant what is overdue. Because tasks live in the same workspace as team chat, meetings and documents, an action item from a meeting becomes a task with an owner and a due date, and a chat message can become a task in one step.

Falls short: nerix is not aiming at portfolio management, resource planning or the reporting depth of the dedicated tools, and the integrations list is shorter. If you run complex projects with many dependencies, test it carefully against your real plan.

Price: Free for one person (3,000 credits a month, never charged beyond that), Plus at 15 euros a month, Team at 24 euros per seat a month from three seats. Tasks themselves are part of the product, and AI work spends credits, with the price shown before you send. See pricing.

How to choose

• You want the simplest thing. Trello or Basecamp.
• You want one tool for everything and enjoy tuning it. ClickUp.
• Your team needs status to be visible at a glance. monday.com.
• Your work starts in meetings and chat. Try nerix, and read project management without the overhead.
• You are two people. Asana's free plan or any free plan will do, and the choice matters less than the habit of using it.

Pick one real project, move it, and run it for two weeks. If people stop opening the tool by week two, the tool is wrong for the team, however good its feature list.

Before you switch

Write down how your team really uses Asana: which projects, which views, which automations and who looks at what. Many teams find that they use a tenth of it, and that list is your shopping list. Export to CSV, import one project into the new tool and check that owners, due dates and subtasks arrive. Recreate only the rules you still need. Agree a single place for requests so work does not split between the old and new tools, and set a date when the old one becomes read-only.

The short version

The best Asana alternatives depend on what you are leaving: price (Trello, Basecamp), weight (Trello, nerix) or limits (ClickUp, monday.com). Every option here has a free plan with a real limit, so read it first. Move one project, run it for two weeks, and keep Asana until the new tool has earned its place.

Prices checked in October 2026 and they change. Check the official pages: ChatGPT, Claude, Google AI plans, Google Workspace, Grammarly.

What to look for

A good AI email writer should do four things. It should draft from a few facts, match your tone, reply to an email you paste in and let you change the result quickly. Beyond that, check where your data goes, what the free plan limits and whether the draft can sit in your mail client or has to be copied across.

The options at a glance

ChatGPT

Good at: a flexible assistant for drafts, rewrites, shorter versions and tone changes. The free plan includes everyday text chat, with separate limits on tools such as file uploads and image generation.

Falls short: it lives in its own window, so you copy drafts into your mail client. Free access has limits that OpenAI says can change, and its model list changes often.

Price: Free, Go at 8 dollars a month in the US, Plus at 20 dollars, Business from 20 dollars per user a month billed annually (25 monthly).

Claude

Good at: drafts that read naturally, and long email threads you paste in for a summary and a reply. Claude's free plan includes chat on web, desktop and mobile, with file creation and connections to apps.

Falls short: same as ChatGPT: a separate window, so you copy the result across. Usage limits apply on every plan.

Price: Free, Pro at 17 dollars a month billed annually (20 monthly), Team standard seats at 20 dollars per user annually, according to Anthropic's page.

Gemini and Google Workspace

Good at: drafting where you already write. Google lists Gemini in Gmail on its AI Plus plan at 4.99 euros a month, and Workspace Business Starter lists a Gemini assistant in Gmail from 7 dollars per user a month on an annual plan.

Falls short: the free Gemini plan is a chat assistant, so the Gmail features come with a paid plan, and Starter has basic access with limits on advanced features. It suits Google users more than anyone else.

Grammarly

Good at: improving what you wrote, in any app or browser box: tone, clarity, correctness. The free plan lists 100 generative AI prompts a month, Pro lists 2,000.

Falls short: it is stronger at polishing than at drafting from a pile of facts. Plan details differ by region, and its Business plan is by quote, so check the page for your country.

Price: Free, Pro at 12 euros a month on Grammarly's euro page.

nerix

Good at: emails that depend on information you already have. In Email drafts, you tell nerix who the email is for and what it should say, or paste the one you received and ask for a reply. The draft opens beside the chat with To, Subject and the message, you change it in one click and you send it when you are ready. Because nerix can also chat with your sources, a reply to a client can draw on the contract or quote in your library, with the source shown. You choose the model, and nerix.ai runs on servers in the European Union today.

Falls short: Email drafts is in early access, so expect rough edges. nerix is a workspace, not a plug-in for your mail app, and it has fewer ways of working inside Gmail or Outlook than the suite tools do.

Price: Free for one person (3,000 credits a month, never charged beyond that), Plus at 15 euros a month. An email draft spends a little of the credits, and the app shows the price before you send. See pricing.

How to choose

• You want the most flexible assistant. ChatGPT or Claude, on the free plan first.
• You work in Gmail all day. Test Gemini where you write.
• Your drafts are mostly good and need polishing. Grammarly.
• Your replies depend on contracts, quotes and notes. Try nerix.
• Your emails are sensitive. Read the data terms of each plan, and prefer EU hosting if it matters to you.

Whichever you choose, the writing basics still decide whether emails get answered. Our guide to business emails that get read and answered covers them, and prompts that give usable first drafts covers the asking. Also read how to check AI answers before you send anything with numbers or promises in it.

Habits that make any tool better

The tool matters less than the brief. Give the reader, the goal and the one action you want, in a sentence. Paste a past email of yours so the tone matches, and name anything that must not appear, such as a price or a date you have not confirmed. Ask for two versions of different length and take the better one. Read the result aloud: if you would not say it, change it. Never let an AI add a fact you did not supply, and check names, dates and amounts every time before you press send.

The short version

The best AI email writer depends on where you write: ChatGPT and Claude for general drafting, Gemini for Gmail, Grammarly for polishing and nerix for replies built from your own documents. Every one has a free plan with limits, so start there. Always read the draft, check any fact and keep sensitive details out unless the data terms suit you.

Prices checked in October 2026. Official pages: Otter, Fireflies, Fathom and Granola.

The tools side by side

Otter

Otter is one of the best known transcription tools. Its free Basic plan gives 300 transcription minutes a month, up to 30 minutes per conversation, and a small number of AI chat questions. Pro raises that to 1,200 minutes and 90 minutes per meeting. Otter lists Pro at $16.99 a month, although its page also shows promotional prices, so check the checkout for what you will pay.

Good for: people with many meetings who want a live transcript and a quick summary.

Falls short: the free plan's 30 minute cap rules out most real meetings, and the promotional pricing makes the real cost harder to read.

Fireflies

Fireflies joins meetings, records and transcribes them, and keeps a searchable library of calls. Its pricing page lists Free, Pro, Business and Enterprise. In its own published guide, Fireflies puts Pro at about $10 per seat a month billed yearly, and Business at about $19, but its pages are not fully consistent on free limits, so read the live page.

Good for: sales and customer teams who search past calls for what was promised.

Falls short: with tiers, credits and storage rules, it takes care to see what your plan includes.

Fathom

Fathom is known for a generous free plan: unlimited recordings and transcriptions and instant AI summaries. Premium is $20 per user a month, or $16 billed yearly, and adds advanced summaries, action items and a conversational assistant. Team is $19 per user ($15 yearly) with two users minimum, and Business $34 ($25 yearly) adds CRM sync and coaching metrics.

Good for: individuals and small teams who want a free tool that works from the start.

Falls short: some AI features are limited on the free plan, and the more advanced tools are aimed at sales teams.

Granola

Granola takes a different approach: it captures audio on your own device and does not join the call as a bot, which Granola lists as included on all plans. You type your own notes and it enriches them. Basic is free with 30 days of history, Business is $14 per user a month and Enterprise $35.

Good for: people who do not want a visible bot in client calls.

Falls short: free history is short, and integrations with tools like Notion and HubSpot are on the Business tier. You still need consent from the people on the call.

nerix

We build nerix, so weigh this accordingly. nerix is a workspace where meetings sit next to tasks, documents and team chat. You schedule a meeting with an agenda, take live notes and record decisions during the call, and the transcript is made when Notes is on. Afterwards you press Make the minutes: nerix writes them from the transcript and the notes, you review and approve them, and the recap with action items is emailed to the guests. Action items become tasks in Work with an owner and a due date. You can also upload a recording from elsewhere to get a transcript and minutes.

When you start a call you choose Notes on, No notes or Private, so people know what is kept. A meeting takes any video link, and the live transcript is made when you run the call with notes on. If most of your calls take place in another tool, plan on uploading recordings. Plans are in euros, with a Free plan and Plus at 15 euros a month; the AI work is paid in credits. See meetings and pricing.

Falls short: its pages describe notes for calls run in nerix and uploaded recordings, not a note taking bot for every video tool, and it has no SOC 2 or ISO 27001 yet. It makes the most sense when meetings are part of how your team works, not when you just need a transcript of calls held elsewhere.

Getting better notes from any tool

The tool matters less than the meeting. A few habits make every summary better:

• Start with the purpose. Say the goal of the meeting out loud in the first minute. The summary will be built around it.
• Say decisions aloud. "We decided to move the launch to March" is easy to pick up. A nod is not.
• Name owners and dates. Action items without a person and a deadline are the first thing a summary gets wrong or drops.
• Spell names and numbers. Repeat figures and unusual names once, because they are the most common transcription errors.
• Review within a day. Read the summary while the meeting is fresh, fix it and send it. A correction after a week helps nobody.

Privacy and consent

Recording a meeting means handling other people's voices and words. Before you adopt any tool, answer these questions:

• Who gets told? Announce the transcription at the start, every time, and respect a no.
• Where is the audio processed, and for how long is it kept? Ask the vendor in writing.
• Is it used to train models? Check the plan's terms. Business plans usually say no.
• Who can read the notes? Limit sharing to the people who were in the meeting unless the group agrees otherwise.
• Can you delete it? You should be able to remove a recording and its transcript.

How to choose

If you want a free tool to start, begin with Fathom or Otter's free plan. If you do not want a bot on client calls, try Granola. If your team searches old calls, look at Fireflies. If you want decisions and actions to flow into tasks inside one workspace, try nerix. Then run it on three real meetings and compare the notes against what you remember.

The short version

AI meeting notes save time, but only if you check them. Otter, Fathom and Fireflies are strong dedicated tools, Granola is the bot-free choice, and nerix suits teams that want minutes and action items to turn into tasks. Test two on real meetings, tell people when you transcribe, and read every summary before it goes out.

Prices checked in October 2026. Use the official pages before buying: Acrobat, NotebookLM, ChatPDF, ChatGPT and Claude.

The tools side by side

Adobe Acrobat AI Assistant

Adobe's AI Assistant sits inside the PDF software many offices already use. In Adobe's current lineup, it is included in Acrobat Studio at US$24.99 a month on an annual plan billed monthly (US$34.99 month to month), and not in Acrobat Standard or Pro for individuals. Teams pay US$29.99 per licence a month for Studio. Students and teachers can add it to Pro for US$1.99 a month.

Good for: people who already edit, sign and organise PDFs in Acrobat and want questions answered in the same place.

Falls short: it costs more than the other options here if all you want is questions and answers, and Adobe lists no free AI tier, only free trials.

NotebookLM

Google's NotebookLM, now shown by Google as Gemini Notebook, lets you gather sources in a notebook and ask questions across them. Google's help pages say free users can add up to 50 sources per notebook, and Google AI Pro raises that to 300. Each source can hold up to 500,000 words or 200 MB.

Good for: students and researchers who want to question a pile of papers, with summaries and study aids.

Falls short: it is built around notebooks, not around a business library with folders, permissions and team members, and the limits depend on which Google plan you hold.

ChatPDF

ChatPDF does one thing: you upload a PDF and ask. The free plan lets you analyse two documents a day, and a paid Plus plan removes that limit. Its site did not show a Plus price when we checked, so look at the upgrade page.

Good for: the fastest route from a single file to an answer.

Falls short: the free daily limit is tight, and a single-file tool does not help when the answer is spread over fifty contracts.

ChatGPT and Claude

You can attach a PDF to a conversation in ChatGPT or Claude and ask about it. Both have free plans and paid plans from about $20 a month, with higher limits for uploads and long documents. Claude is often chosen for long files, and ChatGPT adds data analysis and image features.

Good for: one-off questions, and people who already pay for the assistant.

Falls short: files live inside a conversation, not in a library you can search later, and you need to ask for the page reference yourself. If the file is long or scanned, check the answer against the page.

nerix

We build nerix, so judge this section accordingly. nerix keeps your PDFs, spreadsheets, presentations and scans in a document library and answers from them. Every claim carries the document and page it came from, with the passage quoted, and a setting called "Answer only from your documents" makes the assistant refuse rather than fill gaps from general knowledge. You can ask across everything at once, and it can search the web when you allow it, asking first before anything leaves your organisation.

Plans are in euros: a Free plan for one person that is never charged, Plus at 15 euros a month, Pro at 39 euros, and team plans per seat. The AI work is paid in credits, with the price shown before you send a question. See chat with sources, library and search and pricing.

Falls short: nerix is younger than Adobe or Google, it has no SOC 2 or ISO 27001 yet, and it still makes mistakes, which is why it asks you to check the sources. If you only ever read one PDF a week, a simpler tool is enough.

How to choose

• One file, one question: ChatPDF, ChatGPT or Claude is quick and cheap.
• Studying or research: NotebookLM was designed for it.
• You already live in Acrobat: the AI Assistant keeps everything in one place, at a price.
• Many documents, a team and sources: a workspace with a searchable library, such as nerix.

Two checks apply to all of them. First, open the cited page for every number, date and quote that matters. Second, read what happens to your file: where it is processed, how long it is kept and whether it trains models. For confidential material, use a plan with written terms rather than a free tool.

Getting better answers from any of them

The tool matters, but so does the way you ask. A few habits work everywhere:

• Ask for the page. End the question with "and give the page number". A tool that cannot do that is telling you something.
• Ask one thing at a time. "What is the notice period, and who can terminate?" is two questions. Ask them separately and the answers are easier to check.
• Say what you want back. A table of dates, a list of obligations or a three line summary each give a different, more useful answer than "summarise this".
• Allow "not found". Tell the tool to say so when the document does not contain the answer. This cuts the risk of a confident invention.
• Check the scan. If the PDF is a photographed page, look at the text the tool actually read before you trust a figure from it.

For long contracts, read the clauses that carry money, deadlines and liability yourself, and use the AI to find them and to explain them in plain words. It is a fast reader, not a lawyer.

The short version

To chat with PDF files, pick a tool that cites the page. ChatPDF is the quickest for one file, NotebookLM suits research, Acrobat suits Adobe users and ChatGPT or Claude work for one-off questions. nerix suits teams that need to ask across many documents with sources. Verify every answer that matters and check the data terms first.

Prices checked on each vendor's own page on 31 October 2026 (no change from our October 21 check). Official pages: Wix, Squarespace, Framer, Hostinger and Durable.

The builders side by side

Wix

Wix lists a Free plan and paid plans on yearly billing: Light at $17.77 a month, Core at $29.77, Business at $39.77 and Business Elite at $159.77, with a free domain for the first year. Connecting your own domain requires a paid plan. Wix offers an AI chat builder: you answer questions about your business, it generates a site, and you refine it by chatting or with drag and drop.

Good for: a complete builder with many apps, booking and shop features.

Falls short: with so many options, the editor can overwhelm a beginner, and prices vary by location.

Squarespace

On 31 October 2026 the page showed, for our location, Basic at 14.40 euros a month, Core at 21.60, Plus at 38.40 and Advanced at 82.80 on yearly billing, and 20.40, 28.80, 50.40 and 94.80 when you pay month to month. The page says these include an estimated VAT, so your own figure may differ. The page text does not label each figure itself; we read the lower set as yearly because of its Pay annually toggle and note about annual discounts. There is a 14 day free trial without a credit card, and the free domain applies to plans bought for an annual term (one year of registration on available domains). Its Blueprint AI asks about your business and brand, then generates a multi-page site with layout, fonts, copy and images.

Good for: a polished, design-led look, such as for studios, restaurants and portfolios.

Falls short: no permanent free plan, and less flexibility than a fully custom site.

Framer

Framer targets designers and marketers. It lists a Free plan for non-commercial use, Basic at $10 a month and Pro at $30 (its footer says prices are monthly and billed by the cycle you pick at checkout, but the page we read did not show whether $10 and $30 are the yearly or the monthly figure, so confirm at checkout), with custom domains from Basic upward, plus Enterprise on request. It includes AI credits to try on the free plan.

Good for: sharp marketing sites with strong animation control.

Falls short: it is a design tool first, so a business owner with no design habit may find it more than they need.

Hostinger

Hostinger's builder has no free plan, but it offers a 14 day free trial. Plans are listed on long terms with a low promotional monthly price and a higher renewal: Premium at $2.49 a month on a 48 month term ($119.52 paid upfront), renewing at $10.99, for up to three sites; Unlimited is $3.49 renewing at $16.99. Its AI Builder has a manual mode and an agentic mode where you build by prompting.

Good for: the lowest starting price with hosting included.

Falls short: the renewal price is several times the starting price, and the long commitment ties up your money.

Durable

Durable is built for speed. Its Free plan gives a site preview you can share, with 300 AI credits. Launch is $25 a month on the plan card and Grow $49, with a custom domain and more AI credits (1,000 and 5,000 a month). Its comparison table shows lower figures, $22 for Launch and $41 for Grow, which match the page's "Save 15%" yearly toggle; the page does not label them, so confirm at checkout.

Good for: owners who want a first site and a simple CRM without touching design.

Falls short: it is aimed at getting started fast, so look at how much control you get over design details before you commit.

nerix

We make nerix, so keep that in mind. In nerix you describe the business and it plans the pages, designs them in a look of their own, writes the code and checks every page in a real browser at phone, tablet and desktop width before you see it. Pages are real HTML with titles, descriptions, structured data and a sitemap, and a search check runs before every publish. You can ask for changes in chat, adjust spacing and text by hand, and download the whole project as a zip. See websites.

Publishing is the Websites add-on, and every plan includes a tier: Free has three live sites with a small nerix badge, and larger tiers start at 6 euros a month. Plans are in euros, see pricing.

Falls short: it is marked early, sites are published on a nerix web address today and your own domain is next, and it is not an online shop builder like Wix or Squarespace. If you need a custom domain or selling online today, choose a builder that offers it.

What AI cannot do for your site

An AI builder gives you a good first draft quickly, but a few parts of a website stay your job.

The facts. The text it writes about your opening hours, prices, services and guarantees is a guess unless you supplied the details. Wrong information on a business site costs trust and sometimes money.

The pictures. Stock or generated images rarely show your real shop, team or work. Real photos convert better, and customers notice the difference.

The words customers search. A site is found when its pages answer questions people type into a search engine. Write one page for each service, in the words your customers use, with your town or region where it matters.

The basics of trust. Add your address, phone number, company registration and the legal pages your country requires, such as a privacy policy.

The upkeep. Prices change and offers end. Put a monthly reminder in your calendar to read the site as a visitor would.

Questions to ask before you pay

Four checks save the most money. Is the price you see for yearly or monthly billing? What does the plan cost at renewal? Does the plan include your own domain, or only a free one for the first year? And can you export your pages if you leave? For search, also read our guide to a small business website with AI and SEO.

How to choose

1. Do you need to sell online? Then look at Wix or Squarespace first.
2. Do you need your own domain now? Check that the plan you want includes it.
3. How much design control? Framer gives the most, Durable the least.
4. What will it cost in year two? Compare the renewal price, not the starting offer.
5. Who will update it? Pick the tool you will actually open every month.
6. Will you write the content? No builder replaces text that answers what your customers ask.

The short version

A good AI website builder gets you a first site in minutes, but you still own the facts, the photos and the promises on the page. Wix, Squarespace and Hostinger are complete choices, Framer is for design-led sites, Durable is the quickest start and nerix builds from a chat with search checks, with limits today. Compare year-two prices, confirm the custom domain and check every page before it goes live.

Prices checked in October 2026. Vendors change plans often, so use the official pricing links before you buy.

ChatGPT alternatives at a glance

For reference, ChatGPT Business is listed by OpenAI at $25 per user a month, or $20 billed yearly, with at least two paid seats (official pricing).

Claude

Claude, from Anthropic, is popular with people who write and read a lot. It handles long documents well and tends to give measured, structured answers. Anthropic lists a free plan, Pro at $20 a month ($17 billed yearly), and Team seats at $25 a month ($20 yearly) for teams of 2 to 150. A Premium Team seat costs $125 a month ($100 yearly) for heavy users (official pricing).

Where it falls short: it is one family of models from one company, so you cannot swap in a different provider for a task. Anthropic processes content in the United States, which may matter to you for customer data.

Google Gemini

Gemini fits best where your team already lives in Google Workspace. For individuals, Google lists a free Gemini tier, then AI Plus, AI Pro and AI Ultra, with the Pro plan at 21.99 euros a month in Germany. For organisations, Gemini Enterprise Business starts from $21 per user a month, and the Standard and Plus editions from $30 (official plans).

Where it falls short: the plan names and limits are layered, so it takes care to see which one gives your team what it needs. Google describes processing as worldwide, so check the terms if you must keep data in one region.

Microsoft Copilot

If your company runs on Microsoft 365, Copilot is the natural candidate because it works inside Word, Excel, Outlook and Teams. Microsoft lists Copilot Business as an add-on at $18 per user a month on a yearly term (listed from $21, with a promotion for eligible customers) and $25.20 month to month. Copilot Chat itself is included at no extra cost with eligible Microsoft 365 plans (official pricing). We cover it in depth in our guide to Microsoft Copilot alternatives.

Where it falls short: it is an add-on to a Microsoft plan, so it only makes sense if you already pay for one. Without the paid Copilot licence, Copilot Chat cannot reach your organisation's shared data.

Mistral Le Chat

Mistral is a French company, which is why European teams look at it first. Mistral lists a free plan, Pro at $14.99 a month and Team at $24.99 per user a month, with up to 30 GB of storage per user and domain verification. Single sign-on and audit logs are on the custom Enterprise tier (official pricing).

Where it falls short: the business plans are lighter on integrations and admin controls than the largest suites, and Mistral's page does not state where Le Chat data is hosted, so ask them in writing if that decides your purchase.

nerix

We make nerix, so weigh this section with that in mind. nerix is an AI workspace rather than a single chatbot: chat that answers from your own documents with the page of each source shown, a document library, team chat, tasks, a help desk, meetings and email drafts. You choose the model per task across providers, with Mistral (processed in France) as the default and Anthropic and Google when an admin allows them; a new workspace sends its data only to providers in the EU, and an owner can lock it there.

Pricing is in euros: Free for one person, Plus at 15 euros a month, Pro at 39 euros, and team plans per seat, Team at 24 euros (three seats minimum) and Business at 42 euros (ten seats minimum). Every plan includes a monthly block of credits for AI work, the price of a question is shown before you send it, and a spending cap is on by default. See pricing and models.

Where it falls short: it is a younger product with fewer integrations than Microsoft or Google, and it does not yet hold SOC 2 or ISO 27001. Its own security page says so plainly. If your whole company is built on Microsoft or Google tools, their assistants will fit more naturally.

How to choose

Start with the tools you already pay for. A company on Microsoft 365 should test Copilot first; a company on Google Workspace should test Gemini. Both reuse the logins and files you have.

Next, decide how much the location of processing matters. If you handle personal data of people in the EU, shortlist the options that let you control it and read each vendor's data terms, not only the marketing page.

Then think about model choice. If you want one trusted model, a single-vendor assistant is simpler. If you want to use a fast model for routine work and a stronger one for hard questions, a multi-model workspace gives you that without several subscriptions.

Finally, run a two week trial with five real tasks from your own work. Compare answers, speed and the cost per person, and let your team vote.

The short version

There is no single best ChatGPT alternative for business. Claude suits long reading and writing, Gemini and Copilot suit teams already inside Google or Microsoft, Mistral suits teams that want a European company, and nerix suits teams that want answers from their own documents and a choice of models. Compare them on your own tasks, check where your data is processed, and pay only for the seats that get used.

Prices checked in October 2026. Plans, limits and model names change quickly, so treat the official pricing pages as the final word: ChatGPT, Claude and Gemini.

The three side by side

ChatGPT

ChatGPT, from OpenAI, is the best known of the three and has the largest feature list. OpenAI describes Plus at $20 a month as adding higher message limits, voice conversations, image generation, file uploads and analysis, projects, scheduled tasks, custom GPTs, expanded deep research and memory, and use of its Codex coding agent. Paid plans are ad-free, according to OpenAI. For teams, ChatGPT Business is $25 per user a month, or $20 billed yearly, with at least two seats.

Where it falls short: usage caps still apply on every plan, especially at busy times, and the model line-up changes often, so what you get under one plan name today may differ next quarter. Check the model picker in your own account rather than a review. API use for developers is billed separately from the subscription.

Claude

Claude, from Anthropic, is the choice many people make for reading long documents and for writing that sounds measured rather than flashy. Anthropic lists a free plan, Pro at $20 a month ($17 billed yearly), Max from $100 a month for heavy use, and Team seats at $25 a month ($20 yearly) for teams of two to 150.

Where it falls short: it keeps the features around the chat simpler than ChatGPT does, and it offers one company's models only. Anthropic processes content in the United States, which matters if you must keep data in Europe.

Gemini

Gemini, from Google, is the natural fit if your mail, documents and calendar are already in Google's apps. Google lists a free tier that includes image creation, Deep Research, Gemini Live, Canvas and Gems. Paid plans in Germany are AI Plus at 4.99 euros a month, AI Pro at 21.99 euros with 5 TB of storage and four times the free usage, and AI Ultra from 99.99 euros. Gemini Enterprise Business, for organisations, starts from $21 per user a month.

Where it falls short: because the plan bundles storage and several products, it is harder to see exactly what the AI part costs you. Google describes processing as worldwide, so check the terms for sensitive material.

What actually differs between them

The three are closer than the marketing suggests. For everyday questions, summaries, rewriting and brainstorming, any of them does a good job, and the differences between their latest models show up mainly on hard problems.

The differences that matter in daily life are practical:

• Where you already work. Gemini connects naturally to Google's apps. ChatGPT and Claude are separate places you go to.
• Features around the chat. ChatGPT has the most: voice, images, scheduled tasks and custom assistants. Claude keeps it simpler. Gemini adds Google's own tools.
• Writing style. Models write differently. Many writers prefer one style over another, which is a matter of taste, so test it.
• Limits. Every plan has usage caps, and how soon you hit them depends on your habits. Heavy users end up on the $100 tiers or above.
• Data terms. Where content is processed and whether it can be used to improve models differs by plan. Business plans generally offer stronger commitments than free consumer plans, so read the terms that apply to your plan.

Which one for which job

A few typical situations show how the choice plays out:

• A solo writer or consultant who reads long reports and drafts proposals: try Claude first, then ChatGPT, and keep the one whose drafts need the least editing.
• A small office on Google Workspace that wants help in mail, documents and meetings: start with Gemini, because it is already next to the files.
• Someone who wants one app for everything, including voice and images: ChatGPT has the longest feature list, so it is the easy default.
• A team that handles customer data in Europe: begin with the data terms, not the model. Shortlist the plans whose processing location and retention you can accept, and compare only those.

The model matters less than the habit. People who give clear instructions, paste the real material and ask for a check at the end get better results from any of the three than people who change brands every month.

A fourth option: choose the model per task

Because no model is best at everything, some people use more than one. You can pay for two or three subscriptions, or use a workspace that routes to several providers. nerix does the second: you pick a model per task from Mistral, Anthropic, Google and DeepSeek, or let the easy picker choose a level, and each answer names the model that wrote it. Plans are in euros, with Plus at 15 euros a month, and a free plan for one person; see pricing and models.

Be clear about the trade-offs. You use the models through nerix, so you get its feature set, not each maker's own app features such as ChatGPT's custom assistants. And nerix is a younger product without a SOC 2 or ISO 27001 certificate yet, which its security page states. Its strength is answering from your own documents, with the source page next to each claim, see chat with sources.

How to choose

1. Try all three free plans for a week on real work, not on test puzzles.
2. Use ten of your own tasks, including two hard ones, and put the answers side by side.
3. Count the limits. If you hit the free cap daily, price the paid plan; if not, stay free.
4. Check data terms for the plan you would buy, especially for customer or staff information.
5. Pick one for a month, then review. Switching is cheap, because you keep nothing locked in except your habits.

The short version

ChatGPT, Claude and Gemini are close in price and all have a free plan. ChatGPT has the most features, Claude is often preferred for long documents and careful writing, and Gemini suits Google users. Choose by testing them on your own tasks, check where your data is processed, and consider a multi-model tool if you want to choose per task instead of per brand.

Using AI well is mostly a habit of checking. It is not hard, and it takes less time than doing everything by hand. The routine below shows how to check AI answers quickly, and which ones always need a human.

Know why answers go wrong

Understanding the causes helps you spot the risk.

1. It guesses. An assistant predicts likely words. When it does not know, it can still produce something plausible.
2. Its knowledge has an end date. It may not know recent events, prices, laws or changes.
3. It lacks your context. It does not know your customers, contracts or agreements, unless you give them.
4. It can misread your documents, especially long, scanned or badly formatted ones.
5. Your question may be ambiguous, and it will answer one reading without telling you.
6. It tends to agree. If your question assumes something false, it may go along with it.

None of this makes it useless. It means you treat the output as a draft from a quick colleague who sometimes bluffs.

Ask it to answer from your documents

The safest way to get a factual answer about your business is to base it on your own documents. Put the contract, the price list or the policy in a library and ask the assistant to answer from them. An answer tied to a page lets you open that page and read the exact words.

If the assistant says the documents do not contain the answer, that is a good result, not a failure. It is better than a guess.

Use sources, then read them

Where an answer comes with sources, use them. Click through and check:

• Does the source exist, and is it the right one?
• Does it say what the answer claims, or something near it?
• Is it recent enough, and from a reliable place?
• Does the quoted passage keep its meaning in context?

It is common for an answer to be roughly right but with one detail changed. The check is to find the sentence in the source and compare it to the claim. For web answers, prefer original sources, such as an official page, over summaries of summaries.

Know what to double check

Not everything needs the same care. Verify the things where an error costs the most:

• Numbers. Prices, totals, percentages, dates, dosages, dimensions.
• Names and titles, of people, companies and products.
• Legal and tax statements. Rules vary by place and change over time.
• Quotations and citations. Make sure the person said it and the source exists.
• Anything about safety, health or money.
• Claims that sound too neat. A very specific statistic with no source is a warning sign.

For low stakes text, such as a friendly reminder, a light read is enough.

Ask the assistant to help you check

You can use the assistant on its own output, carefully:

• "Which parts of this answer come from the documents, and which are your own knowledge?"
• "List each factual claim in your draft and the source for each."
• "What would need to be true for this to be wrong?"
• "Where are you least sure?"

These do not replace your own reading, but they often surface weak points. Treat its "I am sure" with caution.

Test with a case you know

When you start using AI for a task, try it on a case where you already know the answer. Check ten of them. You will learn where it is strong and where it slips, which is more useful than any general advice. Repeat the test when you switch to a different model, since they differ in care and style. Our post on choosing an AI model for the job explains how to think about it.

Keep a human in charge of decisions

AI can draft, summarise, search, compare and suggest. A person decides, signs and sends. For anything that affects a customer, an employee, a contract, a payment or a person's rights, a human reads it first and takes responsibility. If a decision about a person is involved, a person must make it, and the person affected should be able to ask why.

Never send an AI draft to a customer unread. Never paste in confidential or personal data unless you know how it is handled. Our post on keeping your data in the EU covers what to ask.

Create team habits

A few simple rules, written on one page, protect a team:

1. Say when text was drafted with AI if it matters to the reader.
2. Check every number and name before it leaves the building.
3. For facts about our business, use our documents.
4. Keep the sources with the output.
5. When in doubt, ask a person who knows.

Encourage people to report when AI gets something wrong, so the team learns where the risks are.

Where nerix helps

In the chat, nerix answers from your own documents and from the web, with the sources shown, so you can open the page each sentence came from. Your documents live in the library, where you control what is there. You can choose among several models for different jobs, a quicker one for light tasks and a more careful one for work that matters.

nerix can still be wrong. The sources are there so you can check, and the final decision is yours.

The short version

Treat AI output as a draft. Base factual answers on your own documents and read the sources. Verify numbers, names, legal points and quotes. Test on cases you know, and keep a person responsible for every decision.

Start from the task, not the model

Models differ, but the task decides what matters. Ask four questions first:

1. How hard is it? A simple rewrite, a lookup and a summary of a short note are easy. A long contract review, a tricky calculation or a multi-step plan is hard.
2. How much text goes in? A paragraph is small. A fifty-page report is large, and some models handle that far better than others.
3. How much does a mistake cost? A slightly awkward email costs nothing. A wrong clause in a contract might cost a lot.
4. How sensitive is the text? Public marketing copy is different from customer records or legal documents.

The answers point you towards a level of model, and a place where it should run.

Three levels are enough for most work

Rather than comparing models one by one, think in three levels. nerix uses the same idea in its Easy picker: Fast, Balanced and Best.

• Fast: quick and cheap. Good for everyday questions, short rewrites, quick summaries, classification and anything you will skim.
• Balanced: a good default for most work: drafting documents, answering from your files, writing emails, analysing a report.
• Best: the most capable and the most expensive. Use it for hard questions, long documents, careful analysis and tasks where a mistake is costly.

Start at Balanced. Move down to Fast when answers are consistently good enough, because you save credits and time. Move up to Best when you see mistakes in reasoning, missed details in long documents or flat, generic writing where you need depth.

Where your text is processed

Choosing a model also means choosing who handles your text, and in which country. This matters for confidentiality, for customer contracts and for rules such as the GDPR.

In nerix, the Easy picker lets you choose where your text is processed: Anywhere, Europe, United States, China or Worldwide, as offered. nerix then picks a model and says which company answers. Some practical points:

• If you work with personal data of people in the EU, prefer Europe, and read your own obligations. Your customers may ask where their data goes.
• Providers differ. Mistral's models are processed in France, in the EU. OpenAI and Anthropic process in the United States. DeepSeek's own API processes data in China, and nerix prints a caution on its picker. Google's processing is worldwide.
• Your workspace can limit providers. Owners and admins choose which companies may answer for their workspace, and can restrict it to ones hosted in your region.

The Security page lists where each provider processes content today. If a provider's location or terms are not acceptable for a type of content, do not allow it for that workspace.

Look at cost honestly

Every answer costs something. In nerix, credits pay for every answer, web search and export, and each answer shows its cost. Larger models cost more per answer, so running everything on the Best level can empty your credits quickly with little benefit.

A sensible habit:

• Use Fast for volume: summarising many short items, tagging, drafting routine replies.
• Use Balanced for your daily work.
• Keep Best for the questions that deserve it, and check whether the answer is actually better.

Look at what a typical week costs and adjust. A small saving per answer becomes large across hundreds.

Speed and length

Larger models usually answer more slowly. For a quick back-and-forth, that delay is annoying. For a one-off report, it does not matter. Match the model to the way you work.

Also check how much text a model can handle at once. If you need to ask questions about a long document, make sure the model can read enough of it, or use a system that finds the relevant passages first, so the model reads only what it needs. In nerix, library answers use the relevant passages from your files and show their sources.

What the model is good at

Models have different strengths. Some are better at writing in a natural voice, some at code, some at step-by-step reasoning, some at working across languages. Maker websites will tell you their model is excellent at everything. Treat that as marketing.

The only evidence that counts is how a model does on your work. Which brings us to the test.

Test with your own examples

Before you settle on a model for a recurring task, run a small test:

1. Collect ten real examples of the task, including two or three difficult ones.
2. Run them on two levels, for example Balanced and Best.
3. Compare the answers side by side. Are they correct? Complete? In the tone you want?
4. Check the details. Names, numbers, dates and sources.
5. Decide. If the cheaper level is good enough on all ten, use it. If it fails on the hard ones, use the better one only for those.

Do not judge by one answer. Models vary from run to run, and one good or bad result tells you little.

Let the system choose, and know when to choose yourself

For most people, the Easy picker is the right place to start: you say how good and where, and nerix chooses. Every answer names the model that wrote it, so you can see what is happening and change it.

Choose an exact model yourself, with the Advanced picker, when you have a reason: a policy that requires a specific provider, a task where you have tested one model and know it works, or a need to compare. Each model shows its level and roughly how many credits an answer costs, so the trade-off is visible.

Questions to ask about any model

If you are evaluating a model or a provider, ask:

• Where is my text processed?
• Is it used to train models, and can I stop that?
• How long is it kept?
• What does it do badly?
• What does it cost per answer at my usage?
• What happens if the provider is unavailable?

In nerix, your documents are never used to train a model, by nerix or by a provider. Check any other tool you use against the same question.

The short version

Match the level to the difficulty: Fast for easy and frequent, Balanced for most work, Best for hard and costly-to-get-wrong. Choose where the text is processed according to how sensitive it is. Watch the cost. Test with your own examples. And prefer a tool that tells you which model answered, so you are never guessing.

This is not legal advice, and the rules differ from one country to another. It is a reading guide to the contract clauses that cause the most surprises, what they mean in plain words, and what to ask about each before you sign anything.

How to read a contract you did not write

Read it twice, with different questions each time.

1. First pass: what do I get, and what do I give? Ignore the small print. Check that the work, the price, the dates and the people are what you discussed.
2. Second pass: what if it goes wrong? Now read the clauses about payment, changes, ending, blame and disputes. Imagine the worst realistic day and see who carries the cost.

Write down your questions as you read. A short list of marked clauses with a reason for each is far more effective than a general "can we look at the terms?".

Payment terms

Look for the due date, the way it is counted ("30 days from invoice" or "30 days from approval"), late fees, and any right to hold back money. If you are the one being paid, check that nothing lets the other side delay payment until a third party has paid them. If you are the one paying, check what you must do to dispute an invoice and by when.

Automatic renewal

A contract for a year can quietly become a contract for another year. Find the renewal clause, the notice period and the way notice must be given (by email, by post, to which address). Put the last day to give notice into your calendar when you sign, with a reminder a month ahead. If the term is long, ask for a right to leave early with a modest notice.

Changes to price and scope

Some contracts let one side change prices or terms by announcing it. Check whether the change needs your agreement, and what you can do if you do not accept: leave without a fee, or stay on the old terms until the end of the period. For your own contracts, our contract amendment template is the clean way to record an agreed change instead of relying on emails.

Ending the contract

Read both the right to end and the cost of ending. Questions to ask:

• Can either side end it without a reason, and with how much notice?
• What do I pay for work already done or goods already ordered?
• Are there fees for leaving early, and are they in proportion?
• What must the other side give back, such as data, files and equipment?

If you need to end an agreement, a short, polite and exact letter does the job. The contract termination letter template has the parts a notice needs.

Liability and indemnity

These two clauses decide who pays when something breaks. A limitation of liability caps what one side can be made to pay, often at the fees under the contract. An indemnity makes one side pay for another's costs if certain things happen, such as a claim from a third party.

Check three things: is the cap mutual, is it a sensible amount for the risk, and is the indemnity limited to things you control? A one sided, unlimited indemnity in a small contract is a reason to stop and ask.

Intellectual property

If you are paying for something to be made, who owns it, and when? If you are supplying material, what may the other side do with it? Look for words such as "assigns all rights", "work for hire" and "licence". Ask whether you may keep using the result if you stop paying, and whether the maker may reuse parts of it.

Confidentiality and data

Check that the duty is mutual, that it has an end (often a number of years), and that it has the usual exceptions for information that is already public. If personal data of customers or staff will be handled, look for a clause about how it is protected and where it is kept. Our post on keeping your data in the EU explains what to ask a supplier.

Service levels and guarantees

If the contract promises response times, uptime or delivery dates, look at what happens when they are missed. A promise without a consequence is a wish. A consequence without a reasonable limit is a trap. The service level agreement template shows the usual shape: what is measured, the target, and the remedy.

Governing law and disputes

This clause says whose law applies and where disagreements are settled: a particular court, or arbitration. For a small business, a distant court or an expensive arbitration can make a good claim not worth bringing. If the place is far from you, ask for your own location, or for a simple first step such as a meeting between named managers.

The entire agreement clause

"This agreement is the entire agreement between the parties" means that promises made in emails and calls but not written in the contract may not count. If someone promised you something in the sales conversation, make sure it is in the document.

What to do with your questions

Send your list in one message, not drip by drip. For each point, say what you want changed and the reason in a sentence. Offer a middle path where you can. Keep the tone friendly: the other side usually wants the deal too.

Record what is agreed in the document itself, with a new version number, and sign the final version. Do not rely on a side email to change a signed term.

Where nerix helps

Upload the contract to your library and ask nerix questions about it in the chat: "What is the notice period to end this?", "Does it renew automatically?", "Which clauses limit our liability?" Answers come with the page they were taken from, so you can read the exact words yourself.

That is a way to find the clauses faster, not a replacement for judgment. nerix can miss things and cannot know your situation or your law. For large amounts or unusual terms, ask a lawyer to review it.

The short version

Read once for the deal and once for the bad day. Pay special attention to payment, renewal, ending, liability, ownership and disputes. Ask for changes politely and in writing, and put the final terms in the signed document.

Fixing the thing in front of you is necessary and not enough. A corrective action changes how the work is done so that this kind of problem becomes rare. It is one of the most useful habits a small business can have, and it does not need to be complicated.

Six steps, in order

1. Describe the problem. Plain facts: what, where, when, how it was noticed, who or what was affected.
2. Contain it. Stop it getting worse and put the customer right.
3. Find the cause. Ask why until you reach something you can change.
4. Decide the action. One or a few changes, each with an owner and a date.
5. Do it.
6. Check that it worked, after enough time has passed to see, and close it.

Most failures happen at steps 3 and 6: people stop at the first answer, and nobody checks later.

Describe the problem without blame

Write the facts in one or two sentences: "On 4 March, order 1182 was shipped with the blue model instead of the green. The customer wrote on 7 March." Leave out guesses and adjectives. A problem described as "John was careless" gets defended. A problem described as "the order sheet lists colours by code, and the codes for blue and green differ by one digit" can be fixed.

Contain first

Containment is what you do today: send the right item, refund, apologise, warn the people affected, check whether other orders have the same problem. If the customer needs a message, a short, honest apology works better than a long one. The customer apology email template gives the shape: say what happened, say what you are doing about it, say what happens next.

Check for others. If one order had the wrong colour, look at the others packed in the same batch.

Find the cause by asking why

The classic method is simply to ask "why?" and keep going. Example:

• Why was the wrong item sent? Because the packer picked the blue box.
• Why did they pick blue? Because the code on the order sheet looked like the code on the blue box.
• Why do the codes look alike? Because we number colours in one sequence with one digit apart.
• Why did nobody notice? Because the check at packing only compares the first three digits of the code.

Now there are two things you can change: the codes, and the check. "The packer was careless" would not have helped anyone.

A few warnings:

• A person is almost never the root cause. If the answer is a name, ask what made the mistake easy: unclear instructions, no training, too much time pressure, a bad tool.
• There may be more than one cause. Write them all, then pick those you can act on.
• Do not guess. If you cannot tell, add a check to see what happens next time and write down that you are gathering evidence.
• Ask the people who do the work. They often know the cause immediately.

Choose actions you can finish

Good actions are specific, owned and dated. "Be more careful" is not an action. "Renumber colour codes so that no two differ by only one digit, by 20 March, owner: Priya" is.

Prefer changes that make the mistake hard to make over reminders to people. In order of strength:

1. Remove the cause altogether, for example by changing the codes.
2. Build in a check, for example a scan that compares the whole code.
3. Make the right way easier, for example a photo on the order sheet.
4. Train or remind, which works but fades.

Match the effort to the risk. A small slip does not need a project. A repeated or serious problem, or one that could harm someone or break a law, does.

Check that it worked

Set the check date when you set the action. Choose a date far enough away that the problem would have appeared again if the fix did not work: one or two months for a monthly process, longer for a rare one. On that date, look at the evidence: the orders since, the complaints, the records. If the problem is gone, close the action and write down what you saw. If it is not, go back to the cause.

Close only when you have looked. "Done" and "worked" are different words.

Keep a simple record

For each problem keep a short record: the number, the date, the description, the containment, the cause, the actions with owners and dates, the check and the result. A table or a list is enough. After a few months, read the records together. Patterns show up that single cases hide: the same supplier, the same step, the same day of the week.

Corrective, preventive and improvement

You will hear three terms. Corrective action deals with a problem that has happened. Preventive action deals with a risk you can see before it happens. Improvement is making something better that was not wrong. They use the same method, so a team that is good at the first is good at the others.

Where nerix helps

In Checks (early access), a minor or major issue, or an observation, opens a numbered issue. Its corrective action is a task in Work with an owner and a due date that follow how serious it is, and an owner or the person who ran the check closes the issue only after checking that the fix worked. If a result is changed later, the issue follows it.

Outside audits, you can use Work for any problem the same way: a task for each action, owners, dates and a check task on the date. In the chat you can paste your notes and ask nerix to help with the why questions, to suggest what else to check or to draft the message to the customer. It can ask good questions. It does not know your process, so the answers must come from the people who do the work.

The short version

Describe the facts. Put the customer right today. Ask why until you reach something you can change. Choose a few specific actions with owners and dates, prefer changes that prevent the mistake over reminders, and check later that it worked.

Prices checked in October 2026 and they change. Open the official pages before you buy: DocuSign, Dropbox Sign, PandaDoc, Adobe Acrobat Sign, Documenso.

Are electronic signatures valid?

Mostly yes, with exceptions. In the EU, the eIDAS regulation says an electronic signature cannot be refused legal effect only because it is electronic, and it separates simple, advanced and qualified signatures. A qualified signature has the same legal effect as a handwritten one. In the United States, the ESIGN Act and the state UETA laws set a similar basic rule for most commercial documents. Some document types, such as certain family-law or property papers, are often excluded or need extra formalities. This is general information, not legal advice. Ask a lawyer about contracts that carry real risk.

The options at a glance

DocuSign

Good at: the broadest recognition, so counterparties rarely hesitate, along with a wide integration list. Its pricing pages describe Personal, Standard and Business Pro plans, and the Personal plan includes a small number of envelopes a month.

Falls short: cost climbs per user and envelopes are limited on plans, so a team that signs often should read the limits. Its own pages show slightly different figures in places, so confirm the current price and the envelope allowance on the plans page.

Price: from roughly 10 dollars a month for one person on annual billing. Check the plans page.

Dropbox Sign

Good at: doing one thing plainly. The page lists Essentials at 10.05 dollars a month billed annually (15 dollars monthly) for one user, Standard at 17.50 dollars per user billed annually for two or more users, and Premium by quote. It also offers a free option for signing a single document.

Falls short: it is a signing tool, not a document builder, and the free option is narrow. Teams of one will find Essentials enough, but you need two users for Standard.

PandaDoc

Good at: documents that win business: proposals, quotes and contracts with signing built in. A Free eSign plan is listed, Starter is 19 dollars per seat a month billed annually, and Business is 49 dollars.

Falls short: if you only need signatures, you pay for features you will not use. The pages we checked described the free plan's document and template limits differently, so check the exact limits before relying on it.

Adobe Acrobat Sign

Good at: teams that already live in PDFs and Adobe tools, and organisations with bigger compliance needs. Adobe sells it with Acrobat plans for individuals, teams and enterprises.

Falls short: the plan structure is varied and depends on region and billing choice. We could not confirm one current price, so check Adobe's page for your country.

Documenso

Good at: an open-source signing product with hosted and self-hosted routes. The page lists a Free plan with 5 documents a month and up to 10 recipients per document, Individual at 25 dollars a month billed yearly, Teams at 40 dollars a month with 5 users, and custom plans, including self-hosting.

Falls short: a younger product with a smaller ecosystem. Self-hosting means you run, secure and back it up. Check the repository for the licence terms that apply to you.

nerix

Good at: documents you already write with it. In nerix, AI output lands in the Sheet as a document with versions, and a document can go out for signing with "Ask to sign" from Documents. The signer types a name, agrees to sign and the request keeps a trail of who opened and signed it and when. The final PDF goes to everyone and the version is marked as signed.

Falls short: nerix is not a dedicated e-signature service. The signature is a simple one, a typed or drawn name with an audit trail, and it does not offer advanced or qualified signatures with identity checks. It has no template library of thousands of forms and fewer integrations than DocuSign. Use it where a simple signature is legally enough for the document, and use a specialist when you need more.

Price: nerix has no per-signature fee on its pricing page. The plans are Free (3,000 credits a month, one person), Plus at 15 euros a month and Team at 24 euros per seat a month from three seats, and AI drafting spends credits. See pricing.

How to choose

• You sign a few documents a month. A free plan from Dropbox Sign, PandaDoc or Documenso may be enough.
• You send proposals and want signing at the end. PandaDoc.
• Your clients expect DocuSign. Consider paying for it for the few cases that need it.
• You want to keep data on your own server. Documenso self-hosted, with someone to run it.
• You draft contracts and want signing in the same place. Look at nerix for simple cases.

Before you choose, ask what level of signature your contract needs and where the signed copies will be stored. Our guide to contract clauses to read twice before you sign is a good companion.

Before you switch

Keep your signed documents. Download the completed PDFs and the certificates or audit trails from your current service before you cancel, because you may need them years later. Check whether your counterparties or your industry require a specific provider or a qualified signature, and whether your contract templates need re-creating in the new tool. Ask where signed copies are stored and in which country, and how long they are kept. Finally, send a test document to yourself and to a colleague on a phone, since the signing experience for the other person is what decides whether contracts come back signed.

The short version

DocuSign alternatives include Dropbox Sign for plain signing, PandaDoc for proposals, Adobe Acrobat Sign for Adobe users and Documenso for open source. Free plans exist but carry limits on documents. Most commercial contracts can be signed electronically, but check your own case, and this is not legal advice. nerix covers simple signing inside a drafting workflow, not specialist needs.

Formal does not mean cold or old fashioned. The best formal letters are plain, short and calm. They are written so that a stranger, such as a manager, a judge or an auditor, could read them in a year and understand exactly what happened and what was asked.

Know your one purpose

Before you write, finish this sentence: "After reading this letter, the reader should ___." Pay the invoice. Confirm the cancellation. Replace the faulty item. Accept that Maria can sign on my behalf. If you have two purposes, you probably need two letters.

Then decide what you will do if the reader does not respond, because the letter should say it.

The structure that works

1. Your details and the date. Name, address, contact information, and the date written.
2. Their details. The person or department, the company and the address. Use a name if you can find one.
3. A reference line. A subject that identifies the matter: "Invoice 2041 dated 3 March, unpaid" or "Termination of subscription, account 77812".
4. The opening. Say why you are writing in the first sentence.
5. The facts. What happened, in order, with dates, numbers and documents.
6. What you want. One clear request, with a date.
7. What happens next. The step you will take if there is no reply, and how to reach you.
8. A courteous close and your signature.

Keep it to one page where you can. Attach copies of documents, never originals, and list them at the bottom.

Be exact about facts

Strong letters are made of specifics:

• Dates: the day the service was ordered, delivered, due and not paid.
• Amounts: the figures, the currency and what they cover.
• References: invoice, order, contract and account numbers.
• Earlier contact: "I called on 12 March and spoke to Ahmed, who promised to call back. I wrote on 19 March. I have not had a reply."

Leave out opinions and speculation about motives. "You have ignored us" is an opinion; "I wrote on 19 March and have had no reply" is a fact that makes the same point.

Ask for one thing, with a date

"Please pay the 1,250 owed by invoice 2041 by 28 March." "Please confirm in writing by 15 April that the contract ends on 30 April." Vague wishes get vague answers. Choose a deadline that is fair, usually seven to fourteen days, and say what you will do afterwards.

Keep the tone steady

Firm and polite is a strong position. Avoid sarcasm, capital letters and threats you will not carry out. Do not accuse; describe. If you are angry, write the angry version, put it aside and rewrite it the next day.

If you are the one in the wrong, say so briefly and move to the solution. Our post on payment reminder emails shows the gentler first steps before a formal letter is needed.

Common types and their jobs

A demand for payment. Used after friendly reminders have failed. It states the invoice, the amount, the due date, the late fees allowed by your terms or law, the new deadline and what you will do next. The demand letter for an unpaid invoice template has the parts. Keep it factual: a letter that overstates the amount or threatens something unlawful can hurt your case.

A cancellation or termination. Used to end a contract or subscription. Check the notice period and the required way to give notice first. State the contract, the date you want it to end, and ask for written confirmation, including that no further charges apply. The cancel a contract or subscription template covers the usual points.

An authorization. Used to let another person act for you, for example to collect a parcel or deal with an office. Name the person, say exactly what they may do, for how long, and sign. The authorization letter template is a model.

A complaint. Used for a serious fault. Say what you bought, what went wrong, what you have already done, and the remedy you want.

Delivery and proof

How the letter reaches the reader can matter as much as what it says. If the contract names a method, use it. Otherwise choose one that leaves a trace: email with a delivery or read record, registered or tracked post, or a handed copy with a signature. Keep a copy of the letter as sent, and a note of the date and method.

Be careful with rules about notices to consumers and about debt collection, which vary by country. If a large amount is involved, ask a lawyer to read the letter before it goes.

Follow up

If the date passes, do what you said you would do. Send a second, shorter letter that refers to the first. Failing to follow through teaches the reader that your deadlines are not real.

Where nerix helps

Start from a free template and fill in a short form; the letter builds itself and downloads as Word or PDF, and what you type stays in your browser.

In the chat, you can tell nerix the facts and the outcome you want and ask for a first draft, or paste your angry draft and ask for a calmer version that keeps every fact. It opens beside the chat, with each version kept. Email drafts (early access) does the covering email and sends nothing until you press Send.

It does not know the law that applies to you or what you agreed on the phone. Check every date and amount, and ask a professional about anything with real money or legal risk behind it.

The short version

Know your one purpose. Use a clear structure. Write facts, not opinions. Ask for one thing by a date. Stay firm and polite, choose a delivery method that leaves proof and follow through on what you said.

Prices checked in October 2026 and they change. Open the official pages before you rely on a limit: ChatGPT, Claude, Gemini, Canva, Perplexity.

The options at a glance

ChatGPT

Free plan: OpenAI's free-tier help page says free users get web search, data analysis, file and image uploads and image creation, and everyday text chat that is not capped, subject to abuse-prevention safeguards. File uploads, image generation, voice and data analysis each have their own limits.

Where it stops: a lighter model than paid plans, and tool limits that bite when you work all day. Its terms and data settings differ by plan, so check them for client material.

Paid: Go is 8 dollars a month in the US, Plus is 20 dollars, and Business is 20 dollars per user a month billed annually.

Claude

Free plan: Anthropic lists chat on web, desktop and mobile, web search, file creation, memory across conversations, app connections and up to five projects on Free.

Where it stops: usage limits and access to its lighter models only. Heavy daily use will reach the cap.

Paid: Pro is 17 dollars a month billed annually (20 monthly), and Team standard seats are 20 dollars per user annually.

Gemini

Free plan: Google's page lists chat with its Flash-Lite model, image creation and editing, Deep Research, voice conversations and Gems, with 15 GB of storage.

Where it stops: usage limits, and Gemini in Gmail and other Google apps comes with the paid plans. If you pay for Google Workspace, check what your plan already includes.

Paid: Google AI Plus is 4.99 euros a month and AI Pro is 21.99 euros a month on Google's euro page.

Canva

Free plan: Canva says Free includes limited AI access for design, images and video, and its help centre says Magic Write draws on a monthly AI allowance on Free. Numbers have changed over time, so look at the current help page.

Where it stops: the allowance, and premium content and brand tools on paid plans. Its Pro price differed between the pages we found, so check the pricing page.

Perplexity

Free plan: basic searches with sources, plus a small allowance of deeper searches. The company's pages disagreed on the exact number, so check it.

Where it stops: the deeper research modes. It is a research tool, not a writing or document tool.

Paid: Pro is 20 dollars a month, or 200 dollars a year according to one page and 17 dollars a month annually on another.

nerix

Free plan: one person, 3,000 credits a month, and it stops at its limit and is never charged. The credits are the unit of AI work, and the app shows what a question costs before you send it. On Free you can use chat with sources and the library for your own documents, and the app lists a free tier of the Websites add-on with a small nerix badge.

Where it stops: the monthly credits. A heavy research day can use them up, and AI work then waits until next month unless you add a credit pack. Free is one seat, so team chat and shared libraries need a team plan. It is a newer product with fewer integrations than the big names.

Paid: Plus is 15 euros a month, Pro 39 euros, and Team 24 euros per seat a month from three seats. nerix.ai runs on servers in the European Union today, and you can choose the model. See pricing.

When paying starts to make sense

• You hit the limit weekly. A plan around 8 to 20 dollars a month is often cheaper than the hour you lose.
• You share work. Teams need shared libraries and admin controls that free plans lack.
• You handle client data. Paid and business plans often have clearer data terms. Read them.
• You depend on a feature. If one tool saves you hours, pay for that one and stay free on the rest.

How to choose

Pick one general assistant first, since it covers drafting, summaries and brainstorming. Add Canva if you make visuals, and Perplexity if research eats your week. Add nerix if the questions are about your own contracts, quotes and notes, and read our guide to getting answers from your own documents. Whatever you use, apply the habits in checking AI answers before you rely on them, because a free answer that is wrong costs more than a paid one.

Use free plans safely

Free does not mean careless. Do not paste passwords, bank details or other people's personal data into a tool whose terms you have not read. Check whether the free plan uses your conversations to improve its models and whether you can switch that off. Keep a short list of what you use and what you put in it, so a colleague can follow the same rules. Save useful prompts in one shared document. And keep a human check on anything that goes to a customer, a tax office or a court: AI drafts are a start, never the final word.

The short version

The best free AI tools for small business are ChatGPT, Claude or Gemini for general work, Canva for design, Perplexity for research and nerix for your own documents. Free plans are real but limited, and the limits differ, so read them first. Start with one assistant, add tools only when a task needs them and move to paid when you hit the limit weekly.

Below, you will see how answers from your own documents work, how to prepare for them, and how to tell a good answer from a bad one, so you can chat with your documents and get answers you can check.

How it works, in plain words

When you add a file to a library, a system reads it and breaks it into passages. When you ask a question, it finds the passages most likely to contain the answer, hands them to an AI model along with your question, and the model writes a reply based on those passages. Showing which passages were used is what lets you check.

There are two ways the search can find passages, and a good system uses both:

• Exact words. Finds passages that contain the words you typed. Best for names, numbers, clause numbers and codes. "Clause 14.2" or "invoice 1042" should find exactly that.
• By meaning. Finds passages that talk about the same thing even in different words. Best for questions such as "can we cancel early?" when the contract says "termination before the end of the minimum term".

In nerix, the library offers both: you can search by exact words or by meaning, and the chat can answer from your files and show its sources.

Why sources matter more than fluent answers

An AI model writes fluent text, and fluent is not the same as true. A model can produce a confident, well-formed answer that is wrong, or that blends what your document says with what is generally true elsewhere. The cure is not to trust the model less in the abstract. It is to make every answer checkable.

A good answer shows where each claim came from, so you can:

1. Click the source and read the original passage.
2. Confirm it says what the answer says.
3. See which document, which page and which version.

In nerix, each answer shows its sources, and you can open the passage and its page. If a sentence has no source, treat it as the model's own words, and check it before you rely on it.

Prepare your documents

The quality of the answer depends on the quality of the library. A small amount of preparation helps a lot.

Keep one current version

If the library holds three versions of a contract, the system may quote the old one. Remove superseded files, or name them clearly. "Supplier agreement, signed 2026" is better than "final_v3_new".

Use readable files

Text-based PDFs and Word documents work best. Scans are read too, but photos of pages at an angle or in poor light produce errors, and numbers are where errors hurt. Check important scanned documents by eye.

Organise in folders

Group files by subject: contracts, policies, supplier manuals, HR. Folders help you control what a question searches, and help people find things themselves.

Mind the limits

In nerix, each file can be up to 128 MB. Each file passes through states, Waiting, Reading, Indexing and Ready, and you can ask questions about it once it is Ready. A file that failed to read should be fixed or replaced, not ignored.

Do not upload what you should not

Be thoughtful about what goes in. Documents full of personal data should only be uploaded where you have the right to process them, and you should know where they are stored. nerix stores data in the EU, on servers in Germany, and has settings to hide names, emails and amounts before text goes to a model. Read the Security page to understand what applies to you.

Ask good questions

You get better answers from better questions. A few habits:

• Be specific. "What is the notice period in the Acme agreement?" works better than "tell me about Acme".
• Name the document or the period when it matters. "In the 2026 supplier agreement" avoids the 2024 one.
• Ask for the source. "Quote the clause" makes the model show its evidence.
• Ask one thing at a time for important matters. Combine questions only for exploration.
• Say what you will do with it. "I need to decide whether to cancel before June" helps the model pick what is relevant.

For summaries, ask for structure: "list the obligations on each side" or "list every date and deadline". Lists are easier to verify than prose.

How to spot a bad answer

Even with sources, answers can go wrong. Look for these signs:

• No source for a specific claim. A date, an amount or a clause number with nothing behind it.
• A source that does not say it. Open the passage. Sometimes the answer overreaches what the text says.
• Mixed-up documents. The answer combines two files, or quotes the wrong version.
• Confidence about silence. If the documents do not cover your question, the right answer is "I cannot find this", not a plausible guess.
• Stale facts. The document is dated, and the situation has changed.

When the answer matters, such as a legal deadline, a payment, or a safety rule, open the source and read it yourself. Use the AI to find the passage faster, not to replace reading it.

Keep it to your documents when you need to

Sometimes you want the model to use only what is in your files and not add general knowledge. In nerix, the assistant settings have an option to answer only from your documents. Use it when you are checking what a contract actually says rather than what contracts usually say.

At other times you want both: your documents plus current facts from the web. nerix can search the web when a question needs current facts, such as a rule in force now, and names the sites it used, so your documents and outside sources are clearly separate. An administrator can set web search to ask first or switch it off.

What it cannot do

Be honest about the limits:

• It cannot know what is not in the library. A verbal agreement or an email you did not upload is invisible to it.
• It does not give legal advice. It can find and summarise what a contract says, but it does not know how a court in your country would read it.
• It can misread. Tables, footnotes and unusual layouts are hard, and a number from a table is exactly the type of thing to verify.
• It does not replace a person who knows the business. It shortens the search, not the judgement.

A simple way to start

1. Pick one small set of documents you search often, such as your supplier contracts.
2. Upload them, remove old versions and wait until they show as Ready.
3. Ask five questions you already know the answers to, and check them against the sources.
4. If the answers are right and the sources are clear, widen the library. If not, fix the files first.

Testing with questions you can already answer is the quickest way to learn what the system does well on your documents, and where it needs a careful eye.

The short version

Ask in plain words, expect a source with every claim, open the source when it matters, and keep your library tidy. Answers you can check are useful. Answers you cannot check are a risk with good grammar.

The standards are less frightening than their reputation. At heart they ask you to do what a well run business already tries to do: know what you promise, do it, check that you did and fix what goes wrong. The work is in writing it down and keeping evidence, and the steps below show how to prepare for an ISO 9001 or ISO 27001 check.

This is a roadmap, not a guarantee. Certification is granted only by an independent body after its own audit, and the requirements are in the standards themselves, which you should read or have explained by a qualified adviser.

What the two standards are for

ISO 9001 is about quality management. It asks you to understand your customers' needs, plan how you meet them, control the work, measure results and improve.

ISO 27001 is about information security. It asks you to identify what information you hold and the risks to it, choose controls to deal with those risks, and keep checking that they work.

They share a skeleton: a clear scope, leadership that takes responsibility, planning around risks, support such as skills and documents, operation, evaluation through audits and reviews, and improvement. Many small companies work on them together.

Decide why and how far

Start with the reason. A customer demand, a tender, a wish to be more organised or a need to show you handle data responsibly all lead to different efforts. Then decide the scope: which parts of the business, which locations and which services are included. A narrow, honest scope is better than a broad, shaky one.

Set a realistic timeline. Many small companies need several months to build the habits and gather a few cycles of evidence. Rushing produces paper that does not match reality.

See where you stand

Do a gap check against the requirements. For each, ask: Do we do this? Do we write it down? Can we show evidence? Mark each as met, partly met or not met, and write what the evidence is.

Be honest. The point is to find the gaps now, not to hide them from a certifier who will find them later. If you cannot show evidence, then it is not met, however sensible the practice.

Build what is missing, in proportion

Common things small companies need to create or tidy:

1. Policies, short ones: a quality policy or an information security policy, signed by the owner.
2. Roles and responsibilities, so everyone knows who owns what.
3. A list of risks and how you handle them. For 27001 this includes an inventory of information assets, a risk assessment and the controls you choose.
4. Procedures for the work that matters, as short checklists. Our post on turning a process into a checklist shows how.
5. Supplier checks for those you depend on.
6. Training and awareness, with records.
7. Incident and complaint handling, with a way to learn from each.
8. Internal audits and management reviews, on a rhythm.

Do not copy a big company's manual. Write what you do, in plain words, and only what you need.

Collect evidence as you go

Evidence is what turns a claim into a fact: a record, a log, a signed document, a screenshot, a result. An auditor will ask to see it, usually by sampling. Keep it organised so you can find it in minutes.

Good habits:

• Record at the time, not later from memory.
• Keep one place for the evidence of each requirement.
• Date and name things.
• Keep what you need and delete what you do not, taking account of the law on personal data.

Run internal audits and a review before the real one

An internal audit shows whether your system works in practice. Do at least one full cycle before an outside audit, cover the whole scope and close the findings. Then hold a management review to look at results and decide improvements. Our posts on your first internal audit and preparing a management review explain how.

Certifiers look for a system that has been running and improving, not one that appeared last week.

Choose a certification body, and prepare people

If you decide to certify, look for an accredited body, ask for a quote and the steps. Typically there is a document review and one or two audit stages. Prepare your people: tell them what an audit is, that honesty is expected and that they should answer the question asked, with a simple, true answer and the evidence. Do not rehearse false answers.

Do not overclaim

Be careful with the words you use. "We follow the principles of ISO 27001" is different from "we are ISO 27001 certified". Do not use the certified mark or say you are certified before you hold a certificate, and keep it within the scope it covers. Customers, and in many places consumer law, expect accuracy.

Keep it going

Certificates are checked again, usually every year, with a full renewal after a few years. The system must stay alive: audits, reviews, actions closed, risks updated, new staff trained. If it becomes a chore done once a year, it decays and the next audit hurts.

Where nerix helps

Checks (early access) includes a Get ready for a check page that starts from a library of about 90 frameworks, including ISO 9001, ISO 27001, GDPR and NIS2, and adds the laws a framework requires; it also has eight ready plans for internal checks. Getting ready labels each requirement Evidence found, Partly found, Not found or Can't tell, with the document behind it, never counts a requirement as found without evidence, and a person confirms every result. Issues become tasks in Work with owners and dates, and the yearly business review can be prepared from your workspace's own records.

Keep your policies, procedures and evidence in the library, where they can be searched and where nerix can answer questions with the page the answer came from. A readiness check is not a certificate and not a guarantee: only an accredited certification body can certify you, and nerix does not replace an adviser who knows the standard.

The short version

Know why you want it and decide an honest scope. Check where you stand against the requirements, build what is missing in proportion and keep evidence as you go. Run internal audits and a review first, and never claim certification you do not hold.

A fair, early, kind and clear approach works better for the person, the team and the business. Below is a framework for handling a performance problem early, fairly and in writing. It is not legal advice: employment law differs by country and by contract, so check what applies to you, especially before any formal step.

Be sure there is a problem

Before you talk, get clear on the facts.

1. What exactly is the problem? Late deliveries, errors, conflicts, missing targets, behaviour? Write specific examples with dates.
2. What is the standard? Is it written down, and does this person know it? A rule nobody told them about is your problem, not theirs.
3. Is it the person or the situation? Unclear instructions, too much work, a broken tool or poor training can look like poor performance.
4. Is it new? A good worker who suddenly changes may be facing something outside work.
5. Are others treated the same way? Compare fairly.

If you find the cause is partly yours, that is good news: you can fix it.

Talk early and in private

Do not wait for the yearly review. At the first sign, find a quiet time and place, give a little notice that you would like to talk, and say it is about how things are going, not a trap.

A shape that works:

1. Start with the purpose. "I want to talk about the last three client reports, because I think we can make them better together."
2. Describe, do not label. "Two reports went out with the wrong totals, on 3 and 17 March" is better than "you are careless".
3. Ask for their view. "What is going on from your side?" Then listen, properly. You may learn something.
4. Explain the impact. Why it matters to customers or colleagues.
5. Agree on what good looks like. Specific and measurable where possible.
6. Offer support. Training, a checklist, a buddy, fewer tasks for a while.
7. Set a date to review. A week or a few weeks, depending on the problem.

End the talk by summarising what you both heard. Then write a short note and send it: the date, the issue, what was agreed and when you will review. Our follow up after a meeting template gives a tidy format.

Find the cause

Ask rather than assume. Common causes include:

• the person does not know what is expected,
• they lack a skill or the training,
• the process or tools make errors easy,
• they have too much to do or conflicting priorities,
• personal circumstances, such as health, family or money worries,
• a poor fit between the person and the role,
• motivation, which is often the result of one of the above.

Match the response to the cause. Skills need training, load needs reprioritising, personal difficulties may need time off or flexibility. Our leave request template shows how an employee can ask for time off, which is useful to know when someone needs a break.

Support first, then expectations

Give real help for a fair time. If you say "you must improve" without offering anything, you have not done your part. Offer specific things: a session with a colleague, a checklist, a weekly look at their work. Check in regularly and give honest feedback, both good and bad. Notice improvement and say so.

Keep records, fairly

Keep brief, factual notes: dates, examples, what was said and agreed, support given. Share them with the employee. Records protect both sides and make later decisions fairer. Keep them private and store them safely. In many places employees have a right to see what you hold about them.

If it does not improve

When there has been time and support and the problem continues, you may need a formal step. Check your contract, your policy and the law before doing anything, since some places require specific steps, notice and the chance for the person to respond or to bring someone with them.

A written warning states the facts, the earlier conversations, the standard expected, the support given, the time allowed for improvement and the possible consequences. Our employee warning letter template shows the usual parts. Do not send it as a surprise: nothing in it should be new to the person.

If the outcome is that the employment ends, follow your contract and the law on notice and reasons, and treat the person with respect. The employment termination letter template is a starting point, but this is a point where advice from a professional is worth paying for.

Protect the team

Others see how you handle problems. If one person's poor work is ignored, the rest conclude that effort does not matter. If a person is humiliated, they conclude that honesty is dangerous. Fair and private handling earns trust from everyone.

Look after yourself

These conversations are stressful. Prepare, rehearse the first two sentences, and talk to someone you trust before and after. Do not do it on a Friday evening, and do not do it when you are angry.

Where nerix helps

Turn the agreed actions into tasks in Work with an owner and a date, including the review date. In the chat, you can describe a situation and ask nerix to help word the opening of a difficult conversation in plain, kind terms, or to turn your notes into a clear summary. A monthly one to one form in Feedback (early access) gives you a steady place to talk.

nerix does not know your employment law, your contract or the full story. The decisions and the words are yours, and for formal steps, take professional advice.

The short version

Check the facts and the cause, including your own part. Talk early, in private, describe rather than label and listen. Support the person, agree on what good looks like and keep factual records. Take formal steps only after support and time, and check the rules first.

A small team does not need a call centre to do this. It needs a routine that everyone knows, a place where complaints are kept and a habit of learning from them. This guide is a routine for handling customer complaints calmly and keeping the customer.

Make it easy to complain

If customers cannot find where to complain, they will do it in public. Put a clear contact on your website, your invoices and your packaging. One address or form is better than five. Say who reads it and how fast you answer.

Every complaint, however it arrives, should end up in one list: an email, a message, a phone call, a comment on social media. If a colleague takes a call, they write it into the list the same day. Complaints that live in one person's inbox disappear when that person is away.

Acknowledge quickly

The first reply matters most. Within a day, tell the customer:

• that you have received it and understand what it is about,
• who is handling it,
• when they will hear from you next.

You do not need the answer yet. You need the customer to know that a human has it. A good opening is short: "Thank you for telling us. I am sorry the order arrived damaged. I am Maya, I will look into it today and write to you by tomorrow afternoon."

Then keep the promise about when you will write.

Find out what happened

Before you reply in detail, check the facts. Read the order, the delivery record, earlier messages and any photos. Ask the customer only for what you really need, and ask once. If the matter involves a colleague, hear their version before you answer.

Put the customer first in your thinking, and the facts first in your decision. Most customers are right about the main point, even when they exaggerate the details.

Make it right

Decide on the remedy: a replacement, a refund, a repair, a credit, a corrected invoice, a different service or, sometimes, an honest explanation and no money. Check your terms and the rules where you are, since consumers often have rights that your policy cannot remove. Our returns and refund policy template helps you write down what you offer, so decisions are consistent.

Some guidance:

1. Offer the fair remedy first. Do not make the customer ask three times.
2. Explain the reason if you cannot give what they asked for, in plain words, with what you can do.
3. Keep the same standard for every customer. Unfair treatment spreads fast.
4. Where the customer is wrong, say so kindly and show what you checked.

Write replies that sound like a person

Avoid fortress language: "We regret any inconvenience" and "as per our policy". Write the way you would speak to someone standing in front of you.

A reply that works has these parts:

1. Thank them and name the problem in their words.
2. Say what happened, if you know, without excuses.
3. Say what you are doing, and when.
4. Say what they need to do, if anything.
5. Close with a real name and a way to reach you.

The customer apology email template follows this order. One apology, sincere and specific, is worth more than three vague ones.

It helps to know what customers write when they complain. The complaint and refund request template shows how a clear complaint looks from their side: what was bought, what went wrong, what they want.

Handle the angry customer

Anger is usually about being ignored. Do not argue with the tone. Respond to the facts. Take a breath before replying, and if a message makes you angry, wait an hour. If a customer is abusive, you may set a limit politely, and you should protect your staff.

Where a call is better than writing, call. Then confirm in a short email what was agreed.

Learn from every complaint

Every month, read the list as a whole. Count by cause: late delivery, wrong item, unclear price, rude reply, product fault. A cause that appears three times is not a coincidence. For the serious ones, use the habit in Corrective actions that fix the cause: describe, contain, find the cause, act, check.

Share what you learn with the whole team, including the good news. A thank you from a customer who was helped is a good way to end a meeting.

Know when to escalate

Decide in advance which complaints go to the owner: legal threats, safety, large sums, press and anything involving personal data or discrimination. Write the rule down, so nobody has to guess under pressure.

Where nerix helps

The Help desk gives a small team one queue. Customers write through a portal, a website widget or email; your team sees every request in one list, replies publicly or leaves an internal note, and sees what is about to miss its target. A macro is a saved reply, such as asking for more details, which you change before you send. Requests that need follow up can become tasks in Work.

In the chat, you can paste a complaint and ask nerix for a first reply in your tone, then edit it. You decide the remedy; nerix only helps with the words.

The short version

Keep one list. Acknowledge in a day. Check the facts. Offer the fair remedy without making them ask three times. Write like a person. Read the whole list every month and fix the causes.

Most proposals that lose were not beaten by a better offer. They lost because the reader could not tell what they were being asked to approve, or had to guess what happened after they said yes. This guide covers what to put in, in which order, and how to keep it short enough to be read, and a free business proposal template is there when you want to start from a draft.

Start with the reader's problem, not your company

The first thing in a proposal should be a sentence or two that describes the situation the reader is in, in words they would use themselves. "You are opening a second branch in March and the booking system you use today cannot show both branches in one calendar." That sentence proves you listened. A paragraph about your founding year and your values proves nothing yet.

You can only write that sentence if you asked questions first. Before drafting, get answers to these:

• What is happening now that makes them look for help?
• What does a good result look like, in their words, and how will they know?
• What is the deadline, and what is driving it?
• Who decides, and who else has to agree?
• What is the budget range, even roughly?

If you could not get an answer, say what you assumed. "We have assumed the content is ready by 15 March" is useful to the reader and protects you.

Put the summary on the first page

Many readers will only read the first page, and the person who decides is often not the person you spoke to. Write a summary that stands alone: the problem, what you propose, the price, the timeline and the next step. If you copied that page and sent it alone to a manager, it should still make sense.

A good summary has four short parts:

1. The situation in one or two sentences.
2. What you will do, in plain words, as outcomes: what exists at the end that did not exist before.
3. What it costs and when, with the total and the dates.
4. What happens next: sign here, or reply to this email, by this date.

Write it last, even though it comes first. Once the rest is clear, the summary almost writes itself.

Describe the work as things the reader can check

The middle of the proposal is where you describe the scope. The most common weakness here is vagueness: "full support", "a modern website", "ongoing optimisation". None of those can be checked, so they cause arguments later.

Describe the work as deliverables and steps that the reader can tick off:

• "Five pages: home, services, about, prices and contact, written and designed by us."
• "Two rounds of changes after the first draft. A third round is charged at the hourly rate below."
• "A one-hour training session for up to four people, recorded."

Then say what is not included. A short "Not included" list is one of the most useful things in any proposal. It stops the most common dispute, which is the client assuming something was part of the price. If the work is large, a statement of work holds these details formally; our statement of work template is a good start, and the project proposal template fits work that runs in phases.

Show why you, with evidence you actually have

You do need a section on why the reader should choose you. Keep it short and make it specific. Two or three relevant pieces of past work, described in a sentence each, are worth more than a page of adjectives. Say what you did, for what kind of client, and what came of it.

Only claim what is true and what you can back up. Do not invent client names, numbers or quotes, and do not use a testimonial you do not have permission to share. If you are new and have little to show, say what you do have: the relevant skills, how you work, and a small first step that lets the reader try you with little risk. Honesty about a short track record reads better than a stretched one.

Give the price in a way that is easy to say yes to

Put the price in the proposal. Show the total clearly, and show what it is made of if the reader would want to see that. Make three things explicit:

• Currency and tax. State the currency, and whether tax such as VAT or sales tax is included.
• Payment terms. A deposit, milestones or payment on delivery, and how many days an invoice is due.
• Validity. "This price holds until 30 November" gives the reader a reason to decide, and protects you from a price that no longer works.

Offering two or three options can help when the reader's budget is unclear, as long as each option is complete in itself. Do not offer ten. A decision gets harder with every extra choice.

Make the next step obvious

End with one clear action. "To go ahead, reply to this email with 'approved', and we will send the agreement and the first invoice" is better than "we look forward to hearing from you". If the proposal needs a signature, say where it goes and how. Put a date for when you will follow up if you have not heard, and then do it.

Check it before you send it

Read the proposal as the reader would, once, from the top, in five minutes. Then check these:

• Could someone who only read page one explain what is being proposed?
• Is every number, date and name correct, and the same everywhere it appears?
• Does any sentence promise something you cannot deliver?
• Would you be comfortable if they held you to every line?
• Is it free of filler, and free of anything you copied from a previous client?

The last point matters more than people think. A proposal that still mentions the previous client's name or industry is one of the quickest ways to lose trust.

Where nerix helps, and where it does not

You can start from a free template: the business proposal template asks a short set of questions, fills the document in as you type, and downloads as Word or PDF. It needs no account, and what you type stays in your browser.

If you would rather talk it through, ask nerix in the chat to write an offer. It drafts the first version from what you tell it, opens it in a document beside the conversation, and keeps every version so you can compare what changed and go back. You can then ask for it shorter, firmer or in simpler words, or edit the text yourself.

What it cannot do is know your client. The facts that win a proposal, the real problem, the real budget and the real history, come from you. Treat the draft as a starting point that saves you the blank page, then put your own knowledge into it before it goes out.

A proposal that wins is usually a plain one: it names the problem, shows the work, states the price and makes the next step easy. Everything else is decoration.

This guide covers what to put in a quotation, how to word it, and the details that prevent the conversations nobody enjoys, and a free quotation template goes with it.

Quotation, estimate, proposal: know which you are sending

The three words get mixed up, but they mean different things, and the difference matters:

• A quotation is a fixed price for a defined list of items. If the client accepts, that is the price.
• An estimate is your best guess, and the final cost may differ. If you send an estimate, say so, and say how much it could change.
• A proposal explains the problem and your approach and then gives a price. It persuades as well as prices.

If the client needs to decide between suppliers on price, send a quotation. If they need to be convinced that you understand the problem, write a proposal and include the price in it. Whatever you send, label it with the right word at the top.

What every quotation should contain

Think of the quotation as something a stranger could pick up and understand without calling you.

1. Who and who. Your business name and contact details, and the client's name or company. Include a tax or company number if the law where you are requires one.
2. A number and a date. A quotation number lets both sides refer to it. The date shows when it was written.
3. The items. One line for each thing you will supply, in plain words, with its price. If quantities matter, show them.
4. The total. Clearly stated, with the currency, and a statement on tax: whether VAT, GST or sales tax is included or will be added.
5. What is included, and what is not. This is the part people skip and later regret.
6. How long it is valid. Give an end date.
7. Payment terms. A deposit, stages or payment on delivery, and when an invoice is due.
8. How to accept. Reply to an email, sign and return, or place an order. Make it one clear step.

Our free quotation template has these parts ready: as many priced lines as you need with the tax and the total worked out for you, what is included, validity and how to accept. You fill in a short form, the document fills itself in, and you download it as Word or PDF.

Describe items so they cannot be misread

Vague lines are where disputes come from. Compare:

• "Website design": vague. How many pages? Who writes the text? How many rounds of changes?
• "Five-page website (home, services, about, prices, contact), design and build, two rounds of changes": clear.

You do not need to write an essay. You need enough detail that two reasonable people would agree what was promised. If an item has limits, state them: hours, quantities, dates, number of revisions.

Price in a way that is honest and easy to compare

Pricing is part strategy and part honesty. A few principles hold up:

• Show the total first. Clients look for it. Do not make them add up lines.
• Do not hide costs. Delivery, installation, setup and other fees should be on the page. Surprises after acceptance damage trust more than a higher honest price.
• Say what is optional. If something is an extra, mark it as such, with its own price, so the client can choose.
• Be consistent. The same job for a similar client should not have a wildly different price unless something is actually different.

If you are not sure what to charge, work out your costs, the time involved and what you need to earn, then check the market. Do not start from the lowest price you think they will accept. A price that is too low is hard to raise and attracts clients who negotiate on everything.

Tax, currency and rounding

Three small things that cause a surprising number of problems:

• Tax. State whether prices include tax. If you must charge it, show it separately. Tax rules differ by country, so check what applies to you.
• Currency. Name it, especially when you work across borders. "1,200" means nothing without a currency.
• Arithmetic. Check it twice. A wrong total on a quotation is awkward to correct, and may bind you to the lower figure.

Validity: give the price a deadline

A price that never expires is a risk. Costs change, your schedule fills, and a quotation from last spring can come back months later. Write an end date: "valid until 30 November 2026". Fourteen to thirty days is common, though the right period depends on how fast your costs move.

A deadline also helps the client. It gives them a reason to decide rather than let the message sink to the bottom of the inbox.

Make saying yes easy

Tell the client exactly what to do. "To accept, reply to this email with 'Accepted' or sign below and send it back. We will then confirm the start date." If you need a deposit, say how much and how to pay it. If you want a signature, make clear where.

After acceptance, keep the record. Save the accepted quotation with the reply that accepted it. If you later raise an invoice, use the same item names and prices so the two documents match. Our invoice template is a good partner for the next step, and the sales offer template fits when you are selling goods rather than services.

Common mistakes

• No end date. The price lives forever.
• Missing exclusions. The client assumes everything is included.
• Mixing estimate and quotation. The client hears "fixed", you meant "about".
• Different names for the same thing. Items on the quotation, the invoice and your emails should match.
• Sending it without reading it. A wrong date, name or total is the most avoidable error in business.
• Silence afterwards. If you have not heard in a few days, follow up once, politely, before the validity date.

Using AI for the first draft

If you would rather not start from a form, ask nerix in the chat to write an offer, and tell it what you are selling, the price, and how the client accepts. It drafts the quotation, opens it in a document beside the chat, and keeps each version so you can go back, and you can ask for it shorter, firmer or simpler. It can also be sent by email as a PDF or Word file from the document, or sent for signing.

What it cannot do is know your costs, your tax obligations or what you agreed on the phone. Check every number and every item yourself before it goes out. A draft that saves you ten minutes is not worth a wrong total.

The short version

State who, what, how much, what is included and what is not, until when, and how to accept. Keep the language plain. Check the arithmetic. A quotation that is easy to understand is easy to accept, and easy to enforce if it ever comes to that.

Below, you will find what data residency means, where AI makes it more complicated, and what a small business should check to keep its data in the EU when it uses AI. It is general information, not legal advice. For decisions with real consequences, speak to a data protection professional where you are.

What people mean by "data in the EU"

When a vendor says your data is in the EU, they usually mean one of several different things. They are not the same:

• Storage. Your files, conversations and logs sit on servers in the EU.
• Processing. The computation happens in the EU, for example an AI model reading your text to write an answer.
• Access. Who can read the data, and from where. Staff outside the EU with access are a different matter from staff inside it.
• Backups and logs. Copies and records can sit somewhere other than the main store.
• Sub-processors. The other companies the vendor uses, each with their own locations.

A claim that covers only storage leaves a lot of questions open. That is why the next section matters.

Why AI makes it harder

With an ordinary web app, your data is stored in one place and used by that app. With AI, there is an extra step: your text is sent to a model, and the model may run somewhere else, run by another company.

So when you ask an AI tool a question about a contract, several things happen:

1. Your documents are stored with the vendor.
2. The relevant passages are retrieved.
3. Those passages, with your question, are sent to a model provider.
4. The provider processes them, in a location you may not have chosen, and returns the answer.

A tool can store everything in Germany and still send text for processing to a model in the United States. Neither fact is automatically wrong, but you need to know both. Under the GDPR, transfers of personal data outside the EU need a legal basis and safeguards.

What to ask any AI vendor

Put these questions to any provider, and expect clear written answers:

1. Where is my data stored, and where is it processed? Ask separately.
2. Which AI providers receive my text, and where do they process it? Ask for the list.
3. Is my content used to train models? By you, and by them.
4. How long is it kept, and can I set the period?
5. Can I export and delete everything, including from backups, and how long does deletion take?
6. Who are your sub-processors? Can I have the list?
7. What happens in a breach? How and how fast will you tell me?
8. What certifications do you hold? And be wary of claims you cannot verify.

An answer such as "we take privacy very seriously" is not an answer. A specific one is: a place, a period, a list.

What nerix does, and what it does not

We would rather be exact than reassuring, so here is what is true today.

• Storage and processing in the EU. nerix runs on servers in France, with files and backups in the Netherlands. Today the European Union is the one region. United Kingdom and United States capacity is not live yet, and the Security page will say so on the day it is.
• Providers differ, and you choose. An organisation chooses which AI providers may process its content. A new workspace is EU only: Mistral, which processes in France, and models on nerix's own server. Other providers, such as Anthropic and Google, process elsewhere and stay off until an administrator allows them, and DeepSeek's own API processes data in China, which nerix flags with a caution. An owner can lock the workspace to its region. Names of the people and clients the workspace knows are replaced with codes before text reaches any provider.
• No training on your content. nerix never uses your documents to train a model, and neither does Mistral. The product shows what each other provider may do before you allow it.
• Redaction. Names, email addresses and account numbers can be replaced with placeholders before text is sent to a provider. It cannot catch everything, so it reduces exposure and is not a guarantee.
• Retention and erasure. Retention is set per organisation. Erasure takes effect within 30 days, including in backups, and you can export a machine-readable copy of your content.
• Audit log. An append-only record that nobody, including an owner, can edit.
• What we do not have. nerix does not yet hold SOC 2 or ISO 27001, and says so. The public API is not live yet.

The Security page and the sub-processor list give the details, and the sub-processor register is available on request.

A checklist for your own business

Whatever tools you use, run through this once:

Know what personal data you hold

List the kinds of personal data your business handles: customer contact details, orders, support messages, employee records. You cannot protect what you have not listed.

Know why, and for how long

Under the GDPR, you need a reason for each use of personal data, and you should keep it no longer than needed. Write down the reason and the period for each kind.

Choose tools deliberately

For each tool that touches personal data, note where it stores and processes it, who the sub-processors are, and whether a data processing agreement is in place. Prefer tools that answer this clearly.

Limit what goes into AI

Do not paste into any AI tool what the task does not need. If you are summarising a complaint, you often do not need the customer's full name and address. Use the redaction option where it exists, and be careful with special categories of data such as health information.

Tell people what you do

Your website needs a privacy notice that says what you collect, why, how long you keep it, who receives it, and how to exercise their rights. Our website privacy notice template is a careful starting point, and you should check it against what you actually do.

Be ready for requests

People have the right to ask what you hold about them and to ask for it to be deleted. The usual deadline for a reply is one month, though it can vary. Our personal data access request and personal data deletion request templates show what such requests look like, which helps you recognise and handle them when they arrive.

Keep a record

Write down your decisions: which tools, which providers, why. If a customer or an authority asks, you can show your reasoning.

Common misunderstandings

• "EU hosting means compliant." It does not. It helps with one question among many.
• "Anonymised, so it does not count." Genuinely anonymous data is outside the GDPR, but removing a name is often not enough to make data anonymous.
• "The vendor is responsible." Vendors have duties, and so do you. You decide why and how personal data is used, and that brings your own obligations.
• "We will fix it when someone asks." Fixing it afterwards is slower and costlier than choosing well at the start.

When to get help

A small business can handle the basics with a clear list and a few good templates. Get professional advice when you process sensitive categories of data, handle data about children, transfer data outside the EU on a large scale, or have been asked a difficult question by a regulator or a large customer. A data protection officer or a lawyer who knows your sector earns their fee in those cases.

The short version

Ask where data is stored and where it is processed, and treat them as two questions. Find out which AI providers see your text and where they run. Make sure your content is not used for training. Share only what the task needs. Keep a short record of your choices. And remember that location is one piece of data protection, not the whole of it.

What minutes are for

Minutes have one job: to let someone who was there, or was not, find out what was decided and what happens next. Everything else is optional. A useful set of minutes answers five questions:

• Who was there, and who sent apologies?
• What was decided? Not discussed: decided.
• Who will do what, and by when?
• What was left open, and who will bring it back?
• When and where is the next meeting?

If your minutes are three pages of who said what, almost nobody will read them. If they are five clear lines, they will be used. A decision stated plainly is worth more than a faithful account of the argument that led to it.

Why AI helps, and where it goes wrong

AI is good at the mechanical part. Given a transcript or a page of rough notes, it can pick out the decisions, list the actions with their owners, and write them in a consistent shape. That takes a job that used to be twenty minutes and makes it a two-minute read.

It goes wrong in predictable places:

• Names and numbers. A transcript can mishear a name, or a figure, and the draft will repeat the mistake confidently.
• Who owns an action. If nobody said "I will do that", the draft may guess, or assign it to whoever spoke last.
• Decisions that were only suggested. "We could move the launch to March" is not "the launch moves to March". Check that proposals were not turned into decisions.
• Tone and politics. A draft does not know what is sensitive. Some things belong in the room and not in the record.

So the rule is simple: AI drafts, a person who was there approves. Treat the draft like a colleague's first pass, not like a recording of the truth.

Before the meeting: make the minutes easy

The best minutes start before anyone speaks. A short agenda, with an owner for each item, gives the draft its structure. In nerix, a meeting has a Before tab for exactly this: the agenda with a person for each topic, the guests and whether they are coming.

Then decide how you will capture what happens. There are two practical routes:

1. Live notes. One person types short notes during the meeting: decisions, actions and owners. This is the most reliable input, because a human decided what mattered at the time.
2. A recording. If everyone knows and agrees the meeting is recorded, the transcript becomes the input. It is more complete and less selective, so the draft needs more checking.

Many teams use both: live notes for decisions and actions, a transcript to settle what was actually said.

During the meeting: capture decisions as they happen

When a decision is made, say it out loud in one sentence and let the note-taker write it down. "So we agreed: the offer goes to the client on Friday, Maya sends it." Saying it twice, once to decide and once to record, removes most of the later arguments.

NXFIG0X In nerix, the During tab has live notes, decisions and action items side by side, so these are captured as separate things rather than buried in a paragraph. That matters later: an action item that exists as an item can become a task with an owner and a date, and a decision that exists as a decision can be found again.

After the meeting: draft, check, send

Within the hour, while people still remember, do this:

1. Make the draft. In nerix, the After tab has Make the minutes. It writes the minutes from the transcript or notes. If you have a recording, you can upload it there to get a transcript first.
2. Read it against your memory. Check names, numbers, dates and every decision. Fix what is wrong, and cut what should not be in the record.
3. Send it for review. Minutes can be sent to others for review and approved before they go out, so the record is agreed rather than assumed.
4. Send the recap. One email to the guests with the summary and the action items.

Do not skip step two. A fast draft that nobody checked is how a wrong deadline ends up in writing.

Turn actions into work, the same day

Minutes that only list actions do nothing by themselves. The test of a good meeting process is whether the actions end up where people already look. In nerix, action items can be filed as tasks in Work, with an owner and a due date, so they appear in people's own lists and boards rather than only in a document. If your team talks in Spaces, the conversation that follows can live there too, in the topic for that project, instead of in five separate email threads.

If you do not use nerix for this, the principle still holds: every action leaves the meeting with one owner and one date, and lands in the place where that person looks every day.

A simple format that works

Use a short, steady shape so people learn where to look:

• Meeting: name, date, time, who attended.
• Decisions: numbered, one sentence each.
• Actions: what, who, by when.
• Open questions: what is still undecided, and who will bring it back.
• Next meeting: date.

Our free meeting minutes template has this shape ready to fill in, and downloads as Word or PDF. For the message that goes out afterwards, the follow-up email after a meeting is a good starting point.

A note on recordings and privacy

If you record, tell people before you start and let them say no. Some meetings should never be recorded: personnel matters, legal advice, sensitive negotiations. For the ones you do record, know where the audio and transcript go. nerix stores data in the EU, on servers in Germany, and never uses your content to train a model, and the Security page explains what happens to text when it is sent to a model provider. Reading it takes five minutes, and it is worth doing before the first meeting you record.

The short version

Capture decisions and actions as they happen. Let AI write the first draft from them. Check names, numbers and decisions yourself before it goes out. Then make sure every action becomes a task with an owner and a date. That is most of what makes meetings worth holding.

Prices checked in October 2026. Vendors change plans often, so check the official pages: Microsoft, ChatGPT Business, Claude, Gemini and Mistral.

Where Microsoft Copilot stands

Microsoft lists Copilot Business as an add-on at $18 per user a month on a yearly term (originally from $21, with the discount offered to eligible existing customers until the end of 2026, for the first year) and $25.20 month to month. Bundles are listed too: Microsoft 365 Business Standard with Copilot at $23.50 per user a month billed yearly, and Business Premium with Copilot at $32. Copilot Chat is included at no additional cost with eligible Microsoft 365 plans.

Its strength is reach. It works inside Word, Excel, PowerPoint, Outlook and Teams, and with a Copilot licence it can use the files and mail you already have. Microsoft's documentation says Copilot Chat data is stored and processed in the EU or EFTA for EU customers, with a caveat: under heavy load, model calls can reach other regions.

Its limits are the other side of the same coin. It needs a qualifying Microsoft 365 plan, it is priced as an add-on, and without the paid licence Copilot Chat cannot read your organisation's shared data, although you can upload files to it directly.

The alternatives at a glance

ChatGPT Business and Claude Team

These are the two general-purpose assistants most teams try first. ChatGPT Business is $25 per user a month, or $20 billed yearly, and a workspace needs at least two paid seats. Claude Team is the same price, $25 a month or $20 yearly, for teams of two to 150, with a Premium seat at $125 a month ($100 yearly) for heavy users.

Both give a team a shared workspace with admin controls and business data terms, and neither requires Microsoft. Where they fall short: they do not read your Microsoft 365 files by themselves, so you upload documents or set up connectors, and each offers only its own maker's models.

Gemini Enterprise

Google lists Gemini Enterprise Business from $21 per user a month and Standard or Plus from $30. It is the counterpart of Copilot for companies on Google Workspace, so it makes the most sense if that is where your files are. If your company is on Microsoft, it brings little of Gemini's main advantage.

Mistral Le Chat

Mistral lists Team at $24.99 per user a month, with up to 30 GB of storage per user, domain verification and data export. SAML single sign-on and audit logs are on the Enterprise tier, priced on request. It appeals to European teams who want to buy from a European company. Mistral's page does not state where Le Chat data is hosted, so ask before assuming.

nerix

We make nerix, so read this with that in mind. nerix is not an assistant bolted onto one office suite. It is a workspace where chat answers from your documents with the page of each source shown, alongside a library, team chat, tasks, a help desk, meetings and email drafts. You choose the model per task across providers: Mistral is the default, processed in France, with OpenAI, Anthropic and Google available, and an owner can restrict the workspace to providers hosted in its region. Hosting is in Germany.

Prices are in euros: Free for one person, Plus at 15 euros, and team plans per seat, Team at 24 euros (three seats minimum) and Business at 42 euros (ten minimum, with single sign-on and an audit log). Credits pay for AI work, shown before you send, with a spending cap on by default. See pricing and models.

Falls short: it does not live inside Word, Excel or Outlook, it has fewer integrations than Microsoft, and it has no SOC 2 or ISO 27001 certificate yet, as its security page says. It suits teams who want the AI to work on their documents and their team's work in one place, not teams that want an assistant inside Office.

How to choose

1. Try Copilot Chat first. It costs nothing extra on eligible plans. If it covers what people ask, you may not need a licence at all.
2. Count who needs the paid licence. The add-on is priced per person. Buy it only for people who work in Office all day.
3. Decide where your knowledge lives. If it is in SharePoint and Outlook, Copilot's native access is hard to match. If it is in PDFs, shared folders and mixed tools, a document-first workspace may serve better.
4. Decide on model choice. One vendor's models are simpler. A multi-model tool lets you use a cheaper model for routine work.
5. Check data terms and location for the exact plan you would buy.
6. Run a two week trial with five real tasks and compare the answers and the cost per person.

A word on switching costs

Leaving Copilot is rarely all or nothing. Your files stay in Microsoft 365, and your people stay in Outlook and Teams. What changes is where the AI work happens. Teams that move part of it usually keep the following in mind.

First, the assistant outside Microsoft will not see your mail or SharePoint unless you connect it, so decide which documents you will bring across and where they will live. Second, rules about client data still apply: put the rule in writing, such as "no client names in the free tool", and give people the approved tool so they are not tempted by an unapproved one. Third, count the full cost, including admin time, training and the licence you may still keep for a few Office power users.

The short version

Microsoft Copilot is hard to beat if your work is inside Microsoft 365, and its included chat costs nothing extra. If the add-on price or the single vendor bothers you, ChatGPT Business, Claude Team, Gemini Enterprise, Mistral Le Chat and nerix are all credible. Compare them on your own tasks, check where data is processed, and buy seats only for the people who will use them.

Below, we cover what an NDA does, when a one-way NDA fits and when a mutual NDA is fairer, and which parts to read carefully before you sign or send one. It is general information, not legal advice. Rules differ between countries and states, so where a lot depends on it, have a lawyer where you are look at it.

What an NDA does, and what it does not

An NDA does three things. It defines what counts as confidential. It says what the receiving side may and may not do with that information. And it sets out what happens if someone breaks the promise.

It does not make information secret by itself. If someone is determined to misuse what you shared, an NDA gives you a legal claim after the fact, not a lock. That is why the first protection is always to share less: give people what they need for the purpose and no more, and share the most sensitive parts last, if at all.

An NDA also does not turn an idea into property. It protects the confidentiality of what you disclosed. It does not stop someone from independently coming up with the same idea.

One-way NDA: one side shares, one side protects

In a one-way NDA, sometimes called unilateral, one party discloses and the other receives. Only the receiver is bound.

Use a one-way NDA when the flow of information really goes in one direction:

• You are about to show a supplier, a freelancer or a contractor your plans, and they have nothing confidential to show you.
• You are hiring or onboarding someone who will see your customer details.
• You are briefing an agency on a launch that has not been announced.
• An investor or buyer will review your numbers before a deal.

The advantage is that it is short and simple, and it protects the side that needs protecting. The risk is that it can look one-sided if the other party is also going to share something. If they will, a one-way NDA leaves their information unprotected, and a fair counterpart will ask for a mutual one.

Our free one-way NDA template covers this case, and downloads as Word or PDF.

Mutual NDA: both sides share, both sides protect

In a mutual NDA, sometimes called bilateral, each party can disclose and each promises to protect what it receives.

Use a mutual NDA when both sides will exchange sensitive information:

• Two companies are exploring a partnership or joint project.
• A company and a supplier are designing something together.
• A possible merger or investment where both sides open their books.
• Two freelancers are teaming up to bid for a larger job.

A mutual NDA is usually easier to agree, because neither side feels it is taking all the risk. It also avoids the awkward moment when the first NDA turns out not to cover what the other side later wants to share. If you are unsure which to use and the discussions could go both ways, a mutual NDA is the safer starting point.

Here is the mutual NDA template, also free to fill in online.

The clauses worth reading carefully

Whichever type you use, these are the parts where agreements differ and where problems appear.

Definition of confidential information

Is it everything the other side learns, or only what is marked "confidential"? A broad definition protects more but may be harder to defend. A narrow one is clearer but can leave gaps. Many agreements cover information that is marked confidential and also information that a reasonable person would understand to be confidential.

The exceptions

Almost every NDA excludes information that was already public, that the receiver already knew, that the receiver developed independently, or that came from a third party who was free to share it. These are normal and fair. Check that they are there, and that they cannot be stretched to swallow the whole agreement.

Permitted use

The receiver should be allowed to use the information only for the stated purpose, for example "to evaluate a possible partnership". Without that, the agreement says what they must not tell people, but not what they may do with it themselves.

Who else may see it

Receivers often need to share with their own staff, advisers or contractors. Good agreements allow this only to people who need to know and who are bound by similar duties, and make the receiver responsible for what they do.

How long it lasts

Set a period that fits the information. A product launch date stops being secret on launch day. A trade secret such as a formula may need protection for as long as it stays secret. Many agreements use a fixed term for general information and longer protection for trade secrets. A term that is too long can make the agreement harder to agree, and one that is too short can leave you exposed.

Return or destruction

What happens to the documents and files at the end? The usual answer is that the receiver returns or deletes them on request, and confirms that they have done so, with a sensible exception for copies that law or backups require them to keep.

Governing law and disputes

Which country's or state's law applies, and where would a dispute be heard? This matters more than people expect when the two sides are in different places. It is also one of the points where local legal advice is most useful.

Mistakes that make an NDA useless

• Signing it after the meeting. The NDA protects what is shared after it is signed. Sign first.
• Naming the wrong parties. Use the legal name of the company, not a brand name, and check who is actually signing.
• A vague purpose. "For business discussions" gives the receiver a lot of room. Say what the purpose is.
• No way to prove what was shared. Keep a simple record of what you disclosed and when.
• Using an NDA to cover everything. If an agreement tries to protect everything, courts and counterparties take it less seriously. Protect what really matters.

Before you send or sign one

Ask four questions. What exactly am I protecting? Is information going one way or both? For how long does it stay sensitive? Does this agreement fit the law where we are?

For a simple, low-risk exchange, a careful template is a sound starting point. If you want to adapt the wording, you can open a template in the nerix chat and ask for changes, for example a shorter term, an extra clause for contractors, or a plainer version. nerix writes the draft, but it is not a lawyer and does not know the law where you are. For anything with real money or a real trade secret behind it, have a qualified lawyer read the final version.

An NDA is a small document that sets the tone for a relationship. A clear, fair one, signed before the sharing starts, usually earns more trust than it costs.

Prices checked in October 2026. They change often and differ by country and billing period, so open the official pages before you decide: Notion, Coda, ClickUp, Google Workspace.

Why people look for an alternative

Notion AI is capable, and most complaints are about packaging rather than quality. On Notion's pricing page the Free and Plus plans include Notion AI as a limited trial, and the Business plan, listed at 19.50 euros per member a month, is where it is included. For a team of ten, that is a real jump from the 9.50 euros Plus plan. Others find Notion's blank-page flexibility more work than they want, or they already pay for another suite that includes AI.

The options at a glance

Notion AI

Good at: one place for notes, wikis and databases, with AI that can work on the pages you already have. Notion's Business plan lists its AI agent, AI meeting notes and enterprise search (in beta).

Falls short: the price of the plan that includes AI, and the time it takes to set up a workspace well. On the Free and Plus plans, AI is a limited trial, so you cannot build a habit on it.

Price: Free, Plus at 9.50 euros and Business at 19.50 euros per member a month on Notion's euro page. Enterprise is custom.

Coda

Good at: documents with tables, buttons and automations inside them, so a doc can behave like a small app. Coda AI works on that content. Paid plans include monthly AI credits for Doc Makers, and the credit amounts rise by tier.

Falls short: Coda is priced per Doc Maker, which is easy to misread, and the free plan gives only a trial of AI. The company is now showing its product under the Superhuman Docs name, which can confuse a first visit.

Price: Coda's pricing pages have changed recently and sources disagree, so check the current figure on their site.

ClickUp

Good at: work management first, with docs, chat and AI around the tasks. ClickUp's Free Forever plan has unlimited tasks and members, and its pricing page lists a small block of AI credits on it.

Falls short: a lot of features means a lot of settings. The free plan has tight storage and caps on spaces and automations, and AI is metered in credits, with extra credits sold in packs.

Price: paid plans are listed from about 9 dollars per user a month billed yearly, but ClickUp's page shows two different layouts, so confirm on the page.

Google Workspace with Gemini

Good at: Docs, Gmail and Drive are probably where your files already live, and Gemini works inside them. Business Starter lists basic Gemini access.

Falls short: Starter limits the advanced features, such as generating presentations and building spreadsheets, to higher plans. It is a suite, not a wiki, so structure is up to you.

Price: Business Starter is 7 dollars per user a month on the annual plan and 8.40 dollars on the flexible plan, per Google's help page.

nerix

Good at: working from your own documents. You put files in the library, ask questions in chat and get answers with sources. AI output lands in the Sheet as a document with versions, so you can edit it, compare versions and restore an old one. You choose the model, and nerix.ai runs on servers in the European Union today.

Falls short: nerix is not a copy of Notion's page-and-database model, and it will not replace a wiki you have built over years. It is a younger product, and it has fewer integrations than the big suites.

Price: Free for one person, with 3,000 credits a month, and it stops at its limit instead of charging you. Plus is 15 euros a month, and Team is 24 euros per seat a month from three seats. A credit is the unit of AI work, and the app shows what a question costs before you send it. Details are on the pricing page.

How to choose

• You mainly want your own documents searchable and answerable. Start with nerix or Coda.
• Your team lives in tasks. ClickUp keeps notes close to the work.
• You already pay for Google Workspace. Test Gemini first, since you may already have it.
• You love Notion's structure and only dislike the AI price. Stay, use the trial, and use a separate chat assistant for drafting.

Whatever you pick, run a test on real material: a long meeting note, a messy policy, a client brief. Check the answers against the source, as described in how to check AI answers before you rely on them.

Before you move anything

Moving a workspace is the expensive part, not the subscription. Export your Notion pages first, as Markdown or CSV, and open the files to see what survived: tables, linked databases and images are the usual casualties. Move one area, such as a single team's notes, and live with it for two weeks. Keep the old workspace read-only for a month so nobody loses a page they need. Also check who owns the data and where it is stored: if your clients ask about EU hosting, find the answer for each tool before you move, and write down who can see what.

The short version

Notion AI alternatives fall into four groups: docs that act like apps (Coda), task-first tools (ClickUp), suites you may already own (Google Workspace) and document-centred AI workspaces (nerix). Notion includes full AI on its Business plan, so the cheapest path may be a free plan elsewhere. Test two options on your own files for a week before you move anything.

Big companies have onboarding departments. Small ones have a better tool: attention. With a simple 30 day plan, a small team can give a new hire a better start than many large firms.

Before day one

Between the signed offer and the first morning, do the practical things so that nothing is missing when the person arrives.

1. Paperwork. Send the contract and forms early, so day one is not spent signing.
2. Equipment and access. A computer, accounts, passwords, keys and a desk or a remote setup, ready and tested.
3. A message. A short, warm note from the manager and one from the team. Our welcome letter template is written for clients, but its structure suits any welcome: say you are glad, say what happens first, give a contact.
4. The plan. Tell the person where to be, when, whom to ask for and what the first day looks like.
5. A buddy. Name a colleague who answers small questions, shows where things are and has lunch with them.

Day one

Keep it simple and human. Greet the person at the door or on the call. Show them their place, introduce them to the team, and explain the day. Give them a few easy things to do so that they feel useful by the afternoon: set up accounts, read a short guide, shadow a colleague.

Avoid a day of reading policies in silence. Cover the essential rules (safety, security, hours, how to report sickness), and leave the rest for the following days.

The first week

The goal of week one is orientation. By Friday the person should know:

• what the company does and for whom,
• who is who and who to ask about what,
• how the team talks (which chat, which meetings, which tools),
• what their role is and what is expected in the first month,
• where documents, processes and examples are kept.

Plan the week with some structure: a short talk with the manager each day, time shadowing colleagues, a first small task with a clear finish, and an end of week talk. Ask what was confusing. You will hear about every gap in your own explanations.

Weeks two and three: learning by doing

Now give real work, in small pieces, with support. Choose tasks that matter but where a mistake is cheap. Say what a good result looks like. Review the work together, praise what is right and correct what is not.

Write down three goals for the first 30 days. For example:

1. Handle customer emails on their own with a check by the buddy.
2. Learn the order system and process five orders without help.
3. Meet each team member for a short chat.

Keep the goals few, concrete and achievable. People are anxious in the first month, and unclear expectations make it worse.

Make knowledge easy to find

New people ask the same questions, and the answers often live in someone's head. Each time a new hire asks something that is not written down, write it down. After a few hires you have a guide. Keep it in one place, searchable, and let the new hire fix mistakes in it. They see the gaps better than anyone.

Talk regularly

Short, steady talks beat long, rare ones. A weekly 20 minute check in in the first month, then every two weeks. Questions to ask:

• What has gone well this week?
• What has been confusing or slow?
• What do you need that you do not have?
• Is the work what you expected from the interview?
• Is there anything you hesitate to ask?

Write down the answers and act on one thing each time. Our follow up after a meeting template helps keep these notes tidy.

Day thirty

At the end of the month, hold a proper conversation. Review the three goals, say what has been good, name what to work on and set goals for the next 60 days. Ask for feedback about the onboarding itself: what helped, what was missing, what you should change for the next person. This is the most valuable survey you will ever run, because you can use the answers within weeks.

If it is not working, say it kindly and early. A new hire who is struggling needs more support or a different role, and it is much kinder to say so at day thirty than at day ninety.

Common mistakes

• Nobody is expecting them. The cheapest way to make someone feel unwelcome.
• Too much at once. A new person remembers a fraction of day one.
• Too little to do. Boredom feels like being unwanted.
• Hidden rules. Unwritten habits, such as who has coffee at ten, matter more than you think.
• Silence from the manager. Check in, even when everything seems fine.

Where nerix helps

Make the plan a project in Work: tasks for before day one, week one and the 30 day goals, each with an owner and a date, and the checklists a manager needs. Give the new person a place in a Space for the team, where they can ask questions in the open and find the answers later.

Feedback (early access) has a 30 60 90 day onboarding form, a weekly check in and a monthly one to one among its twelve starting forms. Copy one, change any question and send a link. In the chat you can ask nerix to draft the welcome message or the first week plan from your notes. It does not know your people or your rules, so adjust the draft to fit.

The short version

Prepare before day one. Make the first day human and light. Give the first week structure and the next weeks real work in small pieces. Write three goals, talk weekly and ask for feedback on the onboarding itself at day thirty.

The cure is not a clever tool. It is a small set of rules that everyone follows, and you can set up a system in an afternoon so everyone can find your business documents.

Decide what counts and who owns it

Start by listing the kinds of documents you keep: customer contracts, quotations and offers, invoices and receipts, supplier documents, employee records, policies and procedures, meeting notes, marketing material, certificates and licences.

For each kind, name an owner: the person responsible for it being filed and up to date. Without an owner, nothing is filed.

Keep the folder structure small

Deep, clever trees fail, because people cannot remember where a document belongs. Use two or three levels at most, with the first level matching how you think about the business. For example:

1. Customers
2. Suppliers
3. Finance
4. People
5. Policies and procedures
6. Projects
7. Marketing

Inside Customers, one folder per customer. Inside a customer folder, a short fixed set: Quotes, Contracts, Invoices, Correspondence. The same pattern everywhere means no one has to learn it twice.

When in doubt where something goes, pick the most likely folder and rely on search for the rest. Do not create a new top level folder for a single document.

Name files so they explain themselves

A good file name tells you what it is without opening it. A reliable pattern is date, who or what, and type, in that order:

• 2026-03-14 Green Valley quotation 1182
• 2026-04-02 Supplier contract Atlas Packaging
• 2026-05-01 Staff handbook v3

Put the date first in the year, month, day format so files sort in order. Avoid "final", "final2" and "new". Avoid names that only make sense to the person who made them. Write numbers the way your invoices do.

Agree the pattern, write it on one page and put the page where people look.

Version without chaos

Drafts are where trouble starts. Rules that work:

1. One live version. There is one current file, in one place. Others are marked as old or kept in a history.
2. Version numbers in the name, or use a tool that keeps the history, so you can go back.
3. Change notes. A line on what changed and who changed it.
4. Signed means locked. Once a document is signed or sent, save it as a final copy and edit only a new version.
5. Do not email edits around. When five people send back five versions, you have five problems. Use one shared copy.

Decide what is the "source" and what is the "output": the editable file and the PDF you send. Keep both, and name them the same.

Decide where it lives

The worst system is two places. Choose one home for each kind of document and say so. If the home is a shared drive, a document system or a library, everyone must know its name and have access. Avoid keeping business documents on personal laptops, in personal email or in chat messages only.

Set access carefully. Not everyone needs to see employee records or salary information. Give each group access to what they need, and review access when people join and leave.

Keep what you must, and only that

Write a short retention list: for each kind of document, how long you keep it and why. Tax records, payroll and some contracts have legal minimums that vary by country. Personal data should not be kept longer than you need it, and people may have rights to ask what you hold. Check the rules that apply to you, and ask your accountant.

Once a year, clear out what has passed its date, and note what you deleted.

Make search work

Search is only as good as what it can read. Scanned pages with no text, pictures of documents and badly named files are hard to find. When you scan, make the scan searchable, or store the text. Use consistent words, such as "quotation" rather than five different names for one thing.

Tags or short descriptions help for documents where the title does not say enough, such as a certificate with an obscure number.

Make it a habit

A system fails when it takes effort. Reduce the effort:

• Provide templates with the right names and structure, so new files start right. Our meeting minutes template and invoice template are examples of documents that always have the same shape.
• File at once, not "later". Later never comes.
• Do a monthly ten minute tidy: what is in the downloads folder, the desktop and the inbox that should be filed?
• Teach new hires on day one.
• Appoint one person to keep the rules alive.

Where nerix helps

The library holds your documents in one place that you can search by meaning as well as by word, so "what did we agree about cancellation with Atlas?" finds the contract even if the word "cancellation" is not in the title. In the chat you can ask questions about your own documents and each answer shows the page it came from. That makes it easier to find the right clause, and to check it.

Documents nerix writes open beside the chat and keep every version, so you can go back. Numbers and prices can be worked on in the Sheet. nerix cannot decide what is important to keep or what the law requires; the rules and the naming still need to come from you.

The short version

List the kinds of documents and give each an owner. Keep folders few and the same everywhere. Name files by date, subject and type. Keep one live version, one home and short retention rules. File at once and tidy monthly.

Below is a sequence of payment reminder emails, what to say in each, with a template for each stage, and when to stop being polite and start being formal.

Start before there is a problem

The best reminder is the one you never need to send. Most of what gets invoices paid on time happens before they are late:

• Agree terms in writing. The due date, the amount and how to pay should be stated in the quotation or contract, and repeated on the invoice.
• Invoice promptly. An invoice sent a month after the work arrives when the client has stopped thinking about it.
• Make paying easy. Put bank details or a payment link where they cannot be missed. State the invoice number to use as a reference.
• Send it to the right person. Ask who approves and pays invoices, and address it to them, not only to the person you work with.
• Be consistent. If you chase some clients and not others, they notice.

Our free invoice template covers the essentials, and a payment reminder template is ready for the next step.

A sequence that works

Choose a rhythm, write it down, and follow it for everyone. Here is a sensible one. Adjust the days to your terms.

Before the due date: a friendly heads-up (optional)

Three to five days before it falls due, a short note: "Just a reminder that invoice 1042 for 1,200 EUR is due on 14 November. Bank details are on the invoice. Let me know if anything is needed from our side." Not everybody does this. It helps most with new clients and large invoices.

The day after: a plain reminder

The day after the due date, send a short, neutral message. Assume an oversight. "Our records show invoice 1042 was due yesterday and has not been paid yet. It may have crossed with your payment. If it has, thank you, and please ignore this. The invoice is attached again for convenience."

A week after: a clear follow-up

If there is no answer, write again, still polite, but more direct. State the invoice, the amount, the original due date and how many days overdue it is. Ask for a specific action and date: "Please let me know by Friday when payment will be made, or if something is holding it up."

Two to three weeks after: a firm notice

Change the tone, not the manners. Be explicit that this is the second or third reminder. State what you will do next: pause further work, add the late fee your agreement allows, or send a formal demand. "If we have not received payment by 28 November, we will have to pause work on the current project."

After that: the formal demand

If a client who clearly received the invoice still does not pay, a formal demand letter is the next step. It restates the facts, the amount, the deadline and the consequences, in writing. Our demand letter for an unpaid invoice is a careful starting point. Before you send one, or consider collection or legal action, check what applies where you are, and consider asking a professional. Rules about interest, fees and notices vary widely.

What every reminder should contain

Whatever the stage, include the same details, so the reader can act without looking anything up:

1. The invoice number and date.
2. The amount and currency.
3. The original due date.
4. How to pay, with the reference to use.
5. The invoice attached again. Never make them search for it.
6. One clear request, with a date.
7. A way to reach you if there is a problem.

Keep it short. A reminder that needs scrolling will not be read to the end.

Tone: firm is not rude

You can be kind and clear at the same time. Some principles:

• Assume good faith at first. Most delays have innocent reasons, and an accusing tone makes people defensive.
• Be specific, not emotional. "The invoice is 12 days overdue" is better than "I am very disappointed".
• Do not threaten what you will not do. If you say you will pause work, be ready to.
• Keep every message on the facts. You may need these emails later. Write each one as though a third party will read it.
• Thank them when they pay. It costs nothing and keeps the relationship intact.

Phone, too

Email is a good record, but a short phone call or message can unstick a payment in minutes, especially when the problem is process rather than intention. After the second reminder, consider calling, and follow up by email with a summary: "Thanks for the call. As discussed, payment of invoice 1042 will be made on 21 November."

When the client says they cannot pay yet

Sometimes the answer is honest: cash is short. You have options, and it is better to choose one than to let the invoice age:

• A short extension, in writing, with a new date.
• A payment plan, with amounts and dates, confirmed in writing.
• A partial payment now, the rest later.

Whatever you agree, put it in an email and ask them to confirm. A vague promise helps nobody. If you offer a plan, think about what you will do if the first date is missed.

Using AI to draft reminders

nerix can write these for you. Ask in the chat to write an email, tell it the invoice number, the amount, the due date and how late it is, and say what tone you want. It writes the draft, and what it cannot know, such as a name or an amount, stays as a blank for you to fill in. You can then make it shorter, warmer or firmer with one click, and copy it or open it in your email app to send.

Two honest limits. nerix is not an accounting or invoicing system, so it does not know which of your invoices are overdue unless you tell it, and it does not chase them for you on a schedule. Keep that tracking in your accounting tool or a simple list. And it is not a lawyer: before any demand letter or collection step, check what the rules are where you are.

The short version

Set clear terms. Send invoices promptly and to the right person. Follow a steady sequence: a heads-up, a plain reminder, a clear follow-up, a firm notice, then a formal demand. Keep each message short, specific and polite, with the invoice attached again. Most clients pay when it is easy to pay and clear that you will follow up.

Prices checked in October 2026. Official pages: Perplexity, ChatGPT, Gemini, Claude, Kagi and Brave.

The options side by side

Perplexity

Perplexity is an answer engine: you ask, it searches the web and replies with numbered sources. Its pricing page lists Pro at $20 a month or $200 a year, with Max and enterprise plans above it. Pro adds higher limits, file uploads and more.

Where it is strong: speed, and the habit of showing sources every time. Where it falls short for some people: it is built around the open web, so it does not know your own documents, and its answers still need checking, like every tool here.

ChatGPT, Gemini and Claude

All three general assistants can search the web as part of a conversation, with free plans and paid plans from about $20 a month. ChatGPT Plus is $20 a month. Google lists a free Gemini tier that includes Deep Research, and paid plans from 4.99 euros a month in Germany. Claude has a free plan, Pro at $20 ($17 billed yearly) and Team seats from $20 per seat yearly.

Good for: people who want search, writing, files and analysis in one assistant, and who already pay for one of them.

Falls short: answers are woven into prose, so sources are sometimes less prominent than in a tool built around them. Check the links yourself, and note the usage limits on free plans.

Kagi

Kagi is a paid, ad-free search engine with an AI assistant. Its pricing page lists Professional at $10 a month and Ultimate at $25 a month, with Assistant access scaling with the plan and premium models in Ultimate.

Good for: people who want search results without advertising and tracking, with AI as an extra.

Falls short: you pay for search, which many people are not used to, and it is a search engine first, not a research agent.

Brave Search and Ask Brave

Brave says Ask Brave is free, works on any browser, needs no account and always grounds answers in the web, with sources. Brave also says questions are never used for training and that it does not retain IP addresses. Chats expire automatically.

Good for: free, private quick answers.

Falls short: it is built for quick answers, not long research reports, and Brave itself advises double checking AI responses before quoting them.

nerix

We make nerix, so keep that in mind. nerix is not a web search engine. It is a workspace where you ask questions across your own contracts, reports and notes, and every sentence shows the document and page it came from. A setting called "Answer only from your documents" makes it say so when the files do not hold the answer, and it offers to search the web, asking first before anything leaves your organisation.

You choose the model per task across Mistral (processed in France, the default), OpenAI, Anthropic and Google, and each answer names the model that wrote it. Plans are in euros: a Free plan, Plus at 15 euros a month, and team plans per seat. See chat with sources, library and search and pricing.

Falls short: if what you need is the fastest cited answer from the open web, Perplexity or a search engine does that job more directly. nerix is a better fit when the answer is in your own files. It still makes mistakes, and the product tells you to check the sources.

How to choose

• You search the open web all day and want quick cited answers: Perplexity, or the web mode of ChatGPT or Gemini.
• You want privacy and no ads: Kagi if you will pay, Brave if you want free.
• You want one assistant for everything: ChatGPT, Gemini or Claude.
• The answer is in your own documents: a workspace with a library and citations, such as nerix.

Whatever you pick, build the habit of opening sources. Ask the tool for the exact passage, check the date of the page, and be wary of claims that appear with only one source.

Questions to ask before you switch

Switching tools costs time, so it is worth knowing what you actually want from the change.

Is it the price? Perplexity Pro at $20 a month matches ChatGPT Plus and Claude Pro. If cost is the issue, the saving is in free plans (Brave, or the free tiers of the assistants) or in Kagi at $10 a month, not in another $20 subscription.

Is it the sources? Look at how each tool shows them. Perplexity numbers its sources by default. Others show them only when you ask, so prompt for links and quoted passages.

Is it privacy? Read what each vendor says about retention and training for your plan. Brave and Kagi are built around privacy. For work documents, a business plan with written terms is safer than any free tool.

Is it depth? If you need a long, structured report on a topic, try the deep research modes in the assistants, and expect to spend time verifying the result. A quick answer engine and a research report are different jobs.

Is it your own material? If half your questions are really about files you already own, an answer engine on the open web will keep missing the point. That is where a document workspace pays off.

The short version

Perplexity is strong at fast, cited web answers, and its alternatives win on other points. Kagi and Brave win on privacy, ChatGPT, Gemini and Claude win on being one assistant for many jobs, and nerix wins when the answer sits in your own documents. Try two for a week, open the sources, and pay only for the one you keep using.

This is a management review. Standards such as ISO 9001 and ISO 27001 require one, but you do not need a certificate to benefit. For a small business it can be a single focused afternoon, if the preparation is done beforehand.

Why bother

Day to day work is full of urgent things. Important things, such as a customer complaint that keeps coming back or a supplier who is getting worse, never feel urgent until they hurt. A review forces them onto the table with facts. It also gives you a record of decisions, which is useful for new managers, auditors, banks and investors.

Choose a few questions

A good review answers a small number of questions. A common set:

1. Goals. Did we do what we set out to do last period? Where did we fall short?
2. Customers. What are they telling us: satisfaction, complaints, repeat business?
3. Quality and problems. What went wrong, how often and did the fixes work?
4. Audits and checks. What did our internal checks find, and are the actions done?
5. Suppliers. Are the ones we depend on performing?
6. People. Do we have the skills and capacity? How is morale?
7. Risks and changes. What has changed in our market, laws and tools? What could hurt us next year?
8. Resources. What do we need to do next year's goals?
9. Improvements. What are our best opportunities?

You do not need all of them every time, but cover each at least once a year.

Gather the facts beforehand

The meeting is not the place to collect data. A week before, ask each owner for a one page summary of their area: the key numbers, what changed, what went well, what did not and what they propose. Keep the same format each time so that you can compare over time.

Useful facts, each from your own records:

• sales and margins against the plan,
• complaints, returns and corrective actions: number, causes, status,
• on time delivery and error rates,
• audit findings and how many are closed,
• supplier issues,
• staff survey results, turnover and training done,
• decisions from the last review and whether they were carried out.

Do not invent numbers or use ones you cannot back up. Say "we do not measure this" where that is the truth, and decide whether you should.

Put the summaries into one short pack and send it two days before. Ask everyone to read it. If the meeting begins with reading, you have lost the afternoon.

Run the afternoon

Two to three hours is plenty. A simple agenda:

1. Last time (10 minutes). What did we decide and what happened?
2. The pack, area by area (60 to 90 minutes). Each owner gives two minutes on the key points, then the group discusses. Ask what is surprising, what is getting worse and what is the cause.
3. Risks and changes (20 minutes).
4. Decisions (30 minutes). Move from discussion to actions.
5. Close (10 minutes). Read back the decisions and who owns them.

The chair keeps time, keeps people on facts and asks "so what do we do about it?". Disagreement is welcome. Blame is not.

Decide, don't just discuss

The product of the review is a short list of decisions, each with an owner and a date. Examples:

• Change the supplier for packaging by 30 June, owner: Dana.
• Add a second check to invoicing from next month, owner: Omar.
• Hire one person for customer support in the third quarter, owner: the managing director.
• Drop the lowest margin product line by the end of the quarter.

Aim for a handful. Five decisions done are better than twenty forgotten. Include resource decisions: money, time and people.

Record it

Write minutes the same day: the date, the attendees, the topics, the decisions and the owners. Keep them short. Our meeting minutes template gives the layout, and the follow up template is useful for sending the decisions to people who were not there. Keep the pack and the minutes together, so the evidence behind each decision can be found.

Follow through

Turn each decision into a task. Check them at your regular management meetings, and at the start of the next review ask the first question: were last time's decisions done? If the answer is often no, the problem is not the review, it is follow through, and that is a decision for the next one.

Common mistakes

• No preparation. The meeting becomes a long update.
• Only good news. A review with no problems is not a review.
• No decisions. A talk is not a review.
• Too many people. More voices, fewer decisions.
• No follow up. The most common failure.

Where nerix helps

Checks (early access) includes the yearly business review as one of its eight ready plans. The review can open by itself a few days before its date, with its questions filled in from a starting template and prepared from your workspace's own records, so the pack starts from real data, not from memory. Decisions become tasks in Work with owners and dates, and a decision with no owner is easy to see.

If you hold the meeting in nerix Meetings, the notes can become minutes and tasks. nerix can help you word a summary, but it only knows what is in your workspace, so add what is not there, and judge what the numbers mean yourself.

The short version

Choose a few questions. Collect one page per area beforehand, from real records. Spend the afternoon discussing causes and deciding. Write a short list of decisions with owners and dates, then check them at the next review.

The good news is that customers accept a fair increase more often than owners expect, when it is announced early, explained plainly and handled with respect. Here is how to write a price increase letter that keeps your customers.

Decide the number with care

Start from your own figures, not from fear. Work out what your costs have done since the last increase, what you need to earn for the work, and what similar businesses charge. If you do not know your margin per product or service, find out first.

Some practical points:

• A small, regular increase is easier to take than a big one after years of silence.
• Round numbers are easier to explain than odd ones.
• You may not need to raise everything. Raise where cost grew and demand is steady, and be careful where a competitor is close.
• Check your contracts. Fixed price agreements and subscriptions may have rules about when and how prices can change, and some places have consumer protection rules for notices.

If you do not have a spreadsheet of your prices, make one: product or service, old price, new price, percentage change. A Sheet is a good place to see the changes side by side and to check the arithmetic before anything is sent.

Choose who hears first, and how

Your biggest and longest standing customers deserve a personal message, or a call from you, before a general email. Smaller customers can receive a clear written notice. Make sure nobody hears it from a third party first.

Send the notice by the channel you usually use with them. If you invoice by email, email is fine. If contracts require notice in writing to an address, follow that.

Give enough notice

Notice protects the relationship more than the wording does. People need time to budget, compare and decide. Put the date the new price takes effect in the first lines, and make sure it is after the notice period your terms or the law require.

Orders already agreed, quotations that are still valid and invoices already issued should keep their old prices. Say so, because it removes a common worry.

Write the notice

Keep it to a short page. A good order:

1. The news. "From 1 February, our monthly plan will cost 54 instead of 49."
2. The reason, in one or two sentences. True and specific. "Our supplier costs and wages have risen, and we want to keep the quality you rely on."
3. What stays the same. Service, support, anything you promise.
4. What it means for them. If an order or plan is running, say what price applies and until when.
5. What they can do. Questions to a named person, the option to change plan or to end the agreement under the existing terms.
6. Thanks.

Our price increase notice template has these parts ready to fill in.

Words to avoid

Do not over apologise. "We are so sorry, we hate doing this" makes the increase sound like a mistake. A calm, respectful tone works better: you are telling them a fact and explaining it.

Do not blame others in a way that sounds like an excuse, and do not hide the increase inside a list of other changes. Do not use vague terms such as "adjustment" when you mean a higher price.

Do not promise "this is the last increase". You do not know that.

Answer the pushback

Some customers will ask why, some will ask for a discount and a few will leave. Prepare for each.

• Why? Give the same honest reason again, with one more detail.
• Can I keep the old price? Decide in advance whether there is any case where you will say yes, such as a long contract or a very small account, and be consistent. If you say yes to everyone who asks, the increase does not happen.
• I am thinking of leaving. Ask what matters most to them. Sometimes a different plan or a smaller package serves them better. If the answer is that they cannot afford it, accept it graciously. A respectful goodbye is better than a bad deal.

Reply to every message within a day. Silence reads as embarrassment.

Watch what happens

After the change, track how many customers stay, move to another plan or leave. Note which reasons come up. A few cancellations after a fair increase are normal. A wave of them tells you the price is out of step with the value people see, which is a reason to improve what you sell, not only to lower the price.

When something goes wrong

If your notice was late, unclear or wrong, say so quickly and fix it. A short, plain apology and a corrected price do more good than a long explanation. The customer apology email template shows the tone.

Where nerix helps

In the chat, tell nerix who the customers are, the old and new prices, the date and your reason, and ask for a draft notice. Email drafts (early access) opens it beside the chat with To, Subject and the message; you can ask for a shorter, warmer or firmer version, and each change is kept as a version. A blank is left wherever nerix could not know a fact, and nothing is sent until you press Send.

nerix does not know your contracts, your margins or the law on notices where you are. Read the draft as the customer will, and check every figure and date.

The short version

Work out the number from your costs. Tell your best customers first. Give clear notice, with the date and the reason, and keep running orders at the old price. Be calm, not apologetic, answer questions quickly and watch what happens.

What a project actually needs

Strip it back and a project needs five things:

1. A goal in one sentence, stating what is true when it is finished.
2. A list of the steps, broken down until each one is a task a single person can finish.
3. An owner for each task. One name, not a team.
4. A date for each task, even a rough one.
5. A place everybody looks, where the current state is visible without asking.

Everything else is optional until you feel the pain it solves. If you can answer "what is this project for, what are we doing next, who is doing it, and when?" in ten seconds, you are managing it well.

Write the goal and the edges

Before listing tasks, write two short things.

The goal. "The new price list is live on the website and sent to all customers by 30 November." Not "improve pricing". A goal you can check is a goal you can finish.

What is not included. Projects grow in the dark. A list of what you are deliberately not doing stops the quiet addition of extras. If the project is for a client, this belongs in a written scope. Our statement of work template and project proposal template give that shape.

Break it down until it is small

A task such as "launch the campaign" is not a task. It is a project. A good task is something one person can start and finish, usually within a few days, and everyone could tell whether it is done.

A useful test: could someone else look at the task title and know what to do? "Write the three product descriptions for the price list" passes. "Content" does not.

Break work down as far as you can still keep track of it. For most projects, ten to thirty tasks is plenty. If you have two hundred, you have gone too deep, or you are managing several projects as one.

One owner, one date

Two rules, and they do most of the work.

One owner. When two people are responsible, neither is. If a task needs two people, give it to one of them and name the other as a helper in the comments. The owner is not necessarily the one who does everything. They are the one who makes sure it happens.

One date. A task without a date will slide. The date does not have to be perfect, but it has to exist, because it is what lets you see what is late. When a date has to change, change it where everyone can see, and say why.

Pick the right view

The same set of tasks can be seen in different ways, and each answers a different question.

• List: what do I do today? Good for personal planning, sorted by date or priority.
• Board: where is everything in the process? Columns such as To do, In progress, Waiting and Done show the flow and show where work piles up.
• Table: compare many items by their details: owner, date, priority, tags. Good for planning and clean-ups.
• Calendar: what is due when? Good for anything with deadlines or for spotting a crowded week.

In nerix, Work offers all four on the same items, so you do not have to maintain separate lists. You can also save a view, such as "due this week" or "assigned to me", and come back to it. States can be named to fit the way your team works: the defaults run from Triage and To do through Doing and Waiting to Done.

Keep the work and the talk together

A common cause of overhead is that tasks live in one tool and conversation about them lives in another. Someone asks in chat "did the price list go out?", someone else answers in an email, and the task still says "in progress".

The simplest fix is to keep discussion attached to the task. Comments on the item hold the decisions and the questions. If you use Spaces for team chat, a message can be turned into a task, so something that was agreed in conversation does not depend on someone remembering it. Meetings work the same way: actions decided in a meeting should end up as tasks with an owner and a date, and not only as lines in minutes.

The weekly check

One short, regular review does more than any amount of reporting. Fifteen to thirty minutes, once a week, with the same four questions:

1. What was finished? Note it. It keeps morale up and shows progress.
2. What is stuck, and why? The most important question. Name the blocker and the person who can remove it.
3. What is due in the next two weeks? Is anything at risk?
4. What should we stop, change or add? Remove what no longer matters, so the list stays honest.

Look at the board together. Anything that has sat in the same column for more than a week deserves a sentence of explanation. Do not turn it into a status recital in which everyone reads out their own list. That belongs in the tool, so the meeting can be about decisions.

Status updates that people read

If you have clients or a manager who need updates, keep them short and regular. A good update has four parts:

• Where we are, in a sentence.
• What we finished since the last update.
• What is next.
• What is at risk, or what we need from the reader, with a date.

Bad news belongs at the top, not hidden at the bottom. People trust a team that says "this is late, here is why, here is the new date" far more than one that is always green until it is suddenly red. Our project update email template has this shape ready.

Mistakes to avoid

• Too many tools. Every extra place to check costs attention. One list beats three.
• Planning too far ahead. Plan the next two to four weeks in detail and the rest loosely.
• Tasks with no owner or date. They will not be done.
• Never closing things. Finish or delete. A list full of stale items teaches people to ignore it.
• Measuring activity instead of results. Ask whether the goal is closer, not whether people look busy.

Using AI where it helps

AI is useful for the setup. Describe the project to nerix in the chat, and ask it to propose the steps, and it can draft a task breakdown for you to correct. It can also summarise a long thread into the decisions and actions that came out of it, and help draft the weekly update from the tasks it is allowed to see. It does not know your team's capacity or your client's politics, so treat what it proposes as a first draft and adjust dates and owners yourself.

The short version

Write the goal. Break the work into small tasks. Give each one owner and one date. Keep everything in one place everyone looks. Meet weekly for fifteen minutes about what is stuck. Update the people who need updates, with the bad news first. That is project management with the overhead taken out.

If you have never done one, the first is the hardest, because you are inventing the routine. This guide gives you a plan you can follow in a week.

What an audit is, and what it is not

An audit asks three questions about a part of your work:

1. Do we have a rule or a way of doing it that we agreed?
2. Do people follow it?
3. Does it do what we need?

It is not a hunt for someone to blame, and it is not a test of people. It checks the system. If you treat it as a trial, people will hide things and the audit will show you a tidier picture than the truth.

Choose one area and write down why

Do not audit everything. Pick one area for the first time. Good choices are the ones where a mistake costs money or trust: taking and fulfilling orders, handling customer complaints, invoicing, managing a supplier, or looking after customer data.

Write one sentence on the purpose. "To check that every customer complaint is logged, answered within two days and followed up with a fix" is a purpose you can test. "To look at customer service" is not.

Then choose the standard you audit against. It may be your own written procedure, a customer's requirement, a law, or a recognised standard such as ISO 9001 for quality or ISO 27001 for information security. If you have no written procedure yet, the audit still helps: it will show you what people actually do, which is what you should write down.

Pick the auditor and tell people

The auditor should not audit their own work. In a small team, ask a colleague from another area, or a trusted outsider. Give them an hour of preparation and the authority to ask questions.

Tell the people being audited when it will happen and what for. A friendly note is enough: "Next Tuesday Sara will look at how we handle complaints. She will read a few records and ask questions. It is about the process, not about anyone's performance."

Prepare the questions

Write 8 to 15 questions before you start, each of which can be answered by evidence. For the complaints example:

• Is there a written way to record a complaint? Where is it?
• Pick five complaints from the last three months. Is each one logged with the date and the customer?
• Was each answered within the time we promised?
• For each one, what was done to fix the cause?
• Do the people who handle complaints know the rule?

For each question, note what evidence would answer it: a record, an email, a screen, a person's explanation. Evidence beats opinion.

Do the audit

Sit with the work. Ask people to show you, not to tell you. Pick samples at random, not the ones people offer. Write down what you see in plain words, the date and where you saw it.

Some tips for the conversation:

• Be curious, not clever. "Show me how you did this one" gets better answers than "why didn't you follow the rule?".
• Ask open questions and let silences run a little.
• Say thank you. People are doing you a favour by being open.
• Do not fix things during the audit. Note them. Fixing as you go hides the pattern.

Judge each point

For every question, choose a result:

• Conforms: the rule exists and is followed.
• Observation: it works, but you see a risk or an idea.
• Minor finding: a gap that is not a serious risk, such as one record missing.
• Major finding: a serious or repeated gap, such as no record at all or a rule that is widely ignored.
• Not applicable: it does not apply, with a reason.

An issue needs a note: what you saw, where, and which rule it breaks. Keep the language neutral. "Three of five complaints had no reply date recorded" is a finding. "The team is careless" is not.

Write the report and agree on actions

A one page report is plenty: the purpose, the date, the auditor, the results, the findings and a sentence on the overall picture. Share it with the people audited before anyone else sees it, so they can correct a mistake of fact.

For each finding, agree on an action with an owner and a date. Aim to go beyond "we fixed this one" to "this will not happen again": ask why it happened, and change the thing that allowed it.

Close the loop

Set a date to check that each action worked. An audit that produces a list of findings and no follow up is a paper exercise. When the fix is checked, close the finding, and note the date.

Then plan the next one. Many small companies audit one area every month or quarter, so that everything is looked at over the year, and the riskiest areas more often.

Where nerix helps

Checks (early access) is built for this. The plan says what is checked, how often and by whom. A few days before a date, the check opens by itself with its questions filled in from a starting template; eight are ready, including a yearly internal check for ISO 9001 or ISO 27001, a supplier check, a process check and a weekly 5S check. Each question has the evidence asked for. You choose Conforms, Minor issue, Major issue, Observation or Not applicable and write what you saw, adding a link to the evidence. An issue needs a note, and a Not applicable needs a reason.

NXFIG0X Every finding becomes a task in Work with an owner and a due date, and it can be closed only after someone checks that the fix worked. In the chat you can ask nerix to help word a finding neutrally or to draft the summary. The judgment about what you saw stays with the auditor.

The short version

Choose one area. Write a purpose you can test. Use an auditor who is not auditing their own work. Prepare questions and look for evidence. Record findings in neutral words, agree on actions with owners and dates, and check that they worked.

A request for proposal, or RFP, fixes that. It tells every supplier the same thing about what you need and asks them to answer in the same way. The result is offers you can put side by side and a decision you can explain. It does not have to be long or formal.

Quote or proposal?

Choose the right kind of request.

• A request for quote fits when the product is known: ten chairs of this model, a print run of this size. You want prices, delivery and terms.
• A request for proposal fits when you describe a problem and want the supplier to propose a solution: "we need to take online bookings and reduce no shows". You want ideas and approach as well as cost.

For simple things, a short email is enough. Our request for quote email template shows what to include. For bigger or less clear needs, the request for proposal template gives you the structure used below.

Be clear about what you need

Before writing, talk to the people who will use the result. Write down:

1. The problem or goal. What are you trying to achieve, and why now?
2. The scope. What must be delivered, and what is out of scope?
3. Must haves and nice to haves. Separate them. If everything is a must, nothing can be compared.
4. Constraints. Budget range, deadline, systems it must work with, legal or security requirements.
5. How success will be judged. Results you can see after the work.

If you do not know your budget, say it is open, but be aware that suppliers will otherwise guess, and the offers will be very different. Giving a range is often better: it helps good suppliers propose the right solution.

Write a short RFP

One to three pages is usually enough. Include:

• About you. Who you are, in a paragraph.
• The need. Goal, scope, must haves, constraints.
• What to include in the response. The questions you want answered, in the order you want.
• Process and dates. When questions close, when answers are due, when you will decide and when the work should start.
• How you will choose. The criteria and their weight.
• Contact. One person for questions.
• Terms. Confidentiality, how long offers must stay valid, that you are not bound to choose any.

Keep the language plain. Complicated documents get fewer good responses.

Ask the same questions of everyone

For comparison, structure the response. Ask each supplier to give:

1. A short summary of how they would solve the problem.
2. The work plan and timeline, with milestones.
3. The team who will do it, with their relevant experience.
4. Two or three similar past projects and references you may contact.
5. The price, broken down into parts, with what is included and what is extra, and the payment schedule.
6. Assumptions and risks.
7. Support after delivery.
8. Anything you ask for security, data handling or legal status.

Ask them to keep to a page limit. You will thank yourself later.

Be fair, and be seen to be fair

Send the same information to everyone at the same time. If a supplier asks a question whose answer would help others, share the answer with all, without naming who asked. Give enough time to respond, a week or two for a small request. Do not use one supplier's ideas to bargain with another, and do not ask for free design work that you do not intend to pay for.

If you already prefer one supplier, say so honestly and consider whether an RFP is a fair process or a waste of other people's time.

Choose with criteria

Before reading any response, decide how you will score. A simple set of criteria, each with a weight:

Each person on the panel scores each response, then you compare and talk. Look at total cost, not only the headline price: extras, support and what happens in year two. Call references and ask what went wrong and how the supplier handled it.

Put the scores in a Sheet, where the weights and totals are calculated for you, and keep the record. If a cheaper offer is not chosen, you can show why.

Negotiate and decide

Go back to your top one or two with specific questions and a request for a final offer. Check the details that matter: what is included, how change requests are handled, who does the work and what happens if it goes wrong. Then tell all suppliers the outcome, politely, and offer to give brief feedback to those who ask.

Put it in writing

The winning proposal is not yet a contract. Turn it into one: a statement of work or agreement with scope, price, timeline and terms. A purchase order is useful for goods. Do not start the work, or pay a deposit, until the terms are agreed in writing.

Common mistakes

• Vague needs. You get vague offers.
• Too many suppliers. Quality of evaluation falls.
• Price only. The cheapest offer may be missing half the work.
• No criteria. The choice follows the best presentation, or the best friend.
• No reference calls. They are the cheapest due diligence.

Where nerix helps

In the chat, tell nerix what you need and the constraints, and it drafts a first RFP that you edit. Paste suppliers' responses, or upload them, and ask for a side by side comparison of price, scope and assumptions, or for the points where an offer is silent. Answers show the page they came from, so you can check each claim. Scores and totals can be worked out in the Sheet.

nerix does not know your priorities or the supplier's reputation, and it can misread a table. Check the numbers, and make the decision yourself.

The short version

Choose between a quote and a proposal. Describe the goal, scope, must haves and constraints. Ask everyone the same questions and treat them fairly. Score against criteria decided in advance, call references, and turn the winner into a written agreement.

This guide describes a way to run a help desk with two to ten people, without turning it into a department.

The signs it is time

You probably need a help desk if you recognise any of these:

• You ask in the team chat, "did anyone reply to this?"
• A customer writes twice because the first message went unanswered.
• You cannot say how many requests came in last week, or how long they took.
• The person who knows the answer is on holiday and nobody can see the history.
• Requests arrive by email, by phone, in chat and through a web form, and live in four places.

None of these needs a complicated tool. They need one list that everything lands in.

Principle one: one list, every channel

Every request, whatever way it arrives, becomes an item in one place. An email, a form on your website, a phone call someone writes up: all of them are requests with a requester, a subject and a description.

In nerix, the Desk is that list. Customers can write through a portal, a widget on your website or by email once those are set up, and if someone got in touch another way, you can add a request yourself with New request. Staff see all of them together, with lists for the ones that matter most: Unassigned, Mine, Waiting on customer, and Breached or due soon.

The channel matters less than the rule: if it is not in the list, it does not exist.

Principle two: every request has one owner

A request with two owners has none. When a request arrives, someone takes it, and their name goes on it. Everyone can see who, so nobody duplicates work and nobody assumes.

For a small team, a simple way to share the load is a "take next" habit: when you finish something, take the next unassigned request, oldest first. Desk has a Take next button for exactly this, which gives you the next unassigned request. It removes the cherry-picking that leaves the hard requests to age.

Ownership can move. If you are out, or the request needs someone else, hand it over, with a note saying why. The owner field should always answer the question "who is looking at this right now?"

Principle three: public replies and internal notes are different things

Support work involves two conversations: the one with the customer, and the one among the team about the customer. Mixing them is how an internal remark such as "this customer is difficult" ends up in an email.

Keep them separate. In Desk, a Public reply goes to the requester, and an Internal note stays with the team. Use notes freely: what you tried, what you found, who you asked. The next person who picks up the request, or you on a different day, will thank you.

When you need another person's input without bringing them into the customer's thread, a side conversation lets you ask them directly while the request stays in one place.

Principle four: say how fast you will reply, and keep the promise

Customers are more patient than you fear, if they know what to expect. Pick two targets and write them down:

• First reply: how soon every request gets a human answer. This does not need to be the solution, only an acknowledgement that someone is on it.
• Solution: how soon you aim to resolve a request, usually by priority.

Choose numbers you can meet on a normal week with your real team, including weekends and holidays. If you promise four hours and manage them one day in three, you have taught customers that your promises mean nothing. A longer target that you keep is worth far more.

Desk shows response targets on each request, First reply and Solution, and collects the ones that are late or close to late under Breached or due soon. Start your day there. If that list is empty, the day is going well.

Principle five: write things once

Most support questions are repeated. Password resets, delivery times, refund rules, how to export data: you will answer these hundreds of times. Write the best answer once, save it, and reuse it.

Saved replies, called macros in Desk, do this. A good macro is not a robotic block of text. It is a well-written reply with blanks for the details, which you read and adjust before sending. The goal is consistency and speed without losing the human touch.

Two habits keep macros good:

• When you find yourself typing the same answer a third time, make it a macro.
• When a macro gets a follow-up question, fix the macro.

Some situations need more than a macro. A genuine apology for a mistake should sound like a person wrote it. Our free customer apology email template is a good starting point, and if refunds come up often, a clear returns and refund policy saves everyone time by answering the question before it is asked.

Principle six: close the loop

A request is not finished when you have answered it. It is finished when the customer knows it is finished. Mark a request solved only when the problem is actually solved, and tell them. In Desk, solving a request tells the requester.

Where a request reveals a bug, a gap in your product or a wrong line on your website, make a task for it and link it. Desk sits next to Work, where tasks live, so a problem found in support can become a task with an owner and a date, rather than a complaint that nobody remembers.

What to measure, and what not to

You do not need a dashboard of forty numbers. Four are enough:

1. How many requests came in this week. To see trends and plan staffing.
2. How long to the first reply. Is the promise kept?
3. How long to solution. Where are things getting stuck?
4. What the top three topics are. These are the things to fix at the source, so people stop asking.

Be careful with measures that reward speed over quality. If you judge people on how fast they close requests, they will close requests. Ask also whether customers had to come back with the same problem.

A simple weekly routine

• Daily, first thing: check Breached or due soon, then Unassigned.
• Daily, last thing: make sure nothing is waiting on you that you can answer in five minutes.
• Weekly, 20 minutes: look at the top topics, add or fix a macro, create tasks for what should be fixed at the source.
• Monthly: look at the targets. Are they still the right ones?

Setting it up in nerix

The Desk is one of the team places in nerix, alongside Work, Spaces and Meetings. It needs Work and the collaboration features switched on, and people who manage the desk set up request types, the portal, widgets and macros in its settings. You do not have to configure everything on day one. Start with one list, a couple of request types and a handful of macros, and add the rest when the need is real.

What a tool cannot do is decide how your team treats customers. That comes from you: a clear owner, an honest target, a good answer written once, and the habit of closing the loop. The system only makes those habits visible.

A short weekly planning meeting solves both. It gives the team a shared picture of the week, a clear set of priorities and an owner for each thing. Done well, it takes half an hour and saves many hours of confusion.

Decide the purpose

A weekly meeting is for coordination. It is not for long discussions, training or detailed status reports. Say what it covers: what we did, what we will do, what is blocking us and what we need to decide. Anything else gets its own time.

Keep the group to the people who work together this week. If half the room has nothing to say, consider splitting.

Keep the rhythm

Same day, same time, same length. Start on time even if someone is missing, and end on time. A room that runs over trains people to arrive late. Use a call link or a room that is always the same.

For remote teams, ask people to turn on their cameras if they are comfortable, but do not insist. What matters is that everyone can speak.

Prepare in five minutes

The person leading the meeting, who can rotate, looks at the list of tasks and projects before the meeting: what is due this week, what slipped, what is waiting. They write the agenda as a short list. Team members update their own tasks beforehand, so the meeting is not spent on "where are we with X?" questions that the list could answer.

A simple agenda for thirty minutes

1. Wins and news (3 minutes). One good thing each, or one piece of news. It sets the tone.
2. Last week (5 minutes). What was due, what is done, what is not and why.
3. This week's priorities (10 minutes). The three to five things that matter most. Who owns each, what done looks like, what could stop it.
4. Blockers and help (7 minutes). Who needs something from whom? Agree who will help and by when.
5. Decisions (3 minutes). Anything that needs a yes or no now.
6. Recap (2 minutes). Read back the actions.

If a topic needs more than a couple of minutes, write it down for a separate talk and move on. A "parking list" is the most useful tool a chair has.

Set few priorities

The week has limited hours. If you list twelve priorities, you have none. Ask: if only three things get done this week, which? Make them clear, with an owner each. Everything else is "if time allows".

Describe results, not activity. "Send the quotation to Green Valley" is clear. "Work on sales" is not.

Leave room for what is unplanned. Support requests and urgent jobs will arrive. A good rule is to plan around two thirds of the available time.

Name owners and dates

Every action has one owner, even if several people help, and a date. "We should update the price list" is not an action. "Dina updates the price list by Wednesday" is. Write them down during the meeting, in a place everyone can see.

Handle problems in the meeting without solving them there

When a blocker comes up, find out who can help and agree on when they will talk. Do not spend ten minutes of everyone's time fixing a problem for two people. Say "Sam and Lee, can you sort this out today? Report back tomorrow."

Keep notes short and shared

Take notes of decisions and actions only, and send them the same day. The follow up after a meeting template and the meeting minutes template give shapes you can use. Five lines are enough for a weekly meeting. The list of actions should live where the team works, so that it is looked at between meetings.

Start the next meeting with the last actions. If they are not done, ask why, without blame: was it unclear, too big or blocked?

Common mistakes

• Status theatre. Everybody reads out what they did. Use the task list for that.
• One person talks. The chair should draw others in.
• No decisions. If it ends with "let us think about it", set a date to decide.
• Too long. Shorten it before people stop coming.
• Cancelling when busy. That is when you need it most.

Adapt as the team grows

Under five people, a ten minute stand up may be enough. With a larger team, ask each sub team to meet first and send one person to a short cross team meeting. Review the format every few months: ask the team what is useful and what is not, and change it.

Where nerix helps

Keep the week's tasks in Work, where each has an owner and a due date and you can see the list, a board or a calendar, so preparation takes a minute. Post notes and questions in a Space, so the discussion that follows has a place.

For meetings held in nerix Meetings, the notes can be turned into minutes with decisions and tasks, which keeps a written record without anyone typing it all. nerix can draft the summary, but check it before you share it, since it can miss context or mishear a name.

The short version

Same time every week, thirty minutes. Look at last week, choose three to five priorities with owners and dates, find blockers and decide what needs deciding. Park long discussions, write down actions and start the next meeting with them.

Many managers skip them when they are busy, or hold them as status meetings where the person reads out a list. The difference between a useful one and a wasted one is mostly structure and attitude.

Make it regular

Fix a time and keep it. Weekly suits new people and busy periods; every two weeks suits most teams; monthly is the longest that still works. Use the same day and hour, so it becomes part of the week.

Cancelling a one to one sends a clear message about what is more important. If you must move it, move it, do not drop it, and say why.

Make it theirs

The person should come with items. Ask them to add topics before the meeting, in a shared note or list. Often the best use of the time is the thing they would not have raised in a group: a worry about a colleague, a question about the future, a frustration with a tool.

You have items too, but treat the first half as theirs. If you talk for most of the time, change your habit.

A simple structure

Here is a shape for a 30 minute one to one:

1. How are you? (3 minutes) A real question. Listen to the answer, including what is not said.
2. Their topics. (10 minutes) What do they want to discuss?
3. Work and priorities. (7 minutes) What is going well? What is blocked? Is anything unclear?
4. Feedback, both ways. (5 minutes) Something specific you noticed, and a question: "Is there anything I could do differently to help you?"
5. Actions. (5 minutes) What will each of you do before next time?

Vary it. Every few meetings, spend a whole session on growth: what they want to learn, where they would like to be in a year, what would make the work more interesting.

Questions that open things up

• What is the most important thing on your plate this week?
• What is getting in your way?
• What are you enjoying, and what are you not?
• Where do you feel you are learning, and where not?
• Is there something you think I do not know about?
• If you were running this team, what would you change?
• How is your workload, honestly?

Ask, then wait. Silence is not a failure. People often answer the real question after a pause.

Listen properly

Put away your phone and your laptop. Take a few notes, and tell them you are doing so. Repeat back what you heard: "So the late deliveries come from the supplier changing the schedule, and you have no way to see it earlier?" If you disagree, ask a question before you answer. If you cannot solve something, say so and say what you will find out.

Do not use the meeting only to check progress. Progress can be seen in the work. Use the time for what cannot be seen there.

Give feedback in small pieces

Say what you noticed soon after it happened, specifically and kindly. "In the client call yesterday you explained the delay clearly and calmly, and the client relaxed" is feedback a person can repeat. If something needs to change, say it plainly and offer help. Save only the big topics, such as pay or a serious problem, for their own conversations.

Keep a short record

After the meeting, note the actions in two or three lines: who does what by when. Share the note, so you both have the same version. Our follow up after a meeting template and the meeting minutes template give formats. Do not write a transcript. Notes that run to pages will not be read.

Before the next meeting, read the last note. Starting with "Last time you said you wanted to learn the invoicing system, how is that going?" shows the person that they were heard.

Do what you said

The quickest way to ruin one to ones is to promise things and not do them. Keep your actions small and finish them. When you cannot do something, tell them why. People can accept a no. They cannot accept silence.

Adapt to the person

New people need more structure and more frequent talks. Experienced people may want fewer and more strategic ones. Remote workers need the time more, because you do not meet in the corridor. Some people open up on a walk or in a call without video; others prefer writing. Ask how they would like to do it.

Common mistakes

• Status reports. If it is a list of tasks, send it by message and use the time for something else.
• Cancelling. Every cancellation is a message.
• Talking too much. Aim for the person speaking most of the time.
• Using it only for problems. Include praise and plans.
• No follow up. If nothing happens between meetings, people stop bringing things.

Where nerix helps

Keep tasks that come out of one to ones in Work, with an owner and a due date, so nothing depends on memory. In Feedback (early access) a monthly one to one form and a weekly check in are among the twelve starting forms, which you can copy and change. People can fill in a few questions before the meeting, and you read the answers beforehand.

If you hold meetings in nerix, notes can be captured and turned into minutes and tasks. You decide what is kept, and a private talk should stay private. In the chat, nerix can help you shape a list of questions for a person in a particular situation.

The short version

Hold them on a fixed rhythm, and make them the person's meeting. Use a simple structure, ask open questions and listen. Give small, specific feedback, write two or three lines of actions and do what you promised.

Prices checked in October 2026 and they change, so confirm them on the official pages: Slack, Microsoft Teams, Zulip, Mattermost.

Why teams look beyond Slack

Slack's free plan keeps messages searchable for 90 days, allows up to 10 apps and offers 1:1 huddles only, according to its pricing page. That suits a short trial. Once the history matters, you move to Pro, listed at 6.75 euros per user a month billed yearly and 8.25 euros billed monthly. Those are fair prices for a mature product, but they add up per person, and some teams would rather have their chat inside a tool that also holds tasks and files.

The options at a glance

Slack

Good at: speed, a large directory of integrations and a design most people already know. Paid plans keep unlimited history, and Slack's pricing page lists AI summaries, search and daily recaps.

Falls short: the free plan's 90-day history and 1:1-only huddles, and a per-active-user bill that grows with the team.

Price: Pro is 6.75 euros per user a month billed yearly, Business+ is 15 euros, on Slack's euro page. Enterprise+ is by quote.

Microsoft Teams

Good at: chat, calls and meetings in the suite many offices already pay for. Microsoft says a free version exists for small businesses, and Teams Essentials is listed at 4 dollars per user a month billed annually.

Falls short: Microsoft's free page lists meetings up to 60 minutes and 5 GB of storage per user, so heavier use means paying. Teams can feel heavy if you only want simple chat.

Price: Free, then Essentials at 4 dollars per user a month, annual. Bundles with Microsoft 365 are priced separately.

Zulip

Good at: every message belongs to a topic inside a stream, so a busy team can come back to a conversation hours later and still follow it. Zulip is open source and can be self-hosted.

Falls short: the model takes a day or two to get used to, and the free cloud plan limits search history to 10,000 messages and file storage to 5 GB in total.

Price: Standard is 6.67 dollars per user a month billed annually or 8 dollars monthly. Plus is 10 dollars annually with a 10-user minimum.

Mattermost

Good at: organisations that must keep data on their own servers. It is built for self-hosting, with options from a single server to air-gapped setups.

Falls short: you run it, or pay someone to. The free Entry tier has server-wide caps, and Mattermost's pricing page asks you to contact sales for the paid plans, so check what applies to your size.

Price: free Entry tier for self-hosting, aimed at teams under about 50 people. Paid prices are by quote.

nerix

Good at: keeping talk next to the work. Team chat in nerix is organised into spaces and topics, with direct chats, voice notes, calls and search, and you can turn a message into a task or a meeting. Private spaces keep private work private. The assistant can also set up spaces and request types from a short description of your organisation, and nothing changes until you apply it.

Falls short: nerix is not trying to match Slack's app directory, so if you rely on dozens of integrations, test those first. It is a newer product, and its chat is one part of a wider workspace rather than the whole product.

Price: Free for one person, 15 euros a month on Plus, and Team at 24 euros per seat a month from three seats. See the pricing page. A free plan covers one seat, so trying team chat with colleagues means a team plan.

How to choose

• You already pay for Microsoft 365. Use Teams and skip a new bill.
• You want calmer conversations. Try Zulip's topic model.
• Your data must stay on your servers. Mattermost or self-hosted Zulip.
• Your pain is that chat, tasks and files live in three places. Look at nerix, and read team chat that keeps the work in one place.
• You rely on many integrations. Slack may still be your best option.

Pilot with one real project for two weeks, with the people who talk the most.

Before you switch

Chat is a habit, so a switch fails when half the team stays behind. Agree a date, move the active channels together and archive the rest. Decide what to keep: most teams do not need three years of banter, but they do need the decisions, links and files, so export or pin those first. Check the notification defaults, since a new tool that pings everyone about everything will be muted within a week. Finally, check what happens to guests and clients who joined your old channels, because many tools treat external people differently from members.

Also think about who is in the room. Contractors, clients and part-time helpers often need to join a channel or a space without getting access to everything, so check how each tool handles guests and what it costs to add them. Mobile matters too: if half your team answers from a phone, install each app on a real phone during the pilot and see how notifications behave at 7 in the evening.

The short version

The best Slack alternatives for small teams are Teams for Microsoft shops, Zulip for threaded talk, Mattermost for self-hosting and nerix for chat connected to work. Free plans exist everywhere, each with a different limit, so read the limit before you commit. Run a two-week pilot and check that your history can move.

Start with the questions customers ask

Before any design, write down what a stranger needs to know to choose you. For a local business, the list is short and nearly always the same:

• What do you do, in one sentence?
• Where are you, and where do you work?
• What does it cost, or how do I find out?
• Why should I trust you?
• How do I contact you, and when are you open?

These become your pages and your headings. A bakery needs a menu, a story, how to order for events, and where to find it. A plumber needs the services, the area, an emergency number and proof of qualifications. If your site answers these five questions quickly, you are most of the way there.

Plan pages around what people search for

Search engines match what people type to pages that answer it. People rarely search for "welcome to our website". They search for "wedding cake near me", "boiler repair Leeds" or "accountant for freelancers". So give each important service or product its own page with a title and heading that say what it is, in the words customers use.

A practical starting set for a small business:

1. Home: what you do, for whom, where, with one clear action.
2. One page per main service or product, each with its own details and price or how to ask.
3. About: who is behind it, with real names and a real photo if you are comfortable.
4. Contact: address, phone, email, hours, a map link and a simple form.
5. Questions: the things customers ask before buying, answered plainly.

Resist the urge to build twenty thin pages. Five good ones beat twenty that say the same thing.

What AI is good for here, and what it is not

AI is useful for the heavy lifting: proposing the page structure, writing a first version of each page, and producing the working code. In nerix you describe the business in the chat, and it plans the pages, designs them in a look of their own, writes the code and opens the result in a real browser at phone, tablet and desktop width before you see it. The Golden Crumb site above is an invented example bakery built from one message, and it shows the idea: home, menu, story, catering and how to find it.

It is not good at facts it cannot know. Prices, opening hours, the name of your street, your qualifications and your photos have to come from you. Read every page for things that are plausible but wrong, such as a service you do not offer or a promise you cannot keep. A site that sounds right and is wrong costs you customers.

A few habits help:

• Give it real details in your first message: the business, the town, the services and prices, what a visitor should do.
• Ask it to use your words where you have them, such as an old brochure or a menu.
• Replace placeholder photos with real ones when you can. Real photos of your premises and your work build trust that stock images do not.
• Read it all aloud once. If a sentence sounds like any business anywhere, rewrite it with something specific.

The search basics that matter most

You do not need a specialist to get the fundamentals right. These are the things that make the biggest difference for a small site.

A clear title and description for every page

The title is what appears as the blue link in search results, and the description is the line beneath it. Each page needs its own, written for a person: what the page is, and why to click. Keep titles to about 60 characters and descriptions to about 160, so they are not cut off. Do not repeat the same title across pages.

One main heading per page, then a sensible order

Each page should have one main heading that says what the page is about, followed by subheadings in order. This helps readers skim and helps search engines understand the page.

Words for every image

Every image needs a short description, called alt text, that says what it shows. It helps people using screen readers and gives search engines context. "Fresh sourdough loaves cooling on a rack in the Golden Crumb kitchen" is useful. "Image 1" is not.

Real pages that load quickly

Search engines read the HTML of a page. A site that arrives as an empty shell and fills in later with scripts can be harder for them to read. nerix publishes each page as real HTML, with its own title and description, structured data for the business, a sitemap and a share card. Speed matters too: small images, few scripts and no unnecessary clutter.

Information that helps search engines understand your business

Structured data is a small block of machine-readable facts behind the page: your business name, address, opening hours, the questions you answer. It helps search engines show richer results. It must match what is on the page, so only mark up what is true and visible.

Work on a phone first

Most visitors to a small business site arrive on a phone. Check every page at a narrow width: text readable without zooming, buttons easy to tap, no sideways scrolling, phone number that you can tap to call.

Build trust, because search engines notice what people notice

A site that looks careless or evasive loses people quickly, and people who leave quickly tell search engines something. Make it obvious that a real business is behind it:

• A real address and phone number, and an email that you answer.
• Prices, or at least how pricing works.
• Terms people can read, and a privacy notice that says what you collect and why. Our free website privacy notice template and terms and conditions of sale are careful starting points, not legal advice, so check what applies where you are.
• Reviews and examples only if they are real. Never invent a customer, a quote or a number.

Checking before you publish

A good build is checked before anyone sees it. nerix runs a search check before every publish and stops a site that would hurt its own ranking: a missing heading, an image without words, a link to a page that does not exist. Whatever tool you use, run through the same list yourself:

• Every page has its own title and description.
• Each page has one main heading.
• Every image has alt text.
• No link leads nowhere.
• It reads well on a phone.
• The contact details are right.

Publish, then keep it alive

Publishing is not the end. Look at the site again after a week with fresh eyes. Add the questions customers actually ask you. Keep opening hours and prices up to date. In nerix you work on a draft while the live site stays as it is, publish when you are happy, and can go back to any earlier version in one step. Sites are published on a nerix web address today, and your own domain is coming soon but is not available yet.

Publishing is part of the Websites add-on, and every plan includes a tier of it, so check the pricing page for what is included.

The short version

Answer the five questions a stranger has. Give each service its own clear page. Let AI do the building and your knowledge do the facts. Get the basics of titles, headings, images and speed right, and show that a real business is behind it. That is most of what small business search optimisation is, and none of it needs a trick.

A supplier audit is simply a structured look at how a supplier does what they promise. For a small company it can be light, quick and friendly. The aim is trust with evidence, not suspicion.

Start with a list and a ranking

Write down everyone you buy from. For each, note what you buy, how much you spend and what happens to your customers if they fail. Then rank them by risk:

• High: you cannot easily replace them, or their failure stops your work or harms a customer. Examples: your main manufacturer, your software host, the person who handles customer payments or data.
• Medium: their failure hurts, but you can work around it in a few days.
• Low: you can switch with little effort.

Spend your effort on the high group first. For the low group, a quick look at reviews and an invoice check is plenty.

Decide what matters for each

The questions depend on what they supply. Some themes appear often:

1. Delivery. Do they deliver the right thing, on time? Do they tell you early when they cannot?
2. Quality. How do they check their work? What happens when something is wrong?
3. Capacity and continuity. What if their key person is ill, or their site is out of use? Do they have a backup?
4. Legal and safety. Are they allowed to do what they do? Do they hold the licences, insurance or certificates the work needs?
5. Information and data. Do they handle your or your customers' data? How is it protected, where is it kept and who can see it?
6. People and ethics. Do they treat their workers fairly and follow the law? This matters more in some trades.

Pick the three or four that matter most for each high risk supplier.

Choose the method

You have three levels of effort.

A questionnaire. Send a short list of questions and ask for evidence with the answers: a certificate, a policy, a sample record. Ten questions are enough. It is quick for both sides and gives you something to file.

A call or video visit. Ask them to show how they do the work. "Can you show me how an order moves from receipt to dispatch?" Watching reveals more than reading.

A site visit. For suppliers whose failure would be serious. Tell them in advance what you want to see and who you want to meet. Bring a short checklist and take notes.

In each case, keep the tone collaborative. Most suppliers welcome a customer who cares about quality.

Ask questions that need evidence

"Do you have a quality process?" gets a yes. "Please send your procedure for handling a faulty batch, and one example from the last year" gets the truth. For each answer, ask what proves it.

You can use a recognised certificate such as ISO 9001 or ISO 27001 as one piece of evidence. Check that it is current, covers the work you buy, and was issued by a real body. A certificate does not replace your own look at the things you rely on.

Record and judge

For each question, record the result: meets what you need, partly meets it, does not meet it, or does not apply. Write what you saw or received. Then give the supplier an overall view: approved, approved with conditions, or not approved.

Be fair and consistent. Judge each supplier against the same standard for their risk level.

Agree on actions together

If you find gaps, share them quickly and plainly, with the evidence, and agree on actions with an owner and a date: they send a missing certificate, they add a check, they confirm a backup arrangement. Follow up on the dates. A serious gap in a high risk supplier may mean a plan to change supplier, so start looking before you must.

Put your expectations in writing where they matter. A service level agreement states what is measured and what happens when targets are missed, and a purchase order fixes what you are buying and when. If you are choosing between several suppliers, a request for quote email asks them all for the same information.

Review on a rhythm

Suppliers change. Set a review date for each: every year for high risk, every two or three years for medium. Also review after any serious problem, a change of ownership, a move or a change in what they supply for you. Keep the last questionnaire and notes so you can see what has changed.

Do not forget the soft signals

Between audits, listen. Late answers, staff turnover, delivery changes without notice, requests for early payment and vague replies can all be signs of trouble. Note them and ask.

Where nerix helps

Checks (early access) includes a supplier check among its eight ready plans. The plan can open the check on its own a few days before it is due, with its questions filled in. Each question has the evidence asked for, you choose a result and write what you saw, and an issue becomes a task in Work with an owner and a due date.

Keep the supplier's certificates and policies in your library, where you can search them and ask nerix questions with the page each answer came from. For instance, "When does this certificate expire?" nerix can mistake or miss a detail, so open the cited page before you rely on it.

The short version

List your suppliers and rank them by risk. Check the high ones on what matters most for the work, using evidence. Record fair results, agree on actions with dates and review on a rhythm.

The problem is not chat. It is chat being asked to do jobs it is bad at: storing decisions, tracking tasks and acting as a filing cabinet. This guide is about using chat for what it is good at, and keeping the work itself in one place.

What chat is good at, and what it is not

Chat is excellent for:

• Quick questions that need a fast answer.
• Coordination: "I am running ten minutes late", "who has the key?"
• Social contact, which matters in teams that are not in the same room.
• Getting attention for something urgent.

Chat is poor at:

• Remembering. Messages scroll away.
• Deciding. A decision halfway down a thread is easy to miss.
• Assigning. "Can someone look at this?" usually means nobody does.
• Storing documents. Files shared in chat become impossible to find.

The practical lesson: use chat to talk, and move the results of the talk somewhere durable.

Structure that helps: spaces and topics

A flat stream of messages mixes everything. A little structure helps a great deal.

In nerix, Spaces hold a team's talk, one topic at a time. A space can be a team, a project or a function, such as General, Support or Product Launch. Inside a space, each topic is its own conversation with a title, so a question about the price list does not get lost among a discussion of the holiday rota. Every space starts with a General topic, and you can start a new topic with a title and a first message when a new subject begins.

Direct chats are for one person or a small group, up to twenty people, for talk that does not belong to a space.

Some guidelines for a small team:

• Start with few spaces. A general one, one for each real project or function, and that is it.
• One subject per topic. If the subject changes, start a new topic.
• Name topics so you can find them. "Price list November" beats "Question".
• Archive what is finished. A space for a project that ended just adds noise.

Choose who sees what

Not every conversation belongs to everyone. In nerix, a space can be Open, so everyone in the workspace can see it, or Private, so only its members can. A Restricted space is stricter still: only its members can see it, and even admins must log a reason to look. Guests, people outside your team such as a contractor or a client, see only the spaces and topics they are added to, not the rest of the workspace.

Be deliberate about this early. It is easier to start private and open up than the other way round, and a sensitive discussion in the wrong place is hard to take back.

Turn decisions into tasks

The most useful habit for a team is simple: when something is decided in chat, it leaves chat. A decision with an owner and a date becomes a task. A decision without them is a good intention.

In nerix, a message can be turned into a task, so "Maya will send the revised quote on Friday" becomes an item with an owner and a due date in Work, rather than a line that scrolls away. You can also type a command in the message box to make a task, start a poll or start a meeting, so these steps happen where the conversation is.

A good routine at the end of a discussion:

1. State the decision in one sentence. "We are going with option B."
2. Name the owner and the date. "Dan will update the page by Wednesday."
3. Make the task. Not later. Now.

After a meeting, the same principle applies. Send a short note with the decisions and actions, such as the follow-up email after a meeting, and make sure every action is a task with a name on it.

Write messages that can be acted on

How you write matters as much as where. A few habits make a team's chat far more useful:

• Say what you need, and by when. "Can you check the numbers in the Q4 sheet by Thursday?" beats "Can someone look at this?"
• Name the person. Use a mention for the one who should act. If it is for everyone, say so.
• Put the point first. Lead with the question or the decision, then the background.
• Keep it in one message. Five short messages in a row ping five times. One clear message pings once.
• Use the thread or topic. Reply where the conversation is, not in a new message.
• Attach, do not paste. Share files into the conversation so they are stored with it.

Calm notifications

Constant interruption is the other major cost of chat. People cannot do deep work if they feel they must answer instantly. Agree some basics as a team:

• What is urgent? Define it. For many teams: something is broken for a customer, or someone is waiting on you right now to proceed. Everything else can wait for the next time someone checks.
• Response expectations. Same working day is a reasonable standard for most messages. Say so, and people stop checking every minute.
• Notification settings. In nerix, you can choose to be notified about All messages, Mentions only or Nothing for each space. Most people do best with mentions only for busy spaces.
• Use mentions sparingly. If everything pings, nothing stands out.
• Respect time zones and hours. Messages do not have to be answered at night.

Search and history

If people cannot find old messages, they stop trusting chat as a record. Make sure the team knows how to search, and put important things in the right place: decisions in tasks or documents, files in the library, not in a thread from last spring. In nerix, you can search messages from Spaces, and Ctrl K opens "Search or jump to…" for everything else.

Using the assistant in chat, with care

nerix lets you ask the assistant from within a space, for example to summarise a long thread or to draft a reply. This is useful when you return from leave to four hundred messages. Two cautions apply. Check the summary against the thread for decisions and numbers before acting on it. And remember that a space can be set so that AI help is off; when it is, the assistant sees nothing from that space. If a space holds sensitive talk, that setting is there for you.

Rules a small team can actually keep

Write down a few rules, no more than six, and make them visible. For example:

1. Decisions are written down as tasks or documents, not left in chat.
2. Every task has one owner and one date.
3. Urgent means customer impact or someone blocked. Otherwise, reply the same working day.
4. One subject per topic.
5. Use mentions for people who must act.
6. Archive finished spaces.

Review them after a month. If a rule is never followed, change the rule or drop it.

The short version

Use chat to talk and the rest of the system to remember. Keep spaces few, topics specific and visibility deliberate. Move every decision into a task with an owner and a date. Write messages that can be acted on, and set calm expectations about notifications. A team that does this can find the work, not just the conversation.

Writing the process down does not need to be bureaucratic. A one page checklist that people actually use is worth more than a folder of manuals that nobody opens.

Choose processes worth writing

Do not document everything. Start with the ones where it matters most:

• Mistakes are costly. Wrong invoices, wrong shipments, errors with customer data.
• Many people do it. Differences multiply.
• It happens rarely. People forget the steps between the times.
• It is risky. Safety, security, legal requirements.
• New people must learn it quickly.

Pick one to begin with. Finish it, learn from it, then pick the next.

Watch the real thing

Before you write, find out what actually happens. Ask the person who does the work to show you, and watch. Do not accept "we always do X" without seeing it. Write down the steps in order, the tools, the documents used, the decisions and the points where things go wrong.

Then ask a second person to show you the same process. The differences between them are valuable. They show where the steps are unclear, or where one person has found a better way.

Decide the best way, together

Look at the differences and the pain points and agree on the best way to do it, with the people who do it. Remove steps that add nothing, move checks to where they catch problems and fix what is clearly broken. Writing the process down is a good moment to improve it.

Keep it honest. A procedure that describes an ideal world no one lives in will be ignored.

Write short, active steps

Use plain language and one action per step. Start with a verb. Number the steps in the order they happen.

Compare:

• "Orders should be checked prior to being dispatched in accordance with the relevant criteria."
• "1. Open the order. 2. Check that the address is complete. 3. Check that the item and size match the order. 4. Pack and add the delivery note."

Add the details that stop errors: where to find something, what a correct result looks like, what to do if it does not. Use screenshots or photos where they save words.

Include for each process:

1. Purpose and scope. What it is for, when it applies.
2. Who is responsible.
3. What you need. Tools, access, documents.
4. The steps.
5. What to do when things go wrong, and who to ask.
6. Records. What is saved, where and for how long.

Keep it to one or two pages. If it needs more, split it.

A checklist beats a paragraph

For routine work, a checklist is better than prose. Pilots and surgeons use them because they work: they stop a tired, rushed or distracted person from skipping a step. A good checklist is short, has clear yes or no items and sits where the work happens.

Do not turn a thinking task into a tick list. Use checklists for things that must always be done, and leave judgment to people.

Test it with someone new

Give the draft to someone who does not know the process and ask them to follow it while you watch. Where they hesitate or ask a question, the document is missing something. Fix and test again. This is the only way to find out whether it works.

Get it approved, then released

Ask the people who do the work and the owner of the area to read the final version. Give it a name, a version number, a date and an owner. Put it in the one place where everyone looks, and retire older copies. Tell the team about it in person, not only by email, and explain what changed and why.

Keep it alive

Procedures decay. People change how they work, tools change, rules change. Set a review date, at least once a year, and give the owner the job of checking it. Encourage anyone who finds a problem to say so, and make it easy to suggest a change. A procedure that is wrong should be fixed within days.

An internal audit is a good way to see whether procedures match reality. Our post on your first internal audit shows how.

Measure whether it helps

Look for the signs: fewer errors, faster training, less time asking "how do we do this?", fewer complaints. If nothing improves, the procedure is probably too long, too vague or not used.

Where nerix helps

Keep your procedures in the library. People can search them by meaning and ask nerix in the chat questions such as "How do we handle a return?" and get an answer with the page it came from, so the person can check the original. You can also ask nerix to turn your rough notes into numbered steps or a checklist, which you then test with the people who do the job.

Use Work to turn a recurring process into tasks with owners and dates, and Checks (early access) to check regularly whether the work follows the procedure. nerix does not see how your work really happens, so watch the real thing first.

The short version

Pick a process where mistakes are costly or many people do it. Watch it as it really happens, agree the best way with the people involved, write short numbered steps, test with a newcomer and give it an owner and a review date.

A good offer is quick, warm and exact. It makes the decision easy to say yes to, and it protects both sides from misunderstanding in the first month. Here is how to write a job offer letter, with a template you can fill in.

Settle the terms before you write

Decide these inside the company first, so the letter does not wander:

1. The role. The title and the main responsibilities, and who the person reports to.
2. The pay. The amount, whether it is per year, month or hour, how often it is paid, and whether it is before tax. Bonuses, commission and overtime need their own lines.
3. The hours and place. Full or part time, usual days, where the work is done, and any remote or hybrid arrangement.
4. The start date. A specific date, or the way it is set, such as after the notice period at their current job.
5. The extras. Holiday, sick pay, pension or retirement contributions, equipment, training, anything else you offer.
6. The conditions. Anything the offer depends on, such as references, a background check where the law allows, proof of the right to work or a probation period.

If you do not know the answer to one of these, find out before sending. A vague line becomes a dispute later.

Make a phone call first

Call the person before you send the letter. Say you would like to offer them the job, say the main terms in a sentence or two and ask if there is anything that would stop them accepting. This lets you hear the hesitation before it is on paper, and it is a courtesy that people remember.

Tell them the letter will follow today or tomorrow, and keep that promise.

What the letter should contain

A good offer letter is a page or two. Start with the good news in the first sentence, then the facts, then the next step.

• Greeting and offer. "We are delighted to offer you the position of Operations Assistant at Green Valley Foods."
• The key terms, in a short list or table: title, manager, start date, pay, hours, place, probation period if any.
• Conditions, stated clearly and kept to the ones you need.
• How to accept, and by what date. Sign and return, or reply to an email.
• What happens next. The employment contract, paperwork, first day, who will contact them.
• A warm close with a real person's name and contact details.

Our job offer letter template has these parts ready to fill in. The employment contract template is the full document that follows, but check it against the rules of the country where the person will work, since employment law varies a lot.

Words that help

Use plain, human language. Say "we would like you to join us" rather than "we are pleased to extend a conditional offer of employment". Avoid anything that sounds like a threat or a trap.

Be careful with promises. "You will get a raise after six months" is a commitment someone will remember. If it is a hope, say "we plan to review your pay after six months". If something is not decided, say so.

Be consistent with the job advert and the interview. If you told them there was a car allowance or flexible hours, either they are in the letter or you explain what changed and why.

Handle questions and negotiation

Expect questions. Answer them quickly and in writing, so there is a record. If the person asks for more, decide in advance what you can change: pay within a range, a start date, a day of remote work, extra training. Some things you cannot change without making it unfair to current staff. It is fine to say so, kindly.

When you agree to a change, send a new version of the letter with the change in it and say that it replaces the earlier one. Never leave two different versions in circulation.

When the answer is no

If the person declines, thank them. Ask, once, if there is anything that would have changed their mind. You may learn something about your pay, your process or your reputation. Keep the door open: people change jobs more than once.

If you are the one who needs to decline an offer or a candidate, a short, kind message is better than silence. The decline offer email template is a useful model for tone: thank them, be clear, and do not over explain.

After yes

A yes is not the end. Between acceptance and the first day, keep in touch. Send the contract, the first day plan and a message from the team. People who hear nothing for a month sometimes accept another offer. Plan the first week, with a named person to ask and a few small tasks the person can finish.

Where nerix helps

In the chat, tell nerix the role, the terms and the tone you want, and ask for a first draft of the offer. It opens beside the chat as a document, with each version kept, and you can ask it to make the tone warmer, shorter or more formal. Email drafts (early access) writes the covering email, leaves a visible blank wherever it could not know a fact such as a date, and sends nothing until you press Send.

nerix does not know the employment law where you are or what you agreed on the phone. Check every number, every date and every condition before the letter goes out.

The short version

Settle the terms first. Phone before you write. Put the role, pay, hours, start date, conditions and the way to accept in one clear letter. Answer questions in writing, put changes in a new version and be gracious with a no.

Many people avoid agreements because they imagine pages of legal language. A good one for a small job is the opposite. It is short, it uses ordinary words, and a client can read it in ten minutes and say "yes, that is what we agreed".

This guide walks through the parts, in the order they usually appear, with the questions each part must answer.

Start with who and what

Name both sides properly: the legal name of your business or yourself, the client's company name or full name, and an address for each. If you work as a company, use the company name, not a brand name, because the agreement binds the one who signs it.

Then describe the service in one or two sentences, in the way you would explain it to a friend. "We will design and set up a five page website for the client's bakery" is better than "web services". The detailed list comes next, but the opening sentence keeps everyone pointed in the same direction.

Write the scope as a list

The scope is the part that matters most. It answers two questions: what will you do, and what will you not do.

• List each deliverable as a thing someone could check off. "Three logo options in the first round" can be checked. "Branding" cannot.
• State the limits: number of revisions, hours included, number of pages, meetings, locations.
• State what you need from the client and by when: texts, access, photos, decisions. Many delays are the client's, and the agreement should say what happens when they are late.
• List what is not included. If you will not write the texts, host the site or fix problems caused by someone else, say so.

If the job is large or has stages, put the detailed scope in a separate statement of work and refer to it from the agreement. Our statement of work template is built for that, and the freelance service agreement and consulting agreement templates cover the agreement around it.

Price and payment

Be exact. Say the price or the rate, the currency, whether tax is included, and when each payment is due. If you take a deposit, say how much and that work starts when it arrives. If payment is in stages, tie each stage to something visible, such as "on approval of the design" rather than "when we are about halfway".

Add what happens when payment is late: a reasonable interest rate or fee if the law where you are allows it, and the right to pause work. Do not invent a punishing number. A fair, modest term is easier to enforce and easier to get agreed.

Say how expenses are handled. Travel, stock photos, printing and software licences should either be included in the price or be charged at cost with the client's approval first.

Changes will happen, so plan for them

The client will ask for something extra. That is normal, and it is not a problem if the agreement says how it is handled: the client asks in writing, you say what it changes in price and time, the client agrees, and only then do you do it.

A sentence such as "work outside the scope is quoted separately and starts only after the client approves the quote" saves more friendships than any other clause. It also gives you a polite thing to say: "Happy to do that, here is what it adds."

Who owns what

Clients often assume they own everything you make the moment they pay, and makers often assume they keep everything. Neither is automatically true, and the rules differ between countries, so write it down.

Decide and state:

1. Whether ownership of the finished work passes to the client, and when (usually on full payment).
2. Whether you keep the right to show the work in your portfolio.
3. What happens to tools, templates and materials you brought to the job. Most people keep those and give the client a licence to use them within the work.
4. What happens to material the client provided. It stays theirs, and you promise to use it only for the job.

Confidentiality and data

If you will see the client's customer lists, financial figures or personal data, say that you will keep them private and use them only for the work. If you will handle personal data of other people, the law where you work may require specific terms, so read the rules that apply to you or ask a professional.

For a standalone confidentiality agreement see NDA basics. A short confidentiality clause inside the service agreement is often enough for ordinary work.

Ending the work

Agreements fail most often at the end, so it pays to describe it early:

• Finishing. How the client accepts the work, and how many days they have to raise problems.
• Stopping early. How much notice either side must give, and what the client pays for work already done.
• Serious problems. What happens if one side breaks the agreement and does not fix it within a stated number of days.

Keep these short and symmetric. A term that only helps you looks one sided, and clients notice.

Liability, in moderation

Many agreements limit how much you can be asked to pay if something goes wrong, often to the fees for the job. This is common and reasonable, but laws restrict what such limits can do, especially for consumers and for harm to people. Use the wording from a trusted template, and have a professional check it if the amounts are large.

Signing and keeping it

Both sides should sign, or accept in a way that leaves a record, such as signing a PDF or replying "agreed" to the final version. Keep the signed copy and the emails around it together in one place, named so that you can find it in a year.

A few habits help:

1. Send the draft in an editable format first, so the client can ask for changes.
2. Number the versions and make sure the one signed is the last one.
3. Put the start date and the end date, or the way the end is decided, on the first page.
4. Read it once more, out loud if you can. A clause that is hard to say is probably hard to understand.

Where nerix helps

You can start from one of our free templates and fill in a short form. The document builds itself, and you download it as Word or PDF. What you type stays in your browser.

If you want to adapt the wording, ask nerix in the chat to turn your notes into a first draft, tell it the scope, the price and the payment stages, and ask it to make a clause shorter or in simpler words. It opens the draft in a document beside the chat and keeps each version. The numbers and dates in a document and Sheet can be filled in beside it.

It does not know your law, your risks or what you agreed on the phone, so read every line yourself. For large or unusual agreements, a short review by a lawyer is cheap compared with a dispute.

The short version

Say who, what, how much, by when, what happens when things change and what happens when the work ends. Use plain words, keep it to a few pages and sign it before the work starts.

Good email is not fancy. It is clear about who it is for, what it says and what you want. Below are the habits that make the most difference when you write business emails that people read and answer.

Know what you want before you write

Finish this sentence: "I want the reader to ___ by ___." Approve the quote by Friday. Tell me which time suits them. Send the missing document. If you cannot finish it, you are not ready to write, and the reader will not know what to do either.

If you want several things, consider whether you need several emails. A message with five questions often gets an answer to the first.

Write a subject line that does the work

The subject line decides whether the email is opened and how it is filed. It should say what the email is about, and, if possible, what you need.

Weak: "Hello", "Question", "Following up". Better: "Quote 1182: please confirm by Friday 14 March", "Meeting request: 30 minutes on the new menu", "Missing: signed delivery note for order 551".

Put the key word first and keep it short enough to read on a phone. Change the subject when the topic changes, so the thread stays findable.

Open with the point

Do not make the reader dig. The first sentence says why you are writing and what you need. Context comes after.

Weak: "I hope you are well. I wanted to touch base regarding the thing we spoke about last month and see whether there have been any developments." Better: "Could you confirm by Friday whether you would like the larger table? It affects the order I place with the carpenter on Monday."

A short greeting is polite. A paragraph of pleasantries before the ask is not.

One email, one main ask

State the ask plainly, make it easy to answer and give a date if there is one. "Please reply with yes or no" is easier than "let me know your thoughts". If you need a choice, offer options: "Would Tuesday at 10 or Thursday at 14 suit you?"

If you ask the reader to do something, say what exactly and by when. If something is optional, say so.

Keep it short and easy to scan

Short paragraphs, plain words, one idea each. Use a list when you have steps or items, and bold sparingly for a date or an amount that must not be missed. Cut anything that does not help the reader to act. Read it on a phone: if it is a wall of text, trim it.

Put attachments where they are useful, name them clearly ("Quote 1182 Green Valley.pdf") and mention them in the text. Check you attached them.

Choose the right tone

Match the relationship and the situation. With a new contact, be courteous and direct. With a colleague you know well, be friendlier. When delivering bad news, be clear, kind and brief. When a matter is serious or tense, avoid sarcasm, capital letters and exclamation marks, which are easy to misread in writing.

Read it as the recipient would. Would you be happy to receive it? If you are angry, write it, leave it and rewrite it the next day.

Use To, Cc and Reply all with care

Put the person who must act in To. Use Cc for people who need to know, and mention why. Do not copy a manager to pressure someone. Think before using Reply all: does everyone need this? When you add someone to a thread, say who they are and why.

Common types and what they need

An introduction. Say who you are, how you found them, why you are writing and a small, specific ask. Our introduction email template has the structure.

A meeting request. Say the purpose, the length, the options for time and how to reply. The meeting request email template is built that way.

An out of office reply. Say the dates, whom to contact instead and what happens to the message. See the out of office reply template.

A follow up. Short, polite and helpful: "Following up on my email of 4 March below. A yes or no on the larger table by Friday would help, as I order on Monday." Do not make the reader scroll to understand it, and do not say "per my last email".

Check before you send

A quick check catches most embarrassments:

1. Is the right person in To, and no one wrong in Cc?
2. Is the ask clear and does it have a date?
3. Are names, numbers and dates correct?
4. Is the attachment there and the right one?
5. Would I be comfortable if this were read out in a meeting?

For anything important or sensitive, wait a few minutes before sending. Many errors are found on the second read.

Know when not to email

Email is poor for complicated disagreements, emotional topics, quick back and forth and anything that needs tone. A call is better for those, followed by a short email that records what was agreed. It is also poor for urgent things: if it is urgent, phone.

Keep records tidy

Important emails are part of your records. File decisions, approvals and agreements with the project or customer they belong to, and keep the thread together. A short summary email after a call ("As agreed today: ...") is a habit that prevents many disputes.

Where nerix helps

Email drafts (early access) writes an email or a reply from a few words, or from the one you received. The draft opens beside the chat with To, Subject and the message, and every field can be edited in place. One click makes it shorter, warmer or firmer, or translates it, and each change is kept as a version. Where nerix could not know a fact, such as a date, it leaves a blank in double braces and counts them, and it will not send an email that still has one. Nothing is sent until you press Send.

In the chat, you can paste a long thread and ask for a two sentence summary and a suggested reply. You still check the facts and decide what to say.

The short version

Know what you want and by when. Use a subject line that says it. Open with the point, ask one clear thing and keep it short. Choose the tone for the person, check the details and call when email is the wrong tool.

You need three documents for most businesses that sell online or to the public: terms of sale, a returns and refund policy, and a privacy notice. Below is how to write terms and conditions, a returns policy and a privacy notice in plain words.

Start with what you actually do

Before writing, answer these questions about your business:

• What do you sell, to whom (consumers, businesses or both) and where?
• How do customers order and pay?
• How and when do you deliver or perform the service?
• What happens if something is wrong, late or not wanted?
• What personal data do you collect, why and who else sees it?

Policies that describe a different business from the real one are worse than none. If you promise next day delivery in the terms and take a week, you have a problem the lawyers will not solve.

Terms of sale

These say how the deal works. Cover:

1. Who you are. Legal name, address and contact details.
2. What you sell and how the price is shown, with tax and delivery.
3. How a contract is formed. For example, an order is accepted when you confirm it.
4. Payment. Methods, when it is taken, what happens if it fails.
5. Delivery or performance. Times, areas, costs and what happens in a delay.
6. Cancellation and returns, linking to the returns policy.
7. Faults and guarantees. What you do if goods or services are not as described. Consumer law in many places gives rights that cannot be removed, so do not try to.
8. Liability. Reasonable limits, without claiming to exclude what the law does not allow.
9. Changes and complaints. How you change terms, and how a customer complains.
10. Governing law.

Our terms and conditions of sale template is organised this way. Fill in the short form, read the result critically, and remove what does not apply.

Returns and refunds

This is the policy customers actually read, usually when they are worried, so it must be easy. Say:

• how long they have to return something and from what date,
• what condition it must be in,
• how to start a return and where to send it,
• who pays for return postage,
• how and when the refund is paid and in what form,
• what cannot be returned, such as made to order items, with a clear reason,
• what happens with faulty goods, which is a separate and often stronger right.

Be generous where you can afford it. A clear, fair policy raises sales more than it costs in returns. Our returns and refund policy template gives the structure.

Whatever you write must match the law. Many places give consumers a statutory cooling off period or right of withdrawal for distance sales. You cannot offer less than the law gives.

Privacy notice

A privacy notice tells people what you do with their personal data. In many places the law requires one, and describes what it must contain. In plain words, cover:

• who you are and how to contact you about data,
• what data you collect (name, email, address, payment details, browsing data),
• why you collect it and on what legal basis,
• who you share it with (payment provider, courier, email service),
• whether it leaves the country or region,
• how long you keep it,
• the person's rights to see, correct and delete their data, and how to use them,
• how to complain to the authority.

Be honest and specific. "We may share your data with third parties" says nothing. "We send your name and address to our courier so they can deliver your order" is clear. Our website privacy notice template covers the common points. If you use analytics, advertising or cookies, mention them and check what consent is needed where your visitors are. For more on where data lives, see keeping your data in the EU.

Write in plain words

Short sentences. Everyday words. Headings that say what is under them. Numbers rather than "a reasonable time". Examples where a rule might confuse. If a paragraph takes three reads, rewrite it. This is not only kind to customers; plain terms are easier to apply and to enforce, because there is less to argue about.

Keep them true and current

Review your policies at least once a year and whenever something changes: a new product, a new delivery partner, a new law, a new tool that handles data. Put the date of the last update at the top. Keep old versions, because a customer is usually bound by the terms in force when they bought.

If you make a significant change, tell existing customers in good time.

Show them where people look

Link the terms, returns policy and privacy notice from the footer of every page, and from the checkout, where the customer agrees to them. Make sure the checkout shows the key points, such as price, delivery and the right to return, before the final button. Give each document its own page that works on a phone.

Get a professional check where it matters

A template is a good start, but laws differ and details matter. If you sell large amounts, sell to consumers in several countries, handle sensitive data or work in a regulated field, pay a professional to review the documents once. It is a modest cost compared with a dispute.

Where nerix helps

Start from the free templates above, fill in a short form and download the result as Word or PDF. What you type stays in your browser. If you build your site with the Websites tool, these pages can sit in its footer. In the chat, nerix can read a policy you already have and tell you in plain words what it promises, where it contradicts itself or what it leaves out, and it can suggest simpler wording.

It does not know the law that applies to you, so treat its output as a draft to check.

The short version

Describe what you really do. Write terms of sale, a returns policy and a privacy notice in plain, specific words. Match consumer law, keep them current with a date, show them in the footer and at checkout and have a professional check them once.

There are no magic words. The skill is in saying clearly what you want, which is useful anyway. The method below works for emails, letters, summaries, plans and replies, and shows how to write prompts that give you a usable first draft.

Start with the goal

Say what the text must achieve. Not "write a proposal", but "write a one page proposal that persuades a restaurant owner to try our delivery service for a month". The goal tells the assistant what to include and what to leave out.

If you can, add what success looks like: "The reader should reply with a time for a call."

Say who it is for

The same facts read differently for different people. Tell the assistant who the reader is, what they know and how they feel: "a busy practice manager who has never heard of us and is wary of new software." This steers tone, length and the amount of explanation.

Give it the facts

This is the step that matters most. The assistant can write sentences, but it cannot know your prices, dates, names, promises or history. Paste or type them in:

• the key facts as a list, with numbers and dates,
• the earlier email you are replying to,
• anything it must include, such as a deadline or a link,
• anything it must not say.

When you want the assistant to answer from your own documents, put them in your library and ask there, so the answer is based on them and shows its sources.

If a fact is missing, ask it to leave a visible blank rather than invent. This is a very good habit: "If you do not know something, write [to fill in] instead of guessing."

Set the limits

Constraints improve drafts:

1. Length: "Under 150 words", "three short paragraphs".
2. Tone: "Warm and direct", "formal but friendly", "calm, no exclamation marks".
3. Format: "A subject line and a short email", "a table of options", "a checklist".
4. Language and spelling: "British English", "write in French".
5. Words to avoid: "No jargon", "no promises about dates".

Show an example

If you have a past email or letter whose style you like, paste it and say "write in a similar style". This is the best cure for generic text. If you have a bad example too, say what is wrong with it.

Ask for what you want first

Order the request in a way a person could follow. A reliable shape is:

I run a small bakery. Write an email to a café owner who bought from us last year but not this year. Goal: ask whether anything went wrong and offer a free tasting. Facts: last order 14 March, they liked the rye loaf, tasting slots on Tuesdays and Thursdays. Tone: friendly, short, no pressure. Under 120 words. If a detail is missing, leave a blank in square brackets.

That is five sentences, and it will give a far better draft than a one line request.

Iterate instead of starting again

The first draft is a start. Tell the assistant what to change, one thing at a time:

• "Shorter, and move the offer to the first sentence."
• "Less salesy. Remove the second paragraph."
• "Keep the facts but make it more formal."
• "Give me three subject lines."

Each instruction builds on what you have. If you do not like a direction, say so and why. Compare versions side by side and take the best parts. Keep earlier versions, because sometimes version two was the right one.

Check the draft, line by line

Never send the first output without reading it. Check:

1. Facts. Every name, number, date and promise.
2. Claims. Anything that sounds like a statistic or a quote you did not give. Remove it if you cannot verify it.
3. Tone. Does it sound like you, to this reader?
4. Gaps. Did it quietly leave out something important?
5. Rules. Does it respect any legal, contractual or privacy limits you work under?

Assistants can be confidently wrong. They write fluent text whether or not it is true. The more important the document, the more carefully you check.

Be careful with what you paste

Do not paste passwords, secrets or personal data you have no right to share. Understand where your text goes and how it is handled before you paste anything sensitive. Our posts on choosing an AI model and keeping your data in the EU cover how to think about that.

Save what works

When a prompt gives you a good result, keep it. Write a short brief once for each task you repeat, such as a customer reply, a weekly update or a product description, with blanks for the facts. Over a few weeks you build a small set that saves real time.

Where nerix helps

In the chat, you can put your documents in the library and ask nerix to write from them, with each claim tied to the page it came from. Drafts open beside the chat as a document, and each change is kept as a version you can go back to. Email drafts (early access) writes an email or a reply from a few words, leaves a blank where it could not know a fact, and sends nothing until you press Send.

You can choose among the models for different jobs, a quick one for a short reply and a more careful one for something important. You are still the author: read it, correct it and send it under your name.

The short version

Say the goal, the reader and the facts. Set length, tone and format. Show an example. Ask for blanks instead of guesses. Change one thing at a time and check every fact before you send.

Prices checked in October 2026 and they change, so confirm them on the official pages: Zendesk, Freshdesk, Help Scout, Zoho Desk, HubSpot.

What Zendesk costs and why people leave

On Zendesk's German pricing page, Support Team is 19 euros per agent a month billed yearly and 25 euros billed monthly. Suite Team is 55 euros yearly and Suite Professional is 115 euros. AI agents are included but priced by automated resolutions, with a few included per agent and extra ones charged per resolution. Zendesk offers a 14-day trial rather than a free plan. For a team of three handling a modest volume, that is a lot of platform. People move for cost, for simplicity or because they want support next to other work.

The options at a glance

Freshdesk

Good at: ticketing with a long feature list. Freshdesk's page lists Growth at 19 dollars per agent a month billed annually, Pro at 55 dollars and Enterprise at 89 dollars.

Falls short: the page lists no free plan, only a 14-day trial of the Enterprise plan. Its AI is sold in parts: the AI agent includes 500 sessions and extra sessions are priced per 100, and the agent copilot is listed at 29 dollars per agent a month as an add-on for Pro and Enterprise.

Help Scout

Good at: customer conversations that feel like email, without the heavy desk feeling. The free plan covers up to five users and one inbox, with a cap of 100 contacts a month and a small limit on saved replies, tags and articles.

Falls short: paid plans start at 25 dollars per user a month (Standard, up to 25 users). SLA policies come in the higher plans, and its AI chatbot is an add-on charged per resolution.

Zoho Desk

Good at: a free start and a ladder of plans. The page lists a free plan with three user licences and paid plans for Standard, Professional and Enterprise.

Falls short: the pricing page we checked showed rupees, and annual and monthly prices are behind a toggle, so check the page for your region.

HubSpot Service Hub

Good at: companies that already keep contacts in HubSpot, since tickets sit next to the customer record. HubSpot lists free tools for up to two users.

Falls short: the free tools are a starting point, and paid Professional plans carry an onboarding fee, according to the pricing page. Check what ticketing the free tools include before you rely on them.

nerix

Good at: support that sits beside the rest of the work. In Help desk, customers write through a portal, a website widget or email, when you set them up in Desk settings. Requests are tickets with a requester, a type, a state, a priority and an owner, and response targets show a First reply and a Solution time, with a list of requests that are breached or due soon. Internal notes and side conversations stay with the team, and only a public reply reaches the customer. Because requests are the same kind of item as tasks, support and the work it triggers live in one place.

Falls short: this is a lean help desk, not a contact centre. If you need phone support, a large app marketplace or heavy reporting, compare carefully. It is also a newer product than the others here.

Price: Free for one person (3,000 credits a month, and it never charges beyond that), Plus at 15 euros a month, Team at 24 euros per seat a month from three seats. See pricing. If AI help matters to you, remember that AI work spends credits, and the app shows the price before you send.

How to choose

• Support is mostly email and you are two or three people. Help Scout's free plan or nerix.
• You want the classic desk and can pay per agent. Freshdesk or Zendesk.
• You already run HubSpot. Look at Service Hub first.
• You want a free trial run on real tickets. Help Scout, Zoho Desk and HubSpot all list free options.
• You want requests, tasks and documents in one tool. Test nerix.

Whatever you pick, write down your response targets first. A tool is only as good as the rules you set. Our guide to running a help desk for a small team covers that, and handling customer complaints covers the hard cases.

Before you switch

Support data is customer history, so protect it. Export your tickets, macros and help articles before you cancel, and test the import with fifty tickets to see which fields come across. Rebuild your response targets and categories in the new tool instead of copying every old rule, since most desks collect rules nobody uses. Tell customers if the address they write to or the portal link changes, and keep the old channel forwarding for a few months. If you use AI replies, check how each tool charges for them and which data it uses, because that is where costs surprise people.

The short version

Zendesk alternatives for a small business start with free plans: Help Scout, Zoho Desk and HubSpot each list one with limits. Freshdesk is the closest classic desk, and nerix suits teams that want support tickets next to their tasks and documents. Count agents, not features, test with real tickets and check how your data exports.