Main content
EnglishRomână
Contact
EnglishRomână

Case study

Mozar: statutory audits, from order to signature

One platform takes a statutory audit from order to signed report, and every status email sends itself. Auditors, accountants and business owners each work in their own app.

Client
Mozar
Sector
Legal tech, France
Role
Platform and migration
Status
In production

  • One flow

    From order to signed report

    Median, order to signed report

  • ≈7a week

    Updates shipped to users since launch

    48 updates in 46 days

  • 0password resets

    When accounts moved to the new platform

    Existing passwords kept working

Mozar: an accountant opens a mission from the dashboard and expands its progress; on the phone, an entrepreneur answers the questionnaire and gets an instant quote.
FIG. 1Professional workspace and the client's quote

What we built

Quote, payment and signed report in one flow

The mission is priced on the spot, then paid, reviewed and signed in the same place.

Mozar client journey: a mission type is chosen, the questions are answered, the quote counts up, payment is confirmed, the dashboard tracks the audit and the signed report is downloaded. A motion recreation built from the product's screens, with illustrative values.
FIG. 2Client journeyMotion recreation of the real product

Safeguards

Prices change through an agent, only after a person confirms

The Mozar team changes questions and prices by asking an agent in Claude.ai; nothing changes until someone confirms.

FIG. 3Confirm, then change
Confirm, then change: an agent in Claude.ai asks the admin app for a change, the admin app shows a person the proposed change in full, and only after the person confirms is the catalogue updated. If someone edits the catalogue meanwhile, the change is dropped.The agent can read freely. A change request produces the full proposed change for a person to check, and only a confirmation saves it. If the catalogue changed in between, nothing is written. An off switch stops every agent change at once.AgentClaude.aiAdmin appAgent accessProposed changeShown in fullPerson confirmsMozar teamCatalogueLiveDropped

In use

Mozar auditor view of the same mission: each uploaded document with Approve and Request a correction buttons, approved badges, a revision note, a 6 of 10 documents processed counter and the shared discussion.
FIG. 4Auditor document review
Phone view of a completed Mozar mission: a Mission completed status and a final documents list with the auditor's signed report, the signed engagement letter and the representation letter, each marked available.
FIG. 5Signed report delivery

Services

Web platforms, AI agents and security in one build

How the Mozar platform is built: apps, mission engine, integrations

One platform, an app per audience
Auditors, accountants, entrepreneurs and the Mozar team each work in their own web app, on one shared platform.
Mission engine
Questions, conditions and document rules live as data. The Mozar team edits them in an admin builder, and the quote follows.
Payments and e-signature
Card payment, refunds and electronic signature are built into the order flow, and every mission event sends its own email.
Migration without password resets
Accounts and missions moved from the old platform in rehearsed runs, and existing passwords kept working.
Security from day one
Security reviewed from the first release, with automated tests on every update.

Stack

Web apps
Next.js, React, TypeScript
Data
PostgreSQL
Payments and documents
Card payments, e-signature, PDF reports, transactional email
AI
AI agent in Claude.ai with human approval

Next case

A system like this starts with a brief

Project briefAll case studies
Email
contact@elastoapps.com
Studio
Cluj-Napoca, Romania, EU