RubusCollect sends each person a link, works through your list with them in a conversation, keeps every answer in a typed field with the documents attached, and reconciles all of it into one document you can act on.
Answers are attributed today. An aggregate-only mode is being built, and it will arrive as a guarantee rather than a checkbox.
Nordic Holding AS holds 60%. Is that a company, or a person?
It’s a company.
Then I need its owners too — who holds more than 25% of Nordic Holding?
Example use cases
Every one of these ships as a starting template. Take it as it is, or edit it into the questions you actually ask.
One link to a new corporate client. It works through the company, its business, its representative and its beneficial owners — and where the answer is “a few shareholders”, it asks for names and percentages rather than writing that down.
A complete file with documents attached, an approve / reject / more-information decision on the record, and a five-year retention floor that nothing deletes early.
Certifications, insurance, subcontracting and incidents, asked of everyone at once — with certificates uploaded against the item they belong to instead of arriving as a pile of email attachments.
How many hold what, every certificate and policy lapsing inside twelve months, and exactly who still owes you which items.
Seven statements on a scale and three questions in their own words. Nobody is chased by a spreadsheet: it asks, they answer when they have five minutes, and they can stop and come back.
A score per statement and per team, the words that keep recurring in what people would change, and every comment reproduced in full.
Where the repetitive time actually goes, how ready the systems and the people are, and the question most readiness surveys leave out — what in this work has to stay a human decision.
A readiness index by dimension, the hours a year that repetitive work costs, a coverage map of who answered, and what each team said must not be automated.
Write the list yourself as a markdown document. Each line is a field with a type — a date, a number, a yes/no, a document — and it collects exactly those, refusing to invent one you did not ask for.
One table across every respondent, and a template you keep editing as you learn what you should have asked.
How it works
A markdown list, one line per field. Start from a pack — onboarding, supplier compliance, pulse, AI readiness — and edit it, or start from an empty page.
One unguessable link each, to four people or four hundred. They see the whole list before they begin, so they can go and find their documents first.
Every response reconciled into tables and cited claims. Not four hundred transcripts — one document, and the evidence behind each line of it.
Why you can send it to a client
You are asking someone for their passport, their owners, or their honest opinion of their manager. That has to be handled properly, or not asked for at all.
Questions
No. They open a link, talk to it, and close the tab. Coming back to the same link picks up exactly where they stopped, and revoking it takes effect immediately.
It can only write into fields your template defines — a name it made up does not exist and is refused — and it marks anything it had to interpret as low confidence rather than presenting a guess as a fact.
In an object store, under a random key, encrypted at rest. There are no shareable links: every download goes through us so it can be authorised and recorded, and a file is served only to the person reviewing that respondent.
Yes, and it changes what happens to it. A sealed field is encrypted at rest and deliberately withheld from the reconciler, so an identity code can be collected and reviewed but never aggregated over by a script.
Not today — every response is attributed, and an employee survey says so on its first screen rather than in a footnote. An aggregate-only mode with a minimum team size is being built, and it will arrive as a guarantee rather than a checkbox.
Create a workspace, write a template — or take one of the packs and edit it — and send the first link to yourself. Nothing is sent to anybody else until you invite them.
Write the list once. Send it to four people or four hundred. Read one answer at the end of it.
