Volta Book a 20-minute demo

Offers / diagnostic first

Bring theblockage.Leave with the next useful decision.

A scoped conversation about one operating event: who owns it, which systems touch it, and the smallest first build we can defend. No credentials, no exports and no access to your live system to begin.

Get your Operations Blueprint See the eight offers
  • 8productised offers
  • 4delivery stages
  • 1diagnostic before any quotation

What happens after you write, step by step.

Nothing is built before the event, its owner and the acceptance test are written down and agreed. Each stage ends with a decision that belongs to you.

  1. Step 0

    The fit call

    Thirty minutes. You describe the event that keeps coming back, and we say plainly whether it is something we should be doing at all.

  2. Step 1

    Diagnostic

    You receive a current-state map, the priority bottleneck and a recommended first scope. You approve the outcome and name the operating owner.

  3. Step 2

    Blueprint

    The delivery sequence, the integration boundaries, the risk list and the acceptance criteria. You approve scope, timeline and the access model.

  4. Step 3

    Pilot

    A small working workflow in a controlled environment, with its exception handling and its logs in the open. You approve pilot acceptance.

  5. Step 4

    Production

    The documented workflow, an access register, a support hand-off and a monitoring plan. You confirm go-live and the named escalation owner.

E-invoicing, filed and watched every month.

E-invoicing is the law, and from version 15 Odoo moved the Egyptian pieces behind an Enterprise licence. On Community there is no module, no support line, and no warning when filing quietly stops. A system that stopped filing three weeks ago is found by an auditor, not by an accountant, and the penalties are counted per document and per period.

6,000 EGP a month

Onboarding takes ten working days, from kick-off to a go-live we watch for the first five days.

Book a 20-minute demo
  • 6,000EGP a month, monthly or quarterly in advance, stop at the end of any paid period
  • 25,000 to 45,000EGP once for setup, if you are not filing yet, quoted after the call
  • 0setup fee if you are already filing and only need it kept alive

What the monthly service covers

  • Our own ETA connector, licensed to you while the monthly service runs. Built for Community, with no Enterprise seat needed.
  • Filing that runs on its own. Scheduled, overnight, in batches. Nobody sits at a machine pressing a button.
  • Rejections in plain Arabic and English. What went wrong, whose problem it is, what to do. Not a bare error code.
  • Monthly monitoring of filing health and of the signing machine. If documents stop going out, we tell you.
  • Certificate watch. Sixty days' warning before your e-seal expires, and we reconfigure when it is replaced.
  • Up to 100 new product codes a year registered with the Authority as your catalogue grows.
  • Rule changes absorbed. When the Authority changes a format or a validation rule, we make your system comply at no extra charge.
  • Upgrades. Move Odoo to a newer version and your e-invoicing comes with it.
  • A named person to call, Sunday to Thursday, 09:00 to 17:00. Filing down is answered within four working hours.
  • A quarterly written review: documents filed, rejections by cause, and anything that is drifting.

What is not included, said now rather than in week seven

Point-of-sale e-receipts for consumers are a separate obligation on a separate standard. VAT returns, payroll and income tax are priced separately. Old invoices cannot be filed: the Authority refuses documents dated outside its window, so go-live is forward-only and nobody else has a way around that. The e-seal certificate, its USB token and the always-on Windows PC that holds it are yours to buy, and we tell you exactly what to ask for. Your accountant decides how your supplies are classified; we implement what they confirm.

Ten working days, start to finish

  1. Day 0

    The 20-minute call

    We open a real Odoo, raise an invoice, file it, and break it on purpose so you can watch a rejection being cleared.

  2. Day 1

    A copy of your database

    Nothing is done on the live system. We take a copy, install the connector on it, and work there until it is proven.

  3. Days 2 to 6

    Codes, taxes and the e-seal

    Your product codes are registered with the Authority, your tax treatment is confirmed with your accountant, and the signing machine is configured.

  4. Days 7 to 9

    Dry run on the test system

    Real documents go to the Authority's test system until they come back accepted, and every rejection is explained before you see it in production.

  5. Day 10

    Go live, watched

    The connector moves to the live database and we watch the first five days of filing ourselves, every night.

Eight productised offers. The bottleneck picks one.

Each offer begins with a short discovery and design phase, so requirements, access, data quality and policy constraints are established before production work starts.

  • Ops Blueprint

    Start here

    Who it is for. A founder, chief operating officer or finance lead with disconnected tools, unclear ownership and too much manual work.

    First visible win. A ten-working-day operating map, a risk register and a delivery roadmap you can build from.

    Expands into. A full Odoo deployment, a migration, or a platform built for the case.

  • Odoo Rescue and Upgrade

    ERP recovery

    Who it is for. An Odoo owner on a legacy version, or carrying custom modules nobody wants to touch.

    First visible win. A compatibility audit, a phased upgrade plan, and a sandbox path that proves it before the live system moves.

    Expands into. The migration to version 19 itself, and support after go-live.

  • Lead-to-Order Engine

    Volta Inbox

    Who it is for. A service business or a multi-location operator running leads out of WhatsApp.

    First visible win. Consent-based capture, qualification and routing, with a clean hand-off into the CRM.

    Expands into. Booking, quotation, payment, and the rest of the customer lifecycle.

  • Retail Command Center

    Volta RetailSync

    Who it is for. A retail, automotive or e-commerce operator holding stock in more than one place.

    First visible win. One view of stock risk, orders, register activity and the exceptions that need action today.

    Expands into. Store synchronisation, marketplace integration, and replenishment.

  • FieldFlow

    Volta FieldOps

    Who it is for. Construction, petroleum, logistics and field-service operators.

    First visible win. A mobile-first job, trip, proof-of-delivery and cost-capture workflow with an approval trail behind it.

    Expands into. Fleet, payroll, procurement, and a client portal.

  • TaxFlow Compliance

    Egypt and Saudi Arabia

    Who it is for. A finance or ERP lead facing Egyptian Tax Authority or Saudi ZATCA invoicing.

    First visible win. A readiness audit, a map of every invoice event, and a certificate and credential checklist.

    Expands into. The implementation, a tested environment, and monitoring under the monthly e-invoicing service.

  • Knowledge Desk

    AI with guardrails

    Who it is for. An operations leader whose procedures, documents and answers are scattered across chat and shared folders.

    First visible win. A restricted assistant piloted over documents you have approved, answering with its source rather than from memory.

    Expands into. An Odoo-aware assistant, scanned-document intake, analytics, and a controlled hand-off to a person.

  • Operations MVP Sprint

    Build the product

    Who it is for. A founder with an internal tool or an app idea stuck between a prototype and a real system.

    First visible win. A production-ready slice: an authenticated flow, the core data model, and an interface that deploys.

    Expands into. A mobile app, API integrations, analytics, and a monthly iteration plan.

What we ask for, and what we never ask for.

A diagnostic needs your operating context, not your credentials. Access comes later, once, inside a signed scope.

  • A dedicated integration user in Odoo, holding only the permissions the workflow needs, with its keys rotated on a written schedule.
  • Opt-in, approved templates and a human escalation path for anything that sends a message to a customer, made part of the scope rather than discovered later.
  • A traceable event history for e-invoicing, validated in the correct environment, with the tax credentials and the certificate owned by the client and nobody else.
  • An access register with a review date. Named least-privilege accounts, never a permanent administrator login shared around.
  • Nothing sensitive through an open form or a chat. Passwords, API keys, tax certificates, customer records and production database exports are handed over once, securely, inside a signed scope.

Start with the context, not the catalogue.

Describe the operating event you are comfortable describing. We answer with the track we think fits, the boundary we would keep, and what the first two weeks would produce.

Get your Operations Blueprint Message us on WhatsApp

Or send the same on WhatsApp.