Capitán is one no-code platform, and every product below runs on it. They share the same data model, the same automations and the same mobile app — so a work order raised in one place is visible everywhere else, and you are never reconciling two systems that both believe they are authoritative.
Capitán MES
For plants that need to know what actually happened, not what was planned. Work orders, BOMs and processes, machine data read directly from your equipment, and end-to-end in-process traceability including waste and quality control. Start here if material variance, downtime or lot-level traceability are questions you cannot currently answer.
Capitán PM
For work delivered as projects and billed as projects. Budgets, milestones, timesheets and invoicing in a single record, so margin is visible while a job can still be influenced. Construction contractors use it across concurrent sites; software teams use it to separate billable from non-billable time without reconciling three systems.
Capitán HR
For businesses whose scheduling problem is really a capability problem. Employees, assignments, attendance and the skills or certifications that decide who can actually do a given job — so rosters are built against facts rather than memory, and you can prove afterwards who was where.
Capitán FM
For organisations responsible for places rather than products. Assign staff by workplace and capability, schedule preventive maintenance, and track every asset across sites so a fault has a location, a history and an owner. Used by venues, security operations and multi-site facilities teams.
Capitán Inventory
Balances built from movements rather than typed over: receipts, issues, shipments and counts are all transactions, held in warehouses and locations. Stock is costed as it moves on moving average or FIFO, so valuation and cost of goods sold are queries rather than month-end projects.
Capitán Sales
Quotation to order to shipment to invoice to receipt, as one connected chain. Partial fulfilment is the normal case: lines track what has shipped and what stays open, prices resolve from the customer's own list, and invoices carry statutory numbering and allocation numbers.
Capitán Purchasing
What you ordered, what actually arrived and what you were billed for, kept connected. Goods receipts are inventory events, partial deliveries are tracked per line, and a supplier invoice line points at the receipt line it settles — so the three figures reconcile by design.
Capitán CRM
Campaigns, the leads they produce and the customers they become, in the system that also quotes, ships and invoices them. Every lead carries an owner, a priority and a next action date, so the follow-up is a field rather than someone's memory.
Capitán Help Desk
Service tickets that carry their invoicing option from the start, with work logged against them by start and end time. Internal notes stay separate from the customer's account, tickets nest into sub-tickets, and assignment goes to a team or a person.
Capitán Financial
Double-entry books kept where the work happens. Shipments, invoices, payroll and depreciation post to the same general ledger, with VAT rate history, period locking and gapless statutory numbering. Built for Israeli reporting: PCN874, the uniform file, withholding tax and Tax Authority allocation numbers requested at issuance.
Capitán Payroll
Israeli gross-to-net on the same employee records your schedules already use. Income tax, national insurance and pension are computed from separate statutory bases, using time-effective tables so historical runs stay correct. Payslips and the matching journal entries come out of the same run.
Which one should you start with?
Almost nobody needs all of them on day one, and trying usually backfires. The pattern that works is to start with the single question costing you most — unexplained material variance, unquantified downtime, projects whose margin only becomes clear at the end, stock figures nobody trusts, support work that never gets billed, or a month-end close that never quite reconciles — instrument that properly, prove the data is trustworthy, then extend.
Because everything runs on the same no-code platform, extending does not mean a new implementation project each time. If you are unsure which product maps to your situation, talk to our team — it is usually clear within one conversation.