New · Processes
Turn every business process into a more efficient digital process.
Describe how work gets approved at your company — a statement of work, a new hire, a purchase over budget — and Clarilytic turns it into a digital process. Assistants read the documents and do the checking first. People make the decisions. Every step is recorded, and nothing sits in an inbox wondering whose turn it is.
Invite-only pilot · Runs on the documents you already have
- Done: Start form form Client, scope, fee and dates fill the template's blanks
- Done: Draft draft Written from your own statement-of-work template
- Done: Assistant check assistant Rates the risk and flags terms you rarely accept
- Done: Legal ∥ Finance side by side Reviewed at the same time, both approved
- Done: Fee over $100,000? decision $142,500, so the CFO decides
- In progress: CFO approval people In the CFO's tasks, with the assistant's findings
- Still to come: File the approved copy file Filed to your signed-contracts workspace, with an approval page
What changes
Less chasing. Fewer surprises. A record of every yes.
Most approvals are slow for the same reasons: nobody knows whose turn it is, reviewers start from a blank page, and the decision lives in someone's inbox.
Nothing waits in an inbox
Each person sees what's waiting on them in one list. When a review runs past its deadline, it can pass to someone else or move on by itself.
The checking is done before anyone reads
Assistants read the document against your standards and flag what matters, so reviewers spend their time on judgement rather than proofreading.
Work runs side by side
Legal and Finance review at the same time instead of in turn. A process can ask a whole group to approve, or continue as soon as the first person does.
See where the time goes
A performance view shows how long each process takes, which steps hold work the longest, and how often things come back for changes.
How it finds bottlenecks ↓How you build one
From one sentence to a working process.
Explain the process the way you'd explain it to a new hire, then adjust what the designer drafts.
-
Step 1
Describe it
Write how the process works today in plain words. The designer drafts its digital version — the steps, who decides, and where it branches — and shows you what it added before anything is saved.
-
Step 2
Adjust it
Drag steps around the canvas. Choose who approves — a person, a role, or a whole group — name the buttons what your team calls them, and decide what happens when a review is overdue.
-
Step 3
Publish and start
People start it from a short form, or from New document in a workspace. The form's answers fill the template's blanks, and each person finds their part in My tasks.
For every team
The same building blocks, shaped to how each team works.
Six examples. Pick a team to see its process.
Sales
Discount approvals that don't hold up the deal.
A rep needs 25% off to close this quarter. Sales leadership wants to know what the customer has been given before, and nobody wants to dig through old agreements to find out.
- The rep fills in one short form. The history, the arithmetic and the routing happen on their own.
- Small discounts go straight to a manager; large ones reach the person who should see them.
- Once the discount is approved, the same process can start the statement of work. One process can run another.
- Done: Discount request form Customer, list price and the discount asked for
- Done: Check the history assistant Reads the customer's past agreements for earlier discounts
- Done: Work out the net price value List price less the discount, for the order form
- Done: More than 20% off? decision 25%, so the VP of Sales decides
- In progress: VP of Sales people Sees the history and the new price before deciding
- Still to come: Tell the rep notify The decision and the approved price, in one message
Recruitment
A shortlist with reasons, not a pile of resumes.
Fifteen applications are sitting in the role's workspace. The hiring manager wants to know which few are worth a call, and why.
- The assistant does the reading. The hiring manager makes the call, with the reasons in front of them.
- When nobody fits, it says so and takes a different path instead of forcing a pick.
- It reads only the workspaces the person who started the process can open.
- Done: Open the role form Title, must-haves and nice-to-haves
- Done: Read the resumes assistant Scores them against the job description and names the strongest, with reasons
- Done: Top score 85 or more? decision 94, so the shortlist path
- Done: Tell the hiring manager notify The shortlist and the reasons, in the message
- In progress: Hiring manager review people Approve the shortlist, or turn it down
- Still to come: Write the candidate summary report A report from the workspace's documents, with sources
HR
Offer letters from the right template, every time.
An offer needs the current template, the right numbers, and a second signature when the salary is above the band.
- Nobody edits last year's offer. Every letter starts from the template you publish.
- The process spots the signed copy when it arrives, and can tick “Signed offer” on the new-hire checklist.
- Expense claims and reimbursements run the same way: a short form, then a sign-off or a note asking for changes.
- Done: Start form form Candidate, role, salary and start date
- Done: Offer letter draft From the current template, blanks already filled in
- Done: Above the salary band? decision No, so no second signature is needed
- Done: HR review people Approved on the first round
- In progress: Wait for the signed copy wait Continues when the signed letter lands in the workspace
- Still to come: Probation review reminder A reminder set for 90 days after the start date
Procurement
New vendors checked by everyone who needs to see them, at the same time.
A team wants a new software vendor. Legal, Security and Finance all have questions, and nobody wants to be the one holding it up.
- Three reviews run side by side instead of one after another.
- If a review sits too long, it can pass to someone else or move on by itself. You choose which, and after how long.
- At renewal time, an assistant can find the vendor's agreement in your vendor contracts and send it for approval only if it looks risky.
- Done: Purchase request form Vendor, amount and what it's for
- Done: Over $5,000? decision $18,400, so the full review
- In progress: Legal ∥ Security ∥ Finance side by side Legal and Finance approved; Security is reviewing
- Still to come: When all three are done join Continues only once every review is in
- Still to come: Tell the requester notify Approved, with anything to watch for
- Still to come: File the request file The answers filed to your Vendors workspace
Legal
NDAs drafted in your positions and checked against your playbook.
The business needs NDAs quickly. Legal needs every one to hold your standard positions, without drafting each by hand.
- Reviewers see what changed since the last round, with the assistants' findings next to each section.
- Suggested wording applies in one click, and every version is kept in the workspace.
- Use it inside something bigger: vendor onboarding can start the NDA as one of its steps and wait for it to finish.
- Done: Start form form Counterparty, purpose and term
- Done: Draft draft From your NDA template, in your house style
- Done: Contract assistants review assistant Findings against your playbook, section by section
- Done: Legal review people Approved after one round of suggested wording
- In progress: Wait for the countersigned copy wait Up to 14 days, then a follow-up path
- Still to come: Tick the deal checklist checklist “Signed NDA” checked off in the deal's workspace
Finance
Renewals decided on time, not discovered after they happen.
The Cascadia logistics agreement renews automatically unless notice is given by 3 June. Last year, nobody looked until July.
- Nobody has to remember to start on time. The process waits for the date, then brings the agreement to the owner.
- The owner sees the terms that matter and the new total before choosing.
- Budget requests run the same way: a short form, a threshold, and the right person.
- Done: Start form form Agreement, owner and notice deadline
- In progress: Wait wait Until 30 days before the notice deadline
- Still to come: Read the agreement assistant Price changes, notice terms and minimum commitments
- Still to come: Work out the new annual cost value Next year's total, with tax
- Still to come: Budget owner decides people Renew or cancel, on buttons named for the decision
- Still to come: Remind next year reminder Set ahead of next year's notice deadline
These are starting points, not templates you're stuck with. The same steps fit client onboarding, change requests, policy sign-offs, grant applications — anything that runs on documents and decisions.
Process performance
See which step is slowing everything down.
Every process keeps a timeline of what happened and when. The performance view reads it and shows administrators where the time goes — with nothing extra to set up or log by hand.
- The typical pace and the slow tail, side by side. One stuck request can't drag a healthy step's typical time up, and it can't hide either: while it's stuck it shows in the open and overdue counts, and once it moves on, in the slow tail.
- Every step ranked by how long it holds the work and its share of the whole cycle, so the bottleneck has a name instead of a hunch.
- Rework counted: rounds, send-backs, rejections, and reviews that timed out and were handed on — the loops that quietly make a process slow.
- What's open and overdue right now, and what started against what finished each week, so a growing backlog shows up before anyone complains.
Then fix it where you found it: give the slow review a deadline that hands it on, run two reviews side by side instead of in turn, or let an assistant do the first read — and watch the next month's numbers.
The steps you build with
Everything a process needs, in plain words.
People
- Review and approve, reject, or send back with comments
- Ask a person, a role, or everyone in a group
- Suggest wording the author applies in one click
- Hand an overdue review on, or let it move on
Assistants
- Review a draft against your standards
- Work out values a process can use, like a risk rating or a score
- Read the documents in a workspace, or across a portfolio
- Answer from the knowledge you gave them
Routing
- Go one way or another on an amount, a rating, or an answer
- Run steps side by side, then continue when all are done — or the first
- Start from a form or from a new document
- Run another process as a step, and pick up its result
Follow-up
- Notify people, with the details filled in
- File a copy, ending with a page of who approved and when
- Wait for a date, or for the signed copy to arrive
- Set reminders, tick checklists, and write a report
People stay in charge
Assistants do the reading. People make the call.
Nobody approves blind
A document is only marked Approved when a person has reviewed it, and the designer won't publish a process that could skip them. A process that finishes on its own says Completed, never Approved.
Assistants see only what the requester can
An assistant step reads only the workspaces the person who started the process can open. If its answer can't be read, the step pauses and says why, instead of guessing.
Every step on the record
Every decision is on the process's timeline and every version of the document is kept. The filed copy can end with a page listing who approved each step and when.
Bring the process that's slowest today.
Clarilytic is in an invite-only pilot. Tell us which approvals hold your team up, and run them on your own documents.