Pricing
Priced by complexity, not screens.
A simple application with several screens can stay in Micro. A smaller application with realtime data, AI workload, multiple roles or heavier infrastructure can land in a higher tier. We estimate this directly from your actual workflow.
Plans
Canonical plans.
Plan 01
Micro
₹1,499
per mo
Focused operational tools. A simple application can stay in Micro even with several screens.
- · Single primary workflow
- · Up to a handful of internal roles
- · Standard web delivery
- · Core reporting
Plan 02
Standard
₹3,499
per mo
Connected operations across two or three workflows with role separation.
- · Multiple linked workflows
- · Role-based access
- · Notifications and document output
- · Operational dashboards
Plan 03
Advanced
₹7,999
per mo
External portals, field applications, approvals and heavier data handling.
- · Customer / dealer / vendor portal
- · Field or factory application
- · Approval chains and audit needs
- · Private storage and document handling
Plan 04
Professional
₹14,999
per mo
Multi-role business systems with realtime data, AI workload or significant integrations.
- · Complete business system
- · Realtime / offline policies
- · AI or RAG workload
- · Multi-platform delivery
Plan 05
Enterprise
₹29,999+
per mo
Isolated infrastructure, heavy storage or streaming, large user bases and strict support SLAs.
- · Isolated environment
- · Heavy storage / streaming workloads
- · Large user base
- · Priority support and evolution
Determinants
What actually determines the plan.
Six factors. This is why screen count is a poor proxy for cost.
01
Complexity
How many moving parts the workflow has — rules, states, roles and edge cases.
02
Users
How many people use it, and how many different kinds of users need separate views.
03
Infrastructure
Storage, file volumes, streaming, offline policies and isolation requirements.
04
AI workload
How much AI processing runs inside the system, and over how much data.
05
Architecture
How many platforms, integrations and external systems are involved.
06
Support
Response expectations, coverage hours and how fast changes are needed.
Add-ons
Optional add-ons.
Starting prices, not universal fixed prices. The Architect only recommends add-ons that relate to the workflow you described.
Offline / document OCR reader
Read printed or scanned documents on device.
+₹499/mo
Private AI operational assistant
Assistant wired into your own operational data.
+₹1,499/mo
RAG knowledge base / vault
Search and answer over your private documents.
+₹1,999/mo
AI smart classification
Auto-tagging of records, tickets and documents.
+₹499/mo
Immutable audit trail
Append-only record of who changed what.
+₹499/mo
Multi-step approvals
Chain approvals with escalation rules.
+₹499/mo
Tally / accounting exporter
Push vouchers to your accounting system.
+₹399/mo
WhatsApp payload engine
Structured WhatsApp message delivery.
+₹299/mo
Native PWA push
Installable push notifications on web.
+₹399/mo
AI reporting
Narrative reporting over live business data.
+₹999/mo
Advanced analytics
Trends, cohorts and cross-module analysis.
+₹999/mo
Document management
Versioning, folders and controlled sharing.
+₹999/mo
Advanced permissions
Granular field and action-level control.
+₹999/mo
PDF engine
Automated PDF generation and templating.
+₹999/mo
Data import / export
CSV / Excel ingestion and outbound export.
+₹499/mo
Heavy infrastructure and storage workloads are quoted according to architecture and usage rather than a flat add-on rate.
Third-party costs
Costs we do not absorb.
Who pays
If a feature requires a paid external provider, the client owns that provider account and pays the provider directly.
- · Paid messaging providers (for example WhatsApp business messaging)
- · Paid external APIs
- · Third-party AI services
- · Other provider-specific infrastructure
Why it is structured this way
You keep the relationship and the billing with the provider you choose. Binary Zero does not mark up or re-sell those recurring charges, and your provider accounts stay yours if the engagement changes.
Architecture that Binary Zero itself manages — application hosting, private storage and the deployment pipeline — is part of the engagement.
One-time work
Custom and one-time work.
Data migration and consolidation
Volume, format and cleanliness of existing records determine the effort.
Android APK packaging and rollout
Signing, distribution and installation path across your devices.
Windows executable packaging
Workstation deployment and environment-specific configuration.
Integrations
Accounting exports, messaging providers and external APIs, each with their own access requirements.
Offline policy design
Defining what works without a connection and how synchronization resolves.
These items appear in the Architect blueprint where they apply, and are priced in the human-reviewed proposal — never by the estimator alone.
Next step
Get an estimate for your workflow.
Tell us about your business. We'll take it from there — focused tool or complete operational system.