Question 1

What does the autonomous agent actually do day-to-day?

Accepted Answer

The agent runs a three-phase loop on a continuous cadence. Audit reads your directory and one spend source on a 24/7 scan, ranking findings by reclaim dollar against implementation effort. Reclaim pulls duplicates, orphaned seats, and shadow spend onto a consolidation playbook finance can defend at the next renewal call. Renegotiate drafts tone-matched counter-offers from in-corpus benchmark concessions and queues each one for a human sign-off before anything reaches a vendor counterparty. The full loop is documented end to end on /how-it-works.

Question 2

Who on the team has to approve each saved dollar?

Accepted Answer

A named human on your team. The agent is read-only by default — no write action, no counter-offer, no vendor outreach moves without an explicit sign-off row written back to Postgres. Drafts sit in the /app/approvals queue and a member of your team approves, amends, or rejects each one before the agent ever sends anything. There is no automatic send path, and there is no autonomous switch you can flip in production.

Question 3

What does the first 30, 60, and 90 days look like?

Accepted Answer

Days 0–30: connectors land (Okta / Azure AD / Google Workspace plus one spend source — a corporate card, an invoice inbox, or an ERP export). First surfaced savings usually arrive inside 30 days, typically duplicate-license and dormant-seat finds. Days 30–60: the benchmark-driven concession template enters the corpus from in-corpus pricing percentile data; the consolidation playbook starts ranking wins by reclaim dollar against effort. Days 60–90: a first priced-out renewal renegotiation lands, written back to the spend source as named savings on a named contract — not a dashboard aggregate.

Question 4

How is this different from a conventional SaaS spend tool?

Accepted Answer

Visibility tools surface your spend and stop there — finance still has to negotiate, draft, and follow up by hand. WealthBuilt composes around the benchmark corpus: every counter-offer drafts from in-corpus concession data, tone-matches your finance voice, and queues for one-clause sign-off. A conventional tool shows you what you spend; WealthBuilt closes the loop from finding to counter-signed reclaim, with the paper trail to defend it.

Question 5

Where does our inventory and counter-offer data live?

Accepted Answer

In a single managed Postgres instance. Every customer row flows through the Prisma singleton; there is no secondary datastore, no raw SQL written by app code, and no event-stream export of customer data into an analytics warehouse or a third-party data lake. The audit log is generated from the same Postgres, not a separate system of record. EU and UK data residency are available alongside the US default — the region is set at provisioning and held for the lifetime of the account.

Question 6

Do you use our data to train third-party LLMs?

Accepted Answer

No. Nothing owned by your workspace — inventory rows, contract clauses, counter-offer drafts, vendor replies — flows to third-party model training. Reclamp does not pool, resell, or share customer pricing and concession history with other tenants. The agent reads and writes inside your workspace only.

Question 7

How do we pass a procurement review?

Accepted Answer

Every reclaim is a counter-signed record: the draft, the human sign-off row, the vendor reply, and the date the dollar amount landed on the next invoice. Per-request scoping (where: { userId: user.id }) is what every /api handler runs on, so the data path itself supports the audit claim. TLS terminates at the edge, encryption at rest is managed by the database provider, sessions are HttpOnly cookies issued by the auth module — no shared admin cookie, no token in localStorage. The full security packet (architecture diagram, subprocessor list, SOC 2 Type II roadmap) routes to you on /contact under sourceTag="security-packet".

Question 8

What about GDPR and EU / UK data residency?

Accepted Answer

Region is selected at provisioning on the managed provider — EU and UK are available alongside the US default, and the choice is recorded against the environment for the lifetime of the account. There is no separate US backup of EU-resident data, no event-stream export outside the region, and no background job that touches live rows outside the same Postgres the app uses. The three pillars a security lead scans (where rows live, encryption, AI-agent guardrails) are documented on /security.

Question 9

What does each plan cost and what is included?

Accepted Answer

Free is $0/month — covers up to 50 tracked licenses and 5 teammates, with renewal alerts, manual seat and duplicate reporting, and a read-only AI-vendor tail preview. Pro is $25 per month, billed monthly through the platform checkout, and unlocks the autonomous reclaim loop, AI-drafted counter-offers, vendor benchmark concessions, multi-source SSO ingestion, and audit exports. Pro adds unlimited tracked licenses and teammates; Scale layers quarterly reviews and a sales-led rollout on top. The full price ladder is on /pricing.

Question 10

Is the contract annual, monthly, or can we cancel any time?

Accepted Answer

Monthly — no annual lock-in. Sign in, complete checkout, and Pro is active the moment payment confirms. Cancel from your dashboard at any time and your existing data remains intact under Free so you can come back without rebuilding the inventory. There is no procurement queue required to start, and no minimum seat count.

Question 11

What does the enterprise engagement — security packet, signed DPA, custom benchmarks — look like?

Accepted Answer

Reach the team on /contact with sourceTag="security-packet" and we route the security packet within one business day: architecture diagram, subprocessor list, encryption + session lifecycle notes, and the AI-agent guardrail audit trail. A signed DPA and a custom benchmark engagement are scoped as a sales-led rollout with a named contact on both sides. EU / UK residency, custom SSO with audit, and a tailored concession corpus are all in the same engagement shape — one intake, one real reply.

The three sections finance and IT want answered before signing.

How Reclamp works.

Data and security.

Contracts and commitments.

Route the rest of the buying committee's list.