This catalog covers features that already work in Norm CRM. The feature names in bold best demonstrate how the system is built: they connect several stages of work or preserve information that usually becomes important months later.
Use the catalog to check a specific capability. The product story, price, payment terms, and answers to common concerns remain on the home page.
A contact record stores more than a name and phone number. Projects, tasks, meetings, and other work objects can be attached to it, so the relationship can be reconstructed months later without searching through separate services.
Example: record a new acquaintance and its source, then later open the shared project and most recent meeting from the same contact.
A contact can have a source, role, notes, tags, and several ways to get in touch. Phones, email, Telegram, VK, LinkedIn, and arbitrary communication channels are stored separately.
Example: find former clients with a particular specialization or remember which conference introduced a contact.
A contact can have a last-contact date and a preferred follow-up interval. Norm CRM shows who has not been contacted for too long; reminders can be disabled for individual people.
Example: return to former clients with whom a project went well instead of remembering them by chance.
The import wizard accepts CSV and VCF/vCard files, maps fields, selects rows, and assigns tags. It shows possible matches before saving; merging fills blank fields in the existing contact without overwriting stored data.
Example: import a phone book, tag professional contacts, and merge repeated records by phone number or email.
Limit: one file can be up to 10 MB; CSV, VCF, and vCard are supported. Rolling back an import deliberately preserves later manual edits and newly created relations.
A company or customer can be stored as a counterparty with legal details, while people are kept as its representatives. This separates the legal side of the work from the personal contact list.
Example: keep the contract with a company while connecting meetings and correspondence to its specific representative.
An incoming request can be stored as a lead, assigned a source, and moved through statuses. An unfinished conversation does not disappear among active clients and projects.
Example: record a request from a stream, hold a meeting, and preserve the outcome even when it never becomes a contract.
Repeated services live in a separate reference list with descriptions and prices. They can be reused in proposals and contractual documents without retyping the same material.
Example: describe an interface audit once, then add it to new proposals at its current price.
Norm CRM can assemble a proposal, expose it through a public link, and receive acceptance together with the client's legal details. The internal record preserves both the document and its work history.
Example: prepare a set of services after a meeting, send one link, and receive the details needed to continue formalizing the work.
Public-document interactions are recorded. The history distinguishes a proposal the client has not reached from one they have already started working with.
Example: before following up, check whether the client opened the proposal and acted on the page.
A project brings together its status, participants, tasks, meetings, contracts, files, and links. After completion it remains a history of what was done and under which terms, not merely an item in a current-work list.
Example: open an old project and immediately see the contract, main tasks, materials, meetings, and result without reconstructing the chain from email.
A project has its own status and participant list. Active work can be separated from completed work while retaining the people who took part in decisions.
Example: filter active projects and see the client representatives who approve work inside each one.
A project can have a separate public page for the client. They can follow the part of the work made available to them without entering the freelancer's private account.
Example: send a permanent link where the client checks the project state instead of asking for another manual summary.
Project plans and stages can be shown to the client as a roadmap. It separates the agreed sequence of work from the internal list of small tasks.
Example: show which stages are complete, what is in progress, and what comes next.
A project collects indicators from its connected work. As the history grows, it becomes easier to see the actual volume and compare it with the original estimate.
Example: review the time spent after completion and use the result when estimating a similar project.
My Day brings current tasks, meetings, and attention signals into one place. It is the daily entry point, not another list intended only for long-term storage.
Example: open one screen in the morning to see today's work and commitments that are beginning to slip.
A task has a status and can be connected to a project and other CRM objects. The client context that produced an action remains visible along with the action itself.
Example: record a promise after a meeting, then return from the task to the project and the original agreement.
Tasks can be arranged on Kanban and custom boards. The same tasks and relations remain intact while the user chooses a view that matches the work process.
Example: keep presales preparation separate from active-project tasks.
Meetings are available both as a list and on a calendar. Their records retain the date, participants, contents, and relations to work objects.
Example: check the week's calendar, then open a meeting and prepare using the particular client's history.
Rescheduling does not erase the previous state: a history of changes is preserved. Participants remain part of the meeting context.
Example: see how many times a discussion moved and who agreed on the new date.
A meeting can be added directly from the calendar without entering the full creation flow. Its complete record remains available for details and relations.
Example: reserve a call at the selected time immediately, then add details after the client confirms.
A regular meeting does not need to be created by hand before every occurrence. The calendar core stores its recurrence rule and creates working events from it.
Example: maintain a weekly status call for a long project.
A reminder can be connected to a work object and scheduled relative to an important date. It stays with the task, meeting, or other context instead of becoming a detached note.
Example: receive a reminder before a meeting or return to a promise at a specified interval after an event.
System events and reminders appear inside Norm CRM; supported scenarios also have email notifications. This is a second control layer, not a replacement for tasks and meetings.
Example: see an approaching commitment without manually opening the relevant record.
The timer can be started from the everyday interface and assigned to a work context. Time for tasks that have already ended can be entered manually.
Example: start timing before a task instead of reconstructing the duration from memory in the evening.
If the timer was not running, actual time can be added after the work. A missed start does not have to leave a hole in the history.
Example: add a call or offline work that was not tracked automatically.
A time entry is connected to particular work instead of being stored as one total for the day. Later it is possible to see what the hours were actually spent on.
Example: view not just the length of the working day, but its division between presales, meetings, and delivery for a particular project.
An original estimate can be compared with the actual work. One case says little, but a history of similar tasks reveals recurring estimation errors.
Example: discover that proposal preparation repeatedly takes twice the planned time.
Time indicators are available in several work contexts. A user can inspect a day, a project, or commercial commitments under a contract without exporting records to a separate spreadsheet for each question.
Example: compare project time with the agreements and money received.
A contract brings together services, payment terms, taxes, connected projects, documents, and statistics. It is a working record of the agreement, not just a place for an attached file.
Example: open a contract to see the agreed services, created invoices and acts, and the project to which they belong.
Payment terms and taxes are set in the commercial context and used when preparing documents. This reduces manual recalculation between the contract and billed amounts.
Example: save the appropriate payment scheme for a contract and reuse it in subsequent documents.
An invoice is created inside a contract and exported to PDF. Its contract relation preserves the source of the amount and its place in the commercial history.
Example: create the next invoice under an active contract without copying an old file and replacing details by hand.
A closing act is created in the contract context and is also available as PDF. After the work closes, it remains beside the project and other documents.
Example: prepare an act for a completed stage without later searching for its contract.
Files can be stored in folders and connected to work objects. The same material does not need to be duplicated in several places: relations show it wherever it is needed.
Example: attach source materials to both the project and the relevant meeting.
Limit: the standard plan currently includes 1 GB of user storage.
A report collects selected completed work into a document for the client and the freelancer's own history. It can be connected to a meeting, project, or contract, preserving the source of each result.
Example: prepare a project report for a period, include selected tasks and materials, and keep it beside the rest of the work.
A client can receive a separate public link without access to the private CRM. The result is delivered in a convenient web format while internal information stays closed.
Example: send a monthly report as one link instead of a collection of attachments and messages.
Limit: Norm CRM creates and copies the link; the user sends the message to the client.
A review can be drafted in the CRM, opened to the client through a form, and returned as an agreed version or edits. It stays connected to the work result instead of becoming text with no origin.
Example: after delivering a report, send a link, receive the final review, and preserve it for a future portfolio.
Limit: the CRM creates and copies the link, but does not send it to the client.
Available visit and action events are stored for public reports and reviews. The history helps determine whether the client opened the material and completed the intended action.
Example: before sending a reminder, check whether the client reached the review form.
Recurring income and expenses can be stored separately from one-off documents, with reminders for their associated events.
Example: avoid missing a recurring service charge or a client's repeat payment.
Short notes can be placed over the workspace. They are for temporary information that does not yet need to become a task or a separate object.
Example: leave a brief prompt for the current piece of work.
A separate tool records content publications. It is a niche feature for people who run their own channels and want to retain a history of published material.
Example: record the subject, platform, and state of an upcoming publication.
Streamer mode hides sensitive data in supported interfaces during a public screen demonstration. It reduces the risk of revealing client information by accident, but does not replace checking the screen before going live.
Example: enable the mode before a stream and open a work section with masked names and content.
Repeated values are moved into managed reference lists. A user can adapt the system to their practice without creating another field or spelling variant for every record.
Example: maintain one list of lead sources, service types, and work categories.
The interface works in Russian and English and supports two color themes. These are workspace settings, not separate paid modules.
An account supports TOTP-based 2FA and a list of active sessions. A user can strengthen sign-in security and end access on devices they no longer use.
Example: connect an authenticator app and close an old session after changing computers.