Novidades

O que há de novo na CloseRev

Tudo abaixo já está no produto — nada aqui é planejamento futuro. Correções pequenas ficam de fora; isto é o que mudou para quem usa.

2.4

7 September 2026

Two security reviews, and what they changed for you

You are handing us your customers' phone numbers and your revenue. Here is what is different about how that is held.

Passwords are hashed with scrypt at OWASP's recommended settings. It is memory-hard, meaning each guess costs an attacker 128 MB of memory as well as time — which is what makes cracking stolen password databases with graphics cards expensive rather than cheap. Your password is re-hashed the next time you sign in; you do not have to do anything.
Your account is created when you confirm your email address, not when you submit the form. Until then nothing exists but a pending registration that deletes itself if the link goes unused — so nobody can open an account on your address, set a password on it, and wait for you to find it and adopt it.
Password reset and email verification links are single-use in the strict sense: the database allows exactly one redemption, so two clicks arriving together cannot both work. They were re-redeemable within their window before, and a link sitting in a mailbox is one of the easier things for someone else to reach.
New and changed passwords are checked against passwords exposed in public breaches. The password never leaves our servers — we send five characters of its hash and do the comparison here, so the provider cannot tell which password was checked or whose it was.
Signing in, signing up and resetting a password now sit behind a bot challenge as well as rate limits, which makes working through a list of leaked passwords cost more than it returns.
No analytics or tag manager loads on the pages where you type a password. They had been allowed there, which is one more piece of somebody else's code on the page that matters most.
Exports are safe to open. A cell starting with an equals sign is a formula to a spreadsheet, so a value in a CSV you uploaded could have become a command on the machine of whoever opened your export. Ordinary numbers and negative amounts are untouched.
Anything a CloseRev administrator does to your account is written into a chained record: each entry seals the one before it, and the database refuses to alter a sealed entry. Deleting or editing history now breaks the chain visibly instead of leaving no trace.
The status page tests sign-in and billing rather than only reporting that the site answers, and you can report a vulnerability through /.well-known/security.txt.

2.3

6 September 2026

Sign in your way, and hold us to a number

Put CloseRev through your own security review without waiting on an email back.

Ask for a Service Level Agreement and you get 99.5% monthly availability with service credits behind it. The terms are published, so procurement can read them before you book a call.
Check the uptime yourself: ninety days of history for every component, measured from outside the system it reports on, so an outage cannot go unrecorded.
Sign in through your own identity provider on Enterprise and Agency. Verify your domain and require it for everyone on it, so somebody who leaves loses access the moment you switch them off.

2.2

5 September 2026

Find out what the revenue cost you

Knowing which channel closed the money is half a ratio. Here is the other half.

Enter what each channel cost you per month and every report gains blended and per-channel ROAS.
Open a channel to see which campaigns inside it actually closed revenue, rather than which ones got clicks.
Cut the same revenue by product, location, deal size or match confidence. Every sale appears once, so each cut adds up to the total above it and survives somebody checking.
Compare a month against the same month last year instead of against the quiet one before it.
Your attributed figure got stricter: only high-confidence and human-confirmed matches now count toward a channel. Low-confidence matches nobody had reviewed were being counted, which made attributed revenue look larger than the evidence supported. If your number dropped, that is why, and the new one is the one that survives a finance review.

2.1

5 September 2026

Bring your team, and your clients

Run CloseRev for more than one person, or for more than one client, without either seeing the other.

On Agency, give each client their own workspace with its own data, allowance and retention window, and switch between them from the sidebar.
Invite your team with roles, so a viewer can read a report and cannot change a match.
Two optional helpers, both off until you turn them on and neither able to change a number: one suggests a mapping for column names the synonym list misses, the other writes a short summary at the top of a report.
Column mappings are remembered between imports — upload the same export next month and the mapping comes back for you to confirm.
A guided first run with sample CSVs, and a warning if the two files look like they were uploaded the wrong way round.
Extra records, seats and client workspaces can be bought from the billing page and land on your existing subscription.

2.0

3 September 2026

Revenue by channel, from two exports

Nothing to install, no tracking numbers, no scripts on your site — and it works on months that already closed.

Upload a closed-sales export and a lead or call export, confirm the column mapping, and get attributed revenue by channel.
Phone numbers normalised to the international E.164 standard and email aliases resolved, so the same person matches however each system recorded them.
Unmatched revenue is reported as Direct / Unknown rather than spread across paid channels.
A review screen showing both records side by side with a plain-language reason for every match; confirm or reject any medium-confidence match and the totals recalculate immediately.
Every import is saved as a period, so month-over-month comparison compounds instead of resetting.
PDF and shareable read-only reports, CSV export, and your logo on every report.
Deleting an import removes its records, its match results and the original file from storage — not just a row flag.