Every role, and what it really does.
An employee in LOOPmKit is a project with a main agent. Employees call each other like functions, each with its own budget, memory, skills and connectors, and every call is written to a journal.
Most roles work with text only today. They read, plan, draft and review, but they do not run code, and they have no repository or outside accounts until you connect them.
How a team works
- A wizard creates the projects, skills and main agents in one transaction. If the connection drops, reload and you get the same company.
- You can hire and dismiss copies of an employee; each request is idempotent.
- A call between employees is a function call that returns a reply. Answers delivered later to the caller are still being finished.
- Who tasked whom, the status, the cost and the chain of calls are all journalled.
- Questions and approvals reach you in the web interface and in Telegram.
The ten roles the wizard starts with
You can edit the roster, rename roles, change who reports to whom, and grow the team to 32.
-
Chief of staffText work only
What it doesCoordinates goals, reviews evidence, tracks budgets and prepares decisions for the owner.
Hands work toEvery other role.
Needs a personDecisions are prepared for you, never taken for you.
-
Project managerText work only
What it doesTurns requests into tasks with acceptance criteria, owners and dependencies, and reports verified progress.
Hands work toTech lead and product manager.
Needs a personThe trust ladder applies to everything it does.
-
Product managerText work only
What it doesWrites requirements, sets scope and priorities, and keeps assumptions apart from verified evidence.
Hands work toProduct designer and project manager.
Needs a personThe trust ladder applies.
-
Technical leadText work only
What it doesPlans the implementation, reviews it and insists on tests.
Hands work toBackend, frontend, QA and DevOps.
Needs a personThe trust ladder applies.
-
Backend engineerText work only
What it doesImplements through development tools you configure, and says so when repository or execution access is missing.
Hands work toQA and the tech lead.
Needs a personThe trust ladder applies.
-
Frontend engineerText work only
What it doesBuilds accessible interfaces and checks them with tests and a real browser, through the tools you configure.
Hands work toQA and the tech lead.
Needs a personThe trust ladder applies.
-
QA engineerText work only
What it doesChecks acceptance independently, reproduces defects, and never counts a plan as a passing test.
Hands work toThe developers.
Needs a personThe trust ladder applies.
-
DevOps engineerText work only
What it doesPrepares builds, previews, releases and rollbacks.
Hands work toThe tech lead.
Needs a personA release goes out only after the owner approves it.
-
Product designerText work only
What it doesDescribes flows, responsive behaviour, accessibility and failure states in text.
Hands work toThe product manager.
Needs a personThe trust ladder applies.
-
Support engineerText work only
What it doesTriages, diagnoses and escalates, and drafts replies.
Hands work toThe project manager.
Needs a personA reply is sent only through an approval you have configured.
The extended list
More roles that exist as definitions and templates. Each one is a text employee unless the note says otherwise.
Management
-
SecretaryText work only
One entry point: inbox, mail read through IMAP, calendar, reminders, and routing orders to colleagues.
StatusReads mail only. Live acceptance of the chat scenarios is not done.
Engineering, by stack
-
Go, PHP, Vue and database developersIn progress
Stack skills for Go 1.25, PHP 8.4 with Symfony 8, Vue 3.6 with Nuxt 4 and PostgreSQL 18, and a rule for whom to ask outside their area.
StatusChecked with three cheap live probes. The code-writing path runs in isolated jobs on a git branch, with no push, and was tested with a stand-in for the vendor tool, not a real subscription.
-
Mobile developerText work only
Drafts mobile code.
StatusText only.
-
Security engineerText work only
Reviews the code and configuration sent to it, dependencies, secrets and incidents.
StatusNo scanner tools; it reads what it is given.
Analytics and growth
-
Analyst
Weekly reports from accounting totals, sales, projects and AI spend.
StatusReads files and memory.
-
MarketerIn progress
Strategy, a weekly publication package for your approval, a calendar, and leads passed to the account manager.
StatusChecked as a dry run only. No real posts.
-
Content writerText work only
Articles, posts, threads, captions and case studies in English, Russian and Serbian.
StatusText only.
-
Video producerChecked on a running stack
Voice-over and a rendered video with subtitles, from a script.
StatusChecked on a running stack in one run: a 17-second clip. Delivery to a chat is not built.
-
SMMIn progress
Carries out publications you have approved, through connectors.
StatusNo account is connected and nothing has been published. Comments are queued, and replies go out only from approved templates.
-
Account managerText work only
Answers leads and clients from the public layer of knowledge and keeps one card per enquiry.
StatusHands to the secretary, project manager, lawyer, marketer and support.
Finance and legal
-
Accountant
Double-entry books in PostgreSQL where SQL does the sums, receipts by fiscal QR code, bank statement import, categories, obligations and exports.
StatusTools are for the owner only. The fiscal and exchange-rate presets are for Serbia.
-
LawyerText work only
Contracts, NDAs and compliance questions, with sources.
StatusNot a licensed lawyer, and nothing verifies its answers.
-
ProcurementText work only
Subscriptions, domains, hosting, renewals, costs and reminders.
StatusText only.
-
HRText work only
Drafts specifications for new virtual employees, onboarding and quality scoring.
StatusCreating a real new project needs the owner.
Knowledge and front office
-
ResearcherChecked on a running stack
Summaries and comparisons with sources, through a shared web search.
StatusWeb search was checked on a running stack.
-
Knowledge keeperText work only
Memory hygiene, reusable solutions and consolidation.
StatusText only.
-
ReceptionistIn progress
Prepares call scripts and answers to common questions.
StatusLive telephony is built but has never taken a real call. See Modules.
In the gallery
The gallery ships 15 employee templates and 8 task templates, 23 in all. The wizard starts from 10 roles, and a company can hold up to 32.
What needs a person, for every role
- The trust ladder: read, draft or act. The lower level wins, and a draft waits in the approval queue.
- The approver can edit the arguments before executing.
- One exact publication can be approved in advance, once, within a window of fifteen minutes.
- Quiet hours, budgets per run and per day, and a policy where deny wins.
- Hiring, deployments and publications need the owner by rule, and publication is enforced by the approval system itself.
Honest limits
- The goal of a company that runs itself is not reached. Six of ten acceptance items are still open.
- A configured employee means roles and permissions exist. Repository access, execution tools, outside accounts and acceptance are separate steps.
- The main agents answer from the model alone. A request routed to a developer reaches a text-only agent.
- Models enabled on the founder's own instance are small ones, so quality on hard work is not proven.
Early access starts with a call
The product is at an early stage with a single operator. The repository is private and the terms are not set. If this fits a problem you have, book a short call.
A 20-minute call with the author. The repository is private, so a conversation is the way in.