The orchestrator does the work, Task Desk runs it, the CRM carries it through to a deal. Three equal parts of one platform: each can be taken on its own, and together they work as a single company conveyor.
Below, each part is taken apart up close: what a person actually does by hand, and why this does not turn into one more program that nobody fills in.
You describe the task in plain language. The dispatcher picks the right team of agents out of 23 proven systems, runs the work through a conveyor and hands back a finished file — not text in a chat window, but a document a business can work with.
Law, finance and modelling, marketing and SEO, tenders, recruitment, market analysis, development, logistics. Each system is not a single prompt but a conveyor of agents with their own roles, knowledge and contract for the result.
Word and Excel with live formulas in the cells, presentations, CSV, dashboards with charts. The Excel comes out as a model you can recalculate, not a picture of a table.
If the system you need is missing, the platform assembles it for your task: it designs the roles, the instructions and the agent conveyor from proven templates and submits it for review. The roster grows with your challenges — with no development invoices.
The dispatcher reads the request and the profiles of every system, picks the one to do the job and lays out a plan.
The chosen system carries the task through specialised agents in a conveyor.
An internal council matches facts and references against primary sources. A fact with no source stops the answer.
Finished files to one standard — ready to download in a single click.
The place where a company’s work lives once it has been assigned: tasks and projects, deadlines, people, units and rights. Not one more tracker filled in for show, but a floor where work cannot get lost.
Six stages — from new to finished, deferred or cancelled. A task cannot be finished without a result: the result is a pointer to a specific comment. And the definition of done is copied into the task at the moment it is assigned, and cannot be rewritten after the fact.
If no due date was set, the platform takes the latest date among the work items. Being overdue is not red paint on a screen but a fact written to disk: it shows exactly what has stalled and by how many days.
A matrix of rights: your own unit, your own manager, another unit, another manager. A role is attached to a person or to a whole unit at once. By default everything is allowed — rules are introduced when they are genuinely needed.
Units, positions, employees — and a reporting line that is not drawn by hand but computed from the company’s live state. That is why it does not diverge from reality the day after the meeting.
An employee is not deleted — they are dismissed, access is cut off by itself and the history stays. When someone goes on leave, a stand-in takes over and tasks do not hang. Every change in the company goes into a dated log.
A full system for working with a client, standing right beside the orchestrator: a proposal, a calculation or a contract is born here, in the context of the deal, rather than in a separate program that everything is then copied out of by hand.
A separate directory of companies and people with a stable record number, and deals as separate entities too, each with its own number and its own address. One deal — one place everyone working on it looks at.
From a new client to an active one, with a pilot run and waiting for payment. A drag-and-drop board, with empty stages collapsed. The platform will not let a deal into “Closing” without an amount, and it shows amounts per currency separately — with no invented exchange rates.
A letter or message from an unknown sender lands in the unhandled queue — one click creates the record. A letter from someone known, but with no deal address, waits in the “assign” queue instead of sinking into somebody’s personal inbox.
Your own fields on a deal, a company, a task and a product: text, number, date, yes or no, a list of values, a file. To keep it from turning into chaos there is a single scribe — the system administrator; the fields themselves are filled in by everyone who works with the record.
A field is not deleted — it stops being active, and what has already been entered does not disappear. So configuring a record can never destroy history.
This is the difference between a platform and a set of programs: the next step picks up what the previous one finished, instead of asking a person to carry it across by hand.
“Prepare a quotation for this client on the terms we discussed.” The orchestrator takes the details from the client record and hands back a finished document.
A task is born out of the document: an owner, a deadline, a definition of done. The manager watches it move without asking anyone in a messenger.
The deal advances a stage, the client’s reply lands in its record, and the whole history stays where people will look for it next time.
The first 30 days are the full feature set with no limits. We start with a demo on your own task: bring a typical instruction and we will walk the whole path from the sentence to a finished document, a task and a deal.
SensFlow