TermsBuilder's answer

• ReplyClerk, this is a new product launch

BatesKit's answer:

None yet — the product is launching. There is no account system and no user data collected, so there is structurally no way for us to know who the customers are; that absence is itself part of the privacy design. The first honest conversion number will exist a week after launch.

TermsBuilder's answer

• Next.js, React, TypeScript
• Prisma + PostgreSQL
• Clerk (auth)
• Stripe (billing)
• Resend (email)
• Vercel (deployment)
• Source-monitoring + internal drafting for legal update workflows

BatesKit's answer:

pdf-lib for PDF parsing and rewriting, pdfjs-dist for the render-based redaction and production-QA checks, tesseract.js for on-device OCR of scan bodies, React 19 + TypeScript + Vite on the client, WebCrypto Ed25519 for the offline licence, and Cloudflare Pages + Worker + D1 for static hosting and six anonymous counters.

TermsBuilder's answer

• Attorney-informed + structured generation: documents are tailored from business inputs, not generic copy/paste.
  • Deterministic output: consistent policy quality and format across customers.
  • Built-in operations layer: hosted policy pages, privacy-request workflows, and review-first legal update rollout.
  • Public accountability: legal changelog support for transparent update history.

BatesKit's answer:

The entire PDF pipeline — parsing, numbering, writing and five production-QC checks — runs inside the browser tab. Files never leave the device, which for documents under a protective order is an eligibility requirement rather than a marketing feature. And it is checkable instead of promised: the only requests the page ever makes are six ~30-byte counters (page view, batch finished, check run finished, checkout opened, key verified, error type). Load it once, go offline, and a batch still runs.

TermsBuilder's answer

• Practical for small teams: fast setup, clear pricing, and low operational overhead.
  • More than static templates: combines policy generation with publishing and maintenance workflows.
  • Review-first updates: admin approval before rollout helps prevent accidental or low-quality policy pushes.
  • Business-fit focus: policies reflect how the company actually sells, collects data, and supports customers.

BatesKit's answer:

Acrobat Pro's batch sequence does the numbering but is a subscription for one occasional task. Dedicated desktop Bates software works well and costs $99+, mostly Windows-only. Online PDF tools require uploading litigation documents, which disqualifies them for the sets that actually need numbering. BatesKit runs the whole job locally in any browser, one-time $19, no account. The honest cost is that it is a narrower tool than a processing platform — it numbers and checks, but does not redact or run a review environment.

TermsBuilder's answer

• Ecommerce operators
• SaaS founders and product teams
• Agencies managing multiple client sites
• Creators/digital product businesses
• Any lean online business that needs reliable Terms + Privacy docs without enterprise legal tooling

BatesKit's answer:

Paralegals and e-discovery staff who have to Bates-number production sets, small firms without an Acrobat subscription on every machine, and contract attorneys on laptops where privileged documents cannot be uploaded anywhere.

TermsBuilder's answer

TermsBuilder was built to solve a recurring problem. Teams publish generic legal templates that don’t match real operations and quickly become outdated. The product takes an operations-first approach buy generating business-specific policies, publishing them cleanly, and managing legal updates through a controlled review-and-rollout workflow.

BatesKit's answer:

The chore is mechanical with non-mechanical stakes: numbering has to be continuous across every file, and the files are usually under a protective order, so "upload your folder to our server" is not an available answer. The existing options were a subscription, $99 Windows software, or an upload-based web tool. A browser can now do the whole job locally, so I built the one that assumes nothing leaves the device.