Credently launches: client-approval engine for B2B teams
Client approvals still live in email threads, Slack pings, and half-read PDFs. When a stakeholder goes quiet, projects stall — and when someone finally replies "looks good," you may have no shared record of what was approved, when, or by whom. Credently is now live to give B2B teams a structured alternative: one secure link, a visible deadline, documented decisions, and a verification record you can share without reopening the thread.
The approval problem B2B teams inherit
Most professional services teams lack a repeatable sign-off process. Feedback arrives in fragments, invoices wait on verbal OKs, and procurement asks for proof that does not exist in a chat export. What teams need is a single place where the client sees exactly what is in scope, acts deliberately, and leaves a timestamped trail.
What Credently is — and what launched today
Credently is a client-approval engine for structured B2B sign-off. You create a request from your dashboard, send a secure link to your client, and close the loop with an audit trail and verifiable web certificate; PDF export is available on eligible plans. The launch includes deadlines, email-verified decisions, revision handling, tacit-consent outcomes where configured, and third-party verification via reference code and QR.
Credently is not a project-management suite or a generic e-signature platform. It exists for the moment a deliverable needs a documented yes, a written revision request, or a fair, logged outcome when nobody responds.
Built for agencies, studios, and freelancers
We built for teams that send files or links for review on recurring deadlines: creative agencies, design studios, dev shops, consultants, and freelancers billing on milestones. If you wait on client feedback before you ship, invoice, or advance to the next phase, Credently maps to that step — without asking your client to learn a new tool.
How an approval request works
Each request includes a title, scope description, and links to materials under review. You set how long the client has to respond. Credently emails a link to a focused approval page showing the deadline, the files, and the actions available.
Your account; your client's secure link
You need a Credently account to create and manage requests. Your client does not. They open a secure, tokenized link — no signup, no password, no app install. The creator keeps billing, templates, and history; the client gets a lightweight page built for one decision.
Email verification before any decision
Before a client can approve or request revision, they confirm they control the email address on the request. Credently sends a one-time magic link to that inbox; opening it unlocks the decision buttons. Viewing the page does not require verification — acting on it does.
Approve or request revision — not reject
Credently offers two active choices: Approve and Request revision. There is no reject button by design. Objection is expressed by requesting revision in writing before the deadline — a note your team receives in the dashboard and audit trail. When a client approves, the request closes with a recorded outcome. When they request revision, you can upload a new version and restart the cycle.
Deadlines and tacit consent
Every request runs on a visible approval deadline. The client page states how much time remains and what happens if they do not respond.
If your contract or statement of work already includes a tacit-consent clause — where agreed silence after notice counts as approval — Credently can execute and log that policy. When the deadline passes with no revision request, the request may close as auto-approved, with the outcome recorded in the audit trail. Credently does not invent that legal rule; it documents how your pre-agreed terms played out.
See our guide on tacit consent in client approvals. Counsel can adapt starting language from our sample clause template.
Free vs paid deadline options
On paid plans, you choose among 24 hours, 3 days, or 1 week when creating a request. On the Free plan, every request uses a fixed 1-week deadline, with three sends per month (no rollover) and one seat. See pricing for details.
Audit trail, certificate, and verification
Every request builds a chronological audit trail as events occur: creation, delivery, first view, email verification, reminders, decisions, revised versions, and final outcome. When a request closes, Credently provides a verification certificate with a reference code and QR code linking to a public verification page — so finance, procurement, or legal can confirm the record without your login. PDF audit-trail export is available on Freelancer and higher plans. The certificate supports your documentation; it is not legal advice or a guarantee of enforceability in every jurisdiction.
Optional add-ons: e-signature, Drive, and Stripe
Several capabilities sit alongside the core workflow:
- E-signature — Optionally require a client signature on a PDF as part of approval. Uses e-signature credits; not required for standard approvals.
- Google Drive — Connect Google to sync activity on Drive links attached to a request.
- Stripe Connect — On the Business plan, collect payment after approval in supported flows.
Details are in the dashboard and on the FAQ.
Getting started
- Create a free account — verify your email, pick a plan, and open the dashboard.
- Start a new approval request with client, scope, links, and deadline.
- Send the secure link — your client verifies via magic link, then approves or requests revision.
- Download or share the certificate when the request closes.
Read the FAQ to see how deadlines, tacit consent, and certificates fit your contracts.
A note on contracts and jurisdiction
Credently helps you run and record an approval process you define. It does not determine whether tacit consent or a specific deadline is valid for your client relationship or jurisdiction. You are responsible for contract language, client notice, and whether silence-based approval applies.
Used well, Credently turns informal OKs into structured records — approve, revise in writing, or a logged outcome when the clock runs out.