CRM, ERP and business systems

Customers, mail, tasks, roles and permissions and reports, arranged around the way your company works.

• Daily dashboard — The first screen in the morning lists today's orders, overdue tasks and anything waiting for a decision. The manager can see where to start without going through the menu. Only users with permission to see the dashboard get it.
• Business analytics — Turnover, margin, returns, stock turnover and markets are calculated from the orders in the system, with no separate spreadsheets to keep. You choose the period and market on screen. Reports and stock use the same records, so their numbers match.
• Decision centre — Agent suggestions and report findings are collected in one list, sorted by priority (high, medium, low). Each item links to the screen where you can act on it. A person makes the decision and takes the action.
• Customer file — The file keeps a customer's contacts, orders, tasks and conversations in one place. Wholesale customers also get their own price list, payment terms and an assigned sales rep. You search by name, company ID, city or phone, and the system blocks a second record with the same company ID as it is entered. Sales reps see their own customers; the manager sees everyone.
• Sales rep tasks — Calls, meetings, quotes and visits are logged as tasks with a customer and a due date. When a customer enters a new stage, the system can create the next task according to rules the manager sets up (off by default). Unfinished tasks move to today by themselves every night and the number of times a task was put off is recorded; urgent ones get a list of their own.
• Sales pipeline — Each customer goes through stages you choose (by default from new contact to contract), and the end is won or lost with a reason. The customer file shows the stage reached and every move is a line in the journal. Reports list the stuck customers and the expected weighted amount.
• Quotes — You build a quote from the model catalogue and prices, and it goes to the customer as a PDF. Because it is linked to the deal, the "Quote" stage is marked automatically. Later stages reuse the customer and machine, so you do not enter them again.
• Manufacturer orders — When a sold machine is not in stock, you order it from the manufacturer in the same system. The order has a status and shows which customer and deal it is for. Sales reps can update the customer without calling purchasing.
• Model catalogue — Machine brands and models with their specifications and the brochures you send to customers. Quotes and the machine registry take the model from here. The catalogue is maintained in one place, so all sales reps use the same data.
• Customer machine registry — Each machine sold or serviced has a record with serial number, engine, year and owner. Work orders, warranty cases and replaced parts are added to it over time. When the customer calls, the full machine history is on one screen.
• Service schedule — Service jobs are assigned by technician and day, and the system will not let two jobs overlap in the same slot. Unapproved jobs stay highlighted until the manager approves them. Technicians receive changes on their phones.
• Warranty claims — A warranty claim to the manufacturer for a signed work card: the lines (parts, labour, kilometres) are warranty or for the customer's account, the manufacturer's decision is per line, and the status is worked out from the decisions. The protocol is a PDF following the manufacturer's template, sent by email; rates are fixed when sent. The credit note is tied from Suppliers and bills.
• Service bulletins — Manufacturer campaigns and bulletins with serial-number ranges that are never merged. Machines are searched only in Machines, after confirmation, and a task in Service is made for each marked machine — one per machine per campaign. Reading a bulletin with AI is a checkbox, off, and gives only a draft.
• Technician workload — For a chosen period the report shows, per technician, how many jobs they had, how many they finished and how many are still open. The figures match the manager's mobile app because both use the same source. You can see who is overloaded and who has time to spare.
• Customer map — Customers are placed on the map by the location of their farm, with filters for sales rep and region. A point opens the customer file or navigation to the address. Sales reps plan their visits from the map.
• Transport — Transport of machines and parts is recorded as jobs with a vehicle, a driver and a date. Each driver has a schedule, and a handover protocol is printed at delivery. Arrangements are kept in the system instead of on the phone, so they do not get lost between departments.
• Approvals — Actions that need a human decision wait in a shared list: payments, till discounts above the limit and actions proposed by an agent. The person responsible presses "Approve" or "Reject", and the action goes ahead or stops. Each decision is logged with who made it and when.
• Team chat — An internal chat for the whole team inside the system, with history, photos and attachments. New messages arrive as notifications, on phones too. Work conversations stay in one place instead of spreading across personal apps.
• Team tasks — Every task has an owner and a due date and is tracked until it is done. If you leave the date empty, the system sets a default. Where the system also has group chat, you can create a task straight from a conversation without retyping it. Each person sees their own tasks; the manager sees all of them, overdue ones included.
• Mail — Mail opens inside the system, with several mailboxes over IMAP and SMTP, replies and attachments. Messages are copied into the system together with their attachments, so search is fast and a message deleted on the mail server stays with you. Each mailbox is visible to everyone or only to chosen people. Mail from other modules (quotes, invoices, supplier requests) can leave from a chosen mailbox. The team handles email without switching to another program.
• Calendar — Meetings and tasks with customers are in a weekly schedule with a time and a length. Everyone can see what is on today and this week, and meetings are not hidden away in someone's personal phone (a seller sees their own).
• Shared files — A shared place in the system for the team's documents, such as contracts, price sheets and photos. What each user sees depends on their permissions. Files do not end up in someone's personal inbox or on a single computer.
• Customer risk check — From the order, the system checks the customer's phone, email and name against a public register of unreliable buyers. The result appears next to the order before the parcel goes out. A person decides whether to ship.
• Customer quiz — A quiz on the website asks customers what they need. The answers are saved to their profile and shown in the system, and customers are grouped by the needs they gave themselves.
• Public tenders and programmes — The system downloads procedures from the public portal along with their documents, so nothing is fetched by hand. It assesses whether your company is a fit and flags suspicious procedures. For a procedure you select, it drafts an offer to its requirements.
• Car bulb finder — You find the right bulb by make, model and position in the manufacturer's public catalogue. Data fetched once is kept in the module's cache, so later searches do not wait on the external service. Fetching runs at a slow, steady pace to stay within the catalogue's rate limit.
• Roles and permissions — Each user has a role (owner, sales rep, service, technician, driver, accountant) and sees only their own screens and data. An administrator can "log in as" another user to see exactly what they see, then switch back. A new employee's account and permissions are set up from one screen.
• Multiple companies — Two or more companies run in one system, in one list. A channel belongs to a company, and invoices and sales documents are issued in its name and with its own numbering. Full separation if you want it: an employee sees only the channels, orders, documents and shipments of their companies.
• Built-in manual — The manual is part of the system and describes the screens as they actually are. Any user can read it without a special permission. New staff learn from it instead of asking colleagues about every button.
• Feature requests — The team logs what gets in their way or what is missing directly in the system instead of reporting it by phone. Each request has a status showing whether it is accepted, in progress or done. Development follows this one list, so nothing depends on memories of conversations.
• System map — An interactive diagram of the modules showing which ones connect to which. It helps when a new employee starts and before anything in the system is changed.
• Training — Courses for the team inside the system, each ending with a test. The correct answers are never sent to the browser, so the score appears only after you submit. Every attempt is saved with its score and whether it passed.
• Themes and quick search — Each user picks a colour theme that is comfortable for the whole day. Ctrl+K opens a search across all modules, and a few letters get you to the screen you need without digging through the menu.
• Daily sales rep digest — The seller report is worked out when you open it for a chosen day or period: finished tasks by kind, new customers, won and lost, against the month's goal. The manager sees who did what without asking each person, and can download it as Excel.
• Website inquiries into the CRM — The inquiry form on the website writes directly into a small CRM, with no mailbox in between. Each inquiry has a status, and new ones are counted separately so none go unanswered. From an inquiry you continue to a client, a quote, a contract and a PDF protocol.

Alle Module