The 91% model, shown in full.

Zephior publishes the baseline, arithmetic, assumptions and exclusions behind the Ziva performance reference so buyers can evaluate it without relying on an unexplained headline.

Methodology version 1.0 · Last reviewed 22 August 2026

STATUS

Evidence status

The 91% figure is a reference-workflow planning model. It is not an audited portfolio average, a universal customer result or a contractual guarantee. Actual outcomes must be measured in the customer’s own process.

CALCULATION

Published calculation

(30.0 hours − 2.7 hours) ÷ 30.0 hours = 91%

30.0 hManual baseline
2.7 hZiva-assisted human oversight
27.3 hModeled human time saved
91%Modeled reduction

REFERENCE MODEL

Reference workflow allocation

The model represents one structured, document-heavy response with a prepared knowledge base and an accountable reviewer. It compares active human work, not elapsed calendar time.

Work categoryManual baselineZiva-assisted oversightWhat changes
Intake and requirement setup2.0 h0.4 hImport and structure requirements; a human confirms scope and instructions.
Source discovery and evidence8.0 h0.5 hRetrieve from approved knowledge; a human verifies source fit and currency.
Drafting and assembly12.0 h1.2 hGenerate source-cited drafts; a human corrects, completes and owns commitments.
Review and approval coordination5.0 h0.4 hRoute structured review; accountable approvers retain decision authority.
Formatting, export and final QA3.0 h0.2 hProduce the target file; a human validates buyer format and release readiness.
Total active human time30.0 h2.7 h27.3 hours of modeled human time saved.

ASSUMPTIONS

Conditions required for the reference model

  • The response is within the normal scope of Ziva-supported RFP, tender, DDQ or questionnaire work.
  • Relevant company knowledge is available, current, permissioned and sufficiently structured for retrieval.
  • Buyer files can be imported and exported without material manual reconstruction.
  • Named owners review legal, commercial, security and delivery commitments before release.
  • The comparison excludes knowledge-base remediation, procurement waiting time and work outside the response team’s control.
  • The manual baseline and assisted case produce an equivalent accepted deliverable and use the same scope boundary.

MEASUREMENT PROTOCOL

How a customer should measure its own result

A valid customer result requires a before-and-after design that counts all human work and checks output quality. Draft-generation time alone is not enough.

  1. 01

    Define comparable work

    Select response families with similar size, formats, risk, languages, contributors and approval depth. Freeze the start and end events.

  2. 02

    Record the manual baseline

    Capture active time across intake, search, drafting, subject-matter input, review, correction, approval, formatting and submission QA.

  3. 03

    Run a representative assisted sample

    Use ordinary requests and current source material. Include exceptions, late changes and access-restricted questions rather than a curated demo only.

  4. 04

    Hold quality constant

    Compare accepted final outputs. Track unsupported claims, substantive rewrites, missed requirements, export defects and approval exceptions.

  5. 05

    Report a range and sample

    Publish the median, distribution, sample size and response mix. Separate active human time from calendar duration and software processing time.

BOUNDARIES

What the 91% figure does not claim

  • It does not mean every response is completed 91% sooner on the calendar.
  • It does not mean reviewers can skip source, legal, security, pricing or delivery checks.
  • It does not include the initial work of cleaning a poor or obsolete knowledge base.
  • It does not predict a win rate, revenue result or buyer evaluation score.
  • It does not apply unchanged to unusual portals, scanned documents or unsupported file structures.
  • It is not a substitute for a controlled pilot using the customer’s real workload.

REWORK

Why Zephior does not publish a universal rework rate

Rework depends on source readiness, question ambiguity, required tailoring, reviewer standards and the definition of a correction. Zephior previously displayed a 4% figure without a sufficiently documented public measurement basis. It has been removed. We will publish a rework benchmark only with a defined sample, denominator, collection method and review date.

VERSIONING

Change control

Methodology changes receive a new version and review date on this page. Material changes to the baseline, assisted time, scope or evidence status will also update the Ziva product page.

Measure the workflow that you actually run.

Use a bounded pilot with equivalent work, complete time capture and explicit quality gates.