# LumenDesk 2.0: what small teams should check before trying it

LumenDesk 2.0 is worth a controlled trial if your team already qualifies for access and spends time finding answers in documents. It is not a reason to stop checking those answers. The useful question is whether drafting gets faster after you include the work of checking the result. This article assesses the supplied documents, not hands-on testing by the author or Kingy.

## Who can use it now?

The October 16 announcement opens the browser app to existing Team customers in Canada and the United States. New customers can join a waitlist, not start immediately. An API and EU availability are planned for Q1 2027, with neither an exact date nor a guaranteed rollout. If your workflow needs either, do not budget around delivery yet. [inputs/S1-announcement.md, “Access”]

The assistant accepts searchable PDFs and DOCX files, with a 50 MB limit per file, and drafts answers with page-linked citations. Scanned PDFs need the separate OCR add-on. It does not approve payments, send emails or execute contracts. Think document assistance, not delegated authority. [inputs/S1-announcement.md, “Features”]

## Budget for the workspace, not just one seat

The current price is USD 29 per seat per month, billed monthly with a three-seat minimum. That makes the minimum monthly bill USD 87 before tax, calculated as three seats at USD 29. The USD 19 shown in the October 16 launch screenshot was wrong; the October 17 pricing correction supersedes it. No annual offer is supplied. [inputs/S2-pricing.md, “Current plans”; “Correction”]

The plan includes 500 document uploads per workspace each month—not 500 per person—and unused uploads do not roll over. Extra uploads cost USD 0.08 each. OCR adds USD 12 per workspace monthly, bringing a minimum-size workspace with OCR to USD 99 before tax and overages. Count expected uploads and scans before deciding whether the headline seat price fits. [inputs/S2-pricing.md, “Current plans”]

## Faster drafts are not proven total savings

LumenDesk reports that, in its internal test of 40 procurement packets, median first-draft time fell from 50 to 20 minutes. That is a 30-minute reduction in the reported medians, not evidence that your team will recover 30 minutes on every packet. The measurement excludes human verification, and no raw task-level results are published. It cannot establish end-to-end time saved. [inputs/S1-announcement.md, “Vendor test”]

There is a useful caution from DeskLab's separate observation. Across six searchable procurement PDFs, five answers cited the correct page. One cited the wrong page even though its answer text was correct. DeskLab calls this a small, informal review, not a benchmark; it did not test scans, OCR, privacy or team workflow. Treat it as a reason to inspect citations, not an accuracy score you can generalise. [inputs/S4-independent-review.md, “Method”]

## Check the data terms before uploading

The data policy says customer documents are not used to train LumenDesk's base models. That is narrower than a promise that documents are never retained. Default storage is 30 days; admins can delete earlier. Active-storage deletion occurs within 24 hours, but backups can persist for up to 30 further days. [inputs/S3-data-policy.md, “Handling”]

An external model provider processes requests under contract. There is no on-device mode, and the policy does not promise zero retention or guaranteed regulatory compliance. A team handling sensitive documents should compare those terms with its own obligations before uploading anything. [inputs/S3-data-policy.md, “Processing”]

## A sensible first trial

For an eligible existing customer, I would start with a small set of permitted documents whose answers someone already knows. Ask specific questions, open every cited page and record both drafting time and checking time. Include corrections in the total. Test scans separately if OCR matters; the independent observation offers no evidence for that workflow.

Try it now if that limited exercise fits your access, budget and data rules. Wait if you need immediate new-customer access, EU availability or an API. Keep the decision narrow: does this assistant reduce your team's verified document work enough to justify its bill? The supplied evidence supports investigating that question, not assuming the answer.
