CRM for IT Companies and SaaS: Subscriptions, MRR, Churn Reasons and Custom Development
Reviews6 min read
CRM for an IT company or SaaS: client contact roles, subscriptions with renewal dates, upgrades with MRR change, churn reasons, tickets with SLA and dev projects.

A CRM for an IT company or SaaS is a system where a client company has a decision-maker, a technical contact, an accountant and users; a subscription has a plan, a trial end date and a renewal date; and churn has a date, a reason and a competitor. The team sees MRR, churn and its causes — not just a list of payments.
Website leads arrive in Telegram, demos are scheduled in Google Calendar, payments are visible only at the bank, and only one manager knows why a client left. Below are the client-company card, subscriptions and churn as a team manages them in Mestra.
One-minute check
- Does a client have several contacts with roles?
- Are the renewal date and trial end date visible?
- Is an upgrade or downgrade recorded with the change in MRR?
- Is the reason for leaving chosen from a list?
- Are there support tickets with priority and SLA?
The client company and contact roles
Client type — startup, mid-sized or large company, public sector. The company card has a Linked contacts block with roles:
| Role | What gets sent to them |
|---|---|
| Decision-maker | Renewal and upgrade offers |
| Technical contact | API updates and technical notifications |
| Accountant or payer | Invoices and payment reminders |
| Account administrator | Settings and users |
| User | Training and new features |
Each contact is a separate card with its own channels. When the technical contact writes, the manager immediately sees their role, company and the full history. If the person leaves, the role passes to a new employee, and the company's history stays.
The subscription
| Field | How it works |
|---|---|
| Plan | A link to the product |
| Trial end | A date and a reminder a few days before |
| Renewal date | A reminder to the decision-maker and accountant |
| Status | Trial → active → renewed / cancelled / overdue |
If the client's status is "Churned", extra fields open: churn date, a reason from the list (too expensive, missing features, moved to a competitor, hard to use, support problems, closed the business, didn't implement), a comment, which competitor, whether they can be won back. The list of reasons is editable in settings.
In analytics, "Why clients leave" shows the share of each reason. If 40% of churned clients chose "missing features", the team needs to work on the product, not lower the price.
Client history
| Record | What it captures |
|---|---|
| Subscription | Status, plan, dates |
| Upgrade or downgrade | The MRR difference |
| Support ticket | Priority and SLA |
| Development project | Stages, hours, acceptance |
Product and pricing
A plan has a price per user and per additional user, plan limits, a minimum term and a trial length. For custom development — an hourly rate. A subscription defaults to the "advance for the period" amount type.
Money: subscriptions, MRR and development
A client paid for an annual subscription for 20 users at 1,500 ₽ each — 360,000 ₽. In Mestra, this is an advance that turns into revenue at 30,000 ₽ a month. This client's MRR is 30,000 ₽. If three months later they move to 30 users, the upgrade records an MRR change of +15,000 ₽.
Cloud infrastructure and payment gateway costs are recorded as cost of sales, so the product's gross margin is visible. Custom development is paid by stage: the advance becomes revenue when a stage is accepted.
Process templates
- SaaS sale: lead → demo → trial → onboarding → payment → active client → renewal or upsell.
- Custom development: brief → estimate → contract → sprints → acceptance → support.
A rule like "3 days before the trial ends, if the client hasn't activated the key feature — create a task for the manager" is set up without a developer. A demo in Yandex Telemost or Google Meet is created from the calendar, and the link goes to the client automatically.
Example: what one percent of churn costs
A SaaS with 4,000,000 ₽ MRR loses 4% a month. Cutting churn to 3% preserves 40,000 ₽ of MRR every month — over a year, about 480,000 ₽ of monthly revenue that would otherwise have gone.
Requests and support
Client questions from Telegram, MAX, VKontakte and WhatsApp* go into a shared stream of requests, and a ticket is created straight from the conversation. The AI assistant answers standard questions from the knowledge base around the clock and hands complex cases to an engineer. The API and Albato on the Pro plan connect the CRM to your product and billing.
Related reading: unit economics, client acquisition cost.
How it works in Mestra
At sign-up, choose the "IT and SaaS" industry — contact roles, subscriptions, churn reasons, tickets and both templates appear straight away. The Economy plan costs 390 ₽ per user per month incl. VAT; the AI assistant comes from the Standard plan, and the API on the Pro plan.

FAQ
Is Mestra suitable for a web studio without subscriptions?
Yes. Development projects with stages, hours and acceptance, plus an hourly rate, work without subscriptions.
Can you calculate MRR across all clients?
Yes. Subscriptions are recorded as monthly revenue, and upgrades and downgrades record changes in MRR.
How do you run support?
Tickets are created from client messages, each with a priority and SLA, and the history is stored in the company card.
Bottom line
An IT company grows when it understands why clients renew and why they leave. A CRM with contact roles, subscriptions and churn reasons gives you those answers. Move your clients and subscriptions to Mestra: 15 days free, no card.
WhatsApp is owned by Meta, which is recognised as extremist and banned in Russia.


