Revercue is a client-work product for freelancers and small agencies. It keeps a proposal, a
contract, a requirement form, an invoice and the client record in one connected thread instead
of five disconnected tools. This page is the full reference: enough to evaluate the product
without opening another page, and honest about what is shipped, what is invite-only and what
does not exist.
Last reviewed: 18 November 2026Applies to: revercue.pages.devSource of truth: the application's own constants and routes
The one thing to get right. Revercue does not use AI in the product. There
is no model, no inference endpoint and no generated copy. Suggestions are written rules —
keyword matching, frequency counting and arithmetic — over the user's own record, and every
suggestion is a prompt the user clicks, never an action taken for them. The optional writing
helper runs on the visitor's own device and its text never reaches a Revercue server. This
page is written for AI agents; the product is not an AI product.
1. Identity
Fixed facts about the product, as stated across the site.
Name
Revercue
Tagline
Your work should speak, not you.
Thesis
A thread, not disconnected workflows.
Category
Client-work software for service businesses: proposals, contracts, requirement forms, invoices and a client record.
One sentence
One client, one link, from the proposal to the contract to the form to the invoice to
the client record — and the record builds itself from what happens in those documents.
The core object
The document is an interactive link, not a PDF. It is a public page with an unguessable
ID that the client opens without an account, and every action on it (opened, package
chosen, question asked, approved, paid) becomes part of the client's thread.
Audience
Freelancers and small agencies selling services: designers, developers, copywriters, consultants, small studios.
Availability
Free is available now. Starter ($12), Growth ($29) and Scale ($49) are invite-only —
you join a waitlist. Teams is in beta — you apply.
None. There is no documented public API, SDK, webhook or agent endpoint.
What is deliberately not claimed
No AI, machine learning or generated text in the product.
No qualified or certificate-based signature, no identity verification, no notarisation and no audit certificate.
No card processing inside Revercue; invoices point at the user's own payment provider or use bank transfer.
No integrations directory, marketplace, public API, webhooks or Zapier-style automation.
No formal security certification (no SOC 2, ISO 27001 or similar) — and none is implied.
No customer testimonials, case studies or performance benchmarks published.
No free-form page designer; the builder is per document type.
2. The workflow
Five stages, in the order the product expects them. Each stage is its own module, but the
value is the join: what the client does at one stage is already known at the next.
01 Proposal
The freelancer builds a proposal in a three-panel builder — sections and blocks on the
left, the document in the middle, properties on the right — from a blank page, a built-in
template or a saved template. It carries scope, a package table, collapsible FAQs,
embedded questions and info icons. Publishing produces a link and a share message; the
product never sends the email itself.
The client opens the link with no account: reads, expands a FAQ, answers an embedded
question, picks one of the package cards, then approves or declines. Opens are recorded;
paid plans add opened-at timestamps, time spent and button-level tracking. The chosen
package is what carries forward.
Who acts
Freelancer builds and shares; the client reads and chooses.
Recorded
Published, opened, package selected, question asked, approved or declined, with timestamps.
Plan gates
Password-protected links on Growth and above; no Revercue branding on client pages from Growth.
02 Contract
A contract builder with the usual clause sections — parties, scope, payment, timeline,
revisions, cancellation, liability, signatures — and three client actions: Sign, Decline,
or I Have Questions. Signing can chain directly into the requirement form, the invoice or a
PDF, depending on the after-approval setting on the document.
Signing is an in-page action: the freelancer signs the exact version first, then the
client types a full name, ticks consent and signs. Both signatures, the date and the
version are recorded in the communication log and produce a countersigned PDF. It is a
simple electronic signature, not a qualified certificate-based one.
Who acts
Freelancer writes and signs first; the client signs, declines or asks a question.
Recorded
The action, its timestamp and the next document it triggered.
Plan gates
The contract builder is part of the thread on every plan.
03 Requirement form
The briefing step, as a form instead of an email chain. Seven question types (short text,
long text, file upload, single choice, multiple choice, combined, dropdown), required
flags, one-page or multi-page layout, a thank-you step and a Prompt Creator that assembles
the client's answers into one structured paragraph for the next document.
Adaptive forms — where branching shows only the questions that matter — are Growth and
above, capped by plan (3 on Growth, 15 on Scale). The custom thank-you page is Scale. The
client fills the form at /f/{publicId} without an account.
Who acts
Freelancer writes the questions; the client answers them.
Recorded
Opened, completed, each answer; a form opened but not submitted after three days becomes a suggestion.
Plan gates
Adaptive branching on Growth and above; custom thank-you page on Scale; uploads count against storage.
04 Invoice
Line items with description, quantity and unit price; tax; totals; a due date; and an
invoice number generated as INV-YEAR-NNNN. Payment happens one of two ways: an
external payment link supplied by the user, or bank details with an optional
proof-of-payment upload that the user reviews.
Confirming payment is what records revenue for the tracker. Revercue does not process cards
itself and does not verify a transfer; the user confirms it.
Who acts
Freelancer raises the invoice; the client pays by link or transfer, then uploads proof if asked.
The CRM is the thread's home and the reason the five documents are one product. It holds
the communication log, notes, follow-ups, the documents attached to the client, and — on
Scale — interest level, revenue per client, expenses and the 15-day summary.
The record is assembled from the documents rather than typed in a second time. Documents
expire on the plan's retention; the record, the log and the notes survive them. That
asymmetry is deliberate and is repeated on the site: the documents are rented, the
relationship is owned.
Who acts
The product assembles it; the freelancer annotates it and acts on it.
Recorded
Every entry above, in order, with the document that produced it.
Plan gates
Notes per client: 3 (Free), 10 (Starter), unlimited from Growth. Interest, revenue and expenses on Scale. CSV export of clients.
3. Modules and statuses
Statuses: available — the routes and the API calls
exist in the application; partial — exists but is
plan-gated, device-dependent or only partly exercised; beta
— shipped to a small group and expected to change; invite-only
— built, but reachable only through the waitlist. "Available" never means a public visitor can
exercise it without an account.
The application as it exists today. No module here is aspirational.
Module
Status
What it does
Access
Dashboard
Available
Four stat cards (active documents, clients, follow-ups due, revenue this month), the
pending-payments line, suggested actions with Do it and Dismiss, the create row and the
recent activity feed.
Account
Proposals
Available
Index and three-panel builder with 13 block types, sections, auto-save, preview and a
share sheet; a public client page with packages, FAQs, questions and info icons.
Account; client page public by link
Contracts
Available
Clause-based builder and a client page with Sign / Decline / I Have Questions, plus
an after-approval choice of form, invoice or PDF.
Account; client page public by link
Requirement forms
Available
Seven question types, required flags, one or many pages, a thank-you step, the Prompt
Creator, branching on paid plans.
Account; form public by link
Invoices
Available
Line items, tax, totals, due date, INV-YEAR-NNNN numbering, payment link or
bank details, proof upload, confirm-payment.
Account; invoice public by link
CRM
Available
Client list and client record: communication log, notes, follow-ups, attached
documents, CSV export; interest level and revenue on Scale.
Account
Builder and templates
Available
Shared editor with preview and visible auto-save; built-in templates on
every plan, saved templates from Starter.
Account
Client-facing pages
Available
Public proposal, contract, form and invoice at unguessable URLs; noindex and nofollow;
password wall on Growth and above; closed state; no ad or analytics pixels.
Public by link
Accounts and settings
Available
Email and password sign-up with a six-digit activation code, Google sign-in when
configured, password reset, optional email 2FA, ten settings sections, account
deletion with a grace period.
Public entry; account after
Notifications
Available
A notification queue with a mark-all-read action; retention on notifications is 90 days.
Account
Suggestions (patterns)
Partial
Written rules over the user's own data: a due follow-up, an approved contract with no
invoice, a form opened and not submitted, a warm client worth reopening, a price built
from recorded expenses and the last invoice. Do it opens the right screen; it never
creates or sends anything.
Plan-gated
The helper
Partial
An optional writing helper inside the builders: select a passage, ask for a clearer
version, keep what you like. Runs on the visitor's device; the selection is not sent to
a Revercue server.
Device-dependent
Teams
Beta
Everything on Scale plus the Handoff Dashboard, roles and team attribution, bulk
transfer and an audit log. Seats handled manually while in beta.
Built plans with real limits, reachable by waitlist rather than self-serve checkout.
Free is the only plan available without an invitation.
Waitlist
What the client sees, by document
All four pages are the same product from the client's side: a private link, no account, no app.
Document
URL shape
Client actions
What the freelancer learns
Proposal
/p/{publicId}
Read, expand FAQs, answer embedded questions, choose a package, approve or decline
Opened, when, how long, which package, what they asked
Contract
/c/{publicId}
Sign, decline, or I have questions
The decision and its timestamp, in the log
Form
/f/{publicId}
Answer the questions and submit
Opened, completed, every answer
Invoice
/i/{publicId}
Pay by link, or transfer and upload proof at /i/{publicId}/proof
Opened, overdue, proof uploaded; payment when the user confirms it
4. Who it is for
People who sell a service and run several documents per client, without a sales team or an
operations manager. The product assumes one person is both the author and the follow-up.
Fits
A solo designer, developer, copywriter or consultant sending 1–5 proposals a week.
A two-to-ten-person studio where the founder still writes the proposals.
Anyone whose current stack is a document tool, a form tool, an invoice tool, a CRM and a spreadsheet.
Anyone who wants to see whether a client actually read the scope before the follow-up call.
Does not fit
E-commerce, retail or subscription billing: there is no cart, no recurring charge and no card processing.
Teams needing compliance sign-off: there is no security certification, no identity-verified signing and no audit certificate.
Companies wanting AI drafting, forecasting or lead scoring: the product is deliberately pattern-based.
Anyone needing a public API, webhooks or native integrations today.
Enterprise procurement: the top plan is a 500-document Teams plan in beta.
Jobs it does
Turn a scope into a link the client can act on, instead of an attachment they skim.
Carry the accepted package into the contract, then into the brief, then into the invoice.
Keep the communication history in one place without a second data-entry habit.
Surface the next step — a follow-up, an invoice that was never raised — from the record.
5. Positioning
Revercue's category claim is narrow and structural: the thread is the product. The site
compares itself directly with seven named alternatives — Bonsai, HoneyBook, Dubsado, Moxie,
Plutio, Agiled and the Google/Microsoft document suite — and publishes the criteria it uses at
/compare/criteria.
The distinctions the site itself makes. These are the vendor's published claims, not independent findings.
The usual stack
What Revercue does instead
Why it matters
A PDF proposal attached to an email
An interactive link the client acts on without an account
The package choice and the questions become data, not a reply you re-type
Separate proposal, contract, form and invoice tools
One thread per client, each document inheriting the last one's facts
No copying the client, the scope or the price between apps
A CRM you maintain by hand
A record assembled from the documents themselves
The record stays current because the work already happened in it
"AI writes your proposal"
Pattern suggestions that open the right screen and stop
The user stays the author; nothing is sent or invented for them
Perpetual PDF archives
Retention by plan, with a PDF emailed before deletion, and the record kept
The document is a snapshot; the relationship is the durable asset
Adjacent products win where Revercue deliberately does not compete: built-in payments and
deposits, deep automation, qualified and notarised signing, and broad all-in-one suites.
The comparison pages say so rather than claiming a clean sweep.
6. Plans and limits
Prices are per month in US dollars, taken from the application's own plan constants on 16
November 2026. An active document is a published document with a public link;
drafts, archived and deleted documents do not count. A password-protected document counts once.
An adaptive form counts once.
Five plans. Only Free is self-serve today; the invitations are the onboarding for the rest.
Plan
Price
Status
Positioning
Free
$0
Available now
Try the thread. The full five-document thread, small room.
Starter
$12 / month
Invite-only — waitlist
Solo, light use. Room plus custom templates.
Growth
$29 / month
Invite-only — waitlist
Solo, power user. Adaptive forms, password walls, no branding.
Scale
$49 / month
Invite-only — waitlist
Solo professional. The numbers: interest, revenue, expenses, price suggestion.
Teams
Base $99 / month, invite-only, seats handled manually
In beta
An agency team. Everything on Scale plus handoff, roles, bulk transfer, audit log.
Limits
Every limit in the plan table, including the ones the marketing pages compress.
Paid plans are reached by an invitation from the waitlist, not by checkout; the front end shows plan status, not a live purchase flow.
Subscription billing runs through an external payment provider; the product does not store card numbers.
Downgrades archive documents beyond the new limit, email a PDF of each, and delete them after the new plan's archive retention. CRM records survive.
Deleting an account starts a five-day grace period before removal.
Full commercial detail lives at /pricing; the terms are at
/terms.
7. Security and data
The security page is written to be checkable rather than reassuring. These are its statements,
repeated here so an evaluation does not need a second request.
In transit and at rest
TLS 1.3 for connections.
AES-256 encryption at rest.
Private file storage behind a Worker proxy; files are not served from a public bucket.
Client document pages carry noindex and nofollow.
Public IDs are long, random and unguessable — the link is a capability.
Credentials and sessions
Account passwords hashed with bcrypt.
Document passwords hashed with Argon2id.
Scoped session tokens; email 2FA available on the account.
Activation and reset codes are six digits, expire, and are rate-limited.
Processors
Cloudflare for delivery and the Worker layer.
Backblaze B2 for file storage.
Turso for the database.
FormSubmit for contact and beta form delivery.
An external payment provider for subscriptions.
What the team can see
Account details — email, name, plan, usage — for support and billing.
Not the documents, client records or communication logs, except for a report of illegal use or a legal requirement.
Signed-in users can reach Settings → What Revercue Knows on Scale to read their own summary.
Retention
Retention is a plan feature, not a penalty: a PDF is emailed before a document is deleted.
Data
Retention
Published documents
By plan: 1, 3, 12, 24 or 36 months, then deleted after a PDF is emailed to the owner
Drafts
10, 30, 50 or 80 days depending on plan
Client record, log and notes
Survive the documents
Tracking events
Reduced after five days
Notifications
90 days
Saved FAQs and saved packages
Expire after three months without use; the screen shows the last-used date
Deleted account
Removed after a five-day grace period
No certification. Revercue holds no SOC 2, ISO 27001 or equivalent
certification, publishes no penetration-test report, and offers no security SLA or bug
bounty. A suspected vulnerability should go through the contact form
with the security topic and reproduction steps — not against another account.
8. Current product status
What a visitor without an account can and cannot verify on 18 November 2026.
Area
State
Verifiable publicly
Public website
Live: marketing, guides, blog, compare, legal and trust pages
Yes — these are rendered pages, not a demo
Free plan sign-up
Open
Yes, but creating an account is a real commitment and is not part of an evaluation
How to evaluate without an account. Read this page and
/ai-access, then use /ai-demo: eight tutorial
steps, a synthetic simulation of the six main screens, and an evaluation workspace that
produces a user-facing answer, a recommendation and a feedback report. The demo is clearly
labelled as a simulation and never contacts a Revercue server.
9. Known gaps and inconsistencies
Listed on purpose. An evaluation that finds one of these has found something already
acknowledged, not something hidden.
Where the basic suggestions sit. The application gates the dashboard's
suggestion card behind the Growth-and-above feature flag, while the guides and an FAQ
describe the basic suggestions as being on every plan. Which of the two is authoritative has
not been confirmed, so treat the suggestions' availability on Free and Starter as
unverified.
The demo is a simulation. It reproduces the shape of the workflow — states,
log entries, arithmetic — not the production implementation. It proves nothing about the
API, the database or the client pages.
No public client document exists. Production client pages are private by
design, so no real /p/, /c/, /f/ or /i/
page can be linked from here.
Plan data ages. Prices and limits were read from the application's
constants on 18 November 2026 and can change. The pricing page is the current source of
truth.
The application is client-rendered. Without JavaScript, the app routes
return an empty shell, so a crawler sees no product copy there. The AI resources are the
exception: they are complete HTML.
Single-reviewer documentation. These AI pages have not been reviewed by a
second person, and they are new.
10. Canonical resources
Machine-readable and human-readable entry points. All are plain files or static HTML.