FAQ
Questions about Brikt, answered.
The ones that come up before anybody books anything — about what the AI can and cannot do, what your data is used for, and what this costs the people you invite.
Answers
What people ask before they book a demo.
Can Claude change my schedule without me knowing?
No — and not because of a setting somebody could turn off. Claude drafts; a person applies. Every AI-authored change arrives as a proposal you review on the real grid, and applying it is a deliberate act that is logged and attributed to you.
The claude.ai connector works the same way. It exposes reading and drafting, and there is no apply on the other side of it at all: absent rather than disabled.
Is my project data used to train AI models?
Anthropic's commercial terms do not permit content submitted through their API to be used to train their models, and we do not use your project content to train models of our own.
Can I import my existing schedule?
You can bring a Microsoft Project XML file. Claude reads it and drafts it back to you as a proposal — the same review surface as any other change — so nothing writes straight into your project and there is no bulk load that leaves you guessing at what it did.
A file Brikt cannot read is refused with a clear message rather than half-imported. That is the whole of what exists today, and we would rather say so than promise a format we cannot read yet.
What do external collaborators pay?
Nothing. That is the pricing model rather than an introductory offer.
Pay only for your company's team. Every subcontractor, owner, and architect you invite is unlimited and free.
Which company holds the subscription and which people are external collaborators is decided per project, not by company type — an owner can hold the subscription with the general contractor invited as an external. The free claim attaches to the relationship, never to a kind of company.
Does Brikt replace my scheduler?
No. It makes the schedule legible to everyone who has to work from it, and it drafts for review.
Somebody still has to own the logic, decide what the plan actually is, and judge whether a draft is any good. Brikt gives that person a faster way to work, and gives everyone else a way to read what they produced without being trained on scheduling software first.
What can you give my IT reviewer?
Mechanisms rather than badges: tenant isolation enforced by the database on every query, per-field conflict control, an AI that can draft but cannot apply, deny-by-default reads, authentication through WorkOS with encrypted revocable sessions, and an audit trail that records who changed what and through which door.
Brikt is a small operation and has no third-party audit report to hand you. What it has is a list of mechanisms your reviewer can put questions to in a demo and watch the answer, and a privacy policy that says the same thing without hedging.
How do I get started?
Book a demo and bring a job you are running now. A real schedule with a real problem on it is worth more than a walkthrough of a sample project, and it is the fastest way to find out whether this fits how you work.
Self-serve plans open soon. There is no permanent free tier: Brikt is paid for by the company that runs the schedule, and the people that company invites are free.
Still deciding? Bring us a real one.
The questions that matter tend to be about your job rather than about the software.