Reevo

The claim is the entire identity and it survives the removal test completely: strip the intelligence layer and the thesis collapses, because the product is the shared memory that reads every call, email and deal, then drafts follow ups, updates the record, flags risk and answers pipeline questions on its own.

The claim is specific rather than decorative, the assistant is committed by design to citing the exact call, email or record behind every answer, deal updates and task logging are automatic, and the system of record itself is built around the model rather than having one bolted on.

The company raised eighty million dollars at debut from two marquee firms on exactly this thesis, and the marketing separates shipped capability from roadmap by labeling four features as coming soon, which is the honest version of the pattern this index usually catches vendors faking.

The autonomy claims are real and the split between acting and drafting is stated honestly: the system updates deal records, logs tasks and flags risk on its own, while follow ups are drafted for a human to send. The oversight mechanism is specific and unusual, every answer from the assistant carries a citation to the exact call, email or record it reasons from, which makes the machine's conclusions inspectable rather than oracular, and trust and control appears as a named platform capability on the pricing comparison for both tiers.

Off the top band: the trust and control line is a label whose contents were not retrievable, no permission model, approval step or audit log is described anywhere read, and automatic writes to the system of record are precisely the place a buyer would want that detail.

The design commitment to citations tells a user what evidence an answer rests on, which is a real transparency mechanism, but it discloses the evidence rather than the model: no provider, model family, training approach or method documentation is published anywhere read.

The coming soon labels on intent signals, lead scoring, coaching insights and the command center are genuinely honest disclosure of what does not exist yet, credited here, without substituting for disclosure of how what does exist works.

Named individuals at named companies give video testimonials, a chief executive, a chief operating officer and a marketing manager, and press coverage from major financial outlets is linked, but the coverage is funding news rather than outcome evidence and not one quantified customer result appears anywhere read, no case study, no metric, no named customer with a number.

The sharpest observation sits in the testimonial band itself: one of the four featured endorsements is from a managing director at the venture firm that co led the funding round, an investor presented in the customer proof position, which a careful buyer will discount accordingly.

The platform runs email sequences and a metered dialer, both regulated channels, and no page read names a governing statute, a consent framework, suppression handling, calling time restrictions or any compliance capability at all. Inbound forms and routing exist on the prospecting side.

For a platform whose outreach surface includes provisioned sending domains and telephony, the compliance silence is complete, though nothing marketed sells evasion either, so this sits at the default rather than the bottom.

A privacy notice and terms of service exist at their own routes and were not opened, so this row is flagged. The footer carries a do not sell or share my personal information link on every page, a concrete state privacy law mechanism worth crediting.

The open question is proportionate to the architecture: the product's whole thesis is one memory layer holding every call, email, meeting and record a customer's team produces, and nothing read describes retention, data subject handling or processing terms for that aggregation.

The platform sells contact and company enrichment by metered credits and sources addressable markets, so it supplies third party contact data, and no page read discloses where that database comes from, whether it is licensed, built or brokered.

The launch materials state that the platform generates its own clean first party activity data from emails, meetings and calendars, a real provenance statement, but it covers activity data, not the enrichment database whose credits are on the price card. The load bearing provenance question is the one left open.

The architecture is the sanctioned one: the vendor provisions sending domains and mailboxes itself rather than automating anyone else's interface, operates its own dialer with one provisioned phone number per user, and connects outward through official surfaces including Slack and a model context protocol interface named on the pricing table. Nothing marketed rents identity or drives a third party's user interface. Off the top band under the standing rule, no stated conformance position toward mailbox providers or carriers appears anywhere read.

The stewardship question is as large as the architecture: a single memory layer ingesting every call recording, email and record a customer produces, reasoned over by models, and nothing read states whether that data trains models, whether tenants are isolated from each other's context, or how long recordings persist.

Trust and control is named as a platform capability without retrievable content, and the two certification badges in the footer speak to security process rather than model data handling. For a product whose value is total context aggregation, the absence of a stated training and isolation position is the gap.

Every touch is personalized with full context on each buyer and follow ups are drafted by the model for the rep to send, and nothing read takes any position on what the recipient is told about machine involvement in the messages they receive. The one phone number per user policy means called parties see a stable identity rather than rotated numbers, a structural point in the recipient's favor that the vendor does not itself frame as such. No impersonation tactics are marketed.

The connective surface is thin by design, because the thesis is replacing the stack rather than joining it, and the launch materials say so plainly, powering every workflow directly without relying on integrations or third party data feeds.

What exists is real but sparse: the Slack integration has a described function, the assistant answers with citations in any channel, a model context protocol interface is named on the pricing table without documentation, one click migration moves data in, and release notes are published. No integration directory, no developer documentation and no programmatic interface reference were located. The model context protocol mention is the modern signal here and would move this grade with documentation behind it.

Cloud software with a web application and a Slack surface. No hosting provider, region, data residency option or architecture statement appears anywhere read, at a platform whose memory layer concentrates a customer's entire communications record in one place.

Two named certifications are claimed in the sitewide footer, a completed service organization control type two audit and the international information security standard, alongside the audit body's trust mark. Named, specific and checkable claims put this above the asserted controls tier.

Off the top band: no trust centre page was located, no report access, subprocessor list, penetration test summary or vulnerability disclosure route appears anywhere read, so the badges assert the audits without giving a buyer the artifacts.

The disclosure pattern is inverted and worth recording precisely: every usage meter is quantified while no dollar figure appears anywhere. The comparison table publishes enrichment credits per user, dialer minutes, recorded meeting minutes, active sequence caps per organization, scheduling links, report and dashboard and dataset counts, custom object and field limits, workflow credits and support response hours, dated to the first of the month, and all three tiers still resolve to talk to a human.

A buyer can compute exactly what they would get and nothing about what it costs. A startup program promises special pricing for qualifying companies, also unquantified. The meters are the best in class for a sales led vendor; the missing prices hold this at the middle band.

One click migration is marketed for moving into the platform, and no equivalent is described for moving out. Custom objects, custom fields and the full communications memory would all need an exit path, and no export function, format, retention period, deletion commitment or post termination right appears on any page read. The terms of service were not opened. For a product asking a customer to consolidate their entire revenue stack into it, the one way door is the observation.

Both forces are present and they roughly cancel. On one side, domain purchase and inbox warming are first party product features, the secondary domain architecture this index tracks, and warming is simulated engagement by definition, though the framing here is mild, landing in the inbox rather than beating filters.

On the other side, the published discipline is real and specific: active sequences are capped per organization at fifty or one hundred, dialer minutes are metered, and each user gets exactly one phone number, a notably restrained number policy in a category where a competitor graded this session includes thirty to seventy five numbers per license. No sending volume policy, authentication documentation or deliverability guidance was located.

Fit is stated at tier level, early teams launching their go to market motion, scaling teams running advanced motions, and mature teams needing tailored plans, plus a startup program with a qualification gate, and the positioning is explicitly business to business.

Past those sentences the coverage disclosure is thin: no vertical pages, no geography, no language coverage, no customer counts, and the named testimonial customers are the only visible install base for a platform three quarters of a year past launch.