What is real today, and what is not yet.

A visual pipeline with custom stages, source tracking, a manual rating you set, and rules that distribute new leads round-robin or by workload.

Two-way conversations on the customer record, approved message templates, broadcasts, and follow-up sequences that stop the moment somebody replies.

Quotations built from the design, five document themes or your own letterhead, and a link the customer opens and accepts without logging in.

Map your columns once and import in bulk. A row whose phone or email already exists is skipped rather than duplicated — matched on the values, not by a model.

Trace a roof on satellite imagery, pack it, check each panel for shade by month and hour, take off the mounting steel and export a STAAD model.

Assign surveys, capture photos and location from a phone browser, and generate the survey report. A responsive web page, not an app download.

Stages you define, a planning board with soft gates, a crew week board that warns on double-booking, materials readiness, and daily site updates.

Track each application through its stages with the number of days it has been waiting, so the ones that have stalled surface by themselves. India: DISCOM net metering.

Purchase requests with approvals, RFQs compared side by side, purchase orders that need approval before they can be sent, goods receipts, and vendor bills matched three ways.

Item catalogue, kits and bundles, stock movements with a full history, and multiple warehouse locations that stay separate instead of collapsing into one pool.

Invoices with approvals, credit and debit notes, TDS, payment schedules, receivables ageing with statements, vendor bills and payments, and bank reconciliation.

Maintenance schedules that raise their own visits, service requests and tickets that stay on the customer record, and a commissioning pack at handover.

Roles built from per-module, per-action permissions, each scoped to a user’s own records or all of them. Approvals are separate permissions from doing the work.

Conversion by source, pipeline value and win rates, project cycle time and where jobs stall, and call outcomes with duration.

Items, warehouses, composite kits and stock movements sync both ways with Zoho Inventory, matched on SKU, with conflicts surfaced for a human rather than silently overwritten.

A mobile app on the same backend, for the people who work on site rather than at a desk.

What is missing: In active development and not released. There is no download and no offline mode. The web app is responsive and is used on phones today.

Generation data from installed plants — which have stopped reporting, and which are under-performing per kW installed.

What is missing: The data model and the vendor registry exist; no inverter vendor integration works yet, so today it accepts manually entered readings only.

Sending the quotation document itself into the chat, rather than a link to it.

What is missing: The send path is built and waits on Meta approving a template that can carry a document. The link version works today.

A logged-in area where your customer follows their own installation, opens documents and raises service requests.

What is missing: Not begun. Today a customer gets a read-only progress link and a public quotation page, neither of which needs a login.

Generating invoice reference numbers and e-way bills for Indian tenants who are over the turnover threshold.

What is missing: Blocked until an invoice registration provider is chosen — there is no API to build against yet, so we will not give it a date.

Pushing invoices, bills and payments into the ledger your accountant already works in.

What is missing: Not begun. The GST working exports and CSV downloads are what bridge to your accountant today.

Building your own reports over your own data, rather than the fixed set of analytics screens.

What is missing: Not begun. Each module exports CSV, which is the current answer.

SAML/SSO for companies that manage accounts centrally.

What is missing: Not begun. Sign-in today is Google, email link or password, with optional two-factor.

Separating a company into branches with their own teams and a consolidated view across them.

What is missing: Not begun — there is no branch concept in the data model. Roles and record visibility are how teams are separated today.

Ranking leads by how likely they are to close, learned from your own history.

What is missing: Not begun. Leads carry a rating you set yourself, and assignment rules are deterministic rather than predicted.