What CrewOra has actually done — checked against its own records.
Marketing pages make claims. This page lists only things that already happened on the live product, each one checked against CrewOra's own database or its payment records. No ratings. No testimonials. No targets dressed up as results. If a number is printed here, it happened — and the date beside it is when.
Every employee has done a real job
CrewOra's catalogue holds 73 AI employees. On November 4, 2026, each one was hired through the real product and given a real job — research, writing, bookkeeping, scheduling, support drafts, and more — on the live system, under the same spending caps a customer gets.
All 73 did the work. Each finished job was charged exactly 1 credit and left a settled record in the product's database: 82 graduation jobs in total, because a few employees were tested more than once, and every one of those 82 records is marked settled. Afterwards the database was re-audited claim by claim, independently of the run reports: 73 of 73 employees hold a settled receipt.
That is the bar a CrewOra employee has to clear before a customer can hire them: not a demo, a receipt.
One employee is flagged — and the flag stays public
The SEO Writer twice stated wrong character counts for its own writing: a title that was truly 49 characters it labelled as 51, and in a re-test a title that was truly 57 characters it labelled as 62. Counting characters is that employee's core skill, so it was re-tested once, on exactly that skill — and failed the same way.
Under CrewOra's own rule, a repeat failure keeps the flag permanently. There is no third attempt, and the defect is not quietly edited out of the record. Its job receipts are real; its counts are not trusted. We would rather publish that here than polish it away.
Knowledge Keeper — answers only from your papers
Knowledge Keeper is a CrewOra employee that works from your workspace knowledge base — the papers you put there: your handbook, your price list, your rules, your how-to guides. It answers your team's questions from those papers. Only from those papers.
Every answer shows the paper it came from, right under the answer. If the answer is not in your papers, Knowledge Keeper says “I don't know” — it does not guess, and it never invents a price, a rule, or a fact.
Every question it could not answer goes on a list you can see, so you always know exactly which paper to add next.
This page only says it because it was tested first: 20 real questions, asked against real papers on the live system — 19 of the 20 answered correctly with the source shown, and zero invented answers — and the run's record settled in the product's database, the same bar every CrewOra employee has to clear.
The money cage, tested live
Promises about spending controls are easy to write. These three were run against the live product on November 4, 2026, and the results below are what the database recorded.
Hard caps per employee
Every employee carries a monthly credit limit, and the limit is checked inside the same locked step that admits a job — so a job that would cross the limit is refused before any money is spent. Across all 82 graduation jobs, no employee ever spent past its cap.
The 80% warning fired once, at exactly 80%
A test employee was given a monthly limit of 30 credits and ran 24 small jobs. The moment the 24th job settled — exactly 80% of the limit — the product wrote a budget-warning record. It fired once, at exactly 80%, and not before. Those 24 jobs together cost $0.000912 of real AI usage.
The kill-switch refused the job — and charged nothing
An employee was paused with its kill-switch and then handed a job. The product refused it with an "employee paused" error and charged nothing: $0.00 spent, 0 credits, and the refusal itself written into the audit log. The employee was then unpaused and went back to work.
Team roles are live — and the owner keeps the approvals
Team roles are live: a workspace owner can invite members and admins to work in the same workspace. On November 5, 2026, the roles system was re-tested end to end on the live product — a closing battery of 136 checks, and all 136 passed.
A member of a test workspace ran a real job on the owner’s employee. It settled the way every finished job does — exactly 1 credit, flat — and the charge landed on the owner’s balance, which went from 48 to 47 credits. The member’s own workspace balance did not move at all.
Approvals stay with the owner. In the same battery, a member — and then an admin — tried to decide an approval, and the product refused both: approval decisions are owner-only, even for admins, and the refused attempts changed nothing.
Estimate before. Exact cost after.
Before a job runs, CrewOra shows the customer an estimated cost. After the job, it records the exact cost in the ledger. In one live run on November 4, 2026, the estimate shown before the job was $0.000986; the exact cost recorded after was $0.000038. Both numbers sit in the product's records, side by side — the estimate is never quietly replaced by the actual.
And the totals stay small enough to print: as of November 4, 2026, the product has completed 115 paid AI jobs, and the total real AI cost of all of them is $0.0267 — under three cents, counted directly from the database.
Your records export as JSON, CSV, and PDF
Everything CrewOra's employees do is written to an audit log, and the workspace owner can take it out in one click — as JSON, as a CSV spreadsheet file, or as a PDF.
The PDF claim was tested the same way as everything else on this page: on November 4, 2026, a real PDF was downloaded from the live product and machine-checked against the database. Every one of the test workspace's 7 audit rows was present in the file, and the balances printed on its ledger page matched the database exactly.
That promise caught a real defect the next day. On November 5, 2026, the JSON export was found returning an error instead of the file; it was fixed the same night, and then all three formats — JSON, CSV, and PDF — were downloaded again from the live product and re-checked. All three work.
A real purchase — and a real refund
On November 3, 2026, the founder ran a test purchase through CrewOra's live checkout: a $9 credit pack bought at a test price of $0.90. The charge went through on the live Stripe account, Stripe's confirmation came back to the product and was recorded, and the pack's 500 credits landed in the buyer's workspace.
Then the $0.90 was refunded in full, and the refund was recorded the same way. Charge, credits, confirmation, and refund — all four are on record. Paid checkout is not open to the public yet; this test is how we know the rails work before it does.
On November 9, 2026, a real Pro purchase ran end-to-end on CrewOra's company Stripe account — a $99 plan bought for $1 with a one-time proof code. The payment webhook delivered, the workspace flipped to Pro, and 2,500 credits were issued.
A real support address, and an hourly health watch
Support at CrewOra is a working address, not a form that disappears into a queue: support@crewora.net, printed in this site's navigation and inside the product's help pages.
The product is also watched automatically: a health check reads its status every hour. On November 4, 2026, that watch was verified directly in its scheduler — running every hour, latest check successful, no failures recorded.
Three connections are live — narrow, checked, and stated plainly
Google Calendar is connected — and it has now done real work. On November 5, 2026, the product database was checked directly and held exactly one Google Calendar connection record, marked connected, for the founder workspace. The granted access is exactly two scopes: calendar.readonly and calendar.events. On November 9, 2026, Emma — the workspace's executive assistant — read the founder's real upcoming events through this connection: the run is recorded in the product database as a completed read, and the token-refresh path worked first try. Later the same day, Emma created a real event in the founder's Google Calendar through owner approval — “CrewOra Calendar Proof — Nov 9”, booked for November 10, 2026, 11:00–11:30am. A second event Emma proposed that day was rejected by the owner and was never created.
Gmail is connected — draft-only. It was connected on November 9, 2026, and Emma's first Gmail job ran the same day: through owner approval, Emma created a real draft in the founder's Gmail Drafts — “CrewOra Gmail Proof — Nov 10”. A second draft Emma proposed was rejected by the owner and was never created. Gmail in CrewOra is draft-only — the app cannot send from this connection.
YouTube is connected — narrowly. Its data access is exactly two read-only scopes: youtube.readonly and yt-analytics.readonly. The publish/write path is not included in this connection. The first live reads ran on November 9, 2026: Emma read the founder's channel through this connection, and the channel details, the video list, and the channel analytics all returned real data — the analytics report was a genuine empty dataset, zero views in the period it covers. Comments are not readable yet: Google refused the comments read under this connection's permissions, so comments are not claimed.
The Team Room ran its first real job
The Team Room ran live for the first time on November 9, 2026 — on a real, paid Pro workspace. The owner gave the room one goal: draft a short customer reply for a late delivery, with a follow-up task list. The room's manager, the Job Writer, delegated the work to the Scriptwriter, who finished it and saved the reply in the room as an artifact. The manager then posted the summary — the reply and the task list — back to the room. The run took three turns, and each turn settled at exactly 1 credit, the same charge as a single employee's job.