IMtech

Service

CRM and sales

We build a CRM around the way you sell: enquiries and orders with statuses, a request card with documents and correspondence, price calculation right in the request, accounts for customers and partners. Not a box full of extras, but what your sales team actually works with.

Animation: enquiry cards pass through four narrowing sales stages like a funnel; some drop out on the way, the rest reach a deal, and history rows are added to the customer card.

When you need it

Situations that bring people to us for this service.

  • Enquiries in messengers and email

    A customer's history is scattered across chats, and the answer depends on who remembers what.

  • Statuses have to be chased

    To find out what stage an order is at, the customer writes and a manager searches.

  • Prices are calculated by hand

    Every quote is a spreadsheet and a manager's time, and a mistake costs money.

  • A boxed CRM isn't your process

    Stages, fields and roles don't match how you actually sell.

What's included

  1. Sales analysis

    Where customers come from, which stages an enquiry goes through, who is responsible for what.

  2. Enquiries and orders

    Every enquiry is stored in the system with a status, a reason for each change and a history; notifications go by email or messenger.

  3. Search and filters

    Filters by status and source, search by name and phone number.

  4. Request card

    Addresses, attached documents, PDFs and correspondence — in one place, not in the inbox.

  5. Price calculation

    The customer or a manager sees the price by your rules straight away, and you update the rules yourself.

  6. Customer and partner accounts

    Separate accounts for companies, employees or suppliers; a partner can sell under their own brand.

  7. Roles and access

    Each role sees and changes only what it is allowed to.

  8. Integrations

    Website forms, email, messengers and your accounting system — data reaches the CRM without manual copying.

What you get

  • A description of sales stages, statuses and roles
  • A prototype of the key sales scenario
  • A CRM with enquiries, cards and search
  • Customer or partner accounts, if you need them
  • Links to your website, email and messengers
  • Code and documentation that are open to you

The project path

From the first conversation to daily use

Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.

  1. 01

    Getting to know the task

    You describe the process and what gets in the way. We reply by email with questions and arrange a call.

  2. 02

    Discovery

    We study the process with the people who work in it and write down what the system must change and how we will check it.

  3. 03

    Prototype

    We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.

  4. 04

    Pilot

    We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.

  5. 05

    Launch and growth

    We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.

Systems where we have already done this kind of work.

Technology in these case studies

  • REST API
  • JWT
  • Excel
  • PDF
  • Strapi
  • PostgreSQL
  • Next.js
  • LiqPay
  • Puppeteer
  • Django
  • Django REST Framework
  • Telegram

Questions about this service

Why not use a ready-made CRM?

If it covers your process, use it. We step in when selling has its own rules: complex price calculation, partner accounts, particular statuses.

Can a website form and a messenger be connected?

Yes. An enquiry is stored in the system first, and a notification arrives in the messenger — that's how the cleaning company case study works.

Can partners sell through our system?

Yes. In the road freight case study a partner gets a site under their own brand — with their own logo, language and price coefficient.

Can we start with one part?

Yes. First a prototype of the key scenario, then a pilot, and only after that do we decide what to add next.

Have a project with no ready-made solution?

Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.

Get in touch