Revercue

AI access guide

Where to find everything in Revercue.

This is the index for AI agents, crawlers, evaluation tools and the people who run them. It maps every public page, explains what each one actually contains, records the real status of each product module, and points to the three companion resources: the overview, the demo and the machine-readable capabilities file.

Last reviewed: 18 November 2026 Applies to: revercue.pages.dev Demo data: synthetic

Read this before exploring. Revercue is a client-work product for freelancers and small agencies. The production application is a client-rendered React app: every application page requires an account and JavaScript. This page, the overview, the changelog and the demo's written explanations are plain HTML and stay readable with JavaScript disabled. The demo is an interactive simulation with synthetic data — it is not the production application and it does not contact Revercue servers.

1. What Revercue is

Revercue keeps one client's work in one connected thread: a proposal, a contract, a requirement form, an invoice and the client record that holds them together. A proposal is an interactive link rather than a PDF — the client opens it, reads the scope, picks a package, asks a question and approves, without creating an account. The contract, form and invoice use the same idea, and the client record is built from what happens in those documents.

The public website is the product's shop window: what the thread is, what each document does, what each plan costs and what is available today. The Free plan is available now. Starter, Growth and Scale are invite-only while the product is in its fresh state: you join a waitlist. Teams is in beta: you apply to the beta. Those statuses are repeated on the pricing page and in the demo, and they are the source of truth.

What the site offers

Who the product is for

Freelancers and small agencies who sell services and run several documents per client: designers, developers, copywriters, consultants and small studios. The product assumes the reader sends the link from their own inbox and wants to see what the client did with it. Nothing here is aimed at large enterprises: the plans top out at a 500-document Teams plan that is still in beta.

Why this guide exists

So that an agent can find its way around without guessing, without creating an account and without mistaking marketing copy for a capability. Each entry below states what the page contains, whether it needs JavaScript, whether the content survives without it, and whether it is public or behind login.

2. Website navigation directory

Every route in the application, grouped by audience. The production app is client-rendered: with JavaScript disabled a route returns the app shell and no page body. The exceptions are the AI pages and the static files, which are delivered as complete HTML or plain text.

Public marketing, content and trust pages

Public routes. No account required. All are JavaScript-rendered except the AI pages.
Page and URL What it contains JavaScript Without JavaScript
Home
/
The thesis and the pitch: "a thread, not disconnected workflows". Hero with the dashboard visual, the create–share–track sequence, module cards for proposals, contracts, forms, invoices and CRM, product screenshots, plan prompt and footer links. Required for content App shell only
Features
/features
Seven documented sections — proposals, contracts, requirement forms, invoices, CRM, the builder and suggestions — each with a short explanation, bullet list, product visual and a related FAQ. This is the deepest public description of the module set. Required App shell only
Pricing
/pricing
Five plans with real limits: Free (available now), Starter $12, Growth $29 and Scale $49 per month (invite-only, waitlist), Teams (beta, on invitation, base $99). A full comparison table and billing FAQ. The only working call to action is Start free; paid plans open a waitlist form. Required App shell only
Compare
/compare
A comparison hub against seven alternatives: Bonsai, HoneyBook, Dubsado, Moxie, Plutio, Agiled and the Google/Microsoft document suite. Each comparison page (/compare/{slug}) states its criteria; /compare/criteria explains how the comparison is scored. These are the vendor's own published claims. Required App shell only
Guides
/guides
The index of 25 task-level guides across Proposals, Contracts, Pricing, Follow-ups and Product. Each guide (/guides/{slug}) walks through the actual screens, with product visuals, and ends with related guides. Required App shell only
About
/about
Why the product exists, in the founder's words: five tools and a lost thread, the beliefs behind the design, and what the product deliberately does not do. Required App shell only
Blog
/blog
Five essays about client work: the thread as the product, links instead of PDFs, patterns instead of inference, the self-building client record and what a proposal is for. Individual posts live at /blog/{slug}. Required App shell only
Contact
/contact
The only public contact route: a form with name, email, topic and message. There is no public email address. It is also the route for reporting a suspected vulnerability (put "security" in the topic) and for accessibility problems. Required; form posts to the API App shell only
Beta
/beta
The Teams beta application: name, email, account type, services, monthly volume and what the applicant wants to test. Applications are reviewed by hand; there is no self-serve checkout for Teams. Required; form posts to the API App shell only
Privacy
/privacy
What is collected (account, product, tracking, payment and support data), how it is used, the processors (Cloudflare, Backblaze B2, Turso, FormSubmit, the payment provider), retention by plan, user rights, cookies and account deletion. Required App shell only
Terms
/terms
The service agreement: acceptable use, the plans, content ownership, retention, billing and cancellation, availability, liability, changes and governing law. Required App shell only
Security
/security
A checkable trust page: TLS 1.3, AES-256 at rest, bcrypt for account passwords, Argon2id for document passwords, scoped session tokens, the private file bucket behind a Worker proxy, unguessable public IDs, noindex on client pages, retention and the incident-notification practice. It also states what the team cannot see and what the product does not do. Required App shell only

Account and onboarding routes

Unauthenticated account routes. Creating an account in production is a real commitment: do not do it automatically.
Page and URL What it contains Access
Sign up
/signup
Email, password, terms acceptance and an optional newsletter checkbox. Offers Google sign-in only when that client is configured; otherwise the button says so. Submitting triggers a six-digit email activation code. Public form
Activation code
/signup/code
The six-digit code screen used after sign-up. The code expires and the resend button is rate-limited. Public
Login
/login
Email and password, plus Google sign-in when configured and a link to password reset. Public
Login code
/login/code
The two-factor step for accounts that have 2FA switched on: a six-digit email code. Public
Password reset
/forgot-password, /forgot-password/code
Request a reset code by email, then enter the code and choose a new password. Public
Onboarding
/onboarding/step-1 … /onboarding/step-5
Five steps after sign-up: account type (freelancer or agency), profile and services, legal consent, plan selection (Free is available; paid plans join a waitlist) and a tutorial overlay. Step 3 redirects to step 4. Authenticated, incomplete onboarding

Application routes

All app routes require a signed-in account. None of them is reachable in the public demo.
Page and URL What it contains
Dashboard
/dashboard
The 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.
Proposals list
/proposals
The proposal index: status, client, value and last activity, with the create action.
Proposal builder
/proposals/new, /proposals/{id}/edit
The requirement form, template selection (blank, built-in templates, saved templates), the three-panel canvas (sections and blocks, document, properties), auto-save, preview and the share sheet. The research panel and the on-device helper sit here.
Contracts
/contracts, /contracts/new, /contracts/{id}/edit
The contract index and the contract builder: sections for parties, scope, payment, timeline, revisions, cancellation, liability and signatures, plus the after-approval choice (form, invoice or PDF).
Requirement forms
/forms, /forms/new, /forms/{id}/edit
The form index and the question builder: seven question types, required flags, branching on Growth and above, one page or multi-page, the thank-you step and the Prompt Creator.
Invoices
/invoices, /invoices/new, /invoices/{id}/edit
Line items, quantity, unit price, tax, totals, due date, the payment arrangement (external payment link, or bank details with a proof upload) and the confirm-payment action that records revenue.
CRM
/crm, /crm/{id}
The client list and the client record: communication log, notes, follow-ups, the documents attached to the client, interest level and revenue on Scale, and the 15-day summary. The record is built from the documents.
Notifications
/notifications
The notification queue, with a mark-all-read action.
Settings
/settings/{section}
Ten sections: profile, appearance (dark, light, system), plan, security (2FA, sessions), notifications, saved FAQs, saved packages, revision prices, what-revercue-knows and delete account. /settings redirects to /settings/profile.

Client-facing document pages

Public in the sense that the client needs no account; the link itself is an unguessable capability URL.
Page and URL What it contains
Public proposal
/p/{publicId}
The proposal in the freelancer's branding: packages, collapsible FAQs, embedded questions, info icons, approve or decline. May be gated by a password on Growth and above, and shows a closed page when the document is closed or expired.
Public contract
/c/{publicId}
Sign, Decline, or I Have Questions. The signature is a typed full name plus consent, recorded with the date and version; it is not a qualified signature.
Public invoice
/i/{publicId}
The invoice the client receives: line items, totals, due date, the payment link or the bank details, and the overdue state.
Proof upload
/i/{publicId}/proof
A file upload for bank-transfer proof, used with the account-details payment option.
Public form
/f/{publicId}
The requirement form as the client fills it: the question set, branching, progress and the thank-you page.

Utility, error and static resources

Error routes are part of the app; the static resources are served as files.
Page and URL What it contains
Offline
/offline
What still works when the network is gone: documents already open in the browser.
Session expired
/session-expired
The explanation and a route back to login.
Forbidden
/403
Shown when an account lacks access to a resource.
Server error
/500
The generic failure page, with a retry path.
Not found
/{unknown}
The app's 404 page for any route the router does not recognise.
AI access
/ai-access
This page. Static HTML, readable without JavaScript.
AI overview
/ai-overview
The self-contained product reference: identity, workflow, module documentation, pricing, security, status.
AI demo
/ai-demo
The guided tutorial, the synthetic interactive simulation and the evaluation workspace.
AI changelog
/ai-changelog
The verified record of changes relevant to agents.
Capabilities JSON
/ai-capabilities.json
Machine-readable modules, statuses, plans, demo flags and resource URLs.
llms.txt
/llms.txt
A plain-text summary of the product, plans and key pages, written for language tools.
Sitemap and robots
/sitemap.xml, /robots.txt
The canonical public URL list and the crawler rules. Private app and client routes are disallowed.

3. Product features directory

Only modules that exist in the application are listed. Statuses are available, partial, beta, invite-only and unverified. "Available" means the route and the API calls exist; it does not mean a public visitor can exercise it without an account.

AvailableAccount required

Dashboard

The landing screen of the app. Four stat cards (active documents, clients, follow-ups due, revenue this month), a pending-payments line, suggested actions with Do it and Dismiss, a create row and a recent activity feed. Each stat links to the filtered list behind it.

Availability depends on the account and its plan data. Cannot be tested publicly; the demo simulates the same layout with synthetic numbers. Suggested actions and the interest arithmetic are plan-gated.

AvailableAccount required

CRM

The client record and the thread's home: the communication log, notes, follow-ups, the documents tied to the client, and on Scale the interest level and revenue tracker. The record is built from the documents rather than typed in a second time. Clients can be exported as CSV.

Notes are limited by plan (3 on Free). Interest level and revenue are Scale features. The record is only as complete as the documents sent.

AvailableAccount required

Proposals

Built in a three-panel builder from a blank page, a built-in template or a saved template, with 13 block types, sections, auto-save, preview and a share sheet. The client page shows packages, collapsible FAQs, embedded questions and info icons; the client picks a package and can approve or decline. Opens are tracked.

The share sheet gives a link and a message but never sends the email itself. Password protection is Growth and above. The built-in template set currently covers proposal and contract documents.

AvailableAccount required

Contracts

A contract builder with the usual clause sections and three client actions: Sign, Decline, or I Have Questions. The freelancer signs the exact version before publishing; signing can continue the thread to the requirement form, the invoice or a PDF, depending on the after-approval setting. Every action is written to the communication log.

Signing is a typed full name plus an explicit consent tick, recorded with the timestamp and the signed version; the freelancer signs first and the pair produces a countersigned PDF. It is a simple electronic signature: no certificate, no identity verification and no audit certificate, so a deal that needs a qualified signature belongs elsewhere.

AvailableAccount required

Requirement forms

A question builder with seven question types (short text, long text, file upload, single choice, multiple choice, combined, dropdown), required flags, one-page or multi-page layouts, a thank-you step and a Prompt Creator that assembles the answers into a structured paragraph for the next document.

Branching and adaptive forms are Growth and above; the custom thank-you page is Scale. File uploads depend on the account's storage allowance.

AvailableAccount required

Invoices

Line items, quantities, unit prices, tax, totals, an auto-generated INV-YEAR-NNNN number and a due date. Two ways to get paid: an external payment link, or bank details with an optional proof-of-payment upload. Confirming payment records revenue for the tracker.

Revercue does not process card payments itself; the payment link points at the user's own provider. Proof uploads are reviewed by the user, not verified by Revercue.

AvailableAccount required

Builder and templates

The shared document editor: sections and blocks on the left, a white page in the canvas, properties on the right, preview, and auto-save with a visible state. Built-in templates ship with the product; saved templates are a Starter-and-above feature.

The builder is per document type, not a free-form page designer. The saved-template list is loaded from the account; when the API is unavailable the built-in templates still render.

PartialPlan-gated

Suggestions and patterns

Suggested next actions derived from the account's own activity: a follow-up that is due, a contract that should follow an accepted proposal, a client warm enough to reopen. Each suggestion offers Do it or Dismiss, and Do it only opens the right screen — it never creates or sends anything.

The application gates the dashboard's suggestion card behind the Growth-and-above flag, while the guides and an FAQ describe basic suggestions on every plan; which of the two is authoritative is unverified. The advanced set (document suggestions, interest flags, price suggestion) is Scale. What is shown depends on the data in the account.

PartialDevice-dependent

The helper

An optional writing helper inside the builders: select a passage, ask for a clearer version, keep what you like. Its work happens on the visitor's own device, so the selected text is not sent to a Revercue server. Suggestions elsewhere in the product are written rules over the user's record, not generated text.

The helper depends on the browser and device capability and loads silently in the background. On a machine that cannot run it, the button is unavailable rather than failing. It was not exercised in this environment.

AvailablePublic links

Client-facing pages

The public proposal, contract, form and invoice pages the client opens without an account. Long random IDs, noindex and nofollow, a password wall on growth plans, a closed state, and no advertising or third-party analytics pixels.

The link is a capability URL: anyone who holds it can open the page unless it is password protected. There are no demo links published here, because production documents are private.

AvailableServer features

Accounts, plans and settings

Email and password sign-up with a six-digit activation code, Google sign-in when configured, password reset, optional email 2FA, ten settings sections, plan status and account deletion with a grace period.

Plan changes and subscription billing run through the payment provider; the frontend shows plan status but this environment cannot verify a live checkout. Paid plans are invite-only, so there is no open purchase flow to test.

BetaManual onboarding

Teams

The agency plan: everything on Scale plus the Handoff Dashboard, team roles, bulk transfer, team attribution and an audit log. Join from the beta page; seats are handled manually while the plan is in beta.

In beta means under active testing with a small group. The plan exists in the product and pricing data; its team features could not be exercised here.

What is not claimed. No public API, no integrations directory, no qualified or certificate-based e-signature, no card processing inside Revercue, no formal security certification, no customer testimonials and no published performance benchmarks. If a capability is not described here or in the overview, treat it as unverified rather than assumed.

4. AI resources

/ai-overview

The self-contained product reference. Identity, workflow, per-module documentation with statuses, target customers, positioning, real pricing, security, current product status and links. Enough to evaluate Revercue without opening another page.

/ai-demo

The guided eight-step tutorial, a synthetic interactive simulation of the six modules, the evaluation workspace (user-facing answer, recommendation and feedback report) and the evaluation rules. No account, no production data, no real payments.

/ai-capabilities.json

The same facts as structured JSON: identity, resource URLs, module statuses and demo flags, plan table, security summary, demo policy and last-updated date. Content type application/json.

/ai-changelog

The verified record of releases relevant to agents: what changed, what was added, what was fixed, known issues and changes to demo availability. Only entries that can be traced to the repository are listed.

/llms.txt

A plain-text product summary for language tools: the thread, the plans, the pattern approach and the key page URLs.

/sitemap.xml and /robots.txt

The canonical public URL list and the crawler rules, including which private routes are disallowed and where the sitemap lives.

5. Demo instructions

There is no production demo account. Revercue does not publish credentials, and no visitor or agent should create an account in production to look around. What exists is /ai-demo: a self-contained simulation that runs entirely in the browser.

How to enter

  1. Open /ai-demo. Registration is not required and no data leaves the page.
  2. Read the welcome section. It states what the simulation is and what it is not.
  3. Work through the eight tutorial steps in order. Each step explains the module, what to inspect and what result to expect.
  4. Use the interactive panel to try the actions described in the steps. Every action is synthetic and reversible.
  5. Press Reset demo at any time to return the synthetic data to its starting state.
  6. Finish in the evaluation workspace: write the user-facing answer, pick a recommendation and complete the feedback report.

What an agent can explore

Permitted actions

Reading every page, following every public link, using the simulation, and completing the evaluation. Public pages may be linked to and quoted with attribution.

Restricted actions

Synthetic data

The demo's clients, documents, amounts and activity are fictional and generated for the page. There is no real email, no payment processor, no file storage and no database behind it. The reset button restores the starting state, and everything is kept in the browser session only.

Completing the tutorial and evaluation

The tutorial is complete when all eight steps have been read and the simulation actions for each step have been tried. The evaluation is complete when three things exist: a user-facing answer, one recommendation category with its evidence and confidence level, and a feedback report. Both outputs have copy buttons; the report has no submission endpoint and the page says so. To send feedback through the product's own route, use the contact form.

6. Access and limitations

Publicly accessible

Every page in the marketing, content and trust group is public: home, features, pricing, compare, guides, about, blog, contact, beta, privacy, terms and security. So are the AI resources, the sitemap, robots and llms.txt.

Login-protected

The dashboard, proposals, contracts, forms, invoices, CRM, notifications, settings, all builders and onboarding are behind authentication. Client document pages are not behind authentication but depend on a private, unguessable link that this guide does not publish.

JavaScript-dependent

The production site is a single-page React application. Without JavaScript the application routes return an empty shell, so a crawler sees no product copy on them. The AI pages, the sitemap, robots and llms.txt are delivered as complete static files. The demo's written explanations are in the HTML; its interactive panel needs JavaScript.

Features that cannot be tested publicly

Automated access

The public pages may be crawled and read. Do not attempt to authenticate, do not create accounts, do not submit forms, do not probe private or client routes, and do not treat the site as a load-test target. robots.txt disallows the private app namespaces and the client document prefixes; it is a crawler hint, not a security boundary. No public API or agent endpoint exists.

Reporting an error or an accessibility problem

Use the contact form with the page and what happened. For a suspected vulnerability, choose the security topic and include reproduction steps; do not test against another account. Accessibility problems are welcome through the same form. Signed-in users can also use Settings → Feedback, which attaches the account context.

Known gaps in this guide