Why one system instead of a stack of apps
A typical company lives in five to ten windows. Tasks in one tracker, customers in a CRM, customer chats on reps’ personal phones, documents in email, the org chart in a spreadsheet, accounting in yet another app. Someone set each of them up, and each has its own users and permissions. A new hire gets added in six places, and when they leave, someone forgets to remove them from two.
PRANUS works differently. It’s not a set of apps tied together with integrations. It’s one system with many sides, built on shared people, shared permissions, and shared memory.
Services by group
Work and team
- TASKUS: tasks and projects that show not just the owner but whose turn it is, from acceptance and deadlines to hand-offs between departments, delivery, and sign-off.
- GARDUS: a task garden, a living map of company work where abandoned tasks wilt and ask for a decision.
- TEAMUS: org chart, HR, hiring, job descriptions, and permissions. The org chart isn’t a picture: it drives access across every service.
- LOGUS: business rules and processes with formal verification. Logic gets calculated, not guessed.
Customers and sales
- CRMUS: leads, deals, pipelines, and calls. Calls and chats turn into summaries, stages, and tasks on their own.
- SALEUS: an AI sales agent, outreach sequences, AI cold calling, and a mobile app for sales reps.
- SCRAPUS: a database of companies built from their websites, with contacts, industry, country, and personalized proposals for outbound sales.
- TELEGRAMUS: leads from public Telegram channels and groups.
- CONNECTUS: every customer conversation in one inbox, with routing, bots, and history import.
Communication, knowledge, and documents
- CHATUS: a team messenger with calls, one-click approvals, and a Questions board where AI agents come to people for answers.
- MEMUS: company memory, a knowledge base that only answers when it can back the answer with a document.
- DOCUS: documents from template to approval, signature, and records, plus proposals and contracts sent to customers by link.
Money and operations
- BUHUS: accounting, finance, and payroll with local tax rules, bank feeds, automatic statement matching, and month-end close.
- OPTIMUS: ERP for manufacturing, trade, and services, covering inventory, purchasing, routings, and cost of goods.
AI and growth
- AGENTUS: AI employees with roles, permissions, memory, and budgets, plus a control panel that shows what each agent is doing.
- CONTENTUS: a content studio for articles, content plans, video, and social media publishing.
- WEBUS: websites and landing pages built by AI that run on your company’s data from day one.
- DEVUS: an AI developer that customizes the system for your company, from task to release, with a “nothing broke” check.
One fabric: what every service shares
Shared people. Add a person once in TEAMUS and they appear everywhere: tasks, CRM, customer messaging, the team messenger, accounting. One account, one sign-in.
Shared permissions. Permissions follow a person’s place in the org chart. Move someone to another department and their access changes across every service automatically. Offboard them once and access closes everywhere.
Shared memory. Documents, policies, expert answers, and knowledge from customer chats come together in MEMUS. Employees, AI agents, and the personal assistant all answer from it, each within their own permissions.
Shared catalog. One product or service record works across the CRM, documents, and ERP. The proposal, the contract, and the production order all use the same line items.
The AI layer: built in, not bolted on
AI in PRANUS isn’t an “ask the chatbot” button in the corner. It’s a layer that runs through every service.
- A single AI hub. Every model request goes through one gateway: the right model for each task, fallbacks when a provider fails, spend tracking, and limits per person, department, and company. Air-gapped setups use local models.
- Agents act with a person’s permissions. AI sees the task, the customer, the contract, and the account balance at once, but only what the person it works for is allowed to see.
- Agents don’t make things up. Answers come from the knowledge base with a link to the source. When there’s no answer, the agent hands off to people.
- Logic is calculated, not guessed. Rules like “ship only after the acceptance certificate is signed” are checked by LOGUS, which reports an honest confidence level.
- The agent suggests, a person decides. Any configuration change or write to an outside system goes plan, approval, apply, with one-click rollback.
- One window into the whole company. The Assistentus personal assistant takes voice or text, creates tasks, sends reminders, and answers “how are we doing?” See the apps page.
How the services work together: five scenarios
From lead to payment
A lead from your website or social media lands in CRMUS, gets checked for duplicates, and is assigned to a rep. The rep chats in CONNECTUS or calls, and the call is transcribed. At the right stage, the rep sends a proposal from DOCUS by link, the customer accepts it, and the contract is built from the accepted version. The invoice and payment are recorded in BUHUS, and a “ship it” task appears in TASKUS on its own.
A call becomes work and a script
The call is transcribed, and CRMUS gets a summary, a stage, and a follow-up task. The review shows objections and unanswered questions, and the manager gets a report. The Suggest Script button builds a draft from your best calls. It goes into the Sales knowledge base in MEMUS, and the AI sales agent in SALEUS works from it.
The agent doesn’t know, so the company learns
A customer writes in CONNECTUS, and the AI agent searches MEMUS. No answer? The agent tells the customer “let me check with a specialist” and sends the question to CHATUS. The specialist answers, the reply goes straight to the customer, and MEMUS gains new knowledge. Next time, the agent answers on its own.
Hiring for an empty seat on the org chart
There’s an empty seat on the TEAMUS org chart, so you click Find a Person. The AI recruiter builds a candidate profile, searches, talks to candidates, and shortlists them with quotes. The interview goes on the manager’s calendar. After the offer, a hire event issues the order and contract in DOCUS, adds the salary to BUHUS, and gives the new employee access across every service.
Meeting to minutes to tasks
A call in CHATUS or a meeting recorded on a phone gets transcribed, including mixed-language conversations. You get minutes with decisions, risks, and action items. Once approved, action items become tasks in TASKUS, and a summary goes to the company feed.
Where to start
You don’t need all 18 services on day one. In 14 days, the implementation agent launches your first working setup: org chart, permissions, employees, CRM, tasks, customer messaging, and the knowledge base. Everything else comes in later phases. Learn more about implementation in 14 days and cloud, self-hosted, or air-gapped options.
Want to see it on your own tasks? Request a demo.