mybusynessHow do I get started?
Four screens and you are in. We take over your existing books via Excel; this page sets out every step and every limit in one place.
Four screens and you are in
No card, no registry extracts, no specimen signatures. The 3-day free trial starts the moment you set up your company.
Open an account
RegistrationThree fields: name, e-mail, password. One question: am I setting up my company, or do I have an invite code? The account that sets up the company opens with General Manager rights; anyone arriving with an invite code joins their own department.
Introduce your company
setup screen after sign-in
The only required field is the company name. Optional: tax number, industry, city, headcount. Plus your company rules — such as «new customers pay in advance»; every virtual collar follows what you write here. Approval thresholds and privacy rules start on the strict side by default.
Take over your existing books
Documents
The documents screen has two roots: before mybusyness (documents you upload) and created in mybusyness (what the virtual collars produce). On the first side you drop your Excel file and start the data takeover: three steps — choose a target, map the columns, preview and take over.
Give your first job
Cockpit
In the cockpit you write in your own words: «Prepare the November consulting invoice for Example Ltd». The virtual collar shows the plan first — which steps, which blockers, how many credits — you confirm, then it does the work.
It says what it will do first, then does it — asking and planning cost 0 credits. If you do not confirm, no credit is spent.
How your existing books come in
You do not start from zero. We bring in the records you have kept so far, as they are.
Drop your Excel file as it is; we recognise your columns, and where we cannot, we ask you.
Invoices
Your past invoices become records. Your invoice numbers continue from your existing series — you do not have to start a new one.
Customers and suppliers
Your customer and supplier cards are created; statements, reconciliations and payment reminders build on them.
Employees
Your personnel records come in; leave and HR documents build on them.
Step 1/3 — Choose a target · Step 2/3 — Map columns · Step 3/3 — Preview
On the spreadsheet path none of your rows leaves the system — this path is 100% code, not a single row goes to a model. On the PDF path, what leaves is masked text; anything sensitive never leaves.
Connecting your existing systems
This connection is set up on request: write to sales@mybusyness.com and our setup team defines the scope and connects it.
What each department does today
The job catalogue holds 62 jobs; 59 of them run without any model and without using credits — amounts, dates, VAT and thresholds are calculated by code. The examples below come from the product’s own job list.
| Department | Number of jobs | A few things it does today |
|---|---|---|
| Human Resources | 12 | Employment contract draft · Annual leave record · Termination notice draft |
| Accounting | 14 | Create an invoice draft · Prepare a payment reminder · Account statement with ageing · Cash flow report (30/60/90) · Balance confirmation letter |
| Sales | 11 | Prepare a sales quote · Pro forma invoice (as a quote) · Order confirmation · Delivery note draft · Quote follow-up letter |
| Purchasing | 12 | Request for quotation (RFQ) · Create a purchase order · Receive an order · Supplier scorecard · Prepare a reorder |
| General Manager | 7 | Cockpit briefing · Work package (assign the job) · Connection setup guide · Document summary and critical fields · Ask a department’s virtual collar |
| Export | 5 | Export pro forma invoice · Commercial invoice · Packing list |
| Legal AI | 1 | Contract and legal text analysis |
| Import | 0 | Today a question-and-answer department: no tool of its own that produces documents. Purchasing and Accounting prepare the customs paperwork; your customs broker files the declaration. |
| COPAI | — | Not a department but a layer. It has no job list of its own; every external call of the other eight collars passes through here. |
Three jobs use a model and consume credits: Contract and legal text analysis, document summary and critical fields, ask a department’s virtual collar. The remaining 59 are pure code.
Seven actions, including money movement and tax filing submission, are locked in code and never open. The virtual collar does the preparation; an authorised person carries out the transaction.
What happens to your data
We make four promises, and all four are backed by code — not marketing lines, but locks.
Masking before any external model
Before every external call your text is scanned: IBANs are validated with mod-97; phone numbers, e-mail addresses, card numbers and keys are masked. The content is also classified and routed by its class: general content to the cloud, sensitive content only to an in-house model, secrets to no model at all. The masking map is stored encrypted and destroyed automatically after 24 hours. If no local model is installed, a job routed there does not silently slip to the cloud — the system says so openly and the job stops.
Your keys in an envelope-encrypted vault
Only you enter your key; our server stores it encrypted, never shows it again on screen or in logs, and never hands it to a virtual collar. If you connect via OAuth, your password never reaches us. Every entry is wrapped with its own key, and that key is wrapped with a versioned master key — when the master key changes, the entries are re-wrapped. We do not say «we never see your key», because the key reaches the server in plain form over an encrypted connection and is decrypted in memory on every call. We write it as it is.
The audit trail is never deleted
Every job, every model call, every masking step and every finalizing decision is written with chained hashes: each entry carries the hash of the one before, and it can be shown mathematically that no entry was changed afterwards. There is no way to update or delete — even if you remove a connection, the record of what was done through it stays.
The money path is closed in code
Seven actions, including transfers, payment orders, tax returns and customs declarations, are locked away from virtual collars at code level. No prompt, no company setting and no connection can open them. The virtual collar does the preparation; an authorised person carries out the transaction.
On top of this sits the approval engine. Every record gets a colour: green the virtual collar does it directly · yellow produces a draft that the owning department reviews · red only an authorised user of the department. As the amount grows, the colour moves up one level. An action that is not in the catalogue counts as yellow by default: when in doubt, the strict side. The decision is made not by the General Manager but by the department that owns the record. Invoices are finalized in Accounting, HR documents in Human Resources, legal work with the lawyer.
Legal AI flags risky clauses and suggests redlines. Until an authorised lawyer finalizes it, legal output is not final and cannot be exported — the download button stays locked. The product does not replace the lawyer; it gives the lawyer leverage.
Questions you may have
The eight most common questions of the first week. Every answer describes how the product behaves today.
All you need to start is a company name
No card details needed. The first 3 days are free. Nothing is deleted even when the trial ends: only starting new jobs stops, and your documents and audit trail stay as they are.